Deploying Adapter for webSphereMQ Assets

To deploy webMethods MQ Adapter related driver jars to IBM® webMethods Cloud Container, you can select the core MQ adapter package WmMQAdapter from Designer, which will deploy the contents only from <webM\_Home\>\\Integration Server\\instances\\<instance\_Name\>\\packages\\WmMQAdapter\\code\\jars folders.

To enable the assets such as Adapter Connections, Listeners and Listener Notifications on IBM webMethods Cloud Container, ensure that you set the State After Deployment value to enable during deployment from Designer. The state of the assets must be disabled in on-premises before deploying to IBM webMethods Cloud Container to ensure that the on-premises Integration Server messages from IBM WebSphereMQ server are not processed. To deploy webMethods MQ Adapter and asset packages to IBM webMethods Cloud Container, see Deploying Packages and Configuration Assets to Cloud Container.

Note:
  • To connect to an on-premises IBM WebSphereMQ server using VPN, you must substitute the serverName to IP address of the server, as the hostname of the server cannot be resolved.
  • Keep all driver jars in <webM\_Home\>\\Integration Server\\instances\\<instance\_Name\>\\packages\\ WmMQAdapter\\code\\jars\\static folder and then deploy to IBM webMethods Cloud Container.
  • Set the proper package dependency between adapter asset packages and the core Adapter package.

Limitations

Two way SSL connections are not supported.