MFT configuration options on Multiplatforms
Managed File Transfer provides a set of properties files that contain key information about your setup and are required for operation. These properties files are in the configuration directory that you defined when you installed the product.
We can have multiple sets of configuration options, each set of configuration options contains a set of directories and properties files. The values defined in these properties files are used as the default parameters for all Managed File Transfer commands, unless you explicitly specify a different value on the command line.
To change the default set of configuration options that we are using we can use the fteChangeDefaultConfigurationOptions command. To change the set of configuration options that we are using for an individual command we can use the -p parameter with any Managed File Transfer command.
The name of a set of configuration options is the name of the coordination queue manager, and it is recommended that this is not changed. However, it is possible to change the name of a set of configuration options but we must change the name of the config and logs directories. In the following examples, the name of the set of configuration options is represented as coordination_qmgr_name.
Configuration options directory structure
When you configure the product, directories and properties files are created in the following structure in the configuration directory. We can also change these directories and properties files with the following commands: fteSetupCoordination, fteSetupCommands, fteChangeDefaultConfiguration, and fteCreateAgent.MQ_DATA_PATH/mqft/ config/ coordination_qmgr_name/ coordination.properties command.properties agents/ agent_name/ agent.properties exits loggers/ logger_name logger.properties installations/ installation_name/ installation.propertiesThe coordination_qmgr_name directory is a configuration options directory. There can be more than one configuration options directory in the configuration directory. The agent_name directory is an agent directory. In addition to containing the agent.properties file, this directory contains the exits directory, which is the default location for user exit routines and various XML files generated by the fteCreateBridgeAgent and fteCreateCDAgent commands. There can be more than one agent directory in the agents directory of a set of configuration options.
Properties files
- installation.properties
- The installation.properties file specifies the name of our default set of configuration options. This entry points Managed File Transfer to a structured set of directories and property files that contain the configuration to use. Typically the name of a set of configuration options is the name of the associated coordination queue manager. For more information about the installation.properties file, see The MFT installation.properties file.
- coordination.properties
- The coordination.properties file specifies the connection details to the coordination queue manager. Because several Managed File Transfer installations might share the same coordination queue manager, we can use a symbolic link to a common coordination.properties file on a shared drive. For more information about the coordination.properties file, see The MFT coordination.properties file.
- command.properties
- The MFT command.properties file specifies the command queue manager to connect to when we issue commands and the information that Managed File Transfer requires to contact that queue manager. For more information about the command.properties file, see The MFT command.properties file.
- agent.properties
- Each Managed File Transfer Agent has its own properties file, agent.properties, that must contain the information that an agent uses to connect to its queue manager. The agent.properties file can also contain properties that alter the behavior of the agent. For more information about the agent.properties file, see The MFT agent.properties file.
- logger.properties
- The logger.properties file specifies the configuration properties for the loggers. For more information about the logger.properties file, see MFT logger configuration properties.
Properties files and code pages
The content of all the Managed File Transfer properties files must remain in US English because of a limitation of Java. If you edit properties files on a non-US English system, we must use Unicode escape sequences. Parent topic: Configure Managed File TransferRelated information
- SSL properties for MFT
- Java system properties for MFT
- fteChangeDefaultConfigurationOptions
- fteSetupCommands: create the MFT command.properties file
- fteSetupCoordination
- fteCreateAgent