Prepare the file system and queue managers, and determine the name of the integration node agent.
Information about file transfers is held on storage queues that are controlled by WebSphere® MQ, so you must install WebSphere MQ on the same computer as your integration node if you want to use the capabilities provided by the FTEInput and FTEOutput nodes. For information about installing and using WebSphere MQ with IBM® Integration Bus, see Installing WebSphere MQ.
Storage queues that hold file transfer information are owned by the queue manager that is specified on the integration node, and you specify this queue manager by using the -q property of the mqsicreatebroker command; see Creating an integration node and mqsicreatebroker command.
You must also create the system queues required by the FTEInput and FTEOutput nodes; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager. A set of WebSphere MQ script (MQSC) commands is also provided, to enable you to create artifacts that are required by the agent and coordination manager; for more information, see Scripts to create artifacts required for WebSphere MQ File Transfer Edition.
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.
If you configure your integration server to use a different coordination queue manager from the default queue manager that is configured for your integration node, you must define sender and receiver channels between the default queue manager and coordination queue manager. You must also define transmission queues on the default queue manager and coordination queue manager.
On systems using EBCDIC Katakana you cannot use lowercase characters.
mqsireportproperties IBNODE -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.