Myself and Avantage Partners recently completed a proof-of-concept (POC) to prove the capabilities of the BizTalk Server platform to integrate with the Temenos T24 core banking application.
The POC was conducted for a large financial services institution and comprised two main aims:
- To address the technical uncertainty around using BizTalk to enable enterprise-level integration with Temenos T24.
- To build and present a business case for investment in an Enterprise Service Bus to provide integration and messaging capabilities across the organization.
The POC and the ESB business case were successfully completed and presented to the client. Following are more details of the POC.
Logical illustration of the message exchanges that were demonstrated:
Overview of message exchanges:
- For demonstration purposes XML files were used to supply BizTalk with the initiating XML messages.
- BizTalk was configured to watch file locations for the arrival of new files. In real world scenarios, BizTalk is capable of receiving messages in any format (XML, flat file, etc) using a wide array of protocols (SOAP, HTTP, FTP, SMTP, file drop, etc). This was not the “technical uncertainty” that we were resolving, so we defaulted to file-based integration
- BizTalk detects and receives the XML file and creates an inbound XML message (inbound to BizTalk).
- The XML message are mapped to the XML message format required by Temenos.
- The Temenos XML message is sent via a BizTalk SOAP send port to the Temenos web service.
- The BizTalk SOAP send port is configured to receive the Temenos service responses.
- BizTalk writes out the Temenos web service responses to a file location.
Account balance enquiry message exchange details:
- The name of the balance enquiry web service that was used is “AccountBalancetoday” and has the following structure:
Temenos Web Services:
- The web service used to demonstrate the creation of a customer in Temenos is the generic OFS “wrapper” web service named “ofsCall”. It has the following structure:
- The customer creation OFS command used was:
CUSTOMER,INDIV.INPUT.WS/I/PROCESS,BANK1/123456,,
TITLE::={%TITLE%},GIVEN.NAMES::={%FIRSTNAME%},
FAMILY.NAME::={%LASTNAME%},NAME.1::={%FULLNAME%},
SHORT.NAME::={%FIRSTNAME%},MNEMONIC::={%MNEMONIC%},
GENDER::={%GENDER%},MARITAL.STATUS::=SINGLE,
ACCOUNT.OFFICER::=1,SECTOR=1000,INDUSTRY::=2401,
TARGET::=1,CUSTOMER.STATUS::=1000,NATIONALITY::=GB,
RESIDENCE::=XX,CUSTOMER.TYPE::=ACTIVE
- This OFS command was used for demonstration purposes therefore it contains some hard-coded values, and uses “{%…%}” placeholders that were replaced with demonstration data values.
- Our current understanding is that any Temenos OFS “command” can be supplied to this web service, making it possible to interact with Temenos using its full suite of OFS functionality.
A web application was written that demonstrated two integration scenarios, balance enquiry and create customer:
- The web application would accept input values (e.g. first name, last name, etc) and create an XML message file in the BizTalk file receive location when the user clicked on the Temenos request button.
- BizTalk would detect the new XML message file, format the Temenos request, call the Temenos service and return the Temenos response into a Temenos response output file.
- The web application would detect the Temenos response file, read and display the Temenos response contents.
- For the customer creation demo, customer information would be entered in the web application, a customer creation request would be sent to Temenos, and the new customer would be queried and displayed using the Temenos T24 Browser.

Recent Comments