How to Start Your Temenos T24 IRIS API Journey: A Developer’s Guide

If you want to start your journey with the Temenos T24 API using IRIS, it can be a bit daunting given the enterprise-level complexity. Below, we are listing the high-level details to guide you..

Prerequisites

• Development and testing tools are available: Apache Camel, Maven, Spring, Open API Spec, fka Swagger, Postman, Eclipse, Junit.

• OFS Configuration

  
  

API Development

Workbench Installation and Configuration:

• IRIS  Workbench is a Licensed Design-Time Tool that can be effectively used to create Provider APIs as well as Publisher APIs. A separate request is required to the Distribution to acquire the workbench which facilitates you to create the APIs on your own.

  
  

  Identification of Artefacts:

• For T24 Version and Enquiry artifacts to be used in the Interaction Framework, specific rules must be followed. These rules provide a simple and effective governance framework that identifies that a given T24 artifact is used in an AP and allows simple versioning control to be applied to the T24 artifact following semantic versioning

• Provides data type metadata to ensure clean conversion of data from T24 to internet standard data types

• Provides meaningful operation names

• Creation of Artefacts in T24 to use Version and Enquiry

• Creation of a Service Container to run API projects

• Creation of Service Project: Create a service project using the irf service archetype.

  
  

  Creation of Provider API:

• Provider APIs expose core-banking capabilities as RESTful APIs. The key concept is that each Provider API is driven from an inventory that defines the contents of the API in core banking terms. The inventory is used to create the Swagger specification of the API. The inventory file and the generated swagger specification are used to develop the service implementation.

  
  

  Token-Based Security Filter Implementation:

• IRIS Data Services can be supported as an intermediary in an authenticated request with the JWT token as a mechanism for authentication and identification with the help of this functionality. The handling of the JWT token is expected to be fully configurable to support various deployment choices from naive authenticator to the most secure one.

  
  

  Creation of Published API:

• An API defined in Swagger 2.0 may be imported into an API project. The import process will create the Camel routes, mock responses, and wire the routes to the mock responses. This is done using a Maven plugin from your IDE or the command line.

  
  

Deployment and Configuration

Deployment procedure:

• Once the service project is built, the user can deploy it using any of the following application servers:

• JBoss

•  Weblogic

• Websphere

  
  

  T24 Connectivity Configuration:

• The following connectors are used in the connectivity configuration of TAFJ and TAFC:

• JMS Connector - TAFJ & TAFC TOCFEE

• TCS Connector - TAFC TCS

  
  

  SSL Configuration for IRIS:

• Follow this steps to set up SSL/HTTPS support for your Jboss 7 server using the pure Java implementation supplied by JSSE. Firstly, you must configure keys and (self-signed) certificates for your web server.

  
  

  IRIS Mock Services:

• IRIS Mock Services supports dynamic mock response generation based on the fields in API metadata and dynamically generated data maintained by the local mock dictionary. IRIS Mock Services are responsible for generating random data for the metadata fields based on the domain mock files maintained for the same. Random data based on the corresponding field datatype is generated if the fields are absent in the specified domain (specific mock file).

Infrastructure Services and Tools

Directory Services:

• A directory-based service locator is one of the three lookup implementations for dynamically listing the available APIs and displaying the swagger specification. This service locator implementation is available in if-service-locator and configurable in the Application Context XML file as properties of processor ServiceDirectoryProcessor. IRIS R18 APIs adopt Open API Specification and define a schema for all services supported.

  
  

  Importer Tools configuration and usage:

• RIM Importer is a part of the IRIS R18 toolchain, which intends to address the challenge of migrating legacy IRIS-generated APIs to the current IRIS R18. The tool also supports migrating 80% of the existing API involving manual and automated work processes. The tool helps to 'Load, Transform, Validate, and Generate' API Services compatible with IRIS R18.

  
  

  T24 Version and Enquiry Configurations and Analysis

  
  

• T24 Version: This section explains how the T24 Version configuration affects the structure of the JSON that is produced.

  
  

• T24 Enquiry: This section explains how the T24 Enquiry configuration affects the structure of the JSON that is produced.

  
  

Keep up the great work! Happy Performance Engineering!

#APIDevelopment #CoreBankingIntegration #TemenosWorkbench