Doc u m e n t Hist o r y

Revi si o
Dat e Ame n d e d Na m e De s c r i p t i o n
n
1 29 th Marc h 2020 Dhanya J Initial version
Bash e e r
2 12 th April 2021 R21 AMR review
Aham e d

3 25 th April 2022 M.Kum a r R22 AMR review

4 6 th April 2023 M.Kum a r R23 AMR review

H. Sanofa r
5 15 th May 2023 Jdk11 Review
Nish a

2
Co m po n e n t F r a m e wo rk Deploying co m po n e n t S e rvice

Copyri g h t

Copyrig h t © Teme n o s Hea d q u a r t e r s SA 2009- 2023.

All right s rese rv e d.
This docu m e n t cont ain s prop rie t a r y inform a tio n that is prote c t e d by copyrig h t. No part of this docu m e n t may
be repro d u c e d , tra ns m i t t e d , or mad e availa ble direc tly or indirec tly to a third party without the expr e s s
writt e n agre e m e n t of TEMENOS UK Limite d. Receipt of this mate ri al direc tly TEMENO S UK Limite d
constit u t e s its expr e s s per mis sion to copy. Per mis sion to use or copy this docu m e n t expr e s sly exclud e s
modifying it for any purpo s e , or using it to cre a t e a derivative the r ef ro m .

Errat a and Com m e n t s

If you have any com m e n t s reg a r di n g this man u al or wish to repor t any error s in the docu m e n t a t i o n ,
plea s e docu m e n t the m and send the m to the add r e s s below:
Technology Depa r t m e n t
Teme no s Hea d q u a r t e r s SA
2 Rue de l’Ecole- de- Chimie,
CH - 1205 Geneva,
Switze rl a n d

Tel SB: +4 1 (0) 22 708 1150

Fax: +4 1 (0) 22 708 1160

Pleas e includ e your na m e , comp a n y, addr e s s, and telep h o n e and fax num b e r s , and email add r e s s if
applica bl e. TAFJdev@t e m e n o s . c o m

3 Teme no s Application Fra m e w o r k Java – (TAFJ)

 Ta b l e o f C o n t e n t s

Intro d u c t i o n
This section enables you to deploy different T24 Component Service APIs in Temenos Application Framework (TAF) on
supported platforms.

Soft w a r e Req u i r e m e n t s
This section provides you the details of the software required for deploying component services in Temenos Application
Framework (TAF) environment.

Requirement Description

T24 Component Service with its API

Available as part of runtime file.
packages (Release 12 or later)

TAFC runtime environment Applicable for TAFC deployment.

TAFJ runtime environment Applicable for TAFJ deployment.

JCA 1.5 compliant resource adapter that enables J2EE

tocfT24ra-ra.rar (TOCF(EE) T2 components to access T24 through jAgent. To know more, refer
4 resource adapter) to TAFC jAgent user guide. Applicable on J2EE application
server deployment for TAFC.

To download, go
Apache Axis2 – Release 1.8.2
to http://axis.apache.org/axis2/java/core/download.cgi

The supported servers are:

 IBM Web Sphere Liberty Application Server – Release

19.0.0.0+
J2EE compliant application server
 Oracle WebLogic – Release 14.0.0+

 JBoss – Release 7.4+

MS IIS Server 7 Applicable for .NET web service deployment for TAFC.

4
Co m po n e n t F r a m e wo rk Deploying co m po n e n t S e rvice

TAFC Confi g u r a t i o n
This section explains the process to deploy APIs for TAFC specific environment.

Overview for TAFC

This section explains you the deployment and configuration options that are available for TAFC specific environment. All
component services directly depend on libComponentFramework, hence, the Library (lib) needs to be in the following
path:

Platform File Path

Windows TAFC_HOME\bin

Unix or Linux TAFC_HOME\lib

The jsh SJunejo ~ -->jshow -a libComponentFramework.so command helps to verify and list the
following subroutines in the library from jshell:

Object C:\ModelBank\TAFC\lib\libComponentFramework.so

Subroutines  JBC_GetServiceResponseHandler

 JBC_CheckServiceOperationExist

 JBC_GetProxyInterface

 libComponentFramework_version

T24 MB R12+ has all available component services by default in the T24_COMPONENTS directory. Additionally, it
provides extensions for existing component services, along with the native jBC API.

To know more on how to develop a new compo n e n t , refer to the following link (video).

