Answer

Trading Manager has the ability to accept input from a variety of sources, including but not limited to files, FTP, e-mail and IBM WebSphere MQ Series.

Input to Trading Manager is defined through a Get Post Office. To enable Trading Manager to accept input from MQ Series, follow these steps for Partner Manager and Message Manager configuration.

These steps include:

1. Partner Manager Configuration
2. Message Manager Configuration
3. Launcher Settings Configuration
4. Message Manager Deployment and Startup

Partner Manager Configuration:
Open Partner Manager and, once the appropriate Database is selected from the Utilities - Database Settings selection menu, perform the following (Figure 1):

1. Select "Post Offices" from the Menu Bar
2. Select "All Post Offices" from the "Post Offices" pop-up window
3. Click "Add" in the "All Post Offices" pop-up window
4. Enter a Post Office name in the Name field of the "Add Post Office" pop-up window. In this example the Name is defined as MQI
5. Select "MessageQ (server") or "MessageQ (client)" in the Adapter Type field. In this example, the Adapter Type is MessageQ (server)
6. Select the "Get Post Office" Radio Button in the Get/Put Indicator section of the "Add Post Office" pop-up window
7. Specify the Queue Manager Name and Queue Name in the Adapter Command String text box. In this example the Queue Manager Name is QMGR_TMGR and the Queue Name is QNAME_TMGR. The syntax of the adapter command is: -QMN queue_manager_name -QN queue_name
8. Click Save

Figure 1.


Message Manager Configuration:
Start the Integration Flow Designer and open Message Manager, by default named msg_mgr.msd, and perform the following (Figure 2):

1. Expand MessageManager
2. Expand StampAndSort
3. Double click on stampandsortqueue
4. Right click on the stampandsortqueue map and select "Edit Launcher..."

Figure 2.

Launcher Settings Configuration (Figure 3).

1. Expand the Launcher settings pop-up window so that Input(s) --> #1 InTM --> GET --> Source is displayed.
2. Set the Source to be either WebSphereMQ (server) or WebSphereMQ (Client).
3. Set the Command to be the respective MQ Queue Manager Name and MQ Queue Name to read the input from. You can manually type in the values or use the WTX Resource Registry file to select this value.
4. In Figure 3, the Queue Manager Name is QMGR_TMGR and the Queue Name is QNAME_TMGR. Note that this Queue Manager Name and Queue Name must match that defined in step 7 from the Partner Manager Post Office for this type of data. Alternatively you can use the Resource Registry to define this value by editing the mq_example value in your associated mrn file.
5. Click on OK.

Figure 3.


Following the steps will result in the stampandsortqueue map becoming a source event as depicted by the glasses icon on the stampandsortqueue map (Figure 4).




Figure 4.

Message Manager Deployment and Startup:
With the Integration Flow Designer still open to the MessageManager system, generate a new MessageManager system by right clicking on MessageManager and selecting Generate.

This will create a new Msg_Mgr.msl system that will accept input from IBM WebSphere MQ Series.

For Windows environments, ensure that library path for WebSphere MQ Series has been added to your Windows PATH environment variable and for UNIX environments that your LD_LIBRARY_PATH (Linux and Solaris), LIBPATH (AIX) and SHLIB_PATH (HP) have been modified to include a reference to the respective MQ lib directory (32 or 64 bit versions).

If the Launcher is already running, pause, stop and then restart the Launcher.

Windows:

1. Using the Windows Services utility, first select the respective IBM WebSphere Transformation Extender 8.x Launcher service (8.1, 8.2 or 8.3), then select "Pause the service".
2. Once the pause is complete, select "Stop the service."
3. Once the Launcher has stopped, select "Start the service"

UNIX:

1. launcher.sh -pause <port number>
2. launcher.sh -stop <port number>
3. launcher.sh -start

If you have Message Manager configured to start automatically, you can start processing messages from MQ. If Message Manager is not started automatically, start the Management Console, Connect to the server where Message Manager is installed and once connected, start the Compound System to start processing MQ based input.