Installing the server on the coordination queue manager

In this section, we cover how to install the FTE server on the machine that we used in our scenario as the coordination queue manager, WASHINGTON. Our goal in this installation is to create the agent WASH.AGENT on the queue manager, WASHQM, as shown in Figure 3-6 on page 41. We created this FTE server on Windows XP.

Chapter 3. Installing and configuring WebSphere MQ File Transfer Edition 41 Figure 3-6 FTE agent installed on coordination queue manager

The steps for accomplishing this installation are:

1. Start WASHQM.

2. Locate your WebSphere MQ File Transfer Edition server install files.

3. Initiate the FTE server install by running install.exe in the Windows installation directory.

4. Continue with the install wizard, and then accept the licensing agreement.

5. Specify a directory in which to install FTE, as shown in Figure 3-7 on page 42.

Coordination queue manager: For security reasons in a production environment, no agents are installed on the coordination queue manager.

Typically, only administrators have access to the coordination queue manager.

Figure 3-7 Specify FTE server install directories

6. Enter the name of the coordination queue manager, and specify the bindings mode, as shown in Figure 3-8. The queue manager that you name here should already exist. Because the coordination queue manager is local, you can specify bindings mode.

Figure 3-8 Specify the name of an existing queue manager

7. Enter agent queue manager details. You can specify any desired name for your agent, as shown in Figure 3-9. The agent’s queue manager name must refer to an existing queue manager. Because the agent’s queue manager is local, you can specify the bindings mode.

Figure 3-9 Enter agent queue manager details

Chapter 3. Installing and configuring WebSphere MQ File Transfer Edition 43 8. Specify the name of an existing queue manager that you want to use as your command queue manager, as shown in Figure 3-10. Because the command queue manager is local, you can specify bindings mode.

Figure 3-10 Specify the name of the command queue manager

9. Review the install options, as shown in Figure 3-11. You must scroll down to see all of the options that you specified. Click Install.

Figure 3-11 Review installation options

10.The first phase of the install completes with the appearance of the panel shown in Figure 3-12. Do not continue until you run the MQSC commands, as shown in Example 3-4 on page 44.

Figure 3-12 This script must now be run from the command line

WASHQM: The queue manager, WASHQM, must be running.

11.Use the MQ utility, runmqsc, to run the WASHQM.mqsc script from the command line, as shown in Example 3-4. Make sure that there are no errors at the bottom of the script output.

Example 3-4 Running the coordination queue manager script C:\IBM\WMQFTE\config\WASHQM>runmqsc WASHQM < WASHQM.mqsc

5724-H72 (C) Copyright IBM Corp. 1994, 2008. ALL RIGHTS RESERVED.

Starting MQSC for queue manager WASHQM.

1 : DEFINE TOPIC('SYSTEM.FTE') TOPICSTR('SYSTEM.FTE') REPLACE AMQ8690: WebSphere MQ topic created.

2 : ALTER TOPIC('SYSTEM.FTE') NPMSGDLV(ALLAVAIL) PMSGDLV(ALLAVAIL) AMQ8691: WebSphere MQ topic changed.

3 : DEFINE QLOCAL(SYSTEM.FTE) LIKE(SYSTEM.BROKER.DEFAULT.STREAM) REPLACE

AMQ8006: WebSphere MQ queue created.

4 : ALTER QLOCAL(SYSTEM.FTE) DESCR('Stream for WMQFTE Pub/Sub interface')

AMQ8008: WebSphere MQ queue changed.

: * Altering namelist: SYSTEM.QPUBSUB.QUEUE.NAMELIST : * Value prior to alteration:

5 : DISPLAY NAMELIST(SYSTEM.QPUBSUB.QUEUE.NAMELIST) AMQ8550: Display namelist details.

DESCR(A list of queues for the queued Pub/Sub interface to monitor) ALTDATE(2009-04-08) ALTTIME(21.05.12)

6 : ALTER NAMELIST(SYSTEM.QPUBSUB.QUEUE.NAMELIST) + : NAMES(SYSTEM.BROKER.DEFAULT.STREAM+

: ,SYSTEM.BROKER.ADMIN.STREAM,SYSTEM.FTE) AMQ8551: WebSphere MQ namelist changed.

: * Altering PSMODE. Value prior to alteration:

7 : DISPLAY QMGR PSMODE

AMQ8408: Display Queue Manager details.

QMNAME(WASHQM) PSMODE(ENABLED) 8 : ALTER QMGR PSMODE(ENABLED)

AMQ8005: WebSphere MQ queue manager changed.

8 MQSC commands read.

No commands have a syntax error.

All valid MQSC commands were processed.

Chapter 3. Installing and configuring WebSphere MQ File Transfer Edition 45 12.After you successfully run the coordination queue manager script, return to