Component Framework Demo

This section lists the artefacts in NEW_COMP_SRV\dist directory to deploy newly built component service in T24 for
TAFC.

|_ include[Contains C++ header file useful for service extension implementation]

|_ JBCInsert[Contains JBCInserts which can be used by core T24 application to consume
the service]
|_ lib[Contains all deployable artefacts]
|_ data[Contains component service data libraries for different APIs]
|_ cpp[Contains C++ data libraries]
|_ lib<ComponentService>Data.dll
|_ lib<ComponentService>Data.exp
|_ lib<ComponentService>Data.lib

5 Teme no s Application Fra m e w o r k Java – (TAFJ)

 |_ dotnet[Contains .NET data libraries]
|_ lib<ComponentService>DataWrapper.dll
|_ lib<ComponentService>DataWrapper.exp
|_ lib<ComponentService>DataWrapper.lib
|_ java[Contains Java data libraries]
|_ t24-<ComponentService>-Data.jar
|_ proxyAdaptor[Contains component service Proxy Adaptor to consume external services]
|_ cpp[Contains component service C++ Proxy Adaptor libraries]
|_ lib<ComponentService>ProxyAdaptor.def
|_ lib<ComponentService>ProxyAdaptor.dll
|_ lib<ComponentService>ProxyAdaptor.exp
|_ lib<ComponentService>ProxyAdaptor.lib
|_ t24Service[Contains component service native and extended APIs]
|_ cpp[Contains component service native (jBC) and C++ APIs]
|_ lib<ComponentService>.def
|_ lib<ComponentService>.dll
|_ lib<ComponentService>.exp
|_ lib<ComponentService>.lib
|_ lib<ComponentService>Core.def
|_ lib<ComponentService>Core.dll
|_ lib<ComponentService>Core.exp
|_ lib<ComponentService>Core.lib
|_ dotnet[Contains component service .NET API]
|_ lib<ComponentService>Wrapper.dll
|_ ws[Contains component service Provider (Web Service) API]
|_ dotnet[Contains component service .NET Provider API]
|_ t24-<ComponentService>-dotnetws.zip
|_ java[Contains component service Java Provider API]
|_ t24-<ComponentService>-jws.aar

API Deployment for TAFC

This section explains the deployment process of jBC, C++, .NET, Proxy Adaptor and Proxy APIs in TAFC.

jBC Deploym e n t
This API enables applications and other components to access core component implementation within T24. It is
packaged in lib<ComponentService>Core.* library, which has jBC APIs and components for implementation.

EXAMPLE: lib<CustomerService>Core.*, lib<ChargeService>Core.*

6
Co m po n e n t F r a m e wo rk Deploying co m po n e n t S e rvice
Item Description

Existing Packaged within T24 by default and is available in the T24_COMPONENTS directory.
Component

New Component Available in the NEW_COMP_SRV\dist\lib\t24Service\cpp directory

as lib<ComponentService>Core.*.

NOTE: You need to copy the library to T24_COMPONENTS.

Deployment Verify the component deployment and check the available operations in the library
Verification by applying one of the following commands from jshell:

 jsh SJunejo ~ -->jshow -c

<ComponentService>.<OperationName>

 jsh SJunejo ~ -->jshow -a lib<ComponentService>Core

Dependencies Has core jBC routines and does not require deployment of other component service
artefacts.

Invoking jBC API Additional configuration is not required to use this library within T24, as API has
native code.

C+ + Deploym e n t
This API provides access to T24 component jBC implementation for third party system built in C++ language. Additionally,
it converts core C++ objects to jBC format and vice versa by providing standard C++ interface and objects to third party.
This helps you to avoid the need to deal with internal T24 (jBC) format. C++ API is packaged
in lib<ComponentService>.* library, which has C++ interface components and its implementation.

EXAMPLE: lib<CustomerService>.*, lib<ChargeService>.*

Item Description

Existing Packaged within T24 by default and is available in the T24_COMPONENTS directory.
Component

New Component Available in the NEW_COMP_SRV\dist\lib\t24Service\cpp directory

as lib<ComponentService>.*.

NOTE: You can copy the library to T24_COMPONENTS.

Deployment Verify the component deployment and check the available operations in the library by
Verification applying the following command from jshell:

jsh SJunejo ~ -->jshow -a lib<ComponentService>

