SOA-9: Implementing SOA in Financial Services

1
SOA-9 Implementing SOA in Financial Services

• Banco Comafi a Real Leading Case

Hernan Aymard
Javier Betancourt
Sr Solution Architect
Sr. Project Manager
2
Agenda
Implementing SOA

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

3
Banco Comafi
We are doing well if you are doing well

• 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

4
The Challenge

• Enable the seamless integration between banks
  systems and all outsourcer services to its
  customer access to information and services via
  their preferred channel.

CISAT Middleware Primary goal
Bank in phone
Home Banking
CRM
5
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.

6
Agenda
Implementing SOA

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

7
Architecture
4 layers
Easy to change/maintain Business Logic
User Business
Services Backend
8
(No Transcript)
9
Agenda
Implementing SOA

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

10
Software Development Cycle
Different layers different tasks Different
teams

• From Analysis to Deployment

11
Challenges
Integrate more people than software

• 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

COMMUNICATE
12
Architecture Design
Modeling what we do
Use Case Logical Component
Deployment
13
Agenda
Implementing SOA

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

14
Technical Solution - How it works
ESB
3
1
15
Technical Solution
How to create services (steps)

• 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..

16
Technical Solution
How to create services (design)

• 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

17
Technical Solution
24 x 7 solution

• SonicMQ Clustering Replication Brokers
• Sonic ESB OSrvr duplicated services

18
Technical Solution
Orchestration Server

• Transient processes
• Compensation strategy to support undo
  transactions between heterogeneous backends
• Processes as simple as possible (just business
  logic)

19
Software Configuration
Control Versioning Deployment Workspaces

• CVS Directory Services
• Periodical exports diff

20
Infraestructure
HW Implementation

• 2 Win2003 2 AMD Opteron processors - Sonic MQ
  Sonic ESB
• 2 Win2003 4 AMD Opteron processors Sonic
  OSrvr
• Container Deamons as NT Services

21
Infraestructure
HW Numbers

• 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

22
Agenda
Implementing SOA

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

23
Monitoring
How to control
Its all about the Business Logic
Infraestructure Components Business
User
24
Monitoring Solution
How to control this

• 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

25
How the Audit Log System works
ESB
3
1
26
(No Transcript)
27
Agenda
Implementing SOA

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

28
Timeline Project
What we did and we are doing
Home Banking
CISAT Begins..
Call Center Ph 1
Call Center Ph 2
E-Banking for Companies
Bank In phone
29
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
• Dont miss your goal support business logic

30
Business benefits
Numbers

• 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).

• 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.

31
Conclusions
What is surprising about this project is that
the framework for the integration was modified to
emphasize the banks current assets. Any new
functionality or technology that needs to be
incorporated can be quickly and easily added.
Pablo Velazquez Mann,CIO Banco Comafi Group
32
Questions?
33
Thank you foryour time
34
(No Transcript)