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 solutions use both of the following storage categories.

File storage: The FTM solutions 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 solution 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 solution. This instance name is indicated by InstanceName in the table.

Table 1. Mapping the persistent volumes to the network storage directory
Persistent volume name	Network storage directory name
pv-ftm-application	`StorageMountPath/InstanceName/`applications
pv-ftm-debug-data	`StorageMountPath/InstanceName/`debug-data

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