IBM MQSeries transport configuration

You can use the MQSeries transport as a trading or an application transport.

Prerequisites

To use this transport, on the MQSeries server side, the following elements must be properly configured:

• Queue manager
• Queues
• Channel
• Listener
• Queue manager key database (for SSL connections)
• Certificate (for SSL connections)

Note on MQ Server client authentication configuration

Activator supports MQSeries client authentication on the trading pickup side only. It does not support client authentication on the application side. When you set up the connection between an application pickup and an MQSeries Server, be sure to disable the option requiring client authentication on the IBM MQ Server side.

Exchange point configuration

Complete the following fields in the exchange wizard to configure this transport:

• MQSeries connection type – Select an option:
  • Client connection – Select this option to use a channel connection, on the local machine or via the network, to connect to a queue manager.
  • Server binding – Select this option to use an API connection, via shared memory, to a local queue manager.
• MQSeries server – Enter the fully qualified domain name or IP address of the MQSeries host.
• Multi-instance queue manager – Select this option if you are using an MQSeries multi-instance queue manager. See WebSphere MQ multiple instances .
• MQSeries standby server – Enter the MQSeries standby server address.
• Port – Enter the port where the application listens for incoming documents. Default = 1414
• Channel – Enter the name of the MQSeries communications channel configured on the MQSeries server.
• Queue name – Enter the name of the MQSeries queue that receives incoming documents.
• Queue manager – Enter the name of the MQSeries queue manager.
• Convert data – Select this option if you want to convert the characters set of messages received from a queue to the set specified in the Characters set field. Clear the check box to turn off data conversion. This setting does not apply to messages outbound to a queue.
• Characters set – Specify the character set used by the queue manager. This number should match the number used by the queue manager. Default = 819
• This server requires a user name and password – If the MQSeries server requires a user name and password for connections, select this option, and then complete the fields:
  • User name – Enter the user name for connecting to the server
  • Password – Enter the password for connecting to the server
  • Confirm password - Confirm the password
• Use SSL to connect to the IBM MQSeries server – Select this option if you want to use SSL on connections to this MQSeries server.
• Note: For SSL you must add a trusted certificate for access to the IBM MQSeries server after completing the configuration of this delivery exchange.
• When you select this option you must also complete the Select the SSL cipher suite field. From the drop down list, select the SSL cipher suite to use for the connection. The value must match the cipher suite that is configured for the channel on the MQSeries server. The following cipher suites are displayed, however not all of these suites are currently supported.

• Activator JSSE cipher suite	Cipher specification (MQSeries name)
  SSL_RSA_EXPORT1024_WITH_DES_CBC_SHA	DES_SHA_EXPORT1024
  SSL_RSA_EXPORT1024_WITH_RC4_56_SHA	RC4_56_SHA_EXPORT1024
  SSL_RSA_EXPORT_WITH_RC4_40_MD5	RC4_MD5_EXPORT
  SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5	RC2_MD5_EXPORT
  SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA	FIPS_WITH_3DES_EDE_CBC_SHA
  SSL_RSA_WITH_3DES_EDE_CBC_SHA	TLS_RSA_WITH_3DES_EDE_CBC_SHA
  SSL_RSA_WITH_AES_128_CBC_SHA	TLS_RSA_WITH_AES_128_CBC_SHA
  SSL_RSA_WITH_AES_256_CBC_SHA	TLS_RSA_WITH_AES_256_CBC_SHA
  SSL_RSA_WITH_DES_CBC_SHA	DES_SHA_EXPORT
  SSL_RSA_WITH_NULL_MD5	NULL_MD5
  SSL_RSA_WITH_NULL_SHA	NULL_SHA
  SSL_RSA_WITH_RC4_128_MD5	RC4_MD5_US
  SSL_RSA_WITH_RC4_128_SHA	RC4_SHA_US

Click Next if you want to name the exchange. Otherwise, click Finish.

Related topics:

• Community trading pickups and partner deliveries
• Modify an MQSeries pickup or delivery
• WebSphere MQ multiple instances