Configuring a basic WebSphere MQ File Transfer Edition scenario on Windows and Linux

You can set up a basic WebSphere® MQ File Transfer Edition network between a Windows system and a Linux system by following the steps given in this topic. If you have two Windows systems or two Linux systems, you can adapt the instructions in the steps to allow for your setup.

Before you begin

To set up this basic configuration you require the following items:
  • Two systems, one with a Windows operating system and one with a Linux operating system. These systems must be connected on a network.
  • WebSphere MQ for Linux
  • WebSphere MQ for Windows
  • WebSphere MQ File Transfer Edition Server version 7.0.3 or later.
  • WebSphere MQ File Transfer Edition Remote Tools and Documentation version 7.0.3 or later.
Note: This example assumes that you have the same user name on both of the systems and that the maximum length of the user name is 12 characters. If you cannot use the same user name on both systems, you must set up WebSphere MQ security to allow the user name on one system access to WebSphere MQ on the other system.
Note: Do not use a user name with more than 12 characters on the Windows system, for example Administrator. Windows user names that are more than 12 characters long cause WebSphere MQ security problems.

About this task

These steps describe how to set up WebSphere MQ File Transfer Edition agents on two systems. Each agent has its own agent queue manager on the same system. In the examples given, the two systems are called linux_system.example.com and windows_system.example.com. The system linux_system.example.com has a Linux operating system and the queue manager defined on this system is used as the coordination queue manager for the WebSphere MQ File Transfer Edition network. The system windows_system.example.com has a Windows operating system and the agent defined on this system is run as a Windows Service.

Procedure

  1. Set up WebSphere MQ on linux_system.example.com. For more information, see Set up WebSphere MQ on linux_system.example.com.
  2. Install WebSphere MQ File Transfer Edition Server on linux_system.example.com and set up an agent. For more information, see Install WebSphere MQ File Transfer Edition Server on linux_system.example.com.
  3. Set up WebSphere MQ on windows_system.example.com. For more information, see Set up WebSphere MQ on windows_system.example.com.
  4. Create channels between queue managers on the two systems. For more information, see Connect the queue managers QM_LINUX and QM_WINDOWS.
  5. Install WebSphere MQ File Transfer Edition Server on windows_system.example.com and set up an agent to run as a Windows Service. For more information, see Install WebSphere MQ File Transfer Edition Server on windows_system.example.com.
  6. Install WebSphere MQ File Transfer Edition Remote Tools and Documentation on either system. For more information, see Install WebSphere MQ File Transfer Edition Remote Tools and Documentation.
  7. Transfer a file from the system windows_system.example.com to the system linux_system.example.com by using the command line. For more information, see Transfer a file from AGENT_WINDOWS to AGENT_LINUX.
  8. Transfer a file from the system linux_system.example.com to the system windows_system.example.com by using the WebSphere MQ Explorer plug-in. For more information, see Transfer a file from AGENT_LINUX to AGENT_WINDOWS by using the WebSphere MQ Explorer plug-in.

Set up WebSphere MQ on linux_system.example.com

About this task

The queue manager on linux_system.example.com is used as the coordination queue manager, so the level of WebSphere MQ that is installed must be version 7.0 or later.

Procedure

  1. Install WebSphere MQ, version 7.0, or later, on linux_system.example.com. As part of the installation process, install the WebSphere MQ Explorer. For information about how to install WebSphere MQ, see the Quick Beginnings guide for your platform in the IBM® WebSphere MQ Version 7.0.1 documentationxref>.
  2. Ensure that the user name that WebSphere MQ File Transfer Edition uses is in the mqm group. If this user name is different to the user name that is used on windows_system.example.com, you must set up WebSphere MQ security to allow the other user name to access WebSphere MQ on this system. For more information, see the Security section of the IBM WebSphere MQ Version 7.0.1 product documentation.
  3. Create a queue manager on linux_system.example.com called QM_LINUX. You can create the queue manager by using the WebSphere MQ Explorer or by using the command line. To create the queue manager by using the command line, type the following command:
    crtmqm QM_LINUX
  4. Start the queue manager QM_LINUX. You can start the queue manager by using the WebSphere MQ Explorer or by using the command line. To start QM_LINUX using the command line, type the following command:
    strmqm QM_LINUX
  5. Define a listener for QM_LINUX. If you created QM_LINUX by using the WebSphere MQ Explorer, the listener is already defined on the default port of 1414, unless you changed this value. To create a listener for QM_LINUX using the command line, type the following command:
    runmqsc QM_LINUX
    The runmqsc program opens. Type the following commands into runmqsc:
    ALTER LISTENER(SYSTEM.DEFAULT.LISTENER.TCP) TRPTYPE(TCP) PORT(1414) CONTROL(QMGR)
    START LISTENER(SYSTEM.DEFAULT.LISTENER.TCP)

