GIRO Header & Alias Installation Guide

There are 2 flows in GIRO_Inbound.bar file named: InbMsgFlow and InbMsgFlowOFSRequest.

InbMsgFlow is responsible for adding the header to the PACS or CAMT xml and giving the respective output. This message flow will also form the OFS message and will place the same message in a guard queue, which will be the Inqueue for InbMsgFlowOFSRequest flow.

There is 1 Inqueue and 3 Outqueue for InbMsgFlow. By default the Inqueue name is POR.QUEUE and 1 st Outqueue name for GIRO XML staging response to GIRO is INSTANT.OUT.QUEUE, 2 nd Outqueue name for OFS Request flow is INSTANT.OFS.GUARD.QUEUE and 3 rd Outqueue name for GIRO XML response to StandIN is StandIn.

InbMsgFlowOFSRequest will pick up the message from the guard queue and is responsible to connect to Temenos Transact through the Temenos Transact Outbound adapter and update the PSM.BLOB and PPT.SENTFILEDETAILS application. In case the requirement is not there to update the application, then this message flow can be stopped.

There is 1 Inqueue and 1 Outqueue for InbMsgFlowOFSRequest. By default the Inqueue name is INSTANT.OFS.GUARD.QUEUE and Outqueue name is INSTANT.OFS.RESPONSE.

1. To change it to the user defined queues use the following code in the IBM Integration console:
   • mqsireadbar -b "<<location-of-bar-file>>" –r
2. Make changes in the Properties files of the GIRO_Inbound.

   

mqsiapplybaroverride -b "<<location-of-bar-file>>" -k GIRO_Inbound -p "<<location-of-Inbound-Properties-file>>"

The Outqueue is named GIRO.ADAPTER.GUARD.QUEUE which acts as a Guard queue for GIRO_InboundPolling BAR file 2 nd InQueue.

The Inbound Adapter Polls out NRINST xml messages and stage the xml message in the outQueue, which will be picked up by GIRO_InboundPolling BAR file for further process.

The Outqueue name of GIRO_InboundAdapterPoll BAR file for Inbound Adapter flow and 2 nd Inqueue name of GIRO_InboundPolling BAR file has to be the same.

1. To change it to the user defined queues use the following code in the IBM Integration console:
   • mqsireadbar -b "<<location-of-bar-file>>" –r
2. Make changes in the Properties files of the GIRO_InboundAdapterPoll.

   

mqsiapplybaroverride -b "<<location-of-bar-file>>" -k GIRO_InboundPolling -p "<<location-of-InboundPolling-Properties-file>>"

The Outqueues are named PRIORITY.INSTANT.QUEUE, NONPRIROITY.INSTANT.QUEUE, NRINSTANT.QUEUE by default to get the IF events from TPH.

The Inqueue that acts as destination queue for Instant Payment Raw xml is named INBOUND.IF.EVENT.QUEUE and another InQueue named GIRO.ADAPTER.GUARD.QUEUE which picks up the InboundAdapter IF events from the Guard OutQueue of the GIRO_InboundAdapterPoll bar file.

1. To change it to the user defined queues use the following code in the IBM Integration console:
   • mqsireadbar -b "<<location-of-bar-file>>" –r
2. Make changes in the Properties files of the GIRO_InboundPolling.

mqsiapplybaroverride -b "<<location-of-bar-file>>" -k GIRO_InboundPolling -p "<<location-of-InboundPolling-Properties-file>>".

There are 2 flows in GIRO_Outbound.bar file named: OutbMsgFlow and OutbMsgFlowToJMS.

The OutbMsgFlow is responsible for removing the header data and forming the TPH generic XML and place the same in the Outqueue.

There is 1 Inqueue and 2 outqueue for OutbMsgFlow. First Outqueue is responsible to have PACS.008 xml and second outqueue stage all other PACS and CAMT xml other than PAS.008. By default the Inqueue is named as Giro.Outbound.Inqueue and 1 st Outqueue is named OUTBOUND.GIRO.JMS.QUEUE and 2 nd Outqueue is named T24.TWS.QUEUE.

OutbMsgFlowToJMS is responsible for sending the XML from OutbMsgFlow to JMS Queue.

The Inqueue is named OUTBOUND.GIRO.JMS.QUEUE by default for OutbMsgFlowToJMS.

1. To change it to the user defined queues use the following code in the IBM Integration console:
   • mqsireadbar -b "<<location-of-bar-file>>" –r
2. Make changes in the Properties files of the GIRO_Outbound.

   

mqsiapplybaroverride -b "<<location-of-bar-file>>" -k GIRO_Outbound -p "<<location-of-Outbound-Properties-file>>".

