Creating the runtime directory structure for the broker
Table 1 lists
the directories required on each runtime system, their default values
and how you can customize them.
| Directory Name | Default directory | Customization possibility | Description |
|---|---|---|---|
| cache directory | /var/ftm/swift/v324/run/cache |
Set by the dniruntime variable in dni.conf with the appended subdirectory /cache. | Used to store temporary files. |
| trace directory | /var/ftm/swift/v324/run/trace |
Set by the dnitrace variable in dni.conf. | Used to store trace files. |
| xfsm directory | /var/ftm/swift/v324/run/trace/xfsm |
Set by the dnitrace variable in dni.conf with the appended subdirectory /xfsm. | Used to store trace files written by external SFD functions. |
| fsm instance directory | /var/ftm/swift/v324/run/fsm |
Set by the FSMInstanceDir attribute
of the DnfLT CO of the LT.Note: If more than one FTM SWIFT instance
runs on
the same system, make sure each uses a different FSM instance
directory.
|
Used to store temporary files, such as shared memory handles and trace files, written by internal SFD functions. |
| bap directory | /var/ftm/swift/v324/run/bap |
The directory specified by the DNI_BAP_PATH environment variable in the user profile (for example dniprofile) with the appended subdirectory /bap. | Used by the Broker Administration Program (BAP) to store information about deployed message flows for being able to maintain them later. |
To create the required runtime directories and give read
and write access to the group dnilpp, ask the root user to issue
the following commands:
mkdir run_mount_point/cache
mkdir run_mount_point/bap
mkdir run_mount_point/trace
mkdir run_mount_point/trace/xfsm
mkdir run_mount_point/fsm
chgrp -R dnilpp run_mount_point
chmod -R 770 run_mount_pointrun_mount_point
represents the name of the runtime file system mount point you chose. The default is /var/ftm/swift/v324/run.