Reviewing the MFT configuration

We need to review the configuration of our system before you begin.

Managed File Transfer (MFT) requires one or more queue managers to act in the following roles for each defined MFT configuration:

  • A coordination queue manager, which maintains information on the status of each agent in the configuration published to a topic on the coordinator.
  • One or more command or connection queue managers that act as the entry point to the IBM MQ network for MFT commands.
  • One or more agent queue managers that provide the communication between an MFT agent and the IBM MQ network.

Each of the above roles can be performed by a separate queue manager, or we can combine the roles, so that, in the simplest configuration, all roles are performed by a single queue manager.

If we are adding a z/OS queue manager to an existing MFT environment we need to define connectivity between the z/OS queue manager and the other queue managers in the configuration. We can achieve this with manually defined transmission queues, or by the use of clustering.

Each MFT agent communicates with a single queue manager. If multiple agents communicate with the same queue manager, then the agent queue manager will have multiple queues defined for each agent:

  • SYSTEM.FTE.COMMAND.agent_name
  • SYSTEM.FTE.DATA.agent_name
  • SYSTEM.FTE.REPLY.agent_name
  • SYSTEM.FTE.STATE.agent_name
  • SYSTEM.FTE.EVENT.agent_name
  • SYSTEM.FTE.AUTHAGT1.agent_name
  • SYSTEM.FTE.AUTHTRN1.agent_name
  • SYSTEM.FTE.AUTHOPS1.agent_name
  • SYSTEM.FTE.AUTHSCH1.agent_name
  • SYSTEM.FTE.AUTHMON1.agent_name
  • SYSTEM.FTE.AUTHADM1.agent_name

Note that we can define generic security profiles, where we use a profile such as SYSTEM.FTE.COMMAND.*, or we can define specific profiles for each agent.

Parent topic: Configure Managed File Transfer for z/OS


Related concepts