Dependencies Has pure C++ classes and depends on its lib<ComponentService>Data.* data
library.

NOTE: The library is available in the following directories:

 Existing component - Shipped by default within T24_COMPONENTS

 New component - Copy the data library

7 Teme no s Application Fra m e w o r k Java – (TAFJ)

Item Description

from NEW_COMP_SRV\dist\lib\data\cpp to T24_COMPONENTS

Invoking jBC The third party system needs to setup the T24 environment before invoking C++ API.
API
This environment includes setting up the following variables:

 TAFC_HOME

 JBCOBJECTLIST

 JBASE_JBCOBJECTLIST_DIR

 OFS_SOURCE

 JBASE_I18N

 JBASE_LOCALE

 JBASE_CODEPAGE

This is performed by appending T24_COMPONENTS to the following environment

variables:

 Windows - PATH

 Unix or Linux - LIBPATH, SHLIB_PATH and LD_LIBRARAY_PATH

.NET Deploym e n t
This API provides access to T24 component jBC implementation for third party system built in .NET languages. It uses C+
+ Deployment to process the request from T24. It is packaged in lib<ComponentService>Wrapper.dll library,
which has .NET interface components and its implementation. This library is only available for Windows platform.

EXAMPLE: lib<CustomerService>Wrapper.dll, lib<ChargeService>Wrapper.dll

Item Description

Existing Packaged within T24 by default and is available in the T24_COMPONENTS directory.
Component

New Component Available in the NEW_COMP_SRV\dist\lib\t24Service\dotnet directory

as lib<ComponentService>Wrapper.dll.

NOTE: You can copy the library to T24_COMPONENTS.

Deployment Available in the NEW_COMP_SRV\dist\lib\t24Service\dotnet directory

Verification as lib<ComponentService>Wrapper.dll

NOTE: You can copy the library to T24_COMPONENTS.

Dependencies Has pure .NET classes and depends on

its lib<ComponentService>DataWrapper.*data library in
the NEW_COMP_SRV\dist\lib\data\dotnet directory and C++ component.

 Existing component - Shipped by default within

the T24_COMPONENTS directory.

8
Co m po n e n t F r a m e wo rk Deploying co m po n e n t S e rvice
Item Description

 Newly component - Copy the data library

from NEW_COMP_SRV\dist\lib\data\dotnet to
the T24_COMPONENTS directory.

NOTE: To resolve C++ API dependencies for runtime, refer to C+

+ Deploym e n t section.

Invoking jBC API The third party system needs to setup complete T24 environment before invoking
.NET API. This environment includes setting up the following variables:

 TAFC_HOME

 JBCOBJECTLIST

 JBASE_JBCOBJECTLIST_DIR

 OFS_SOURCE

 JBASE_I18N

 JBASE_LOCALE

 JBASE_CODEPAGE

This is performed by appending T24_COMPONENTS to the following environment

variable:

 Windows - PATH

NOTE: Component Service .NET API depends

on libComponentFrameworkWrapper.dll library, which is distributed with TAFC
and available in the TAFC_HOME\bin directory.

Provide r Deploym e n t
This API exposes the T24 component (jBC) implementation as a web service. It is available in the following technologies
for TAFC:

Technology Server

Windows Communication Foundation MS IIS Server 7

Java Supported J2EE Application Server

Proxy Adapto r and Proxy Deploym e n t

Unlike jBC, C++, .NET, and Provider APIs whose core responsibility is to host T24 as data provider (that is, third party
system needs to access T24 and retrieve data by providing industry standard interfaces), the Proxy Adaptor and Proxy
API offers functionalities to access third party system within T24 (that is, making T24 a data consumer). Additionally, it
provides T24 component to switch from its default jBC implementation to standard C++ interface implementation on
runtime, where you can write the custom code to access third party system.

NOTE: Packaged in lib<ComponentService>ProxyAdaptor.* library, which is available in the following directories:

9 Teme no s Application Fra m e w o r k Java – (TAFJ)

  Existing component - COMPONENT_EXT\<ComponentName>\t24Proxy

 New component - NEW_COMP_SRV\dist\lib\proxyAdaptor\cpp

The Proxy Adaptor is deployed when the library is dropped in the T24_COMPONENTS directory. If jBC API finds a
request when checking the deployment, it redirects the request to Proxy Adaptor. On receiving the request, it converts the
format from native jBC to C++ objects before forwarding it to Proxy API and vice versa.