the install wizard, and click Next.

13.You must now run a script to create an FTE agent. Figure 3-13 shows the request to run the script that creates an FTE agent.

Figure 3-13 Request to run the mqsc script that will create an FTE agent

14.Use the MQ utility, runmqsc, to run the WASH.AGENT_create.mqsc script, which we show in Example 3-5. Make sure that there are no errors at the bottom of the script output.

Example 3-5 Running the create agent script

C:\IBM\WMQFTE\config\WASHQM\agents\WASH.AGENT>runmqsc WASHQM <

WASH.AGENT_create.mqsc

5724-H72 (C) Copyright IBM Corp. 1994, 2008. ALL RIGHTS RESERVED.

Starting MQSC for queue manager WASHQM.

1 : DEFINE QLOCAL(SYSTEM.FTE.COMMAND.WASH.AGENT) + : DEFPRTY(0) +

AMQ8006: WebSphere MQ queue created.

2 : DEFINE QLOCAL(SYSTEM.FTE.DATA.WASH.AGENT) + : DEFPRTY(0) +

: DEFSOPT(SHARED) + : GET(ENABLED) + : MAXDEPTH(5000) + : MAXMSGL(4194304) +

: MSGDLVSQ(PRIORITY) +

AMQ8006: WebSphere MQ queue created.

3 : DEFINE QLOCAL(SYSTEM.FTE.REPLY.WASH.AGENT) + : DEFPRTY(0) +

AMQ8006: WebSphere MQ queue created.

4 : DEFINE QLOCAL(SYSTEM.FTE.STATE.WASH.AGENT) + : DEFPRTY(0) +

AMQ8006: WebSphere MQ queue created.

5 : DEFINE QLOCAL(SYSTEM.FTE.EVENT.WASH.AGENT) + : DEFPRTY(0) +

Chapter 3. Installing and configuring WebSphere MQ File Transfer Edition 47 : SHARE +

: NOTRIGGER + : USAGE(NORMAL) + : REPLACE

AMQ8006: WebSphere MQ queue created.

5 MQSC commands read.

No commands have a syntax error.

All valid MQSC commands were processed.

15.After you run the create agent script and make sure that there were no errors, return to the install wizard, and click Next.

16.A message that the install is complete is displayed, as shown in Figure 3-14.

To close the wizard, press Done.

Figure 3-14 Installation complete

17.Open a command line window, change to the c:\IBM\WMQFTE\bin directory, and then start the agent, WASH.AGENT, as shown in Example 3-6.

Example 3-6 Start the agent, WASH.AGENT C:\IBM\WMQFTE\bin>fteStartAgent WASH.AGENT

5655-U80, 5724-R10 Copyright IBM Corp. 2008. ALL RIGHTS RESERVED BFGCL0030I: The request to start agent 'WASH.AGENT' on this machine has been submitted.

BFGCL0031I: Agent log files located at:

C:\IBM\WMQFTE\config\WASHQM\agents\WASH.AGENT C:\IBM\WMQFTE\bin>

18.Ping the agent to confirm that it started, as shown in Example 3-7.

Example 3-7 Ping the agent

C:\IBM\WMQFTE\bin>ftePingAgent WASH.AGENT

5655-U80, 5724-R10 Copyright IBM Corp. 2008. ALL RIGHTS RESERVED FTE bin directory: We suggest that you add the FTE bin directory,

“C:\IBM\WMQFTE\bin”, to the path system variable, which simplifies accessing FTE commands from the command line.

BFGCL0212I: Issuing ping request to agent WASH.AGENT

BFGCL0193I: The request has been received by the source agent.

BFGCL0213I: agent WASH.AGENT responded to ping in 0.469 seconds.

Chapter 3. Installing and configuring WebSphere MQ File Transfer Edition 49 19.Open the agent log, as shown in Figure 3-15.

Figure 3-15 WASH.AGENT log: output0.log

20.Examine the contents of the log, as shown in Example 3-8.

Example 3-8 Contents of WASH.log

************ Start Display Current Environment ************

Build level: f000-20090407-1353 Java runtime version:

J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20080710 (JIT enabled)

J9VM - 20080625_20583_lHdSMr JIT - 20080620_1845_r8 GC - 200806_19

Properties:

agentDesc=Washington's Agent, agentName=WASH.AGENT, agentQMgr=WASHQM, commandPath=c:/curl

coordinationQMgr=WASHQM

************* End Display Current Environment *************

[18/04/2009 14:54:32:343 EDT] 00000001 AgentRuntime I BFGAG0058I:

The agent has been successfully initialized.

[18/04/2009 14:54:33:859 EDT] 00000001 AgentRuntime I BFGAG0059I:

The agent has been successfully started.