Install WebSphere MQ File Transfer Edition Server on linux_system.example.com

Procedure

  1. Install WebSphere MQ File Transfer Edition Server on linux_system.example.com and enter the following values during the configuration steps:
    1. When asked for the coordination queue manager name, enter QM_LINUX. Select bindings transport mode and click Next.
    2. When asked for the agent name, enter AGENT_LINUX. Enter an agent description, for example WMQFTE agent on Linux.
    3. When asked for the agent queue manager name, enter QM_LINUX. Select bindings transport mode and click Next.
    4. When asked for the command queue manager name, enter QM_LINUX. Select bindings transport mode and click Next.
    For information about how to install WebSphere MQ File Transfer Edition Server, see Installing IBM WebSphere MQ File Transfer Edition Server using the graphical installer.
  2. Create the required WebSphere MQ objects on the coordination queue manager QM_LINUX. The commands to create these objects are located in the QM_LINUX.mqsc file in the directory configuration_directory/QM_LINUX. To run the commands, enter the following command:
    runmqsc QM_LINUX < configuration_directory/QM_LINUX/QM_LINUX.mqsc
  3. Create the required WebSphere MQ objects on the agent queue manager QM_LINUX. The commands to create these objects are located in the create_AGENT_LINUX.mqsc file in the directory configuration_directory/QM_LINUX/agents/AGENT_LINUX. To run the commands, enter the following command:
    runmqsc QM_LINUX < configuration_directory/QM_LINUX/agents/AGENT_LINUX/create_AGENT_LINUX.mqsc
  4. Start the agent AGENT_LINUX. At the command line, change the directory to install_directory/bin and run the following command:
    fteStartAgent AGENT_LINUX
  5. Check that AGENT_LINUX is registered with the coordination queue manager. At the command line, change the directory to install_directory/bin and run the following command:
    fteListAgents 
    The command displays a list of agents and AGENT_LINUX is listed.
  6. Check that AGENT_LINUX is ready to process managed file transfers. At the command line, change the directory to install_directory/bin and run the following command:
    ftePingAgent AGENT_LINUX
    The command displays a message that indicates how long AGENT_LINUX took to respond to the ping.

Set up WebSphere MQ on windows_system.example.com

About this task

The queue manager on windows_system.example.com is not used as the coordination queue manager, so the level of WebSphere MQ that is installed can be version 6.0 or later. The maximum length of the user name that you use on this system must be 12 characters.

Procedure

  1. Install WebSphere MQ, version 6.0, or later, on windows_system.example.com. For information about how to install WebSphere MQ, see the Quick Beginnings guide for your platform in the WebSphere MQ Version 7.0.1 product documentation.
  2. Ensure that the user name that WebSphere MQ File Transfer Edition uses is in the mqm group. If this user name is different to the user name that is used on linux_system.example.com, you must set up WebSphere MQ security to allow the other user name to access WebSphere MQ on this system. For more information, see the Security section of the IBM WebSphere MQ Version 7.0.1 product documentation.
  3. Create a queue manager on windows_system.example.com called QM_WINDOWS. You can create the queue manager by using the WebSphere MQ Explorer or by using the command line. To create the queue manager by using the command line, type the following command:
    crtmqm QM_WINDOWS
  4. Start the queue manager QM_WINDOWS. You can start the queue manager by using the WebSphere MQ Explorer or by using the command line. To start QM_WINDOWS using the command line, type the following command:
    strmqm QM_WINDOWS
  5. Define a listener for QM_WINDOWS. If you created QM_WINDOWS by using the WebSphere MQ Explorer, the listener is already defined on the default port of 1414, unless you changed this value. To create a listener for QM_WINDOWS using the command line, type the following command:
    runmqsc QM_WINDOWS
    The runmqsc program opens. Type the following commands into runmqsc:
    ALTER LISTENER(SYSTEM.DEFAULT.LISTENER.TCP) TRPTYPE(TCP) PORT(1414) CONTROL(QMGR)
    START LISTENER(SYSTEM.DEFAULT.LISTENER.TCP)

