Configuring the instance for custom mount points

If you chose not to use the default mount points, configure your instance to be able to use the custom mount points:

  1. If your customization file system is not /var/ftmswift_v324/cus, adapt the directory names in all examples shown in the FTM SWIFT documentation to your needs, for example, when preparing the customization initialization file as described in Preparing a CDP initialization file.
  2. If your runtime file system is not /var/ftm/swift/v324/run:
    1. Copy the sample dni.conf file to your home directory, and give read access to group dnilpp.
      For example: 
      cp inst_dir/run/samples/dni.conf ~/dni.conf
chmod 750 ~/dni.conf 
chgrp dnilpp ~/dni.conf
    2. In the copy of dni.conf, set the variables dnitrace and dniruntime to the appropriate directories.
      For example, if you choose /tmp/ftmswift_v324/run as a mount point, edit the corresponding lines so that it looks like this: 
      # Set the directory to store FTM SWIFT trace information
dnitrace /tmp/ftmswift_v324/run/trace

# Set the directory to store FTM SWIFT runtime and cache data
dniruntime /tmp/ftmswift_v324/run
      Note:
      • If an FTM SWIFT component cannot read or parse the dni.conf file, it stores runtime and trace data in default subdirectories of the following directory: 
        /var/ftm/swift/v324/run
      • If the component cannot access a directory specified in the dni.conf file, the syslog contains messages related to the problem.
      • If dniruntime is set incorrectly, FTM SWIFT cannot work properly.
      • If dnitrace is set incorrectly, FTM SWIFT writes trace information to the directory /var/tmp.
    3. Ask the root user to copy the modified dni.conf file to a directory to which the group dnilpp has read access.
      For example:
      • To copy the file to the default configuration directory that applies to all instances, issue the following command: 
        cp -p ~/dni.conf /etc/dni.conf
      • To copy the file to an instance-specific configuration directory, issue the following command: 
        cp -p ~/dni.conf /var/dni/DNIvINST/dni.conf
        where DNIvINST represents the instance name chosen in the planning phase.
    4. If you chose an instance-specific configuration directory in step 2.c that is not the directory /etc, you must specify your directory in the environment variable DNI_CONFPATH. This enables the runtime components of the FTM SWIFT instance to locate the dni.conf file. How to do this is described in Preparing a message broker and Preparing a user profile for each runtime system on which a broker runs.
    5. Specify your runtime file system mount point in the directory names used in: