See information about the latest product version
Preparing the environment for WebSphere MQ File Transfer Edition nodes
Prepare the file system and queue managers, and determine the name of the broker agent.
Preparing the file system
- workpath/common/FTE
Preparing the queue manager
WebSphere Message Broker tries to create all the required artifacts on the queue manager for the agent, and the coordination queue manager, if appropriate. It might not be possible to create all artifacts, due to the configuration of your machine, or permissions. If it fails to create them, or you want to create them yourself in advance, see Scripts to create artifacts required for WebSphere MQ File Transfer Edition.
Setting the coordination queue manager
- If the broker's queue manager is being used as the coordination queue manager, the broker configures it as a coordination queue manager.
- If you are using a different queue manager as the coordination queue manager, refer to the WebSphere File Transfer Edition Information Center for details of how to configure it as a coordination queue manager.
- Ensures that the correct queue manager is used when the agent is created.
- Makes the agent permanent. If a coordination queue manager has been defined, the agent is deleted only after you undefine the coordination queue manager (for example, by setting it to an empty string), and restart the execution group.
The following state diagram illustrates how the presence of nodes and a defined coordination queue manager affect the state of the agent.

Use one of the following methods to set the coordination queue manager.
Naming execution groups
- Uppercase A-Z
- Lowercase a-z (but there are restrictions on the use of lowercase
letters for z/OS® console support)
On systems using EBCDIC Katakana you cannot use lowercase characters.
- Numerics 0-9
- Period (.)
- Forward slash (/)
- Underscore (_)
- Percent sign (%)
Determining the agent name
- The broker name is 12 characters or fewer (or at least unique in the first 12 characters).
- The execution group names are 15 characters or fewer (or at least unique in the first 15 characters).
- The broker and execution groups do not contain any characters that are invalid for queue names.
- The broker.executiongroup tuples are all unique, even if case is ignored.