Over the past year or so, the MQ support teams have seen a number of customers getting confused about how to use the IBM MQ resource adapter and resource adapter for Jakarta Messaging with WebSphere Liberty. For example, customers are not sure whether they should deploy the resource adapters using the wmqJmsClient-2.0 feature, the wmqMessagingClient-3.0 feature, or as a generic resource adapter. 

Based on the feedback, we've spent the last few months adding a lot more information to the MQ documentation to help with this. The "WebSphere Liberty and the IBM MQ resource adapters" topic discuss the various options that are available to deploy the resource adapters into WebSphere Liberty, and the "Installing the IBM MQ resource adapters" and "Verifying an IBM MQ resource adapter installation" contain child topics which provide step-by-step instructions for each option showing how to install the IBM MQ resource adapter and resource adapter for Jakarta Messaging, and use the installation verification test (IVT) program to make sure everything is working as expected.

In addition to this, it is worth mentioning that the MQ 9.4.3 (or later) resource adapters will log a message when they start up showing how they have been deployed. If the adapters have been installed using either the wmqJmsClient-2.0 or wmqMessagingClient-3.0 features, then they will write the following message to the WebSphere Liberty messages.log file:

The IBM MQ resource adapter has been deployed in WebSphere Liberty using the WebSphere Liberty IBM MQ messaging provider.

If they have been deployed as a generic resource adapter, then they will write the message shown below to an mqjms.log file in the configuration directory for your WebSphere Liberty server:

The IBM MQ resource adapter has been deployed in WebSphere Liberty as a generic resource adapter.

I hope this helps! If you spot anything in the updated docs that you think needs some extra clarification, let me know and we can add it in.