Tag Archives: Websphere MQ

Websphere MQ Cluster Tutorial

How to create a Websphere MQ Cluster:

Step 1: Open Websphere MQ Explorer and create two Queue Managers that will be part of the cluster.

Step 2: Right click on Queue Manager Cluster and Select New->Queue Manager Cluster

Step 3: Specify the following information:

  • Cluster Name
  • First Queue Manager
  • Second Queue Manager
  • Cluster Receiver Channel for First Queue Manager
  • Cluster Receiver Channel for Second Queue Manager

Active Full Repository Cluster:

Step 4: Create a new Queue and add it the Cluster (Specify the Cluster Name)

Step 5: Test Clustered Queue Manager by putting a message on both Queue Managers using a shared Queue (QIn)

amqsput QCluster1 QIn

amqsput QCluster2 QIn

Install and Configure Websphere MQ File Transfer Edition

First Configuration of Websphere MQ File Transfer Edition:

Step 1: Create a Coordination Queue Manager in Websphere MQ Explorer, in my case my coordination Queue Manager is called FTE_COORD

Step 2: Create the Command Queue Manager

Step 3: Start Websphere MQ FTE Installation

Complete all the information for the FTE_COORD Manager in the installation window:

Complete all the information for the FTE_COMMAND Manager in the installation window:

Step 4: After installation you will receive the following message:

C:\Documents and Settings\All Users\Application Data\IBM\WMQFTE\config\FTE_COORD\FTE_COORD.mqsc has been created.
Ensure this file has been run against the coordination queue manager FTE_COORD before attempting file transfers.This can be done by redirecting the contents of the file FTE_COORD.mqsc into a runmqsc session.

Navigate to the path above in the command window and enter the following command:

C:\Documents and Settings\All Users\Application Data\IBM\WMQFTE\config\FTE_COORD>runmqsc FTE_COORD < FTE_COORD.mqsc

The mqsc script will create the FTE System Queues, Topics, namelists,

DEFINE TOPIC(‘SYSTEM.FTE’) TOPICSTR(‘SYSTEM.FTE’) REPLACEALTER TOPIC(‘SYSTEM.FTE’) NPMSGDLV(ALLAVAIL) PMSGDLV(ALLAVAIL)DEFINE QLOCAL(SYSTEM.FTE) LIKE(SYSTEM.BROKER.DEFAULT.STREAM) REPLACEALTER QLOCAL(SYSTEM.FTE) DESCR(‘Stream for WMQFTE Pub/Sub interface’)* Altering namelist: SYSTEM.QPUBSUB.QUEUE.NAMELIST* Value prior to alteration:DISPLAY NAMELIST(SYSTEM.QPUBSUB.QUEUE.NAMELIST)ALTER NAMELIST(SYSTEM.QPUBSUB.QUEUE.NAMELIST) + NAMES(SYSTEM.BROKER.DEFAULT.STREAM+ ,SYSTEM.BROKER.ADMIN.STREAM,SYSTEM.FTE)* Altering PSMODE.  Value prior to alteration:DISPLAY QMGR PSMODEALTER QMGR PSMODE(ENABLED)DEFINE QLOCAL(SYSTEM.FTE.DATABASELOGGER.REJECT) + DESCR(‘Messages rejected by the FTE database logger.’) + DEFPRTY(0) + DEFSOPT(SHARED) + GET(ENABLED) + MAXDEPTH(999999999) + MAXMSGL(4194304) + MSGDLVSQ(PRIORITY) + PUT(ENABLED) + RETINTVL(999999999) + SHARE + NOTRIGGER + USAGE(NORMAL) + REPLACEDEFINE QLOCAL(SYSTEM.FTE.DATABASELOGGER.COMMAND) + DESCR(‘Command messages to control the FTE database logger.’) + DEFPRTY(0) + DEFSOPT(SHARED) + GET(ENABLED) + MAXDEPTH(999999999) + MAXMSGL(4194304) + MSGDLVSQ(PRIORITY) + PUT(ENABLED) + RETINTVL(5000) + SHARE + NOTRIGGER + USAGE(NORMAL) + REPLACE

