Java Message Service (JMS)

For applications using Java Message Service (JMS) that are connected to an on-premises JMS service provider, consider the connection needed to access your messaging provider. If you are using the WebSphere default messaging provider and your JMS queue resources were also moved to the cloud, then you might not need a connection to your on-premises messaging provider.

The following Java classes indicate use of JMS:

• javax.jms.ConnectionFactory
• javax.jms.QueueConnectionFactory
• javax.jms.TopicConnectionFactory
• javax.jms.XAQueueConnectionFactory
• javax.jms.XATopicConnectionFactory

The <res-type> element in the application.xml, ejb-jar.xml, or web.xml deployment descriptors with the following values also indicate use of Java Message Service (JMS):

• javax.jms.ConnectionFactory
• javax.jms.QueueConnectionFactory
• javax.jms.TopicConnectionFactory
• javax.jms.XAQueueConnectionFactory
• javax.jms.XATopicConnectionFactory

This rule is flagged once per Eclipse project or Java archive.

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:

• <cloud host>:<cloud port>/SYSTEM.DEF.SVRCONN (MQ)
• <cloud host>:<cloud port>:BootstrapBasicMessaging (WAS built-in JMS provider)
• tcp://<cloud host>:<cloud port> (ActiveMQ)

Alternatively, you can use IBM Event Streams as a cloud-based messaging service. For more information, see Event Streams.