There are 2 flows in GIRO_OutboundStandIN.bar file named: OutbStdInMsgFlow and OutbStdInMsgFlowToJMS.

OutbStdInMsgFlow is responsible for removing the header data and forming the TPH generic XML and place the same in the Outqueue.

There is 1 Inqueue and 2 outqueue for OutbStdInMsgFlow. First Outqueue is responsible to have PACS.008 xml and second outqueue stage all other PACS and CAMT xml other than PAS.008. By default the Inqueue is named as Giro.StandInOutbound.Inqueue and 1 st Outqueue is named STANDINOUTBOUND.GIRO.JMS.QUEUE and 2 nd Outqueue is named STANDIN.T24.TWS.QUEUE.

OutbStdInMsgFlowToJMS is responsible for sending the XML from OutbStdInMsgFlow to JMS Queue.

The Inqueue is named STANDINOUTBOUND.GIRO.JMS.QUEUE by default for OutbMsgFlowToJMS.

1. To change it to the user defined queues use the following code in the IBM Integration console:
   • mqsireadbar -b "<<location-of-bar-file>>" –r
2. Make changes in the Properties files of the GIRO_OutboundStandIN.

   

   mqsiapplybaroverride -b "<<location-of-bar-file>>" -k GIRO_OutboundStandIN - p "<<location-of-Outbound-Properties-file>>"

3. Catch handler mechanism logs the error both in Local user trace and in the local file system. Change the directory and file name properties of the local directory using the commands below.
4. Use the command below to change Outqueue name for ERROR handling response of GIRO_Inbound BAR.
   • mqsiapplybaroverride -b "<<location-of-bar-file>>" -k GIRO _Inbound -m “com.temenos.giro.inb.InbSubFlow_5#Inb.Sflow5.MQOut:1.queueName= <<name-of-user-defined-outqueue>>”
5. Use the command below to change Outqueue name for ERROR handling response of GIRO_Outbound BAR:
   • mqsiapplybaroverride -b "<<location-of-bar-file>>" -k GIRO _Outbound -m “com.temenos.giro.outb.OutbSubFlow_1#Outb.Sflow1.MQut:1.queueName= <<name-of-user-defined-outqueue>>”
   Text added within <<xxxx>> should be replaced with appropriate values as explained.

Placement of Log4j, PPINST_InstantOutwardXML and JPTM JAR file at IIB workpath

1. The Log4j, JPTM and PPINST_InstantOutwardXML JAR files has to be placed at IIB WORKPATH which can be know through the below command in IIB console: mqsireportbroker <<broker-name>>.

   

2. Navigate to the below folder directory in IIB workpath: <<workpath-of-IIB>>\MQSI\config\<<broker-name>>\shared-classes.
3. Place the log4j, PPINST_InstantOutwardXML and JPTM JAR files in the directory.
4. Restart the broker.

Placement of Log4j properties file.

5. The properties file “log4j.properties” needs to be placed at: <<workpath-of-IIB>>\MQSI\common\wsrr.
6. The location of Log file needs to be specified in the “log4j.properties” file.

   

Creation of Broker,Queue Manager, Inqueue and Outqueue.

7. Create a Queue Manager in the Websphere MQ.

   

8. Create a Broker in IIB console windows: mqsicreatebroker “<<Broker Name>>” -i LocalSystem -q <<Queue Manager Name>>.
9. Create local Inqueue and Outqueue in the Websphere MQ.

   

10. Make sure Payment Polling application are not deployed in the Integration so that there is no confusion among the GIRO bar and TPH bar to poll the xml from the EXIT events.
11. Upon successful creation of Integration Node and Queue Manager, Temenos TransactIIB Adapter should be configured at IIB node level (using MQSICHANGEBROKER command to set the .PAR file for that particular broker). Sample command given below to setup Temenos TransactIIB adapter for runtime.
    • Mqsichangebroker <<Integration_node_name>> -l “<<path-where-par-file>>”

1. Kindly use the previous GIRO_Inbound.bar and GIRO_Outbound.bar file having all the previous properties changes made.
2. Name of L1 Outbound XSLT’s:

   

3. Name of L1 Inbound XSLT’s:

   

4. Name of L1 OutboundStandIN XSLT’s:

   

5. Open the Bar file in archive and navigate to location as shown below and only place all the XSLT as shown in 3 point in the said location:

   <<path-tobar-file>>\GIRO_InboundV01.bar\GIRO_Inbound.appzip\

   

6. Open the Bar file in archive and navigate to location as shown below and only place all the XSLT as shown in 2 point in the said location:

   <<path-tobar-file>>\GIRO_OutboundV01.bar\GIRO_Outbound.appzip\

   

7. Replace the pacs XSLT file in the location above with the XSLT file received from the L1 as mentioned in 2 and 3 points.