[JMS 2.0]

Using the IBM MQ resource adapter with the WebSphere Liberty IBM MQ messaging provider

The WebSphere® Liberty IBM® MQ messaging provider allows Java Message Service (JMS) applications running inside the application server to use IBM MQ systems as an external provider of JMS messaging resources.

In this configuration, the IBM MQ resource adapter is tightly coupled with the WebSphere Liberty IBM MQ messaging provider and provides the following functionality:
  • The ability to pause messaging endpoints after a number of sequential delivery failures.
  • Full support for XA transactions when using client channel definition tables (CCDT) with outbound messaging (this support is not available for activation specifications).
  • [z/OS]On z/OS®, the ability to run Java batch applications.
  • Full trace integration, where the IBM MQ resource adapter trace is written to the WebSphere Liberty trace files.

Features needed to use the IBM MQ resource adapter with the WebSphere Liberty IBM MQ messaging provider

To use the IBM MQ resource adapter with the WebSphere Liberty IBM MQ messaging provider, you must enable the WebSphere Liberty wmqJmsClient-2.0 feature. For more information, see the following topics in the WebSphere Liberty product documentation:
If the IBM MQ resource adapter needs to create secure TLS connections to a queue manager, you must also enable the WebSphere Liberty transportSecurity-1.0 feature. For more information on this feature, see the following topics in the WebSphere Liberty product documentation:
Note: Depending on what the application is doing, other features might be required. For more information, see the WebSphere Liberty product documentation.

You can use the IBM MQ resource adapter installation verification test program to check that the IBM MQ resource adapter has been installed correctly. For more information, see Verifying an IBM MQ resource adapter installation.

Restrictions when using the wmqJmsClient-2.0 feature

The following restrictions apply to the resource adapter when using the wmqJmsClient-2.0 feature:
  • The IBM MQ classes for Java are not supported. For more information, see Running IBM MQ classes for Java applications within Java EE.
  • The IBM MQ resource adapter has a transport type of BINDINGS_THEN_CLIENT. This transport type is not supported.
  • Looking up JMS administered objects (connection factories and destinations) from external JNDI repositories, such as LDAP or a file system repository, is not supported. Applications must use JMS administered objects that are defined in the WebSphere Liberty configuration.

Pausing messaging endpoints after a number of sequential delivery failures

The WebSphere Liberty IBM MQ messaging provider can be configured to pause message endpoints, and stop messages from being delivered to message-driven bean (MDB) applications if a number of sequential delivery failures occur. For more information on how to configure this, see IBM MQ message-driven bean pause in WebSphere Liberty.

XA transaction support with client channel definition tables

When using the WebSphere Liberty IBM MQ messaging provider to do outbound messaging, you can make use of queue manager groups within the client channel definition table (CCDT) in conjunction with XA transactions. This means that it is possible to make use of workload distribution and availability, provided by queue manager groups, whilst maintaining transaction integrity.

In the event of connectivity errors to a queue manager, the queue manager needs to become available again so that the transaction can be resolved. The transaction recovery is managed by WebSphere Liberty, and you might need to configure the transaction manager, so that an appropriate period of time is allowed for the queue managers to become available again. For more information, see Transaction manager (transaction) in the WebSphere Liberty product documentation.

[z/OS]

Running Java batch applications on z/OS

On z/OS, you can use the WebSphere Liberty IBM MQ messaging provider in a Java batch environment. For more information, see the following topics in the WebSphere Liberty product documentation: