Modifying the parameters of the deployed instance of your FTM offering

You can update the configuration parameters for an instance of your FTM offering even after it is deployed.

Before you enable security, make sure that the required certificates are created and configured in the Red Hat® OpenShift® secret for FTM. For more information, see Create certificates.

The following instructions use the Red Hat OpenShift Container Platform user interface to modify the configuration.
  1. Log in as an administrator to the cluster that you deployed your FTM offering to.
  2. View the installed operators on the Red Hat OpenShift Container Platform and select the FTM operator.
  3. Click the tab for the operator API for the FTM offering. The operator API names are shown in the following list.
    • FTM
  4. Use the three vertical dots menu to edit the instance.
  5. Update the configuration by changing the YAML in the editor.
  6. Click Save.
  7. Use the Red Hat OpenShift Container Platform user interface or the Red Hat OpenShift Container Platform command-line interface to confirm that the instance was redeployed successfully. You might need to wait several minutes for all the pods to be running.
If the FTM API operator and the FTM offering are installed in different namespaces, the FTM API operator will not be listed under the list of installed operators. In this case, you need to follow the steps that are shown in the following list.
  1. Go to Home > API Explorer and filter by FTM.
  2. Click the FTM kind and click the Instances tab.
  3. Click Create FTM.

For more information about the parameters that you can use for your FTM deployment, see Configuration parameters for the FTM offerings.

Removing the deployed offering from the FTM operator

Update the FTM custom resource to remove the instance of your deployed offering.

After the instance of your deployed offering is removed, the FTM operator reconciles its resources except the IBM® App Connect resource. The customization added to the IBM App Connect resource is retained. But the IBM App Connect simulator integration runtimes can still fail because it contains references of the simulator bar files of the offering that is removed.

You can prevent IBM App Connect simulator integration runtimes from failing by using one of the following steps.
  • Remove the offering-specific simulator bar file from the common-sim integration runtime definition.
  • Delete the common-sim integration runtime so that the FTM operator re-creates it with the offering-specific simulator bar file. This step deletes any customization that is added to the integration runtime.