Learn how to install WebSphere MQ for Developers for use with IBM Integration Bus for Developers version 10, to be able to exploit features of WebSphere MQ: download and then install WebSphere MQ, through to testing use of MQ features, all in minutes.

  • Background: WebSphere MQ is not a prerequisite for IBM Integration Bus version 10

    On distributed systems, WebSphere MQ is no longer a prerequisite for using IBM Integration Bus Version 10, which means that you can develop and deploy applications with IBM Integration Bus without needing WebSphere MQ. However, some IBM Integration Bus features require access to WebSphere MQ, including the MQ nodes and the event-driven processing nodes that are used for aggregation and timeout flows, message collections, and message sequences. For more information about features that require access to WebSphere MQ, see Enhanced flexibility in interactions with WebSphere MQ in the IBM Integration Bus Version 10 product documentation.

    If you choose to use the IBM Integration Bus features that require access to WebSphere MQ, you can install and use WebSphere MQ within the terms of the license for IBM Integration Bus.

If you want to try IBM Integration Bus for Developers with self-study labs that require access to WebSphere MQ, you can install and use WebSphere MQ Advanced for Developers without charge:

  1. Install WebSphere MQ Advanced for Developers on the same machine as your integration node
  2. Create a queue manager for use with IBM Integration Bus
  3. Create the set of IBM Integration Bus queues on your queue manager
  4. Associate the queue manager with your integration node

This tutorial assumes that you have already installed IBM Integration Bus for Developers on Windows, and want to add WebSphere MQ Advanced for Developers onto the same Windows computer.

Prepare: Download WebSphere MQ Advanced for Developers

Downloading WebSphere MQ Advanced for Developers is straightforward, and only needs you to agree to the license and then save the ZIP file (~512 MB) to your computer.

To download now, click the following button: Download

Result: The software is on your computer, and you are ready to install WebSphere MQ Advanced for Developers

Step 1: Install WebSphere MQ Advanced for Developers

Installing WebSphere MQ Advanced for Developers is little more than to unpack the software.

  • Read a description of installing on Windows

    1. Extract the ZIP file that you downloaded to a directory of your choice

      This creates the subdirectory, cdimage_developers; for example, C:\mqadv_dev80_windows\cdimage_developers

    2. To start the installation process, run the Setup.exe file.

      For detail about the steps to follow, see Installing and configuring using the graphical user interface in the WebSphere MQ version 8 product documentation.

      The installation programs contain links to further information if you require it during the installation process. The installation process has five parts:

      1. Use the Launchpad to check and install software requirements, specify network information, and start the WebSphere MQ installation wizard.
      2. Use the installation wizard to install the software, and start the Prepare WebSphere MQ wizard.
      3. Use the Prepare WebSphere MQ wizard to start the WebSphere MQ service.
      4. Optionally, use the Default Configuration wizard to create a default configuration and associated objects for verifying the installation by using the Postcard application that is supplied with WebSphere MQ.
      5. Optionally, if you completed step 4, use the Postcard application to verify your installation.

Result: You’ve successfully installed WebSphere MQ for Developers for use with IBM Integration Bus.

Step 2: Create a queue manager for use with IBM Integration Bus

This step assumes that you do not want to use the default queue manager, and that you want to use the queue manager name, QM1, as described in the WebSphere MQ product documentation. If you choose a different name, remember to use that name for the queue manager if needed in any self-study labs that you try.

  1. Start IBM MQ Explorer as an administrator. For example, right-click the WebSphere MQ icon in the system tray and then in the context menu click WebSphere MQ Explorer.
    mqsystemtray
  2. In the Navigator view, right-click the Queue Managers folder, then click New > Queue Manager. The Create Queue Manager wizard starts.
  3. In the Queue Manager name field, type QM1.
  4. Select the Make this the default queue manager check box.
  5. In the Dead-letter queue field type SYSTEM.DEAD.LETTER.QUEUE. This is the name of the dead-letter queue that is automatically created when you create the queue manager.
  6. Leave the other fields empty and click Finish, or if that button is disabled, click Next. The Finish button is disabled if the port number conflicts with an existing queue manager, for example the queue manager that is created as part of the default configuration. You must continue through the wizard to change the default port number.
  7. If you clicked Next, continue to accept the defaults and click Next on each page until you get to the final page of the wizard, when the Finish button becomes available. Change the specified port number, for example to 1415, and click Finish.

    IBM MQ displays a Creating Queue Manager dialog window while the queue manager is created and started.

These instructions are taken from Create a queue manager, called QM1 by using the IBM MQ Explorer in the WebSphere MQ product documentation

Result: In WebSphere MQ, you have created a queue manager, QM1, for use with IBM Integration Bus.

Step 3: Create the set of IBM Integration Bus system queues on your queue manager
  1. Open the IBM Integration Console; for example, click Start > All Programs > IBM Integration Bus…Developer Edition > IBM Integration Console…
  2. In the Console window, navigate to the /samples/wmq/ subdirectory of the IBM Integration Bus installation; for example:
    C:\Program Files\IBM\IIB\10.0.0.0\server\sample\wmq
    
  3. Run the following command:
    iib_createqueues.cmd QM1
  4. Optional: If you want to verify that the queues have been created in WebSphere MQ, you can use the WebSphere MQ Explorer or runmqsc command (as follows):
    In the IBM Integration Console, run the following commands (responses are shown after each command):

    1. runmqsc
      5724-H72 (C) Copyright IBM Corp. 1994, 2014.
      Starting MQSC for queue manager QM1.
      
    2. display queue(SYSTEM.BROKER*)
           3 : display queue(SYSTEM.BROKER*)
      AMQ8409: Display Queue details.
         QUEUE(SYSTEM.BROKER.ADAPTER.PROCESSED)
         TYPE(QLOCAL)
      AMQ8409: Display Queue details.
         QUEUE(SYSTEM.BROKER.ADMIN.STREAM)       TYPE(QLOCAL)
      ...
      AMQ8409: Display Queue details.
         QUEUE(SYSTEM.BROKER.WS.REPLY)           TYPE(QLOCAL)
      

See Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager in the IBM Integration Bus version 10 product documentation.

Result: You have created the system queues for IBM Integration Bus.

Step 4: Associate the queue manager with the integration node, TESTNODE_userid
  1. In the IBM Integration Console, stop the integration node:
    mqsistop -i TESTNODE_userid
    
  2. Associate the queue manager with the integration node, TESTNODE_userid
    mqsichangebroker TESTNODE_userid -q QM1
    

    Example output:

    BIP8251W: Service dependencies for component 'TESTNODE_userid' changed to 'MQ_
    Installation1  '; the previous value was '  '.
    BIP8071I: Successful command completion.
    

  3. Start the integration node:

    mqsistart TESTNODE_userid
    

Result: You have associated the queue manager with the integration node.

13 comments on"Installing WebSphere MQ for use with IBM Integration Bus for Developers"

  1. Thanks Ian_Larner. The document was much helpful.

  2. Ian, Thanks for sharing the details explanation for MQ configuring with IIB10 . unable to open the selfstudy Lab link. Please help to share the link

    • @siva Hi
      Thanks for spotting that. I’ve updated the page to link to the MQ lab page from where you can find links to download the PDF and ZIP files. Note the links use the ftp protocol, which some people have problems with; you can change the link address to use the http protocol. (See other comment on the lab page.)
      Regards, Ian

  3. Muhammad Usman July 28, 2017

    I try to download IBM IIB v10 developer edition but each time i got the same error.

    IBM Integration Bus for Developers
    This product is subject to strict US export control laws. Prior to providing access, we must validate whether you are eligible to receive it under an available US export authorization.
    Your request is being reviewed.
    Upon completion of this review, you will be contacted if we are able to give access. We apologize for any inconvenience.

    message code: 53e

    What things i need to be to download IBM IIB v10 developer edition?

    Thanks

    • Ian_Larner July 31, 2017

      Hi Muhammad,
      That message should only appear if the IBM Download system thinks that your country is unknown or unclear. You should get a response allowing or disallowing the download, but I don’t know how long that may take.
      If you don’t get an email allowing your download within a few days, please try the Software Download support.
      Regards, Ian

  4. Hi Ian,
    When I am creating Queue Manager in MQ I am getting error stating that “AMQ7077: You are not authorized to perform the requested operation.
    exitvalue = 119”
    I have tried to get it but things doesn’t work. Kindly reply about this asap.
    Regards,
    Giri.

  5. 8KK7_Indranil_Palit March 31, 2017

    finally done connecting to remote QM from localhost

    • Ian_Larner April 03, 2017

      Thanks for letting us know. Is there anything that you might share to help others?
      Regards, Ian

  6. 8KK7_Indranil_Palit March 31, 2017

    Hi,
    Remote Queue Manager(QM) is Hosted on a (hp-ux) server . The Queue Manager is also set up properly as we use the QM and its Queues with our WESB applications.

    We have installed IIB 10.0.0.7 on Windows 64 bit and are trying to connect the remote QM through IIB App using MQ client connection properties.

    While trying to deploy the IIB app on the node we are getting an error stating :
    BIP2684E: A component was configured to use WebSphere MQ, but the required MQ libraries are not available.

    Please help us.

  7. Hi,

    Can the same steps be followed for unbuntu/linux?

    I tried to follow below link for creating local queue manager connection, but still not succeeded.
    https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bc28612_.htm

    I am getting below error:
    BIP8059E: Command has failed because the component’s Queue Manager is not available.
    The command has failed because the Queue Manager associated with the component is currently unavailable.
    Reissue the command after the queue manager has been restarted.

    The steps which I had taken are as follows:
    1) I already had a IIB installed on linux. Therefore, I installed MQ.
    2) Defined Queue Manager.
    3) Created channed/ Listener.
    4) Created a MQEndpoint policy as below:

    CLIENT
    NGX.QMGR
    localhost
    1414
    NGX_QMGR.SRVCONN
    false

    5) Associated policy with broker using following command:
    mqsicreatepolicy NGX.BRK -t MQEndpoint -l ngx_policy -f /var/mqsi/local_mqm_policy.xml

    6) Stopped broker.

    7) Executed mqsichangebroker to point QMGR.

    8) Started the broker and got same above mentioned error.

    Your help is much appreciable.

  8. HI There,

    Thanks for the detailed explanation,as IIB10 has a feature where MQ is no more a prerequisite while installing IIB10, however if i want to link a remote queue manager to the existing Integration Node , how will i be able to do this ?

  9. Govindaraj Saravanan September 14, 2015

    I have followed the steps mentioned in the pdf file, but i am not able to send a message from the input queue to output queue. I have created two applications, one of them is working but the second one is not working. When i checked the queue manager’s application connection i didn’t find the queues that i created for the second application is not configured to the DataFlowEngine.exe, but the queues from the first application is configured to the DataFlowEngine.exe. I didn’t know how the queues from first application was configured successfully, hence help me in configuring queues with DataFlowEngine successfully.

Join The Discussion

Your email address will not be published. Required fields are marked *