Setting up a test scenario in WebSphere MQ File Transfer Edition - Middleware News

Setting up a test scenario in WebSphere MQ File Transfer Edition - Middleware News

IBM® WebSphere® MQ File Transfer Edition V7 (hereafter called WebSphere MQ FTE) delivers a reliable managed file transfer solution for moving files, regardless of their size, between IT systems without the need for programming.

For a basic description of WebSphere MQ FTE, including its functions, processes, and associated tools, see Welcome to WebSphere MQ FTE in the WebSphere MQ FTE information center.

For information about the basic topology of WebSphere MQ FTE, including the operation of the agent, agent queue manager, coordination queue manager, and command queue manager components, see WebSphere MQ FTE topology overview in the WebSphere MQ FTE information center, and Figure 1 below, from the information center:

Figure 1. WebSphere MQ FTE topology overview

Setting up the scenario

There are many different WebSphere MQ FTE scenarios that can demonstrate its capabilities -- this article uses a basic topology with two queue managers to keep things simple:

Figure 2. Basic topology with two queue managers

Here is a description of this topology:

• The coordination queue manager can reside on either queue manager. The command queue manager and agent queue manager can reside on either queue manager.
• Each server agent uses bindings mode to connect to its queue manager.
• Either server agent can be a source or destination.
• Files can be transferred by sender or receiver channels between the two server agents.

The WebSphere MQ FTE server agent is installed on each endpoint and connected to its agent queue manager, which also acts as a command queue manager. You can appoint either queue manager as the coordination queue manager, but this queue manager must be running on WebSphere MQ V7. In this topology, you can use the WebSphere MQ FTE plug-in for WebSphere MQ Explorer and remote tools.

As mentioned, WebSphere MQ FTE runs on top of WebSphere MQ, so the first step is to make sure WebSphere MQ V7.0.1.2 is installed on both machines, though on the source machine you can use WebSphere MQ V6.0 or later. You then set up WebSphere MQ.

1. Creating the CQM coordination queue manager

1. Create a queue manager called CQM in the coordination machine, which is going to work as the coordination, command, and agent queue manager. Enter the following MQ commands:
   c:\>crtmqm CQM and c:\>strmqm CQM.
2. Download this script at the bottom of the article, and execute it to create the listener and channels:
   c:\>runmqsc CQM < CQM_script.txt .

2. Creating the SQM queue manager

1. Create a queue manager called SQM in the source machine, which is going to work as the command and agent queue manager. Enter the following MQ commands:
   c:\>crtmqm SQM and c:\>strmqm SQM
2. Download this script at the bottom of the article, and execute it to create the listener and channels:
   c:\>runmqsc SQM < SQM_script.txt.
3. After you have configured the WebSphere MQ environment, you are ready to begin the WebSphere MQ FTE Server installation on the coordination queue manager.

3. Installing WebSphere MQ FTE on the coordination machine

1. Launch the WebSphere MQ FTE Server installer and select your preferred language.
2. Click Next in the Introduction section.
3. Accept the License Agreement and click Next.
4. Change the product install folder to C:\IBM\WMQFTE and click Next.
5. Change the configuration folder to C:\IBM\WMQFTE\config and click Next.
6. For Coordination queue manager name, enter CQM. For Connect using the following transport mode, click Bindings:
   
   Figure 3. Define coordination queue manager on coordination machine
7. For Agent name, enter AgentC. For Agent description, enter Coordination Agent. For Agent queue manager name, enter CQM. For Connect using the following transport mode, click Bindings:
   
   Figure 4. Define coordination agent
8. For Command queue manager name, enter CQM. For Connect using the following transport mode, clickBindings:Transport Mode: Bindings:
   
   Figure 5. Define the command queue manager on coordination machine
9. Review the Summary screen and click Install.
10. During the installation process you will see a screen like this. Click Next:
    
    Figure 6. Run on coordination queue manager
11. Also click Next in this screen. You will configure the previous step and this one later:
    
    Figure 7. Run on agent queue manager
12. Click Done.

To configure the previous steps, execute the following commands:

1. Open a command prompt, go to the C:\IBM\WMQFTE\config\CQM folder and run:

   C:\IBM\WMQFTE\config\CQM>runmqsc CQM < CQM.mqsc

   
   .
2. To configure AgentC, go to the C:\IBM\WMQFTE\config\CQM\agents\AGENTC folder and run:

   C:\IBM\WMQFTE\config\CQM\agents\AGENTC>runmqsc CQM < AGENTC_create.mqsc

   
   .
