Information technology is fast changing and so is the financial services
market. An application developed for the needs of today can rapidly become
obsolete. To protect you from this, every Bank Transformation Toolkit solution
has features that allow it to be easily extended and adapted. Changes can
be made to match the evolution of IT systems, business expansion, business
diversification, and other predictable or unforeseen shifts. Following are
some of the ways that the toolkit allows you to compete instead of becoming
obsolete:
- Multichannel enabled
- The multi-tier architecture enables component reuse among delivery
channels. Transaction requests from every channel are handled by the enterprise
systems in the same way as any other channel. This promotes uniform, consistent,
and rapid deployment of financial services through all your delivery channels.
New channels may be added as needed or as they become available.
- Easy integration with existing (and upcoming) systems
- The toolkit integrates easily with present and future systems because
it is based on open Internet standards such as HTML, SSL, HTTP, XML, TCP/IP, JavaBeans™,
Enterprise JavaBeans, and JDBC. It includes JCA compliant
SNA LU0 and LU62 resource adapters to facilitate its ability to develop applications
that interact with other systems.
- Platform portability and system scalability
- Thanks to the portability of Java™ between operating systems and hardware
platforms, toolkit applications can be ported from one operating system to
another with minimal impact. You can easily change your branch platform (for
example, from Windows® to Linux®), and you can also change the role
played by your IT system components. For example, you may want to move part
of the business logic from a branch system running on one operating system
to a regional or centralized system based on a different operating system;
moving the logic between server levels and operating systems is a simple procedure.
- Service Oriented Architecture (SOA) enablement
- The toolkit enables customer applications to support Service Oriented
Architecture (SOA). The transaction flow can now be implemented using the
Process Choreographer. When a complex transaction involves backend web services,
the toolkit supports Web Services JSR 109 standard and it allows web service
invocations from the toolkit's own business layer. On the other hand, the
BTT business logic can be treated as a service to be reused by the other application
systems. Furthermore, the web service interfaces of JCA SNA LU0/LU62 connectors
are in readiness for the web service invocation for legacy connectivity.