Banking transactions are entirely automated these days. However, looking closely at trade transactions, portfolio overviews, account statements, or payments, we notice that everything is connected, and insights must be available in real time.
During the design phase of your core banking integration, you must make critical decisions that could impact the performance and reliability of your entire system. Typically, you have to select one of these integration scenarios
MDB and EJB
Your 3rd party application uses the available OFS API to send and query data from the T24 core banking engine. From a performance perspective, we see the following problems
OFS API issues
Version related problems
Design of enquiries
Wrong usage of events
If API level integration is your choice, please remember that response times depend on the number of parallel requests.
MDB and EJB Integration
Message Driven Beans and Enterprise Java Beans provide a flexible way for all integrations. You specify a port and IP and describe the mapping configuration in application server configuration files.
When software components talk to each other, we use the Integration Framework. There are two types of these integration frameworks
IF inbound to publish content to an Enterprise Service Buds
IF outbound to expose business services or native messages
When users interact with T24, we use the Interaction Framework. It uses the OData protocol and follows a RESTful mindset allowing us to execute GET, PUT, POST, and DELETE requests. The benefit of this interaction framework is that we can access all core banking services and fully decouple user interfaces from T24.
No matter which integration approach you to select, be aware that such design decisions significantly impact your banking applications' reliability. Furthermore, choosing the wrong integration can dramatically increase development and maintenance costs.
Please get in touch with us anytime if you have questions or additional insights. We are here to support your core banking projects.
Happy Performance Engineering!