Deployment of IRIS artefacts

in WebSphere 9.0.0.x
1.0 | November 2019
All post R19 AMR releases up to and including R20 AMR

1.0 | November 2019

All post R19 AMR releases up to and including R20 AMR
Deployment of IRIS artefacts in WebSphere

Contents
1 About this runbook ......................................................................................... 3
1.1 Scope ...................................................................................................................... 3
1.2 Audience.................................................................................................................. 3
1.2.1 Skills .............................................................................................................. 3
1.2.2 Knowledge ..................................................................................................... 3
1.3 Legal........................................................................................................................ 3
1.4 History ..................................................................................................................... 4
2 Introduction .................................................................................................... 5
3 Assumptions and prerequisites ...................................................................... 7
3.1 Assumptions ............................................................................................................ 7
3.2 Prerequisites............................................................................................................ 7
4 Deploying the IRIS R18 artefacts ................................................................... 8
4.1 Deploying the Interaction Framework workbench..................................................... 8
4.2 Deploying the Temenos public APIs ...................................................................... 11
4.3 Deploying the Temenos test APIs .......................................................................... 15
5 Testing the IRIS R18 artefacts ..................................................................... 20
5.1 Launching the IRIS workbench .............................................................................. 20
5.2 Testing the deployed services................................................................................ 20

2
Deployment of IRIS artefacts in WebSphere

1 About this runbook

IRIS R18 API development guide – Deployment of IRIS artefacts in WebSphere describes
how to deploy and test the IRIS R18 runtime and design time artefacts in WebSphere
Application Server.

1.1 Scope
This runbook covers deploying and testing IRIS R18 artefacts in WebSphere. It does not cover
installing or configuring a T24 environment in WebSphere.

1.2 Audience
This guide is aimed at those deploying the IRIS R18 runtime and design time artefacts in
WebSphere application server.

1.2.1 Skills
 T24
 TAFJ
 WebSphere
 Oracle 18c

1.2.2 Knowledge
Readers with a basic understanding of the above listed skills will find the steps contained in
this guide much easier to follow.

1.3 Legal
© Copyright 2019 Temenos Headquarters SA. All rights reserved.
The information in this guide relates to TEMENOSTM information, products and services. It also
includes information, data and keys developed by other parties.
While all reasonable attempts have been made to ensure accuracy, currency and reliability of
the content in this guide, all information is provided "as is".
There is no guarantee as to the completeness, accuracy, timeliness or the results obtained
from the use of this information. No warranty of any kind is given, expressed or implied,
including, but not limited to warranties of performance, merchantability and fitness for a
particular purpose.

3
Deployment of IRIS artefacts in WebSphere

In no event will TEMENOS be liable to you or anyone else for any decision made or action
taken in reliance on the information in this document or for any consequential, special or
similar damages, even if advised of the possibility of such damages.
TEMENOS does not accept any responsibility for any errors or omissions, or for the results
obtained from the use of this information. Information obtained from this guide should not be
used as a substitute for consultation with TEMENOS.
References and links to external sites and documentation are provided as a service.
TEMENOS is not endorsing any provider of products or services by facilitating access to these
sites or documentation from this guide.
The content of this guide is protected by copyright and trademark law. Apart from fair dealing
for the purposes of private study, research, criticism or review, as permitted under copyright
law, no part may be reproduced or reused for any commercial purposes whatsoever without
the prior written permission of the copyright owner. All trademarks, logos and other marks
shown in this guide are the property of their respective owners

1.4 History
Version Date Description Author

1.0 November 2019 Initial release Suvalakshmi V and Dominik

Wietrzak

4
Deployment of IRIS artefacts in WebSphere

2 Introduction
IRIS (Interaction, Reporting and Information Services) is a product that implements Temenos’
Interaction Framework. It makes the bank’s core banking data and functionality (resources)
readily available in a standard way (an API) to any user interface (UI) or application.

IRIS APIs are RESTful and are developed in two variations – Enterprise APIs aka provider
APIs and Experience APIs aka published APIs.

Key to diagram

The Interaction Framework maps and interacts with the experience APIs and the
enterprise APIs.

Enterprise APIs are defined services, for example, Open Banking API, STET and
so on.

Experience APIs are simple services that expose specific core capabilities as a
proprietary API, for example, Internet Banking, PSD2.

Enterprise APIs are the building blocks which orchestrate and expose business capabilities
from record keeping systems such as T24 Transact. They can also provide other banking,

5
Deployment of IRIS artefacts in WebSphere

non-banking capability, such as a RESTful API using OpenAPI specification (OAS) 2.0, aka
Swagger.

Experience APIs expose business capability to the outside world on the Internet. They are
publicly exposed APIs that orchestrate across the enterprise APIs to implement standard API
definitions. Experience API endpoints internally call one or more enterprise APIs with or
without custom mappings present in the API call which changes the functioning of the base
providers.

6
Deployment of IRIS artefacts in WebSphere

3 Assumptions and prerequisites

