ClearBank API Gateway Installation Guide

1. Extract the zip file.
2. In the start.cmd file for Windows and start.sh file for Linux, set the following details:
   • JAVA_HOME variable: points to java jdk location. E.g: C:\java\jdk11\jre
   • PROVIDER variable: contains the queue broker name. It accepts the following values: jboss, ibmmq, activemq, amazonmq, weblogic.
   • PORT variable: can be any available port number to be used by the package.
   • XSLPATH: path of the XSLT files for the current instance/File type.

   If the above values are not set, then the following values will be defaulted,

   • PROVIDER=activemq,
   • PORT=9999,
   • XSLPATH=%CD%\xsl\.
3. In Root path of the extracted package kindly change the application.properties as required.

   Do not change the xslt.path here.

   A sample setup is given below:

   

4. The Inqueue name is named TPHPaymentQueue by default at the time of development. This queue message will be picked up by ClearBank_InboundPayment WAR file to sent the same to ClearBank.
5. To change the default queue name and Clearbank Request URL, the application.properties file of the UKCLBK_ClearBankFpsOutbound.zip can be modified.

1. Extract the zip file.
2. In the start.cmd file for Windows and start.sh file for Linux, set the following details.
   • JAVA_HOME variable: points to java jdk location. E.g: C:\java\jdk11\jre.
   • PROVIDER variable: contains the queue broker name. It accepts the following values: jboss, ibmmq, activemq, amazonmq, weblogic.
   • PORT variable: can be any available port number to be used by the package.
   • XSLPATH: path of the XSLT files for the current instance/File type.

   If the above values are not set, then the following values will be defaulted,

   • PROVIDER=jboss,
   • PORT=9999,
   • XSLPATH=%CD%\xsl\.
3. In Root path of the extracted package kindly change the application.properties as required.

   Do not change the xslt.path here.

4. A sample setup is given below.

   

5. The Inqueue name is named T24AccountQueue by default, since it was used at the time of development of POC. This queue message will be picked up by ClearBank_InboundAccount WAR file to sent the same to ClearBank.
6. To change the default queue name and Clearbank Request URL, the application.properties file of the UKCLBK_ClearBankFpsOutbound.zip can be modified.

Design time configuration steps for ClearBank_InboundAccount are provided below.

1. A new account application version needs to be created.
2. The Exit points must be created for the newly created version.
3. The Temenos Transact Internal JMS queue has to be defined in the IF.INTEGRATION.SERVICE.PARAM application.
4. The queue has to be configured in standalone-utp.xml of the Temenos Transact area.
5. Once a new record is committed the Temenos Transact internal JMS queue will get populated with the necessary account details, which will be processed by Exposed API.

The deployment steps are provided below.

To Start the Service

1. Open a command window in the extracted package location, and execute the start.cmd command.

   Syntax:

   start.cmd [ -p provider ] [ -po port ] [ -xp xslPath ]

   Example: Start.cmd –p jboss –po 9999 -xp [path]

2. Logs will be generated in the log folder for monitoring purpose. E.g. : …\package\log\ console_[providername]_[datetime].txt

To Stop the Service

1. Open a command window in the extracted package location, and execute the start.cmd command.

   Syntax:

   stop.cmd

Special Instructions

1. Commands to generate CSR and PFX with Public and private key that can be used in simulation environment.

   # generate a dummy certificate authority

   openssl genrsa -out CA.key 2048

   openssl req -new -x509 -key CA.key -out CA.crt -subj /CN=CA

   # generate the simulation key and CSR (CSR it the thing you need to upload to ClearBank, so they will know about your public key)

   openssl genrsa -out SIM.key 2048

   openssl req -new -sha256 -key SIM.key -out SIM.csr -subj /CN=SIM

   # Create CRT and PFX files

   openssl x509 -req -in SIM.csr -CA CA.crt -CAkey CA.key -CAcreateserial -out SIM.crt

   openssl pkcs12 -export -out SIM.pfx -inkey SIM.key -in SIM.crt

2. Import the CA certificate provided by Security team in PFX to Keystore JKS format for HTTPS connectivity.

   # Generate PEM file from PFX file

   openssl pkcs12 -in mypfxfile.pfx -out mypemfile.pem

   #Generate P12 format file from PEM file

   openssl pkcs12 -export -in mypemfile.pem -out mykeystore.p12 -name "MyCert"

   # Check the certificate inside the P12 file

   keytool -v -list -keystore mykeystore.p12 -storetype pkcs12

   # Import the P12 and certifictaes in Keystore file

   keytool -importkeystore -srckeystore mykeystore.p12 -destkeystore clientcert.jks -srcstoretype pkcs12 -deststoretype JKS

Deployment in Linux Environment

1. Convert your extracted Camel pack to TAR file. (Right click > 7 zip > Add to archive > archive format "tar")
2. Move this tar file to the linux area using winscp. Transfer settings should be 'binary'.
3. Extract this tar file in Linux area using tera term.
4. Command: tar -xvf <package name>.tar
5. Then run start.sh script .

Kindly ensure that start.sh has 'LF' as line separator.