Vendor specific messaging

For applications using vendor specific messaging APIs, consider the connection needed to access your messaging provider.

The following Java classes indicate use of a third-party messaging provider:

Each vendor specific messaging API type referenced by an application will only be flagged once per Eclipse project (or Java archive). For example, if com.ibm.mq.MQQueue and org.apache.activemq.Connection APIs are both used in an Eclipse project, you will get two results for that project. This will help identify which technologies your application is using.

How to Resolve

If your application is able to directly access the messaging provider, no further action is required.

Otherwise, you can use a VPN tunnel, such as the IBM Secure Gateway for IBM Cloud, to create a secure connection to your existing on-premises messaging provider. For more information about configuring a secure connection, see Configuring a VPN. After configuring your gateway, connect your application to the new destination by using the cloud host and port number that is provided when you created the destination. The following URLs are examples of messaging provider URLs:

For more information about using third-party messaging providers with WebSphere Application Server, see