There are certain assumptions for you to read before you start deploying IRIS R18 artefacts in
your environment. This chapter lists out the assumptions and the prerequisites for the
deployment of IRIS R18 artefacts in WebSphere Application Server.

3.1 Assumptions
It is assumed that you already have a Stack 2 environment set up with WebSphere as the
application server.

Note: To set up a T24 environment, see the stack runbooks that are
published on Temenos Customer Support Portal or Partner Support
Portal.

3.2 Prerequisites
You need the following IRIS R18 artefacts, which you can obtain from your account manager.

Artefact File Description

IRISR18_RunTime_201909.0.1.7z Test APIs with IRIS

irf-test-web
runtime

Temenos public APIs

irf-provider-container IRISR18_Provider_201909.0.1.7z with IRIS runtime

Workbench - design
irf-web-client IRISR18_DesignTime_201909.0.1.7z time tooling

7
Deployment of IRIS artefacts in WebSphere

4 Deploying the IRIS R18 artefacts

This chapter describes the configuration changes required to deploy IRIS R18 artefacts in
WebSphere application server.
Copy the distribution artefacts to Temenos home directory or to any other directory you prefer
in your environment.

4.1 Deploying the Interaction Framework workbench

The Interaction Framework workbench is a development toolkit that facilitates effortless
generation of Temenos IRIS service artefacts. The workbench is a Java application called
irf-web-client.war that you can deploy on your application server.

Procedure

1. In the Linux shell, navigate to $TEMENOS_HOME and unpack

IRISR18_DesignTime_201909.0.1.7z.
cd $TEMENOS_HOME
7z a IRISR18_DesignTime_201909.0.1.7z
The files are extracted to the IRISR18_DesignTime_201909.0.1 directory.
2. Navigate to the extracted directory and copy irf-web-client.war to
$TEMENOS_HOME.
cd IRISR18_DesignTime_201909.0.1
cp irf-web-client.war $TEMENOS_HOME
3. In WebSphere console, navigate to Applications > Application types.

4. Select WebSphere enterprise applications > Install.

5. Select Remote file system and browse to the location of the irf-web-client.war
file.

8
Deployment of IRIS artefacts in WebSphere

6. Click Next.

7. Choose Fast Path install and click Next.

8. Click Next on each page of the wizard and click Finish. Check that in step 4 the
context root is set.

9. Click Save.

9
Deployment of IRIS artefacts in WebSphere

10. In console, navigate to Applications > Application types.

11. Select WebSphere enterprise applications and click the irf-web-client.war

application.

12. Click Shared library references under References.

13. Select irf-web-client_war and click Reference shared libraries.

14. Move T24_Libraries and TAFJ_Libraries to the Selected: list box.

10
Deployment of IRIS artefacts in WebSphere

15. Click OK and Save.

Under WebSphere enterprise applications, you can see the WAR file deployed.

4.2 Deploying the Temenos public APIs

The Temenos public APIs are Enterprise APIs. They include wide scope business banking
APIs as well as the PSD2 Payment Initiation and Account Information services APIs for T24
Transact. Temenos public APIs are distributed as a Java web archive by name irf-
provider-container.
Procedure
1. In the Linux shell, navigate to $TEMENOS_HOME and unpack
IRISR18_Provider_201909.0.1.7z.
cd $TEMENOS_HOME
7z a IRISR18_Provider_201909.0.1.7z
The files are extracted to the IRISR18_Provider_201909.0.1 directory.
2. Navigate to the extracted directory, rename the WAR file and copy irf-provider-
container.war to $TEMENOS_HOME.
cd IRISR18_Provider_201909.0.1
mv irf-provider-container-201909.0.1.war irf-provider-
container.war
cp irf-provider-container.war $TEMENOS_HOME
3. In WebSphere console, navigate to Applications > Application types.

11
Deployment of IRIS artefacts in WebSphere

4. Select WebSphere enterprise applications > Install.

5. Select Remote file system and browse to the location of the irf-provider-
container.war file and click Next.

6. Choose Fast Path install and click Next on the remaining pages of the wizard.

7. In step 3, map the resource references to the target resources and click Next.

12
Deployment of IRIS artefacts in WebSphere

8. In step 4, check that the context root is set.

9. Click Next on the remaining pages of the wizard, and on the Summary page click
Finish.

10. Click Save.

13
Deployment of IRIS artefacts in WebSphere

11. In console, navigate to Applications > Application types.

12. Select WebSphere enterprise applications and click the irf-provider-container.war

application.

13. Click Shared library references under References.

14. Select irf-provider-container_war and click Reference shared libraries.

15. Move T24_Libraries and TAFJ_Libraries to the Selected: list box.

16. Click OK and Save.

17. Under WebSphere enterprise applications, you can see the WAR file deployed.

14
Deployment of IRIS artefacts in WebSphere

4.3 Deploying the Temenos test APIs

The Temenos test APIs are Enterprise APIs. They include a range of sample business
banking APIs for T24 Transact. These APIs are distributed as a Java web archive by name irf-
test-web. This archive comes with an embedded runtime that you can deploy on your
application server.