NOTE: You need to write the custom C++ implementation of the interface <ComponentService>Proxy in
the <ComponentService>Proxy.h file, and make the implementation library available in following environment
variables:

 Windows - PATH

 Unix or Linux - LIBPATH, SHLIB_PATH and LD_LIBRARAY_PATH

The Proxy API has interface header files in the following directories:

 Existing component - COMPONENT_EXT\<ComponentName>\include

 New component - NEW_COMP_SRV\dist\include

TAFJ Configuration
This section explains the process to deploy APIs for TAFJ specific environment.

Overview for TAFJ

This section explains you the deployment and configuration options that are available for TAFJ specific environment.

NOTE: All component services depend on the libComponentFramework.jar library that is available in
the TAFJ_HOME\ext directory.

This is verified by using the below command.

C:\TAFJ\tShow GetServiceResponseHandler
Home : 'C:\TAFJ '
- Project : 'tafj' [ FOUND ]
BASIC source :
'C:\RTC\src\DEV\SoaFramework\build\tafj\basic\GetServiceResponseHandler.b'
JAVA class :
'file:/C:/TAFJ/ext/tComponentFramework.jar!/com/temenos/t24/GetServiceResponseHa
ndler_21_cl.class'
Compiled the : 11 Oct 2011 16:19:18
on : hmll1010336
Timestamp : 1318346358797
Grammar : 1
Include Basic Replacement : false

T24 MB R12+ has all available component services by default in the T24_COMPONENTS directory. Additionally, it
provides extensions for existing component service, along with the native jBC API.

To know more on how to develop a new component, refer to the following link (video).

10
Co m po n e n t F r a m e wo rk Deploying co m po n e n t S e rvice
Component Framework Demo

This section lists the artefacts in NEW_COMP_SRV\dist directory to deploy newly built component service in T24 for
TAFJ.

|_ JBCInsert[Contains JBCInserts which can be used by core T24 application to

consume the service]
|_ lib[Contains all deployable artefacts]
|_ data[Contains component service data libraries]
|_ java[Contains Java data libraries]
|_ t24-<ComponentService>-Data.jar
|_ proxyAdaptor[Contains component service Proxy Adaptor to consume external
services]
|_ java[Contains Java libraries]
|_ t24-<ComponentService>-ProxyAdaptor.jar
|_ t24Service[Contains component service native and extended APIs]
|_ java[Contains Java libraries, Following JAR contains, jBC Impl, jBC, Java and
Proxy API]|_ t24-<ComponentService>.jar
|_ ws[Contains component service Provider (Web Service) API]
|_ java[Contains component service Java Provider API]
|_ t24-<ComponentService>-jws.aar

API Deployment for TAFJ

This section explains the deployment process of jBC, Java, Provider, Proxy Adaptor and Proxy APIs in TAFJ.

jBC Deploym e n t
This API enables applications and other components to access core component implementation within T24. It is
packaged in the T24-<ComponentService>.jar library in com.temenos.T24, which has jBC API and jBC
components for implementation.

EXAMPLE: T24-<CustomerService>.jar , T24-<ChargeService>.jar

Item Description

Existing Packaged within the T24 by default and is available in T24_COMPONENTS directory.
Component

New Component Available in the NEW_COMP_SRV\dist\lib\t24Service\java directory

as T24<ComponentService>.jar.

NOTE: You need to copy the library to T24_COMPONENTS or add the location in
Java CLASSPATH.

Deployment Verify the component deployment by applying jsh SJunejo ~ -->tShow

Verification <ComponentService>.<OperationName> command.

Dependencies Has core jBC routines and does not require deployment of other component service
artefacts.

Invoking jBC API Additional configurations are not required to use this library within T24, as API has
native code.

11 Teme n o s Application Fra m e w o r k Java – (TAFJ)

Java Deploym e n t
This API provides access to T24 Component jBC implementation for third party system that is built in Java language.
Additionally, it convert core Java objects to jVar format and vice versa by providing standard Java interface and objects to
the third party. This helps to avoid the need to deal with internal T24 (jVar) format.

Java API is packaged in T24-<ComponentService>.jar library

in com.temenos.services.<ServiceName>, which has Java API, Java Impl, and Proxy API components.

EXAMPLE: com.temenos.services.<Customer>, com.temenos.services.<Charge>

