IRIS 2.

0 war File Generation

Step 1:
Deploy the 2 war files which is given by temenos in your jboss
irf-web-client - Workbench
irf-test-web - To test the IRIS Services
Give the base URL in the browser-> Workbench gets opened

Select settings tab → click settings → Then the servers page gets opened.
Select your appropriate irf-test-web server.

Click on APIs tab → Click Create Provider API

The Available Artefacts can be displayed. The Artefacts can be Versions(Screen),
Enquiries(Query),AA Product(Product) and so on.
Select the data’s which you want to import.
The API definition page will be displayed.
Give the required details in the field.

Key: It is the main field which helps you to identify your API’s in the deployed
services.
URL field should have the path of your API → Replace id in the Field.
Select the Map To field as your id Which you gave above (SelectionField).

Click Next → click Finish.

Click Download → The data files can be downloaded here.

Start the Design Studio → New → Project.

Select → Maven → Maven Project→ Next → Next.
Select the archetype for creating service → click Next .

Give Artifact Id(Name which you want) →Finish → Then the service project gets created.
Select the archetype for creating container → click Next .
Give Artifact Id(Container name) →Finish → Then the Container project gets created.
Clean the both container and Service project by Selecting,
Right click on Project → Run As → Maven Clean.
Paste the Downloaded files from the Workbench in the Below path,
E:\Akshaya\Design_Studio_19\DesignStudioT24-
R19.45\workspace\AccountBalanceDetails\src\main\resources

Adding Dependencies:
Double click on pom.xml → select Dependencies tab → click Add.

Search your service name in Enter groupId field → select your service → Click OK.
Setting Properties to access the war file,
Double click standalone-comms.properties in ( container project → src/main/resources
→ irf-config )

Give the jboss environment , username and password.

Java.naming.security.principal = username
Java.naming.security.credentials = Password
Install the both container and Service project by Selecting,
Right click on Project → Run As → Maven Install.
War files gets created ( Service container project → target → <.war> ).
After Maven install,
Jar files gets created ( Service project → target → <.jar> ).

Deployment :
Deploy the .war file in your jboss.
E:\Envz\R19\Working JBoss\jboss-eap-7.0_working\jboss-eap-7.0\standalone\deployments
Adding server for view API’s :
Open workbench → click on Settings tab → click Add Server button.

Give the Required Details in the fields → Click ADD.

Select the Server which you created now. Click on Dashboard Tab → Deployed Services.
Click API docs on the right side.

Click Try it out on the right hand. Execute your API by passing values.
Checking API in Postman :
Run postman → click ‘+’ button → paste your API link and add War filename in the link.
Click Send → Response will be shown.
 Orchestration

Question:
Creating orchestration for FT and Account

Req : After Authorization of FT(version), The enquiry which shows the debit Account Id’s
Available balance

Step 1:
Choose the artefacts in the workbench and generate the zip file.

Enquiry : FUNDS.TRANSFER,FT.API.GENERIC.1.0.0
Version : PZ.API.ACCOUNTS.BALANCE.1.0.0
Step 2:
Extract the zip file and place it in the new service project.
Src -> main -> resources

Step 3:
Open the service xml file in the project.
Step 4:
Open the xml file and write the below code under the t24 version processor line in the xml
file.

Above xml file is for version.Here im passing debit AccountId field to the enquiry as
selection field.

Open the enquiry xml file:

Map the debitAccountId to the selection field. (Here we passing headerName which is we
written in the version xml file)

Step 5:
Right click on both project and Container RunAs-> Maven clean & Install.

Jar file created in the service project & war file created in the container project.

Step 6:
Deploy the war file in the jboss.

Add the server in the workbench.

See the deployed services in Dashboard-> Deployed Services

Step 7:
Check the output in postman.

Pass the payload for Funds Transfer version (Mandatory fields is enough)
Pass the Headers which you want.

Click send.
The output should only display the Enquiry values. It doesn’t shows the version output.
But Ft version is successful then only the Enquiry output should otherwise it show an error.
(Available balance in the debit Account which we given is shown below)
 T24 FUNCTIONS