Step 5: Verify that the following system Queues has been created:

Step 6: Connect MQFTE Coordination Queue Manager by right clicking FTE_COORD and selecting ‘Connect’

Step 7: A successful connect will look like the following:

You are now ready to create your first Agent to send files from a source to destination.

Cast Iron Websphere MQ integration Flow

How to integrate Websphere MQ integration flow with Cast Iron tutorial.

Before starting this tutorial make sure that you have the MQ jar files added to the -> Install Module Providers Menu

Step 1: Create a Websphere MQ endpoint by specifying the following information:

  • Websphere MQ hostname
  • Websphere MQ port
  • Queue Manager Name
  • Server Connection Channel Name
  • MQ Privilege User – Username
  • MQ Privilege User – Password

Step 2:  On Websphere MQ Explorer create the following:

  • Local Queue
  • Create Server Connection Channel

Step 3: Create your integration Flow

Step 4: Specify the the MQ Endpoint as one create in Step 1

Step 5: Create the input and output maps for the two activities.

Step 6: Verify and test the integration flow.

Websphere MQ Administration Software

VentureTech – (http://www.venturetech.co.za) has launched an exciting new product to do Websphere MQ administration in a easy and efficient way by saving time and money with command line commands. The WMQ Admin program will provide customer with the ease of getting all the information on their current Websphere MQ environment.

Download the latest version of WMQAdmin at: http://wmqadmin.sourceforge.net/

Websphere Transformation Extender with Websphere MQ

How do you set a input or Output Card to post the transformed or incoming file to a Websphere MQ queue?

This will show how WTX can GET or PUT a untransformed or transformed input or output to a MQ queue.

Step 1: Open up WTX Design Studio and create a Transformation map with input and output card.

Step 2:  Specify the Map Location for the WTX input or output card (depending if you want the message to come from MQ or to put a transformed data to an MQ queue)

Step 3: Select the source to be Websphere MQ (server) and specify the Queue Manager name and Queue you want to place or put the message:

-QMN YOUR_QUEUE_MANAGER_NAME -QN YOUR_QUEUE_NAME

Test this by putting a message on that queue and running the transformation map.

Install Websphere Message Broker V7 on AIX

Install Websphere Message Broker V7 on AIX:

FTP all the relevant files to your AIX machine, this software includes:

1. Websphere MQ for AIX

2. Websphere Message Broker for AIX

Websphere MQ must first be installed before attempting to install WMB as WMB requires lib files from MQ.

Step 1: Open a command window and extract Websphere MQ, next run: sudo smitty

Step 2: Define the file path location of MQ for AIX: /installs/WebsphereMQ

Step 3: Define the “ALL” software needs to be installed and change the license agreement to “YES”

Step 4: Successful install of Websphere MQ

Install Webphere Message Broker:

Step 1: Open command line and navigate to the messagebroker1_runtime folder

Step 2: Run the following commnad: sudo ./setupaix -console

Step 3: Go through the Broker Wizard and confirm that Broker was installed successfully.

After installation navigate to: /opt/mqsi/7.0/bin

Run the following command: sudo ./ mqsicreatebroker WBRK_DEV -q WMQ_DEV

Confirm that broker has been created successfully.

Confirm that you MQ QueueManager listerner was created and started, if it was not started use the following command:

runmqlsr -t tcp -p 1414 -m WMQ_DEV

See link for more information:

http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzah.doc/qc10410_.htm

Run the following command to start the broker: sudo ./mqsistart WBRK_DEV

Run the following command to see if broker and QM has started: sudo ./mqsilist

If all this has been done, add a remote broker definition to your Websphere Message Broker Toolkit and also a Remote Queue Manager to your Websphere MQ or Broker Explorer.