Deploying and Testing Temenos T24 APIs with IRIS

Temenos T24 APIs serve as interfaces that enable external systems, applications, or services to interact programmatically with the Temenos Transact (T24) core banking system. These APIs provide access to specific functionalities and data from T24, facilitating secure and organized integration with digital platforms, third-party providers, financial applications, and internal systems.

We are listing the prerequisites and deployment details and testing approach for developing the Temenos T24 API’s

1. Prerequisites:

Artefact	Description
irf-test-web	Test APIs with IRIS runtime
irf-provider-container	Temenos public APIs With the IRIS runtime
irf-web-client	Workbench - design time tooling

2. Deploying the IRIS  artefacts:

WebSphere and WebLogic are two robust Java application servers utilized in Temenos T24 (currently known as Temenos Transact) environments for the deployment of middleware components. Their function within T24 configurations has transformed alongside Temenos' transition to contemporary and cloud-native architectures; however, comprehending their historical application continues to be pertinent, particularly in on-premise or legacy installations.

Deploying the IRIS  artefacts: Websphere	Deploying the IRIS  artefacts: WebLogic
Deploying the Interaction Framework workbench	Deploying workbench
Deploying the Temenos public APIs	Deploying the Temenos public APIs
Deploying the Temenos test APIs	Deploying the Temenos test APIs

Testing IRIS:

IRIS serves as Temenos' integration platform, facilitating access to T24 services such as inquiries and version calls through multiple protocols including HTTP, SOAP, and REST. When implemented within WebSphere or WebLogic, IRIS functions as a middleware layer that manages the routing of requests to the T24 core system. Conducting tests on IRIS in these environments verifies the proper functioning of the integration layer.

Sl.No	Testing IRIS in Websphere	Testing IRIS in WebLogic
1	Set the default service configuration using the Settings menu.	Set the default service configuration using the Settings menu.
2	Modify the TestWeb Server URL to http://localhost or ipaddress:WebSphere port/irf—test-web.	Change the TestWeb Server URL to http://localhost_or ipaddress:WebLogic port/irf—test-web.
3	Add a new server information for your public APIs with the following URL: http://localhost or ipaddress:WebSphere port/irf-provider-container. The irf-provider-container WAR file is packaged with a runtime.	Add a new server information for your public APIs with the URL http://localhost or ipaddress:WebLogic port/irf-provider-container. The irf-provider-container war is packaged with a runtime.
4	Choose the Irf-Provider-Container under Servers	In Servers, select the irf-provider-container.
5	In the workbench, click Dashboard > Deployed Services	In the workbench, select Dashboard > Deployed Services.
6	Click the API docs near any endpoint using the GET method.	Near an endpoint that has a GET method, click API docs.
7	Click GET and select Try it out.	Click GET and select Try it out.
8	Click Execute. An error response is displayed. This is because the endpoint URL does	Click Execute. This will display an error because the endpoint URL does not point to
9	not point to the application server IP and port as illustrated.	The application server IP address and port.
10	To get a successful response, copy the Swagger URL.	To get a successful response, copy the Swagger URL.
11	Copy the response, paste it in the online Swagger editor (Swagger Editor ) and modify the host to http://localhost_or_ipaddress:WebSphere port/irf—provider-container and schemas to http.	Copy the response, paste it in the online swagger editor (Swagger Editor ) and modify the host to http://localhost or ipaddress: WebLogic port/irf—irf-provider-container and the schemas to http.
12	Click GET and select Try it out.	Click GET and select Try it out.
13	Click Execute. The request URL now points to the correct IP and port, which gives a successful response.	Now, when you execute you could see a successful response, because the Request
14	Alternatively, you can test the API by trying to get a response using any third-party REST client with the following URL: http://localhost or ipaddress:WebSphere port/irf-provider-container/api/v1.0.0/meta/apis	Alternatively, you can test the API by trying to get a response using any third-party REST client using the following URL: http://localhost or ipaddress: WebLogic port/irf-provider-container/api/v1.0.0/meta/apis.
15	Try hitting any endpoint.	Then try hitting any endpoint.
16	Perform similar steps to test irf-test-web.	Follow similar steps to test irf-test-web

We specialize in T24 API DEVELOPMENT – IRIS.

If you are planning to implement IRIS in your T24 release, please contact us. We have a combined proposal for T24 API DEVELOPMENT implementation and training.

Keep up the great work! Happy Performance Engineering! #T24API #TemenosIRIS #WebSphere