T24 R24 Re-Implementation Project
(FAMILIARIZATION TRAINING)
INTERACTION FRAMEWORK
By Andrews Oberko
▪ Interaction is about relation between system and human via a user interface as a
request / response model.
▪ Temenos Interaction Framework allow the bank to easily expose banking services
to a user interface or application.
IRIS API FRAMEWORK
(INTERACTION, REPORTING and INFORMATION SERVICES)
• IRIS is a product that that implements the Temenos Interaction Framework.
• It makes the bank’s core banking Data and functionality readily available in a
standard way to API user-interface or App.
• IRIS is a lightweight edition of Temenos Interaction Framework
• IRIS18 is available from the release 18 of Temenos Transact
• Communicate to T24 using OFS
• Connect via TOCF-EE and TAFJ-EE JMS interfaces.
API REST API, Provider APIs vs Published APIs
❑ IRIS APIs are RESTful and developed in two variations:
• Provider APIs are the building blocks, which orchestrate across and expose business
capabilities from record keeping system like Transact as a restful API using OPEN API
specification known as swagger.
• IRIS will only expose core banking artefacts like Versions, Enquiries, Products or activities
that are specifically designed for APIs.
• Published APIs are defined services that expose business capabilities to the outside
world.
❑ The interaction Framework maps and orchestrates between the provider and APIs and the
published APIs
▪ In a TAFJ Environment, IRIS uses JMS connectors to connect to T24. The
incoming message is put a queue. The MDB listening on the queue picks the
message, forwards it to the EJB which acts as an interface to T24.
Environment Development description
DESIGNING AN API USING IRIS Maven Archetype and IRIS Context
▪ IRIS package is providing two ❑ An archetype is a maven project
war applications: templating toolkit. It is a model from
▪ irf-web-client.war application is which project can be cloned.
the API Framework workbench ❑ The IRIS artefact are provided as a zip
allowing t design the API file
▪ irf-test-web.war application to ▪ The Service-container-archetype is
test a IRIS service used to create the iris container
▪ Swagger UI is part of the irf- project and will contain the list of iris
web-client.war application and services
allow to test also a IRIS ▪ The Service archetype is used to
create the iris project and will contain
definition of provider API
SETTING UP DESIGN STUDIO FOR IRIS
DEVELOPMENT
Service Container Creation
Service Container Archetype
❑ In Order to run any Api project you must have a service container. A service container
hosts one or more service projects
❑ The service container project contains the definition of your Api
❑ The container service project holds references to your service projects and therefore to
the APIs
❑ The service container can be created from Maven Archetype in Design studio
Service Container Creation
Service Container Creation
Service Container Creation
Service Container Creation
Container Project >> jms.properties
❑ The service container must know how to connect to t24.
• The t24 connection properties are set in the file jms.properties
• Pass valid T24 credentials in the property or disabling the default
credentials, to make IRISMETADATA queue as default for metadata request
• Set a desired connection timeout
• A number of retry
• The company id
Enquiries and versions Rules
Step 1 : Deploy the irf-web-client.war and irf-test-web.war in deployment folder of Jboss
Application Server.
Step 2 : deploy IRIS18 in Jboss
Step 3 : To start creating Provider APIs, you are required to connect to T24 to get a list of
artefacts for which you intend to generate an API service by setting up the server
Step 5
For Enquiry, the following ID naming convention must be
followed:
XX.API.COLLECTIONID.SUBCOLLECTIONID.Major.Minor.Patch
Restrictions on Enquiry:
• Header fields should not be used in API enquiries.
• Turn FIELD.LABEL into API style labels
• Use FIELD.DISPLAY.TYPE for data type (Alphanumeric /
amount, date)
• Set ATTRIBS to ''
• Set DESCRIPT to be the operation, e.g.
getAccountBalances
Step 6
For Version the following ID naming convention must be
followed:
TABLE,XX.API.VERBS.RESOURCEID.Major.Minor.Patch
Restrictions on Enquiry:
• Field must be in vocabulary
• Field must have DATA type defined
• Should define verbs related to actions
• Must be explicitly versioned
• Must be prefix with XX.API
Step 7: Once properly configured, you should hover to APIs → Create Provider API and the
Workbench list you all the available artefacts in T24\. You are ready to go and create your
own APIs.
After selecting the artefact to be exposed, parameters regarding the API to be created must
be inputted.
After the provider Api has been created and validated.
The service artefact are ready to be downloaded
Design Time Artefacts
❑ API Framework Workbench allows browsing T24 only for APU specific resources
and automates generation of the API artefacts.
❑ The artefacts generated are an inventory of the T24 version, enquiry and activity
selected in the workbench to be exposed in the service.
• Open API (swagger) definition for the T24 resources
• Service XML with routing and integration logic
Service Project >> Service Archetype
❑ The service project contains the definition of your API
❑ For different APIs, you can create different service . Each for these
service projects will describe and encapsulate the Api definition
❑ In the container project, you will specify which of these service projects
you will like to reference
❑ You can create the service project using maven archetype from design
studio
Step 8 : After the artefacts are generated, the build
is done using design studio.
Service Creation
Service Creation
Service Creation
Service Creation
Container Project >> Update Pom.xml
❑ Reminder: The container project is at runtime a war application and is
embedding all IRIS services we need to expose
❑ In the design studio, the pom.xml file of the container project must be
updated accordingly
❑ After attaching the service to the container and rebuilding, the user can now redeploy the war
file.
❑ Listing the services
Users can discover the services supported using the discovery URL.
Below URL helps users to get the swagger documentation URL for all the services supported in
T24 deployment.
http:<base URL>/container/Api/v1.0.0/meta/apidocs
Below URL helps users to get statistic about deployed Api’s.
http:<base URL>/container/Api/v1.0.0/meta/statistics
Below URL helps users test API using swagger documentation
http://localhost:8085/irf-web-client/public/dist/
Thank You!
