Requirements

The bank wanted to offer trading features for their e-Brokerage venture - so that customers could manage their portfolio through them. The following features were required:

• The brokerage offering should be linked with customer accounts
• Existing legacy backend systems should be able to handle higher transactions due to the new features
• The bank wanted a quick proof of concept version to gauge the issues, risks and benefits of the system

Challenges

• Since this was a greenfield project, a rapid development and deployment process was required
• There wasn't enough infrastructure capacity to handle the expected high transaction volumes
• Integration with the legacy back-end systems

Solution

• An xml based framework was developed (based on MVC design pattern principles) that allowed quick configuration of components, allowed multiple developers to work in parallel on the codebase/various application layers without affecting each other, seamless integration/continuous testing, business object caching, state management etc.
• Business Layer caching was built into the framework to promote reuseability and to reduce the load on the network. Recommendations were given to fine tune the application servers and configuration of the clusters (more machines where necassary).
• VisualAge for Java's Enterprise Access Builder feature was used to build cobol wrappers and to connect with the legacy information systems (CICS hosts) for all transactions. JCA was not released at the time, but the application was futureproof and would work with JCA after minimal code changes.

Duration

8 Months

Technologies used

Java 1.1.8, WebSphere Studio, VisualAge for Java, JSP, JavaBeans, UML, SELECT, EJBs, Websphere, XML, DB2 stored procedures, Enterprise Access Builder, CICS, IBM AS/400

Client Benefits

• Bank Customers were offered one place where they could manage their entire financial picture as seamlessly as possible - the application integrated banking and brokerage offerings in ways that simplied things for the customer, and also improved the bank's marketing efforts.
• Customers and Account balances soared, as did the overall visits to the bank's Web site.
• The percentage of brokerage transactions which involved a transfer from a customer's bank account increased, which boosted profits.
• Quick prototype iterations for the proof of concept which allowed the client to decide on the business case/benefits/requirements etc.
• Scalable system due to efficient application/physical architecture.