So it conducted a proof of concept in 2001 and designed some core applications on Web-architecture using J2EE and central back-end processing using an IBM mainframe. The bank wanted to move servers out of the branches and consolidate them in the central processing center by using partitioning and creating virtual servers running on IBM's zSeries mainframe. That's reduced the time for deployment, cut hardware costs and improved the management of server administration. Now, deploying a new server is a "question of a software command," Whincup says, enabling "scalability and improved response times."
Seeking Flexibility
One challenge was dealing with the "peakiness" of the company's Internet usage and "correctly sizing a server file. We have a flexible approach which can virtualize the server. It can be given as much resources as the mainframe has." Eventually, Whincup says, BPM "will actually eliminate the need for a physical file server."
In addition to IBM's WebSphere middleware, BPM also turned to Jacada Ltd. (Atlanta), to help link the front end to the back-end mainframe. One of the areas to benefit from the new architecture is marketing. "We wanted to be able to do inserts and sales prompts and marketing-driven messages within the operational process," Whincup says. Now cross-selling will be easier, because during the transaction process branch employees will be prompted to propose additional products or services.
The project hasn't been without hurdles; Whincup notes that BPM had to build Linux expertise in-house and rely heavily on IBM. Also, getting a handle on "the kind of transaction volumes" was a challenge. Whincup has been involved in "other significant multiple-channel projects. What makes this project different is the scope and breadth."