IRIS Framework needs to support the following advanced T24 Functions:

• Delete
• Authorize
• Reverse
• Hold
For the above functions we have to manually add the functions in the service xml file in the
project.

As like delete we have to give all the functions in the xml file.

Validate_only:
Validate is an option and not a function. This option is supported for delete, reverse, hold
and input functions. To use validate option, validate_only should be passed as query
parameter and value should be true.
By default, the validate_only is set as property in service.xml and header as validate_only,
as shown below. And the default value of validate_only property is false.
By default, Input function is set.
• If the http Method is DELETE and function property is not specified, reverse function
is set by default.
• If the http Method is GET and function is not specified in service xml, See function is
set by default.
• If the http Method is PATCH, it throws an error "Patch method not supported".
 Enquiry FILE VERSIONS
This feature is provided to specify a dynamic query parameter "file Versions" for all the
Enquiries at runtime to get records based on the FILE.VERSION
To select the tables from which Enquiry will fetch the records (like NAU, LIV, SIM, HIS etc.)
These values should be selected in the multi-value field "FILEVERSION" while designing the
Enquiry record.

To check the file versions in the postman,

If the value given in "file Versions" is not set while Enquiry designing we get an error like
this:-"Option NAU not defined in FILE.VERSION."
 Setting Number of Authorisers using IRIS

IRIS R18 does not set any number of authorisers in the request sent to T24,it uses the no of
authorisers defined at the version level itself.
If needed, IRIS R18 also provides provision to set it in each request by setting property
"number Of Authorisers" in the service xml.

The possible values that can be set are:

0- No authoriser which means that this Version will validate and authorize in one
activity. This will move the record directly to "Live" state.
1- One authoriser will be required. This will move the record to "Unapproved" state.
2- Two authorisers will be required. This will move the record to "Unapproved" state.
blank- It defaults it to the no of authorisers defined at version level.

In case of any invalid values are provided apart from above mentioned , it will take
default no of authorizer which is set in the version level. It doesn’t through any error.
 GENERATING API FOR MULTIPLE VERSION

Next Version:
Create a version with Next version
Step 1:

Choose the Artefact in Workbench

Version : FT.API.ASSO1.1.0.0

Step 2:

Create Service and Service-Container project in design studio and paste the downloaded file in the folder
Service(Multipleservice)→src→main→resource
Step 3:

Open the folder Service(Multipleservice)→src→main→resource→service→XML file

Add the Next Version Id in the service XML file

Next Version : AC.API.NEXT.1.0.0

Then save it and run both the service and service-container project
Step 4:

The war file gets generated and deploy the war file

Step 5:

Add the server in the workbench and check the deployed service
Step 6:

Check the output in postman

Pass the mandatory values (for both version and next version) in the body section and click the send button
Step 7:

You will get the output for next version , it doesn’t show the output for parent version.

Associated versions
Do the same steps for associated version but in step 3 add the associated version in service xml file

Then check the output in postman

Pass the values for the mandatory fields

In this for both parent and associated versions get the same result
 IRIS Auth token Generation(JWT)

The functionality required in IRIS is to provide capability in IRIS to validate the

credentials passed in header(basic Authentication) against T24 and send back the JWT
token for a the successful authentications.
Deploy the war file irf-auth-token-generation-container.war in jboss.
Check it in the postman by the below URL
http://<host>:<port>/IrisAuthTokenGenerator/api/v1.0.0/generateauthtoken
pass with credentials,

The Auth token has been generated.

Creating client own private key:
• Give the below comment in the command prompt
• Change the values which you want (Store password, key password, alias,file
name)
• Note down Store password, key password, alias values
• The .jks file should be created in the respected folder which you open the
command prompt.

Right click on war file -> WEB-INF -> classes -> paste the .jks file.
• Change the store password, key password , alias, filename in the keystore.properties
file which is in the same location.
• Now you can save changes and deploy the same war file in your jboss
• Test the same and you will get own private token for use.