Reference information

The following topics provide reference information for Financial Transaction Manager for Red Hat® OpenShift®.

Persistent storage overview
Persistent volumes are used to store persistent data for pods that need to maintain and share the state between multiple instances. They are also used to share files between two or more pods.
Provide external access to FTM services in Red Hat OpenShift
You might have a program that runs externally to Red Hat OpenShift and needs to access an API that is provided by one of the FTM components.
Update the FTM Red Hat OpenShift routes for load balancing in a production environment
Multiple roles of Business Rules Server
Red Hat OpenShift Container Platform roles in FTM
Red Hat OpenShift Container Platform includes a set of default cluster roles that you can bind to users and groups in FTM.
Readiness and liveness probes for doing health checks in FTM
FTM has startup, readiness, and liveness probes that help monitor the health of your Red Hat OpenShift deployment.
Install and configure an external IBM MQ for FTM
Connect an RMI client to the Transaction Server from outside the cluster
Administering Db2U
The following links provide more information about how to administer and use Db2U on Red Hat OpenShift.
SFTP server deployment
Single sign-on integration
You can create a directory on a persistent volume if you need to keep any configuration files for doing single sign-on integration.
Configuring termination grace periods for the FTM pods
You can configure the pod termination grace period in the FTM custom resource (CR). The default termination grace period is used for the FTM pods if you do not configure a grace period.
Configuring HorizontalPodAutoscaler Target Average Utilization Limits
You can configure the HorizontalPodAutoscaler (HPA) target average utilization limits in the FTM custom resource (CR). This field is optional. If you do not configure it, the default utilization limits are used.
Configuring FTM pod metadata
You can configure FTM pod metadata in the FTM custom resource (CR). The metadata.annotations and metadata.labels lists are optional and can be set to customize pod metadata.
Configuring FTM routes
You can configure the FTM routes in the FTM custom resource (CR). Set the networking.routes[] parameter list to customize the route properties. This list is not mandatory.
Configuring and creating IBM App Connect Enterprise integration runtimes
You can configure and create new IBM® App Connect Enterprise integration runtimes in the FTM custom resource (CR).

Parent topic: Reference architecture and planning