Configure a partner server
How you configure a partner server, when the base server has a separate coordination queue manager
Before starting
Ensure that we have fully completed all the tasks to set up a base server, that includes a configuration queue manager.
The same assumptions made about IBM MQ and the security configuration, as well as the IBM MQ path also apply to the partner server.
Start by setting up the MFT5 configuration directory, and identifying the coordination queue manager by using the fteSetupCoordination command.
Procedure
-
Create the partner server configuration directory by issuing the following command:
fteSetupCoordination -coordinationQMgr MFT5 -coordinationQMgrHost 177.16.20.15 -coordinationQMgrPort 1771 -coordinationQMgrChannel MQMFT.MFT5.SVRCONN
Notes:- When the coordination queue manager is on a different server from the partner server, the
connection to the base server coordination queue manager must be defined as a client connection.
Failure to define the coordination queue manager connection as an IBM MQ client connection, on the partner server, causes any Managed File Transfer command, that connects to the coordination queue manager, to fail.
An example of a command that connects to the coordination queue manager is fteListAgents.
- You do not need to create the IBM MQ definitions as the definitions required by the coordination queue manager were completed when you configured the base server.
- When the coordination queue manager is on a different server from the partner server, the
connection to the base server coordination queue manager must be defined as a client connection.
-
Identify the commands queue manager by issuing the following command:
fteSetupCommands -connectionQMgr CSM1
The commands queue manager does not require any extra IBM MQ definitions. -
Identify the partner agent queue manager, and create the partner agent queue manager, by
issuing the following command:
fteCreateAgent -agentName CSM1AGT1 -agentQMgr CSM1
- Change to the CSM1AGT1 directory.
-
Create the IBM MQ definitions required by the
agent, by issuing the following command:
runmqsc CSM1 < CSM1AGT1_create.mqsc > csm1.txt
- Open file csm1.txt with your preferred editor to confirm that all agent required definitions have been created successfully.
-
Start the agent, by issuing the following command:
fteStartAgent CSRMAGT1
-
Display the agent by typing fteListAgents
We should see output similar to the
following:
C:\>fteListAgents 5655-MFT, 5724-H72 Copyright IBM Corp. 2008, 2020. ALL RIGHTS RESERVED BFGPR0127W: No credentials file has been specified to connect to IBM MQ. Therefo re, the assumption is that IBM MQ authentication has been disabled. Agent Name: Queue Manager Name: Status: CSM1AGT1 CSM1 READY MFT4AGT1 MFT4 READY
Note: if you have not enabled connection authentication in your Managed File Transfer environment, we can ignore the BFGPR0127W message.If we issue the ftelistAgents command and receive the following message, BFGCL0014W: No agents exist that match the current selection criteria., see What to do if your MFT agent is not listed by the fteListAgents command.
If the status of one of the agents is UNREACHABLE, see What to do if the fteListAgents command shows an agent status of UNREACHABLE for further information.
Parent topic: Configure the base server