All Funds Bank (AFB) Customer Onboarding Installation Guide
This document aims at explaining the installation procedures required to install this AFB customer onboarding pack in Mule. The scope of the document is to cover the release mechanism of the AFB customer onboarding.
System Requirements
The following are the pre-requisites for installing the package:
- Mule-enterprise-standalone server.
- Temenos Transact Mule adapter, version exactly as the Temenos Transact version.
General Considerations
Kindly deploy the package during the upgrade to 202102 and above Temenos Transact releases.
Contents of the Package
The pack contains the following Mule components:
- Afb_polling.7zip.
- Customer_onbaording.7zip.
- AFB_XSLT (directory with all XSL files).
- AFB.properties.
Kindly replace or add the below mentioned files.
- Xslt files:
- PT_INTERNAL_TRANSFER_VALIDATION_en.xsl.
- ST_EXTERNAL_TRANSFER_VALIDATION_en.xsl.
- SOO_ORDER_ID_VALIDATION_en.xsl.
- TR_TRANSFER_IN.xsl.
- SOO_INTERNAL_TRASPASO.xsl.
- PT_CONTRACT_ID_ADD.xsl.
- PT_TO_CONTRACT_ID_ADD.xsl.
- ST_CONTRACT_ID_ADD.xsl.
- TR_CONTRACT_ID_ADD.xsl.
- SOO_IT_CONTRACT_ID_ADD.xsl.
- SOO_CONTRACT_ID_ADD.xsl.
- SOO_JOINTHOLDER_CLIENT_ID_VALIDATION.xsl.
- CUSTOMER_UPDATION_VALIDATION.xsl.
- PT_TO_JOINTHOLDER_CLIENT_ID_VALIDATION.xsl.
- PT_JOINTHOLDER_CLIENT_ID_VALIDATION.xsl.
- SOO_IT_JOINTHOLDER_CLIENT_ID_VALIDATION.xsl.
- ST_JOINTHOLDER_CLIENT_ID_VALIDATION.xsl.
- TR_JOINTHOLDER_CLIENT_ID_VALIDATION.xsl.
- Customer Onboarding pack:
- afb_customer_onboarding-1.0.0.zip.
- Order Updation pack:
- afb_orderupdation-1.0.0.zip.
- AFB IF Events Package:
- 1_IF_AFBCustomerOnboardingIFExitPoints_1_JAVA_<release_version>.jar.
Steps for Installing the Package
Follow the steps below to install the package.
Pre-Installation Steps
- Create the property file for the fix interface listing the Temenos Transact adapter configuration, AFB API path and xslt path.
- Place all the xslt file in the path that configured in the AFB Property file.
- Prepare the document priority list to validate the customer document and mention the path of the document priority in the AFB Property file. It is mandatory to have this document list to validate the clients document.
- To create the JMS queue add queue details in the standalone-UTP.
- The queue details are listed below.
<jms-queue name="t24CustomerOnboardingQueue" entries="queue/t24CustomerOnboardingQueue java:jboss/exported/jms/queue/t24CustomerOnboardingQueue"/>
<jms-queue name="t24OrderMgmtQueue" entries="queue/t24OrderMgmtQueue java:jboss/exported/jms/queue/t24OrderMgmtQueue"/>
<jms-queue name="t24SpanishTrasQueue" entries="queue/t24SpanishTrasQueue java:jboss/exported/jms/queue/t24SpanishTrasQueue"/>
- Deploy the Mule pack for afb in the server.
- Make sure that Mule standalone server starts without any deployment error.
Installation Steps
Follow the steps below to install the package.
Transfer the Mule File to the Area
- Place the mule 7zip file in the Mule server apps path
\mule-enterprise-standalone-3.9.0\apps
- After copying the zip file to the app folder, start the server with the AFBHome path. This AFB home path is to pick up the fix property file.
- Use the command below to start.
mule –M-DAFBHome=”Path of the property file
After starting the server, mule pack should get deployed successfully.
Upgrade to the 202010 Release
Deploy the package below when upgrading to the 202010 release.
The package contains the following Mule components:
- EVENTS: 1_IF_AFB_1_JAVA_1.0.
Steps for Installing the Package
Follow the steps below to install the package.
Pre-Installation Steps
- To create the new JMS AFBMarketingOrderQueue queue add queue details in the Jboss Standalone file for the Security Master update.
- The queue details are below:
<jms-queue name="AFBMarketingOrderQueue" entries="queue/AFBMarketingOrderQueue java:jboss/exported/AFBMarketingOrderQueue"/>
- Create the above queues in the queue server as well.
Deploying the PackageBefore starting the deployment process, ensure that the application, version, component aervice and the TSA service that is used in the events in the package, are available in the destination Temenos Transact environment.
Follow the steps below to deploy the package.
- Copy the package to the package folder, under the run directory in Temenos Transact. Here it is UD:
The run directory is the value mentioned in the temn.tafj.runtime.directory.current property of TAFJ configuration file.
- Set the run directory as T24_Home as displayed below:
- Run the T24PackageInstaller command:
- The successful execution of the command will result in the message below.
Success:Update 1_IF_AFB_1_JAVA_1.0 Successfully copied the libraries and binaries.
- The same can be verified by viewing the record in T24.MODEL.PACKAGES application.
- The next step is to execute the packageDataInstaller command to get the exit point and flows created in Temenos Transact.
- Once the above command is successful executed, the same can be verified by checking the T24.MODEL.PACKAGE record, where the DATA.RELEASED has to be set to Y:
- The exit point and the flow record also can be verified for the existence.
Once the deploying the AFB events is done, the following Temenos Transact configurations have to be done:
- For the exit point complex join, it needed to call the Temenos Transact routine. This routine name should be configured in the application IF.CALLBACK.IMPL.CATALOG.
- To poll the data from IF.EVENTS.INTERFACE.TABLE to AFB queue, the following configuration are used.
- Set the INTEGRATION.SERVICE to Auto mode and TSM to Start. This is the service that is used to poll out the IF events data to the corresponding queue.
Transfer the Mule file to the area.
In this topic