SOA-9: Implementing SOA in Financial Services Banco Comafi a Real Leading Case Hernan Aymard Sr Solution Architect Javier Betancourt Sr. Project Manager

SOA-9: Implementing SOA in Financial Services

Banco Comafi a Real Leading Case

Hernan AymardSr Solution Architect

Javier BetancourtSr. Project Manager

© 2006 Progress Software Corporation2SOA-9 : Implementing SOA in Financial Services

Agenda

A SOA Project Layer Oriented Architecture SOA Development Cycle Technical Solution Monitoring Conclusions

Implementing SOA


Growing business – from corporate to individual banking

Trying to secure the trust of customers after 2001 financial crisis in Argentina

New services : 24 hour call center and online home banking

Ensuring world-class customer service and loyalty

Banco Comafi

“We are doing well if you are doing well”


The Challenge

““Enable the seamless integration between Enable the seamless integration between bank’s systems and all outsourcer services to bank’s systems and all outsourcer services to

its customer access to information and its customer access to information and services via their preferred channel.”services via their preferred channel.”

CISAT Middleware – Primary goal

Client Client

Middleware

Backend 1Backend 1

Bank in phone

HomeBanking

CRM

Client Client

Backend 2Backend 2

Backend 1Backend 1


Architecture Definitions

SOA/ESB Benefits

Backend applications will provide services to “the middleware”

Front ends channels will execute transactions to “the middleware”

Each transaction will be executed by a process in which one or more services collaborate with each other.


Agenda

Implementing SOA



Implementation

Architecture

User Business Services Backend

4 layers

Easy to change/maintain Business Logic

Services

Business Logic

Presentation Layer



Agenda

Implementing SOA

A SOA Project 4 Levels Architecture SOA Development Cycle Technical Solution Monitoring Conclusions


Software Development Cycle

From Analysis to Deployment

Different layers – different tasks – Different teams

Ciclo de Vida del desarrollo

Gerencia de Sistemas/Gerencia de ProyectoArea Comercial /

Seguridad Informática / Areas Operativas

Casos de NegocioAnálisis de los

requerimientos de Negocio y Cambio

a los Requerimientos

CCB

Requerimientos del Negocio

Análisis de los requerimientos de Negocio

CONOPSSí se aceptan

Análisis y Diseño Detallado

Fron

t End

Neg

ocio

Back

End

Test

ing

Análisis Detallado

Especificación de Interfase

Especificación de Servicios

BE

Elaboración de criterios de

Aceptación

Especificación de Proceso

No se aceptan

Criterios de Aceptación

Diseño Detallado

Diseño Detallado

Diseño Detallado

Elabración del Plan de Test

de Integración

SRS(1)

SRS(2)

SRS(3)

Plan de Test de Integración

F

P

B

TA

Especificación de Usabilidad e

Interfaz

Especificación de Seguridad

PR

PR

PR

Validación del CONOPS


Define roles & responsibilities of the software.

A strong decision from the customer to define where to go.

Develop a team to support multiple projects around the middleware.

Difficult to estimate effort & time• Not enough history• Very dependent of other

teams

Challenges

Integrate more people than software…

COMMUNICATE


Deployment Infrastructure

Architecture Design

Use Case Logical Component Deployment

Modeling what we do

Middleware components

Business Logic

User Specific Requirements


Agenda

Implementing SOA

A SOA Project 4 Layers Architecture SOA Development Cycle Technical Solution Monitoring Conclusions


ESB1

Technical Solution - How it works

FTPSMTP

6 6

SOAP

WebServicesClient

HTTP

WS

JMX

Management and BAM

Process Model

Orchestration Service

Validate Route

2

DB

WS

HTTP

WS

4

Ba

ck-O

ffic

e A

pp

lic

atio

n

Ba

ck-O

ffic

e A

pp

lic

atio

n

Ba

ck-O

ffic

e A

pp

lic

atio

n

Bac

k-O

ffic

e A

pp

lica

tio

n

53


Define application that owns the service Define how to connect (custom services or

existing Sonic ESB® adapter/servicetype) – Only connectivity

Define service interface Adapt application to provide service Configure service in Sonic ESB® Test it, test it ,test it…..

Technical Solution

How to create services… (steps)


Services independent from each other Services independent from other components

(DB, DLLs, etc.) – Always up & running Control every exception/error – responds

always something Design each service as simple as possible. Avoid services that could fall down all system

if they have a problem Test it, test it ,test it….. Use tools &

methodology for testing

Technical Solution

How to create services… (design)


SonicMQ® Clustering & Replication Brokers Sonic ESB & OSrvr duplicated services

Technical Solution

24 x 7 solution

Node 1 Node 2

Svc1 Svc1


Transient processes Compensation strategy to support undo

transactions between heterogeneous backends

Processes as simple as possible (just business logic)

Technical Solution

Orchestration Server


CVS & Directory Services Periodical exports + diff

Software Configuration

Control Versioning & Deployment Workspaces


Best Performance test – 30 OSrvr processes instances starting at the same time and finishing in less than a second. The Osrvr process executes 3 activities (services)

Actual load: 30000 processes executed (90 % Osrvr processes) by day

1 million msg in the broker (msgs in the processes + logs) by day

+ 400 Endpoints + 160 Transactions + 70 Osrvr Processes

Infraestructure

HW Numbers


Agenda

Implementing SOA



Monitoring

Infraestructure Components Business User

How to control…

It’s all about the Business Logic

Deployment Infraestructure

Middleware components

Business Logic

Functional View


Service Sonic Monitor to gather info about components (using JMX API)• Container states

• Alerts/notifications

Audit Log system• WebSpeed® App & SQL

• Each service Log everything through queues

• Service gathers all the logs and saves in a DB

• XML Server in the future

Monitoring Solution

How to control this …


ESB1

How the Audit Log System works

FTPSMTP

6 6

SOAP

WebServicesClient

HTTP

WS

JMX

Management and BAM

Process Model

Orchestration Service

Validate Route

2

DB

WS

HTTP

WS

4

Ba

ck-O

ffic

e A

pp

lic

atio

n

Ba

ck-O

ffic

e A

pp

lic

atio

n

Ba

ck-O

ffic

e A

pp

lic

atio

n

Bac

k-O

ffic

e A

pp

lica

tio

n

53

Log



Agenda

Implementing SOA

A SOA Project Layer Oriented Architecture The Challenges SOA Design Technical Solution Monitoring Conclusions


E-Banking for Companies

CISAT Begins..

Call Center Ph 1

Home Banking

Bank In phone

Timeline Project

What we did and we are doing…

April 04

Dec 04

March 05

Oct 05

Jan 06

April 06

Call Center Ph 2


Project Conclusions

Define the owners of the functionality Prepare your applications teams to provide

services Choose a technology to support anything Put an eye in the global view Don’t miss your goal: support business

logic


Call Center: 20 screens to pay credit card to 3 clicks. 7 different applications to 1 frontend application.

50 % increase in quantity of customers who use Home Banking (first 6 months).

Business benefits

Numbers

100 % increase in the number of transactions thanks to a wider range of functions.

E-Banking for Companies: Development time reduced 40%. Costs reduced 50%.


Conclusions

Pablo Velazquez Mann,CIO Banco Comafi Group

“What is surprising about this project is that the framework for the integration was modified to emphasize the bank’s current assets. Any new functionality or technology that needs to be incorporated can be quickly and easily added.”


Questions?


Thank you foryour time


Documents

SOA-9: Implementing SOA in Financial Services Banco Comafi a Real Leading Case Hernan Aymard Sr Solution Architect Javier Betancourt Sr. Project Manager