Welcome to the Temenos Connect Internet Banking Integration with T24 course.

In this course, we will cover about the Temenos Connect Components involved in the
Integration of T24.
The learning objectives of this course is as follows:
• Understanding the Temenos Component Architecture
• Creation of Web Service from Enquiries and Versions of T24
• Testing the Web Service using SOAP API
• Creation of an Integration Project for T24
• Mapping the Integration Project with the Solution Project
• Display of T24 Enquiries and Versions in the TCIB Retail Screen
TCIB Retail Component Architecture
1. We see a screen project needing to exchange data with T24
2. An integration project is used to work between the screen project and T24
3. Other integration projects can be used for other external systems
4. Both the screen project and the integration projects are built and maintained using
edgeConnect. In this example, the screen project is termed the solution project. A key
benefit of this design is that the screen project is only concerned with the data it uses,
not the way that data is exchanged with T24.
The integration component handles any conversion and structuring of request/response
data between the two.
5. In practice, there may be many screen projects using each integration component and
there may be many integration components, each dealing with a specific business object
as seen by the user. This also means that the technology supporting the interface with
T24 change, for example from Web Services to OData, then only the integration
component needs to change.

5
Web Services support in T24
• The screenshot here shows the login details in the TCIB Retail Screen
• Based on the screen here let us discuss the steps
involved in the creation of web service in T24 end
like
 Enquiries and Versions involved
 Creation of EB.SERVICE
 Generation of war file
 Testing the service via SOAP UI
 TWS configuration in t24-ds.xml
 OFS.SOURCE record for TWS

7
• The Sample widget displays the last login details along with a drop down for customer
details and messages.

• The equivalent ENQUIRY for last login details in T24 is ENQUIRY AI.LOGIN.DETAILS

8
• The Details & Preferences link in the widget is meant for displaying Customer Details
like phone, email, address, etc.
• Along with the customer details a link ‘Change your Details & Preferences’ is provided
to update the Customer Details too.
• The equivalent enquiry and version are TCIB.CUS.LIST and CUSTOMER,AI.PROFILE
respectively.

9
• Here in this example the creation of PW.ACTIVITY record for last login details is
shown.
• As discussed earlier the enquiry meant for retrieving last login details is ENQ
AI.LOGIN.DETAILS and a PW.ACTIVITY record is created for the target enquiry.
• The PW.ACTIVITY record ID should be prefixed with ‘WS’ since a web service has to be
created using the activity.

10
• Here in this example the creation of EB.SERVICE record for the entire TCIB Retail
project is shown.
• The EB.SERVICE record contains all the PW.ACTIVITY records involved in the TCIB
Retail project
• The PW.ACTIVITY record ID for login details is mapped to the EB.SERVICE record by
multi-valuing the Activity ID.

11
• In order to integrate edgeConnect with T24 a web service should be created for the
T24 enquiries and versions.
• TWS plugin provided by Temenos should be placed in the dropins folder of eclipse in
order to create the web serive project.
• Once added, clicking on File>New>Other displays the option to create TWS Project.

12
• The creation of TWS project prompts to enter the connection method where the
connectivity detail is specified as ‘Agent’ and the port number on which the agent is
listening is entered as one of the connection parameters. The host holds the T24
server’s IP address.

13
• On clicking Window > Show View > Other it provides a list out of which the T24
Services has to be selected.
• The T24 Services lists all the service records available under EB.SERVICE application.

14
• The T24 Services window lists all the EB.SERVICE records out of which the TCIB Retail
service should be selected
• The screenshot displays the EB.SERVICE record in the browser and it’s equivalent in
the T24 Services window
• The T24 Services window displays the ‘Description’ field of EB.SERVICE. Here the
screenshot shows that the description of the EB.SERVICE record ‘TCIB Retail’ is
displayed as the service name in the T24 Services of eclipse IDE.
• Likewise the PW.ACTIVITY record’s Description field is displayed under the Application
(Version) and Enquiry of the T24 Services.

15
• In the T24 Services window an icon is provided in order to create the services for the
TWS project.
• On clicking the icon the services are created in the source folder of the TCIB Retail
project.

16
• Once the services are created the project should be exported as war file.

17
• Once the services are created the project should be exported as war file.

18
• A dedicated connection factory in the t24-ds.xml supports TCIB connectivity as shown
in the screenshot. The IP Address of the T24 server and the port number of listening
agent is specified.
• The WEB-INF\jboss-web.xml invokes this connection Factory. The mode for the
dedicated OFS.SOURCE record "TCIB" is pre-authenticated.

19
• The OFS.SOURCE record should hold the ‘Attributes’ has TWS.
• The field ‘Same Authoriser’ should be enabled since Internet Banking should allow
zero authoriser version for ARC IB users.
• The ‘Channel’ should be given as INTERNET.

20
• The ‘TCIBRetail.war’ file generated through eclipse should be deployed in the Jboss
folder. The relative path for deployment is as follows
…\JBoss\server\default\deploy\...
• On accessing the services of the deployed war file using the following URL
(http://localhost:9095/TCIBRetail/services) the endpoint URL has shown in the
screenshot is displayed.

21
• On accessing the end point URL ‘http://localhost:9095/TCIBRetail/services?wsdl’ the
wsdl page is displayed with all the T24 enquiries and versions web services has shown
in the screenshot.

22
• In order to test the web service a SOAP UI project has to be created for the wsdl -
http://localhost:9095/TCIBRetail/services?wsdl.

23
• In this example we are testing the service login details discussed in the earlier slides
• The default SOAP Request will have ? in the place of values. Replace all the ? with
corresponding values. Here in our case replace the UserName and Password with the
corresponding values.
• Then on executing the request the response is received with the User name and last
login details and corresponding UI screenshot is shown.
Note: You can see a slight variation in the timings of last login, it is the time difference
between testing the request in SOAP and the actual UI.

24
edgeConnect Integration with T24
• Create a new Project in edgeConnect IDE.
• In order to create a web service integration project, click on Tools  Generate
Project  from Web Service…
• On selecting it a pop up window appears prompting to enter the WSDL File Name.
Enter the end point URL (http://localhost:9095/TCIBRetail/services?wsdl) created
earlier.

26
• The ‘Details of the Required Operations’ page provides the list of available SOAP
based operations that we have specified in the WSDL
‘http://localhost:9095/TCIBRetail/services?wsdl’
• These SOAP based operations are nothing but the T24 enquiries and versions in the
web service form.
• Choose ‘LoginDetails’ from the list of operations provided.

27
• On clicking finish it creates the corresponding processes, Data Items along with the
Integration Source and Interface. Thus Web Service Integration Project for Login
Details is created.

28
• The screens displays the Process Editor, Data Store Editor and Integration Editor
whose data are automatically created during the creation of Web Service Integration
Project.

29
1.False
2.OFS.SOURCE, PW.ACTIVITY, EB.SERVICE
3. …/eclipse/dropins
4. SOAP UI

30