+

Search Tips   |   Advanced Search

Create a WebSphere MQ server definition

A WebSphere MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS ) queue-sharing group. To create a WebSphere MQ server definition, you use the console to define the server connection and quality of service properties.

Decide which method to use to configure these resources. We can create a new WebSphere MQ server definition using the console as described in this task, or using the createSIBWMQServer command.

A WebSphere MQ server definition defines the connection to an underlying WebSphere MQ queue manager or queue-sharing group and the associated queues.

When you subsequently add the server as a member of a service integration bus, we can optionally override the server connection settings with the bus connection settings. This means that we can create a WebSphere MQ server definition that is specific to a bus, yet reusable in a multiple bus topology.

  1. Start the console.

  2. Complete either of the following sub-steps:

    1. Navigate to Servers -> New server, choose a server type of "WebSphere MQ server", then click Next.

    2. Navigate to Servers -> Server Types -> WebSphere MQ servers, then click New.
    The WebSphere MQ server [Settings] form is displayed.

  3. Complete the fields as required.

    For more information, refer to the WebSphere MQ server [Settings] form and the following notes:

    Name

    The name that you use for this WebSphere MQ server definition must be unique.

    UUID

    This identifier is assigned automatically when creating a new WebSphere MQ server definition.

    Use bindings transport mode if available

    To connect to a WebSphere MQ queue manager or queue-sharing group in bindings mode, WebSphere Application Server needs to know where to load native libraries from. This information is stored in the Native library path property of the WebSphere MQ messaging provider. To use a direct binding to WebSphere MQ, rather than a TCP/IP network connection, select this option and configure the Native library path property as described in Configure the WebSphere MQ messaging provider with native libraries information.

    If we are using Resource Access Control Facility (RACF ) as the security manager on the WebSphere MQ for z/OS system, and using bindings transport mode, specify in uppercase characters the user names and passwords for authentication aliases. If we are using RACF and client transport mode, we can specify the user names and passwords in either upper or lowercase characters.

    Test connection

    After we have configured the Connection properties, click this button to test the connection to WebSphere MQ.

    Trust user identifiers received in messages

    Select this option if we do not want the user IDs in messages to be overwritten with the administrative name of the WebSphere MQ server.

    JAAS - J2C authentication data

    This item is not available until after the WebSphere MQ server definition has been created.

  4. Click OK to confirm.

  5. Save the changes to the master configuration.

  6. Restart the application server.


What to do next

We are now ready to add the new WebSphere MQ server as a member of a bus.


Subtopics


Related concepts

  • WebSphere MQ server: Connection and authentication
  • User identification
  • WebSphere MQ server: Transport chain security

  • createSIBWMQServer command


    Related information:

  • WebSphere MQ servers [Collection]
  • WebSphere MQ server [Settings]