AFB Polling Installation Guide
This document aims at explaining the installation procedures required to install the containerized package for AFB Polling in both cloud and on-premise deployment. The scope of the document is to cover the deployment of the containerized package for payment message processing for AFB Polling in cloud and on-premise.
The terminology used is as follows:
- UTP: Unified Temenos Platform.
- MQ: Message Queue.
System Requirements
The following are the pre-requisites for installing this package.
For the On-Prem Environment:
- Temenos Payment Hub.
- JMS queue / ActiveMQ.
- JDK 21.
For the Cloud Environment:
- Temenos Payment Hub.
- ActiveMQ.
- Helm.
- Kubernetes.
Pre-Installation Steps
The steps for pre-installing the package are provided below.
The pre-deployment steps for Cloud and On-Prem deployments are the following.
- Unzip the package AfbPolling and place it in the required folder.
- The contents of the package will be as in the screenshot below.

- Edit the system environment variables and click on Environment Variables button.

- Click on the New button to add a new system variable.

- Set the JAVA_HOME in system variables as per below.

- The following queues have to be created in the environment:
- t24IFInboundqueue,
- T24CustomerOnboarding,
- t24OrderUpdate,
- t24AFBPollingErrorQueue.
These queues have to be configured in Temenos Transact in the following path ...\jboss\standalone\configuration\standalone-utp.xml if the environment has JMS queues.
For ActiveMq, the queues can be created from the Active Mq Console.
The application.properties file available in the package has be configured as per the instructions below.
-
Configure the following queues under the section T24 Queue Configurations as displayed below.
- t24IFInboundqueue - Inqueue from Temenos Transact,
- T24CustomerOnboarding – OutQueue to route message to the customer onboarding flow,
- t24OrderUpdate – OutQueue to route the message to the order update flow,
- t24AFBPollingErrorQueue – queue to error message flow.
- The log4j2.properties file will be part of the package in the root directory.


- The Jasypt configurations are displayed below.

The values.yaml Cloud deployment configurations are described below.
- Make sure the queues below are present in the environment.

- Log4j2.properties and Jasypt configurations are captured in the values.yaml file as displayed below.


- Update the COMPANY_BIC with Temenos TransactCompany’s BIC Code.

- Update the values.yaml file with the activemq connection details as required by referring the sample provided below.

- Update the values.yaml file for increasing the instance count (by default it is one).

- Mention the range of memory and cores.

- Update the templates/afbzero-deployment.yaml with the image name as required in the sample below.

- Update the templates/afbzero-deployment.yaml file to configure the container instance of the mount location.

- The application port is 8060 and is configured in the values.yaml files. The ports and IP configuration provided in the values.yaml file is referred in the network-policy.yaml, service.yaml and deployment.yaml.
- Load balancer source IP range is referred from sourceIP_ranges in the values.yaml file.

Installation Steps
The steps for installing the package are provided below.
- Unzip the zip package into a folder AfbPolling.
- Configure the java home path in AfbPolling/start.cmd.


- Run the adapter by double clicking the start.cmd or use a console to run the following command.
start.cmd -p <application_server> -po <port>
- Terminate the adapter by double clicking the stop.cmd or run the following command.
stop.cmd
- Download the Afb Polling zip file and extract it in a folder in the destination system.
- Check if any images exist (using the docker images command) in the destination system. If so remove them using,
- docker images,
- docker rm <image id> command.
- Locate the Dockerfile folder and open the command prompt to execute the following command. This will load the images into docker.
Load Images Syntax:
docker build -t <repository>:<tag>
Eg: afb image
docker build -t afb-polling:dev
- For docker deployment only: Start a local docker registry server using docker image that will be used as a container registry hosting all the afb images deployment.
Start Local Registry Eg: docker run -d -p 5000:5000 --restart=always --name registry registry:2

- Once the registry is started, it needs to tag and push the images that were loaded earlier. Syntax and samples for tag and push are mentioned below.
Docker tag images Syntax:
docker tag <Repository> <local registry host>:<local registry port>/<repository>:<tag>
where,
Repository – afb-polling
local registry host – localhost
local registry port – 5000
tag – dev
Eg: docker tag afb-polling:dev localhost:5000/afb-polling:dev
Docker push images Syntax:
docker push <local registry port>/<repository>:<tag>
Eg: docker push localhost:5000/afb-polling:dev

- Navigate to the helm folder and start afb-polling services using the below command.
Start afb-polling services Syntax:
helm install -name <<image name>> . -n <<image namespace>> --create- namespace
Eg: helm install -name afb-polling . -n afb-polling --create-namespace

- Check if the services are up using below command.
Get pods Syntax:
Kubectl describe pods -n <<image namespace name>>
Eg: kubectl describe pods -n afb-polling
- If the application is running, POD log would be generated with the keyword 'ACCEPTING_TRAFFIC'.
- To uninstall the afb service use the command below.
helm uninstall <<image name>> -n <<namespace name>>
Eg: helm uninstall afb-polling -n afb-polling
Special Instructions
In case of Linux environment:
- Kindly ensure that the start.sh has 'LF' as line separator.
- To start the adapter, run the following command:
sh start.sh -p <provider> -po <port>
- To terminate the adapter, run the following command:
sh stop.sh
In this topic