Deploy the instance of your FTM offering

Use the Red Hat® OpenShift® Container Platform to create and configure the Red Hat OpenShift instance of your FTM offering.

The following instructions show a way that the cluster administrator can use the Red Hat OpenShift Container Platform user interface to create the instance for your FTM offering.

Log in as an administrator to the cluster that you are deploying your FTM offering to.
View the installed operators on the Red Hat OpenShift Container Platform and select the FTM operator. If you installed the IBM Financial Transaction Manager operator into a specific namespace on the cluster instead of into all namespaces, it might not appear in this list of installed operators. If the IBM Financial Transaction Manager operator is installed in a different namespace than the one where the instance of FTM is being deployed, use the following steps to find the operator.
1. Go to the Red Hat OpenShift Container Platform API Explorer.
2. Search for the FTM API by entering FTM in the filter by kind field.
3. Click FTM in the list of kinds. The Create FTM option is on the Instances tab instead of the FTM tab.
Select FTM or Instances. Then, click Create FTM to create the instance that corresponds to the FTM offering that you want to deploy.
Configure the instance for your FTM offering. To configure and create the instance, you can use Form view to show some of the configuration parameters on the user interface. Or you can use YAML view to directly edit the YAML for the configuration. The YAML view provides you with more control over the configuration of the FTM instance. The following list shows some of the parameters that you need to provide values for. Unless otherwise indicated, the parameters are configured in the spec structure in the YAML.
- Provide the name of this instance in the name parameter. The instance name must be unique and match the instance name that was used when the persistent volumes and network storage was configured. The name parameter is not in the spec structure in the YAML.
- Indicate that you accept the license. If you do not accept the license, you cannot create the instance.
- Table 1 shows some parameters that you likely want to configure for the instance at deployment time
- Configure any other parameters that you need for the instance. The configuration parameters that you can use are described in Configuration parameters for the FTM offerings. You can also change the configuration parameters after the instance is created. For more information, see Modifying the parameters of the deployed instance of your FTM offering.
Click Create.
Confirm that the instance was created successfully. View the installed operators on the Red Hat OpenShift Container Platform user interface and select the operator that you deployed. Click All Instances to display the instances for the operator. Verify that the instance name that you just created is shown.

The following table shows some more information about parameters that you likely want to configure for the instance at deployment time. For more information about these configuration parameters, see Configuration parameters for the FTM offerings.

Table 1. FTM configuration for the instance at deployment
Type of configuration	Description
Configure your security, such as adding certificates and securing communication.	Set the TLS parameters for the operator to indicate whether TLS and mTLS communication is enabled for your middleware and FTM. For more information, see Configuration parameters for the FTM offerings.
Configure the name and password for the application secret that you created for your FTM offering.	The application secret is used for your application credentials, such as for a database. In the config.security.password.valueFrom.secretKeyRef parameter, enter the name of the secret and the name of the key to use for the password. If you did not specify a password in the secret, the password defaults to a randomized string that is generated and stored in a secret.
Configure the name of the secret that contains the certificate, key, and certificate authority.	The certificate must be named tls.crt, the key tls.key, and the certificate authority ca.crt. Enter the name of the secret for the certificate in the config.security.certificate parameter.
Configure the values of the storage parameters.	The storage parameter accepts keys that indicate how the operator handles storage configurations. The storage parameter keys map to the following functions or components. Default. When the key for default is specified, the operator creates any missing storage configurations by using its default configuration. Application Debug Gateway IBM® App Connect Enterprise
Configure the config.database group parameters for your database.	The FTM containers connect to the remote database based on the details that are provided in this group. In the database group parameters, specify the connection information for the Db2® hostname and port based on the Db2 operator or external database. If you used the Db2 operator, it creates services of type ClusterIP and NodePort. The service name and IP address that is associated with port `50000/5000*` can be used to configure the hostname and port in the group parameters. If Db2U is deployed in a different namespace than FTM, but is in the same Red Hat OpenShift Container Platform cluster, you need to use the `<db2u-service-name>.<db2u-namespace>` format. This format is needed so that the pods in the FTM namespace can resolve the Db2U service name. If you are using an external database, you must disable automatic configuration for the external database. Set the autoConfig.enable parameter for the specific external database to false.
Configure egress access.	If you use egress rules in the custom resource (CR) to set up egress access, you must reconfigure them every time that you deploy your FTM offering. For example, the connection to an external database is lost if you do not add its egress rules to the custom resource every time you deploy. If you do not want to constantly reconfigure the external connections for your FTM offering, you can define and use your own network policy. For more information about using egress rules, see Configuring the rules for egress access.
Configure whether the operator automatically configures IBM MQ.	Set the config.mq.enableConfigJob to true or false to indicate whether you want the FTM operator to configure IBM MQ.
Configure whether any a reference implementations are deployed.	Use the config.instance.referenceImplementation parameter to indicate which reference implementations to deploy. For more information, see Deploy the FTM reference implementation.