3. Start AgentC and for ease of use add the folder C:\IBM\WMQFTE\bin in the PATH environment variable:

   C:\IBM\WMQFTE\bin>fteStartAgent AgentC

   
   .
4. Check the file output0.log in the agent logs folder C:\IBM\WMQFTE\config\CQM\agents\AGENTC\logs. You should see a message like this:

   ************ Start Display Current Environment ************ Build level: V7.0.2 f702-GM5-20091117-1614 Java runtime version: J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223ifx-20080811 (JIT enabled) J9VM - 20080809_21892_lHdSMr JIT - 20080620_1845_r8 GC - 200806_19 ICU4J version: Unable to determine ICU4J version (ICU4J is disabled) Properties: agentDesc=Coordination Agent, agentName=AGENTC, agentQMgr=CQM, coordinationQMgr=CQM transferRoot=C:\Documents and Settings\Administrator Install Locations: com.ibm.wmqfte.product.root=C:\IBM\WMQFTE com.ibm.wmqfte.product.config=C:\IBM\WMQFTE\config ************* End Display Current Environment ************* [16/08/2010 18:22:27:484 ACT] 00000001 Agent I BFGAG0115I: Relative path transfer root directory: C:\Documents and Settings\Administrator [16/08/2010 18:22:27:500 ACT] 00000001 AgentRuntime I BFGAG0058I: The agent has successfully initialized. [16/08/2010 18:22:29:218 ACT] 00000001 AgentRuntime I BFGAG0059I: The agent has been successfully started.

5. Ping the agent to determine if it is up and running:

   C:\IBM\WMQFTE\bin>ftePingAgent AgentC

   
   .

You are done with the coordination queue manager.

4. Installing WebSphere MQ FTE on the source machine

1. When you get to the Define coordination queue manager screen, for Coordination queue manager name, enter CQM. For Connect using the following transport mode, click Client:
   
   Figure 8. Define coordination queue manager on source machine
2. Configure the coordination queue manager. For Coordination queue manager hostname, enter coordination (your hostname or IP address). For Coordination queue manager port, enter 1818:
   
   Figure 9. Coordination queue manager details
3. Configure the source agent. For Agent name, enter AgentS. For Description, enter Source agent. For Agent queue manager name, enter SQM. For Connect using the following transport mode, click Bindings:
   
   Figure 10. Define source agent
4. On this screen, for Command queue manager name, enter SQM. For Connect using the following transport mode, clickBindings:
   
   Figure 11. Define command manager on source machine
5. Click Next and complete the installation process. Then open a command prompt and go to the C:\IBM\WMQFTE\config\CQM\agents\AGENTS folder. Remember to set up the PATH environment variable and run:

   C:\IBM\WMQFTE\config\CQM\agents\AGENTS>runmqsc SQM < AGENTS_create.mqsc

   
   .
6. Start the agent AgentS, check the logs, and ping the agent like you did above for AgentC.

You have installed and configured both the coordination machine and the source machine.

5. Installing WebSphere MQ FTE remote tools and documentation

1. Close WebSphere MQ Explorer if it is open, launch the Installer, go to the screen Select set of features to install, and select Complete installation:
   
   Figure 12. WebSphere MQ FTE remote tools and documentation
2. Change the installation folders as you did before to C:\IBM\WMQFTE and C:\IBM\WMQFTE\config. Click Use existing:
   
   Figure 13
3. Click Install
4. Repeat these steps on the source machine. After you finish, launch WebSphere MQ Explorer on both machines and you should see the Manage File Transfer tree in the MQ Explorer Navigator:
   
   Figure 14. Manage File Transfer plug-in
5. Now you can use WebSphere MQ FTE to securely transfer a file from one machine to the other. Do a transfer from the source machine to the coordination machine: Right-click on the CQM queue manager in the source machine Manage File Transfer plug-in and select New Transfer:
   
   Figure 15
6. Complete the information as shown and click Finish:
   
   Figure 16. New transfer
7. TestFile.txt is attached at the end. Go to the Transfer log folder and you should see a successful transfer:
   
   Figure 17. Transfer log
8. Check the C:\fte folder on the coordination machine:
   
   Figure 18
9. Open it with Notepad using the command: c:\fte>notepad TestFile.txt:
   
   Figure 19. TestFile.txt