Administer > Manage WebSphere Commerce features > Messaging system > WebSphere MQ


Configure WebSphere MQ for use with WebSphere Commerce

 

+

Search Tips   |   Advanced Search


  1. Identify the Queue Manager that WebSphere Commerce will use.

    To verify existence of queue manager...

    /opt/isv/mqm/bin/dspmq
    QMNAME(QM0.PR.US.CCAIQA64) STATUS(Running)

    The Queue Manager name is case-sensitive.

  2. Verify that the OS system user ID used to start WebSphere Commerce is also authorized for the Queue Manager.

  3. Identify the local message queues for the Queue Manager.

    Verify existence of queues...

    qlist | grep <QUEUENAME>

    To check queue depth high:

    print "display qlocal(<QUEUENAME>) QDEPTHHI" | mqsc | grep QDEPTHHI

    To check queue depth high event:

    print "display qlocal(<QUEUENAME>) QDPHIEV " | mqsc | grep QDPHIEV

    To check queue service interval high:

    print "display qlocal(<QUEUENAME>) QSVCINT " | mqsc | grep QSVCINT

    To check queue service interval high event:

    print "display qlocal(<QUEUENAME>) QSVCIEV " | mqsc | grep QSVCIEV

    Before you can run the qlist command, you may need to source...

    /opt/hd/ca/mars/scripts/cakms000.ksh

    To get queue configuration for each queue

    print "display qlocal (*) all" | mqsc

    The instructions in this chapter assume that the following local message queues are created:

    Queue Description
    hostname.error Default error queue. Collects erratic inbound messages.
    hostname.inbound Used by SendReceiveImmediate mode of the adapter for WebSphere MQ. Where the reply and response messages from the backend system should go.

    Commerce can optionally pick reply and response messages based on an outgoing request to a backend system.

    hostname.inboundp Any message arrive at this queue will be processed in parallel manner.
    hostname.inbounds Any message arrive at this queue will be processed in serial manner based on the message delivery sequence option of the queue.
    hostname.outbound Used for...

    Verify the operating system user ID used to start WebSphere Commerce is also authorized for the message queues. For instructions on authorizing a user ID for a WebSphere MQ message queue, refer to the WebSphere MQ documentation.

    The number of queues to define depends on the application with which WebSphere Commerce is integrated. These five queues are the minimum number of queues required for integration.

  4. For Client mode only, create a listener port for the Queue Manager you created.

  5. Configure WebSphere Application Server for use with WebSphere MQ.

  6. Add the non-root commerce user ID to the mqm user group.

    For Windows, add the Windows user ID used to start WebSphere Commerce to the mqm group.


+

Search Tips   |   Advanced Search