Creating a WebSphere Java MQ transport configuration

You can create a transport configuration that describes the transport settings for a service request that uses the IBM® WebSphere® Java MQ protocol. Transport and security settings can be associated with any service request.

About this task

This topic has instructions to specify the MQ server settings. If you have a single MQ server, you can choose to use the Default Java MQ protocol configuration option. If, for a new request, you must point to another MQ server, you can use the instructions in this topic to create a new transport configuration.

Procedure

  1. Click Generic service client Open Generic Service Client and click the Transport tab.
  2. To create a new Java MQ transport configuration, in Configurations, select Java MQ.
  3. In Create Java MQ protocol configuration, specify a name for the transport configuration.
  4. Complete the following steps in the Settings tab:
    1. Host: Specify the host name or IP address of the MQ server.
    2. Port: Specify the port number that is used on the MQ server.
    3. Channel: Name of the MQ communication channel that is used for sending and receiving messages and specified on the server. This field is case-sensitive.
    4. Queue Manager: Name of the MQ queue manager as specified on the server.
    5. Optional: Use credential: To access the secure server, specify the login credentials that is needed by the connection.
  5. Optional: If necessary, complete the following steps in the SSL tab:
    • Select the Use MQ SSL check box when the connection to the Queue manager uses SSL.
    • Peer Name: Distinguished Name (DN) of the queue manager to be used by SSL. The Distinguished Name is available in the SSL certificate. In MQ, a DN pattern is specified by using the sslPeerName variable of MQEnvironment. Connections succeed only if Peer Name matches the pattern that is specified.
    • Cipher Suites: Select one of the available cipher suites to use for encrypting the transport communications.
    • Fips Required: This option specifies whether the requested cipher suite must use FIPS-certified cryptography in WebSphere MQ.
    • KeyResetCount: The total number of non-encrypted bytes that can be sent and received within an SSL conversation before the secret key is renegotiated. If left blank or set to zero (default), the secret key is never renegotiated. This value is ignored if no cipher suite is specified. Valid values are integers 0 - 999,999,999.
    • SSL Configuration: Select a SSL setting for the connection or click Configure SSL to create a new SSL configuration. See Creating SSL configurations.
  6. Optional: Use the Options tab to configure actions such as read, write, and browse on the selected MQ Queues. Click Edit to select the configuration options.
  7. Optional: Use the Advanced tab to specify the number of queue manager connections for reading messages, temporary destination settings, and to associate a reply with a request.
  8. To test the connection, click Test Transport and then click OK. You have created a new transport configuration to point to a MQ server.

What to do next

You can now send the Java MQ requests to the configured server. See Sending WebSphere Java MQ endpoint requests.
Feedback