COCC Case Study: Novell exteNd™ on SUSE® LINUX

Brent Biernat

Managing Officer Network Services

COCC

Matt Richard

Manager Internet Services

COCC

COCC

Company Facts

Mutually-owned service bureau for community banks and credit unions

130 clients in the Northeastern U.S.

300 employees

$43M annual revenue

COCC

COCC

Company Facts

Services must be secure, scalable, supportable

Annual examinations by multiple banking agencies

COCC

Behind COCC's Portal - Novell

Clients' Business Reason:

Increase information access to key decision makers throughout the financial institution

COCC's Business Reason:

Increase COCC's value to the institution

Cross-sell additional services

COCC

How Does COCC Use exteNd ?

Security

Advanced, role-based

Customizable

Clients can self-manage their content and permissions

Integration

Provide access to disparate applications through a single interface

Dozens of unique web-based products from different vendors

Secure COCC applications, databases, and reports

Security

Proven Role-based Security

Controls information and functions

Delegated administration

Configurable password security policies

Self-service password

Secure delivery of legacy web applications

Activity reports available for examinations

This is for full-screen images (delete this text)

Customizable

Content Management

Documents stored on exteNd server

Clients can access data their way:

DAC – Directory Administration Console

DAV – Distributed Authoring and Versioning

Intranet search capabilities through Autonomy

Facilitates customer disaster recovery

This is for full-screen images (delete this text)

Why SUSE ?

Rapid deployment

Open Source development

Operating system security

Platform stability

Utilize existing knowledge sources

Novell support

In regulated environment, proven support is a requirement

SUSE

The Regulated Environment

exteNd uses eDirectory™ to provide custom security for each user

Role-based access to information and functions

Delegated Administration

Full audit trail

Password standards

Full reporting

Structure for Client Separation

Tree structure isolates one institution from another

Each institution has its own project, further isolating one institution from another

Each institution has its own administrative users

Can grant permissions as needed

Reduces overall product overhead

Increases productivity/responsiveness at each institution

Issues We Faced

Converting to a data center environment

Developing and publishing useful reports

exteNd on mySQL issues

DAV Standardization

Integrated authentication concerns

Identifying customer needs and requirements

QUESTIONS ?

BUS 148

2003-12-08T12:43:39

Robert Bessel