Deploying and verifying IBM MQ bridge for HTTP on WebSphere Application Server V6.1.0.9

Use the following example to prepare a deployment of IBM MQ bridge for HTTP to run the sample HTTP Java programs. The deployment is on WebSphere Application Server V6.1.0.9.


Before you begin

  1. Follow the instructions in Install, configuring, and verifying IBM MQ bridge for HTTP, to copy WMQHTTP.war onto a server accessible to your installation of WebSphere Application Server.
  2. Configure a queue manager, and a queue, to use to test the configuration:

    • In the example, the queue manager is configured as using the values in Table 1:
      Table 1. Queue manager configuration
      Object Value
      Host name itso-01
      Queue manager QM1
      Local queue HTTPTESTQ
      Server connection channel MYSVRCON. Configure an MCA user ID with sufficient authority to read and write to HTTPTESTQ.
      Listener port 1414
  3. Start the queue manager and the listener
  4. Place a test message onto HTTPTESTQ. For example:
    1. Start IBM MQ Explorer.
    2. In the list of local queues for QM1, right-click HTTPTESTQ > Put test message > type First Message > Put message > Close
  5. Start the application server and sign on to the Integrated Solutions Console.


About this task

The example shows the steps to take if you are running WebSphere Application Server V6.1.0.9 as our application server. If you are running a different version of WebSphere Application Server, or running a different application server, the steps are different. WebSphere Application Server V6.1.0.9 is pre-configured with IBM MQ installed as a message provider, using the IBM MQ MQI client libraries. If IBM MQ is not pre-configured as a messaging provider, or if you want to use IBM MQ server bindings, you need to install and configure the IBM MQ resource adapter for JEE into our application server.

Follow the instructions to deploy IBM MQ bridge for HTTP onto WebSphere Application Server V6.1.0.9, and verify the deployment using a browser:


Procedure

  1. In the navigation pane, click Resources > JMS providers > IBM MQ messaging provider.

    We can configure at either Node, Cell, or Server level, depending on your WebSphere Application Server deployment. The example uses Server level deployment.

  2. Under Additional properties, click Connection factories > New.
  3. In the JMS providers form, provide the information in Table 2, or alternatives of your choosing, click Apply> Save.
    Table 2. Set or modify the following fields
    Field Value
    Name WMQHTTPBridge
    JNDI Name jms/WMQHTTPJCAConnectionFactory
    Queue manager QM1
    Host itso-01
    Port 1414
    Channel MYSVRCON
    Transport type CLIENT
  4. In the navigation pane, click Applications > Install New Application.
  5. Insert the path to WMQHTTP.war into the form, and provide a Context root, click Next.
    1. The Context root is optional. mq is the default Context root for the sample HTTP applications.
    2. The Context root forms part of the URI identifying IBM MQ bridge for HTTP. We can omit the Context root, or change it later.
  6. On the Select installation options page of the installation wizard, we do not have to change any of the defaults, click Next.
  7. On the Map modules to servers page, select a Cluster or Server, check the Select box, click Apply> Next.
  8. On the Map resource references to resources page, in the javax.jms.ConnectionFactory form, click Browse... on the IBM MQ bridge for HTTP row.
  9. On the Enterprise Applications > Available resources page, select WMQHTTPBridge, click Apply.
  10. Back in the javax.jms.ConnectionFactory form, select the authentication method.
    1. For the example, choose None, click Apply. The other options require additional configuration.
  11. Check the Select check box for IBM MQ bridge for HTTP, click Next> Next > Finish > Save
  12. In the navigation pane, click Applications > Enterprise Applications.
  13. Check the selection box for WMQHTTP.war, click Start.
  14. Open a browser window. Type http://itso-01:9080/mq/msg/queue/HTTPTESTQ, using the appropriate host name and port.


Results

The browser window displays First Message, if the configuration is successful.


What to do next

Run the sample HTTP Java applications.