Connect the queue managers QM_LINUX and QM_WINDOWS

About this task

For files to be transferred between AGENT_LINUX and AGENT_WINDOWS their agent queue managers must be able to communicate with one another. To enable the queue managers QM_LINUX and QM_WINDOWS to communicate with each other you must set up sender and receiver channels. You can set up channels by using the WebSphere MQ Explorer or by using the command line.

Procedure

  1. On linux_system.example.com, perform the following steps:
    1. Start the runmqsc interface for QM_LINUX. Type the following command:
      runmqsc QM_LINUX
    2. Create the transmission queue. You must create this queue with the same name as the queue manager that you want QM_LINUX to connect to, in this case QM_WINDOWS. Type the following command into the runmqsc interface:
      DEFINE QLOCAL(QM_WINDOWS) USAGE(XMITQ)
    3. Create the sender channel. Define this channel by specifying the host name and port number of QM_WINDOWS and by specifying the name of the transmission queue created in step 1b. Type the following command into the runmqsc interface:
      DEFINE CHANNEL(LIN.TO.WIN) CHLTYPE(SDR) CONNAME('windows_system.example.com(1414)') XMITQ(QM_WINDOWS) CONVERT(NO)
    4. Start the sender channel. Type the following command into the runmqsc interface:
      START CHANNEL(LIN.TO.WIN)
    5. Create the receiver channel. This channel must have the same name as the sender channel that is defined on QM_WINDOWS in step 2c. Type the following command into the runmqsc interface:
      DEFINE CHANNEL(WIN.TO.LIN) CHLTYPE(RCVR)
    6. Exit the runmqsc interface. Type the following command:
      EXIT
  2. On windows_system.example.com, perform the following steps:
    1. Start the runmqsc interface for QM_WINDOWS. Type the following command:
      runmqsc QM_WINDOWS
    2. Create the transmission queue. You must create this queue with the same name as the queue manager that you want QM_WINDOWS to connect to, in this case QM_LINUX. Type the following command into the runmqsc interface:
      DEFINE QLOCAL(QM_LINUX) USAGE(XMITQ)
    3. Create the sender channel. Define this channel by specifying the host name and port number of QM_LINUX and by specifying the name of the transmission queue created in the preceding step. This channel must have the same name as the receiver channel created in step 1e. Type the following command into the runmqsc interface:
      DEFINE CHANNEL(WIN.TO.LIN) CHLTYPE(SDR) CONNAME('linux_system.example.com(1414)') XMITQ(QM_LINUX) CONVERT(NO)
    4. Start the sender channel. Type the following command into the runmqsc interface:
      START CHANNEL(WIN.TO.LIN)
    5. Create the receiver channel. This channel must have the same name as the sender channel that is defined on QM_LINUX in step 1c. Type the following command into the runmqsc interface:
      DEFINE CHANNEL(LIN.TO.WIN) CHLTYPE(RCVR)
    6. Exit the runmqsc interface. Type the following command:
      EXIT

Install WebSphere MQ File Transfer Edition Server on windows_system.example.com

About this task

To run the agent on windows_system.example.com as a Windows Service, the level of WebSphere MQ File Transfer Edition that is installed must be version 7.0.3 or later.