Item Description

Existing Packaged within T24 by default and is available in the T24_COMPONENTS directory.
Component

New Component Available in the NEW_COMP_SRV\dist\lib\t24Service\java directory

as T24<ComponentService>.jar.

NOTE: You can copy the library to T24_COMPONENTS or add the location in
Java CLASSPATH.

Dependencies Consists of core Java classes and depends on its lib-<ComponentService>-

Data.jar data library, which needs to be available in CLASSPATH.

NOTE: The library is available in the following directories:

 Existing component - Shipped by default within T24_COMPONENTS

 New component - Found in NEW_COMP_SRV\dist\lib\data\java

Invoking jBC API You need to perform the following:

 Import T24-<ComponentService>.jar along with T24-

<ComponentSevrice>-Data.jar.

 Pass the T24environment properties (such as OFS_SOURCE to Java API)

as an argument while creating an object and calling the required operation.

NOTE: As each Java API instance represents the TAFJ jSession which is an expensive operation:

 Retain the object in your implementation for better performance

 Reuse it by switching the context for a different user

Provide r Deploym e n t
This API exposes T24 component jBC implementation as a web service. The following methods are used for deploying
Provider API of TAFC:

Deployment Method Server

Common Deployment Supported J2EE Application Server

Application Specific Server Deployment JBoss, IBM WebSphere

12
Co m po n e n t F r a m e wo rk Deploying co m po n e n t S e rvice
Proxy Adapto r and Proxy Deploym e n t
Unlike jBC, Java, and Provider APIs whose core responsibility is to host T24 as data provider (that is, third party system
needs to access T24 and retrieve data by providing industry standard interfaces), the Proxy Adaptor and API offer
functionalities to access third party system within T24 (that is, making T24 a data consumer). Additionally, it
provides T24 component to switch from its default jBC implementation to standard Java interface implementation on
runtime, where you can write the custom code to access third party system.

NOTE: Packaged in T24-<ComponentService>-proxyAdaptor.jar library, which is available in the following

directories:

 Existing component - COMPONENT_EXT\<ComponentName>\t24Proxy

 New component - NEW_COMP_SRV\dist\lib\proxyAdaptor\java

The Proxy Adaptor is deployed when the library is dropped in Java CLASSPATH, followed by adding or updating
the services.properties file in TAFJ_HOME/conf directory or from CLASSPATH. If jBC API finds a request
when checking the deployment, it redirects the request to Proxy Adaptor. On receiving the request, it converts the format
from native jVar to Java object, finds the proxy implementation by using ‘services.properties’ and forwards it to Java API
and vice versa.

NOTE: You need to write the custom Java implementation of the interface <ComponentService>ProxyAPI in T244-
<ComponentService>.jar of com.temenos.services.<ComponentName> package and make it available in
Java CLASSPATH.

The Proxy API has interface header files in the following directories:

 Existing component - T24_COMPONENTS

 New component - NEW_COMP_SRV\dist\t24Service/java along with the Java API

You need to replace <ComponentService> with the name of the component. For example, CustomerService,
ChargeService etc.

Resources

This section provides you additional information on Temenos Application Framework (TAF).

 Java JDK

 J2EE Connector Architecture (JCA) Specification

 JBoss

 Oracle Weblogic

 IBM Websphere Liberty Application Server

 Oracle Glassfish

Appendix

This section provides examples that helps you to understand API deployment for Temenos Application Framework (TAF).

13 Teme n o s Application Fra m e w o r k Java – (TAFJ)

Web Resources for J2EE Application Servers

jBoss 7.4

jca/t24ConnectionFactory com.jbase.jremote.JConnectionFactory
java:jca/t24ConnectionFactory

IBM WebSphere Liberty Application Server 19.0.0.0+

Oracle WebLogic 14.0.0+

jca/t24ConnectionFactory jca/t24ConnectionFactory

Oracle Glassfish 3.0.1

/axis2 jca/t24ConnectionFactory jca/t24ConnectionFactory

Prope r ti e s File
Services.Properties

################################################################################
#######
# This file will be loaded by Proxy Adaptor to find the Proxy Impl class.
# Example:
CustomerService=com.temenos.services.customer.CustomerServiceProxyImpl
#
# Add your entries below
################################################################################
#######
#
<ComponentName>Service=<Fully_Qualified_ProxyImpl_Class_Name>

14