Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider > Interoperating with a WebSphere MQ network > Use a WebSphere MQ server to integrate WebSphere MQ queues into a bus

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 admin 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 by using the admin console as described in this task, or by 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, you can optionally override the server connection settings with the bus connection settings. This means that you can create a WebSphere MQ server definition that is specific to a bus, yet reusable in a multiple bus topology.

Procedure

1. Start the admin 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 you create 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, WAS 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 you are using Resource Access Control Facility (RACF) as the security manager on your WebSphere MQ for z/OS system, and using bindings transport mode, specify in uppercase characters the user names and passwords for authentication aliases. If you are using RACF and client transport mode, you 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 you 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 your changes to the master configuration.

6. Restart the application server.

What to do next

You are now ready to add the new WebSphere MQ server as a member of a bus.
WebSphere MQ server: Connection and authentication
User identification
WebSphere MQ server: Transport chain security

Related

createSIBWMQServer command
WebSphere MQ servers [Collection]
WebSphere MQ server [Settings]

+

Search Tips   |   Advanced Search