Configuring a basic WebSphere MQ File Transfer Edition scenario on IBM i systems

WebSphere® MQ File Transfer Edition supports the transfer of files that are located on an IBM® i platform. You can set up a basic client/server environment to support file transfer operations between IBM i systems using the steps in this example.

Before you begin

To set up this environment, complete the following steps with a user profile that has *SECOFR authority and a /home/user profile directory on each system.

About this task

This diagram shows two IBM i systems: A server system called HAMPSHIRE and a client system called MINNESOTA. The server HAMPSHIRE has an agent called HURSLEY and the client MINNESOTA has an agent called ROCHESTER. The agent ROCHESTER connects to the queue manager on HAMPSHIRE using TCP/IP.

In this setup, there are two IBM i systems: one called HAMPSHIRE that has WebSphere MQ installed, and another system called MINNESOTA that has a client connection to HAMPSHIRE.

The server system, HAMPSHIRE, hosts coordination, command, and agent queue manager functions using the local queue manager QM.HAMPSHIRE. HAMPSHIRE runs the agent HURSLEY that connects using bindings mode to QM.HAMPSHIRE.

The client system, MINNESOTA, hosts the agent ROCHESTER. Agent ROCHESTER connects across the Internet Protocol network to its remote queue manager, QM.HAMPSHIRE, on HAMPSHIRE. Because there is only one queue manager, QM.HAMPSHIRE also serves as the coordination, command, and agent queue manager for the agent ROCHESTER.

