IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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
Preparing the queue manager
Setting the coordination queue manager
Naming integration servers
Determining the agent name

Preparing the file system

IBM Integration Bus uses a location in its work path to store transfers to remote agents. It uses another location as the default directory for received files. The high-level directory path for both locations is:

workpath/common/FTE

Ensure that enough space is available here for files that you will transfer to and from the broker by WebSphere MQ File Transfer Edition.

Preparing the queue manager

IBM Integration Bus 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

When a message flow that contains a WebSphere MQ File Transfer Edition node is deployed to an integration server, an agent is automatically created and started in that integration server. By default, the agent uses the broker's local queue manager as 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 product documentation for details of how to configure it as a coordination queue manager.

Unless you have previously defined the coordination queue manager, the agent is temporary; it is deleted when the flow is undeployed or the broker is stopped. This behavior is acceptable in a test environment. However, for production, the administrator must specify the coordination queue manager for the integration server. Specifying 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 integration server.

A warning is written to the log if the coordination queue manager is not changed from the default.

The following state diagram illustrates how the presence of nodes and a defined coordination queue manager affect the state of the agent.

State machine diagram showing how the presence of nodes and a defined coordination queue manager affect the state of the agent. This diagram summarizes the information in the preceding paragraph.

Use one of the following methods to set the coordination queue manager.

Optional: Use the mqsichangeproperties command.
For example, to set the coordination queue manager to QM2 for integration server myExecutionGroup in broker IB9NODE:
```
mqsichangeproperties IB9NODE -e myExecutionGroup
-o FTEAgent -n coordinationQMgr -v QM2
```
After running this command, you must reload the integration server for the change to take effect.
Optional: Use the IBM Integration Explorer. Right-click the integration server, and select the appropriate options from the pop-up menu.

Naming integration servers

The integration server name is used to form the queue name for WebSphere MQ File Transfer Edition queues. Consequently, the names of your integration servers must conform to the rules for naming WebSphere MQ objects. You cannot deploy a flow that contains a WebSphere MQ File Transfer Edition node unless this requirement is met. Permitted characters are:

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 (%)

See the

WebSphere MQ Version 7 product documentation online for full details of naming requirements.

Determining the agent name

To send a file to a given integration server, users need to know the name of the agent that the broker creates. The agent name is derived from Broker.IntegrationServer, and is not configurable. The total name length is limited to 28 characters, with a maximum 12 characters for the broker name, and 15 characters for the integration server. Broker and integration server names longer than these limits are truncated to form the agent name. The name must be a valid format for generating MQ Series queue name. Ensure that:

The broker name is 12 characters or fewer (or at least unique in the first 12 characters).
The integration server names are 15 characters or fewer (or at least unique in the first 15 characters).
The broker and integration servers do not contain any characters that are invalid for queue names.
The broker.integrationserver tuples are all unique, even if case is ignored.

The value used is written to the event log in message BIP3358. Use one of the following methods to determine the agent name.

Optional: Use the mqsireportproperties command.
For example, to display the FTE agent name for integration server FTESAMPLE in broker IB9NODE:
```
mqsireportproperties IB9NODE -e FTESAMPLE -o FTEAgent -n agentName
```
If the agent has been created, the command returns the agent name. If the agent has not been created, the command returns an empty string.
Optional: Use the IBM Integration Explorer. Right-click the integration server, and select the appropriate options from the pop-up menu.

bc34035_.htm |

Last updated Friday, 21 July 2017