Note: irf-test-web.war does remote JNDI lookup. So there are additional

configuration changes that you need to perform in the WAR file before you deploy
it.

Procedure

1. In the Linux shell, navigate to $TEMENOS_HOME and unpack

IRISR18_RunTime_201909.0.1.7z.
cd $TEMENOS_HOME
7z a IRISR18_RunTime_201909.0.1.7z
The files are extracted to the IRISR18_RunTime_201909.0.1 directory.
2. Navigate to the extracted directory and copy irf-test-web.war to
$TEMENOS_HOME.
cd IRISR18_RunTime_201909.0.1
cp irf-test-web.war $TEMENOS_HOME
3. Create a new temporary directory under the path where you have the irf-test-
web.war file (for example, tmp1) and move the WAR file to the temporary directory.
mkdir tmp1
mv irf-test-web.war tmp1
4. Unpack irf-test-web.war and delete the WAR file.
cd tmp1
jar xf irf-test-web.war
rm –rf irf-test-web.war
5. Navigate to WEB-INF/classes and open standalone-comms.properties. This
file contains connection properties for the connection to the remote host. The file is
referenced in WEB-INF/classes/applicationContext.xml.

6. Change the java.naming.factory.initial to

com.ibm.websphere.naming.WsnInitialContextFactory, which is specific to
WebSphere.

15
Deployment of IRIS artefacts in WebSphere

7. Change the java.naming.provider.url to

iiop://localhost_or_ipaddress:Bootstrap_port and add jmscf.jndi.url
to jms/t24ConnectionFactory. To determine the Bootstrap port, check the
file AboutThisProfile.txt that is present in the log folder
($WAS_HOME/profiles/Profile_Name/logs) of the profile.

Note: The default Bootstrap port is 2809.

8. Modify jndiname as illustrated, change java.naming.security.principal and

java.naming.security.credentials value to WebSphere admin console user
name and password respectively.

Note: Check DMGR_USER and DMGR_PASSWORD that are in

$TAFJ_HOME/appserver/was/setUpEnv.sh to learn the WebSphere admin
console user name and password.

9. Navigate to the temporary directory, repack irf-test-web.war and move it to the

previous path.
jar cf irf-test-web.war *
mv irf-test-web.war $TEMENOS_HOME
8. In WebSphere console, navigate to Applications > Application types.

9. Select WebSphere enterprise applications > Install.

10. Select Remote file system and browse to the location of the irf-test-web.war file
and click Next.

16
Deployment of IRIS artefacts in WebSphere

11. Choose Fast Path install and click Next on the remaining pages of the wizard.

12. In step 3, map the resource references to the target resources and click Next.

17
Deployment of IRIS artefacts in WebSphere

13. In step 5, check that the context root is set.

14. Click Next on the remaining pages of the wizard, and on the Summary page click
Finish.

15. Click Save.

16. In console, navigate to Applications > Application types

18
Deployment of IRIS artefacts in WebSphere

17. Select WebSphere enterprise applications and click the irf-test-web.war

application.

18. Click Shared library references under References.

19. Select irf-test-web_war and click Reference shared libraries.

20. Move T24_Libraries and TAFJ_Libraries to the Selected: list box.

21. Click OK and Save.

22. Under WebSphere enterprise applications you could see the WAR file deployed.

19
Deployment of IRIS artefacts in WebSphere

5 Testing the IRIS R18 artefacts

This chapter describes the steps that are required to test the deployed IRIS R18 artefacts in
WebSphere Application Server.

5.1 Launching the IRIS workbench

Launch the workbench using the following URL:
http://localhost_or_ipaddress:WebSphere_port/irf-web-client
The Dashboard is launched.

5.2 Testing the deployed services

Procedure
1. Set the default service configuration using the Settings menu.

20
Deployment of IRIS artefacts in WebSphere

2. Modify the TestWeb Server URL to

http://localhost_or_ipaddress:WebSphere_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.
4. Choose the irf-provider-container under Servers.

5. In the workbench, click Dashboard > Deployed Services.

6. Click API docs near any endpoint with GET method.

7. Click GET and select Try it out.

21
Deployment of IRIS artefacts in WebSphere

8. Click Execute. An error response is displayed. This is because the endpoint URL does
not point to the application server IP and port as illustrated.

9. To get the successful response, copy the Swagger URL.

10. Paste the URL in any third-party REST client and get the response. Here you could
see the host is incorrect.

22
Deployment of IRIS artefacts in WebSphere

11. Copy the response, paste it in online Swagger editor (https://editor.swagger.io/) and
modify the host to http://localhost_or_ipaddress:WebSphere_port/irf—
provider-container and schemas to http.

23
Deployment of IRIS artefacts in WebSphere

12. Click GET and select Try it out.

13. Click Execute. The request URL now points to correct IP and port, which gives a
successful response.

24
Deployment of IRIS artefacts in WebSphere

14. Alternatively, you can test the API by trying to get 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

25
Deployment of IRIS artefacts in WebSphere

15. Try hitting any end-point.

16. Perform similar steps to test irf-test-web.

26