Procedure

  1. Install WebSphere MQ File Transfer Edition Server on windows_system.example.com and enter the following values during the configuration steps:
    1. When asked for the coordination queue manager name, enter QM_LINUX. Select client transport mode and click Next.
    2. When asked for the coordination queue manager connection details, enter the following values. For host name, enter linux_system.example.com. For port number, enter 1414. For channel, enter SYSTEM.DEF.SVRCONN. Click Next.
    3. When asked for the agent name, enter AGENT_WINDOWS. Enter an agent description, for example WMQFTE agent on Windows.
    4. When asked for the agent queue manager name, enter QM_WINDOWS. Select bindings transport mode and click Next.
    5. When asked for the command queue manager name, enter QM_WINDOWS. Select bindings transport mode and click Next.
    For information about how to install WebSphere MQ File Transfer Edition Server, see Installing IBM WebSphere MQ File Transfer Edition Server using the graphical installer.
  2. Create the required WebSphere MQ objects on the agent queue manager QM_WINDOWS. The commands to create these objects are located in the create_AGENT_WINDOWS.mqsc file in the directory configuration_directory/QM_LINUX/agents/AGENT_WINDOWS. To run the commands, type the following command:
    runmqsc QM_WINDOWS < configuration_directory/QM_LINUX/agents/AGENT_WINDOWS/create_AGENT_WINDOWS.mqsc
  3. Modify the agent AGENT_WINDOWS to act as a Windows Service. Use the fteModifyAgent command to specify that AGENT_WINDOWS runs as a Windows Service and, optionally, to specify the parameters that are used by the service. At the command line, change the directory to install_directory/bin and run the following command:
    fteModifyAgent -agentName AGENT_WINDOWS -s -su user_name -sp user_password
    where user_name is the name of the user account to run the service under. For more information, see fteModifyAgent (modify a WebSphere MQ File Transfer Edition agent).
  4. Start the agent AGENT_WINDOWS. You can start the agent AGENT_WINDOWS from Control Panel > Administrative Tools > Windows Services or by using the fteStartAgent command. At the command line, change the directory to install_directory/bin and type the following command:
    fteStartAgent AGENT_WINDOWS
  5. Check that AGENT_WINDOWS is registered with the coordination queue manager. At the command line, change the directory to install_directory/bin and run the following command:
    fteListAgents 
    The command displays a list of agents and both AGENT_WINDOWS and AGENT_LINUX are listed.
  6. Check that AGENT_WINDOWS is ready to process managed file transfers. At the command line, change the directory to install_directory/bin and run the following command:
    ftePingAgent AGENT_WINDOWS
    The command displays a message that indicates how long AGENT_WINDOWS took to respond to the ping.

Install WebSphere MQ File Transfer Edition Remote Tools and Documentation

Procedure

  1. Install WebSphere MQ File Transfer Edition Remote Tools and Documentation on either system. When asked if you want to use an existing configuration directory, choose Reuse existing configuration. For information about how to install WebSphere MQ File Transfer Edition Remote Tools and Documentation, see Installing IBM WebSphere MQ File Transfer Edition Server using the graphical installer.
  2. Start the WebSphere MQ Explorer. Type the following command:
    strmqcfg
  3. Ensure that the Managed File Transfer section is displayed in the left panel and that when it is expanded it shows a connection to QM_LINUX.

Transfer a file from AGENT_WINDOWS to AGENT_LINUX

Procedure

  1. Create a file on windows_system.example.com at the location c:\files\send\sourcefile.txt.
  2. Create a directory on linux_system.example.com at the location /home/user_name/files.
  3. On either windows_system.example.com or linux_system.example.com, run the following command to request a file transfer:
    fteCreateTransfer -sa AGENT_WINDOWS -sm QM_WINDOWS -da AGENT_LINUX -dm QM_WINDOWS
                      -dd /home/user_name/files "c:\files\send\sourcefile.txt"
    For more information, see fteCreateTransfer (create new file transfer).
  4. Check that the file sourcefile.txt has been copied to /home/user_name/files on linux_system.example.com.

Transfer a file from AGENT_LINUX to AGENT_WINDOWS by using the WebSphere MQ Explorer plug-in

Procedure

  1. On the system where the WMQFTE Remote Documentation and Tools is installed, start the WebSphere MQ Explorer. Type the following command:
    strmqcfg
  2. In the WebSphere MQ Explorer, expand Managed File Transfer > QM_LINUX in the left panel.
  3. Click Transfer Log. A new panel opens on the right. This panel Transfer Log displays information about the transfer that you created in the preceding section.
  4. Right-click Transfer Log in the left panel. A menu is displayed.
  5. Select New Transfer from the menu. The Create New Managed File Transfer window opens.
  6. In the From section, from the Agent list, choose AGENT_LINUX.
  7. In the From section, in the File field, type /home/user_name/files/sourcefile.txt.
  8. In the To section, from the Agent list, choose AGENT_WINDOWS.
  9. In the To section, in the Directory field, type c:\files\receive\.
  10. In the To section, in the File field, type returnfile.txt.
  11. Click Finish.
  12. In the Current Transfer Progress panel at the lower right, you can watch the progress of the transfer that you have submitted.

What to do next

Now that you have set up a basic configuration, you can use it to perform a number of actions, including the following actions:

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/config_basic.htm