Message-Driven Beans (MDB)

For applications using Message-Driven Beans (MDB) that are connected to an on-premises messaging service provider, consider the connection needed to access your messaging provider.

The following Java annotations and method calls indicate use of Message-Driven Beans (MDB):

• javax.ejb.MessageDriven
• javax.ejb.MessageDrivenBean
• javax.ejb.MessageDrivenContext
• javax.ejb.ActivationConfigProperty

The following deployment descriptor element also indicates use of Message-Driven Beans (MDB):

• <message-driven> element in the ejb-jar.xml file.

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.