Create the network storage directory structure

The cluster administrator needs to set up persistent volumes and map them to a network storage directory structure. This task is needed only if you are using static storage provisioning.

The FTM offerings use both of the following storage categories.
File storage
The FTM offerings use file-storage-based persistent volumes that are shared among the FTM containers. These persistent volumes are used to load data, such as user exits. This storage is configured in the FTM custom resource in the spec.storage section.
Block storage
Block storage persistent volumes are created by the dynamic persistent volume provisioning storage class. The block storage persistent volumes are internal and are shared with a single container or pod. Use block storage for IBM® MQ if it is deployed with FTM.

If the network storage persistent volumes do not exist, create them now. If you are deploying the FTM offering in a multiple deployment scenario, the persistent volumes must be shared. Also map the persistent volumes to the network storage directory structure. The following table shows the mapping between the persistent volumes and the directory structure. The names include the name that you are going to give the instance when you deploy the operator for your FTM offering. This instance name is indicated by <ftm-instance> in the table.

Table 1. Mapping the persistent volumes to the network storage directory
Persistent volume name Network storage directory name FTM offerings that use the persistent volume
pv-ftm-ace-workflows-<ftm-instance> StorageMountPath/<ftm-instance>/ace-workflows
  • FTM
  • T2
pv-ftm-application StorageMountPath/<ftm-instance>/applications
  • FTM
  • Check
  • T2
pv-ftm-debug-data StorageMountPath/<ftm-instance>/debug-data
  • FTM
  • Check
  • T2
pv-ftm-gwy-runtime-processing StorageMountPath/<ftm-instance>/applications/gateway-server/runtime-processing
  • Check
  • T2
pv-ftm-image-data StorageMountPath/<ftm-instance>/image-data
  • Check
  • T2
pv-ftm-artifact StorageMountPath/<ftm-instance>/artifact
  • FTM
  • Check
  • T2

If you want, the persistent volumes and NFS directory structure can be created by the operator when the instance for your FTM offering is created. For more information about using this method, see Deploy the instance of your FTM offering.

If you are using NFS V4, the artifacts container for your FTM offering has a sample script and persistent volume template YAML file that you can use to help you set up the NFS V4 directory structure. For more information about how to use these artifacts to create the persistent volumes in the previous table, see Run the Network File System (NFS) Version 4 directory structure setup script and template.