Procedure

  1. Install the prerequisites for WebSphere MQ File Transfer Edition as needed. See Hardware and software prerequisites for details. For this scenario, you must install WebSphere MQ on the server system, HAMPSHIRE, only and not on the client system, MINNESOTA.
  2. Install WebSphere MQ on HAMPSHIRE. Install the base product 5724H72. If you are using WebSphere MQ V6, also install the JMS product 5724L26.
  3. Start the WebSphere MQ subsystem on HAMPSHIRE using the STRSBS QMQM/QMQM command.
  4. Install WebSphere MQ File Transfer Edition V7.0.2 on each system. You must install WebSphere MQ File Transfer Edition Server on the server system, HAMPSHIRE. You can install either the Client or Server edition of WebSphere MQ File Transfer Edition on the client system MINNESOTA.

    For the purposes of this setup type 1-Yes in response to the Skip Configuration prompt in the installer and configure WebSphere MQ File Transfer Edition manually as shown in subsequent steps.

    To configure a WebSphere MQ File Transfer Edition network that contains multiple coordination queue managers, you can add the -p parameter to the commands. See the following topics for details:
  5. Start the QFTE subsystem on each system using the STRSBS QFTE/QFTE command.

    On the server system HAMPSHIRE, complete the following steps 6 through 12:

  6. Verify that local port number 10001 is not currently being used. You can use the NETSTAT command for this verification. If port 10001 is already in use, use a different (currently unused) port in the following steps where port number 10001 is indicated.
  7. Display existing queue managers using the WRKMQM command. Press F6 to create a queue manager called QM.HAMPSHIRE and start this queue manager using option 14.
  8. Display listeners in Work with Listener Objects display using option 27 with QM.HAMPSHIRE. In that display, press F6 to create listener LSR.ROCHESTER for port 10001 and start the listener using option 14.
  9. Create the agent HURSLEY by issuing the following Qshell commands. This agent connects to the queue manager QM.HAMPSHIRE in bindings mode. On IBM i, the installation location and the configuration location are fixed. The product installation is located in the /QIBM/ProdData/WMQFTE/V7 directory in the integrated file system and the data directory is located in the /QIBM/UserData/WMQFTE/V7/config directory.
    1. cd /QIBM/ProdData/WMQFTE/V7/bin
    2. fteSetupCoordination –coordinationQMgr QM.HAMPSHIRE
    3. Pipe the MQSC command script that is generated by the fteSetupCoordination command for QM.HAMPSHIRE using the runmqsc command:
      /QSYS.LIB/QMQM.LIB/RUNMQSC.PGM QM.HAMPSHIRE
      < /QIBM/UserData/WMQFTE/V7/config/QM.HAMPSHIRE/QM.HAMPSHIRE.mqsc 
    4. Set up the queue manager to connect to when you run commands using the following command: fteSetupCommands –p QM.HAMPSHIRE –connectionQMgr QM.HAMPSHIRE
    5. Create the agent HURSLEY using the following command: fteCreateAgent –p QM.HAMPSHIRE –agentName HURSLEY –agentQMgr QM.HAMPSHIRE –agentDesc HAMPSHIRE
    6. Pipe the MQSC command script that is generated by the fteCreateAgent command for QM.HAMPSHIRE using the runmqsc command:
      /QSYS.LIB/QMQM.LIB/RUNMQSC.PGM QM.HAMPSHIRE 
      < /QIBM/UserData/WMQFTE/V7/config/QM.HAMPSHIRE/agents/HURSLEY/HURSLEY_create.mqsc
  10. Start the agent HURSLEY by entering the following Qshell command: fteStartAgent –p QM.HAMPSHIRE HURSLEY
  11. Check if the agent job is running in the QFTE subsystem using the following IBM i command: WRKSBSJOB QFTE If the agent job is not running, check spool files and logs to determine the reason and then take corrective actions.
  12. Verify that the agent is known to the coordination queue manager using the fteListAgents command from Qshell. Ping the agent with the ftePingAgent command: ftePingAgent -p QM.HAMPSHIRE -w 5 HURSLEY

    On the client system MINNESOTA complete the following steps 13 through 17.

  13. Create the agent ROCHESTER (which connects to QM.HAMPSHIRE using a TCP/IP connection) by issuing the following Qshell commands:
    1. cd /QIBM/ProdData/WMQFTE/V7/bin

    2. fteSetupCoordination –coordinationQMgr QM.HAMPSHIRE 
      –coordinationQMgrHost HAMPSHIRE –coordinationQMgrPort 10001 
      –coordinationQMgrChannel SYSTEM.DEF.SVRCONN

    3. fteSetupCommands –p QM.HAMPSHIRE –connectionQMgr QM.HAMPSHIRE 
      –connectionQMgrHost HAMPSHIRE –connectionQMgrPort 10001 
      –connectionQMgrChannel SYSTEM.DEF.SVRCONN

    4. fteCreateAgent –p QM.HAMPSHIRE –agentName ROCHESTER 
      –agentQMgr QM.HAMPSHIRE –agentQMgrHost HAMPSHIRE 
      –agentQMgrPort 10001 –agentQMgrChannel SYSTEM.DEF.SVRCONN
    The fteSetupCoordination command sets up the details of the coordination queue manager, QM.HAMPSHIRE. The fteSetupCommands command sets up the queue manager to connect to when you run commands.
  14. Transfer the MQSC command script that was generated by the fteCreateAgent command on MINNESOTA to HAMPSHIRE. Pipe the script using the runmqsc command:
    1. On HAMPSHIRE, create a temp directory using the following Qshell command: mkdir /temp
    2. Transfer the file: /QIBM/UserData/WMQFTE/V7/config/QM.HAMPSHIRE/agents/ROCHESTER/ROCHESTER_create.mqsc on MINNESOTA to a /temp directory on HAMPSHIRE.
    3. On HAMPSHIRE, pipe the file ROCHESTER_create.mqsc for QM.HAMPSHIRE using the runmqsc command. Use the following Qshell command:
      /QSYS.LIB/QMQM.LIB/RUNMQSC.PGM QM.HAMPSHIRE < /temp/ROCHESTER_create.mqsc
  15. Start agent ROCHESTER using the following Qshell command:
    fteStartAgent –p QM.HAMPSHIRE ROCHESTER
  16. Use the following native command to check if the agent job is running in the QFTE subsystem: WRKSBSJOB QFTE If the agent is not running, check spool files and logs to determine the reason for failure and then take corrective actions.
  17. Verify that the agent is known to the coordination queue manager by using the Qshell fteListAgents command. Ping the agent with the ftePingAgent command as follows:
    1. ftePingAgent -m QM.HAMPSHIRE ROCHESTER
    2. ftePingAgent -m QM.HAMPSHIRE HURSLEY

Task Task

Feedback

Timestamp icon Last updated: Tuesday, 30 January 2018
http://www.ibm.com/support/knowledgecenter/SSEP7X_7.0.4/com.ibm.wmqfte.doc/ibmi_basic_scenario.htm