WAS v8.5 > Deploy applications > Deploy messaging resources > Deploy enterprise applicationsDeploy enterprise applications developed as message-driven beans
We can deploy an enterprise application developed as a message-driven bean in WebSphere Application Server. Message-driven beans can be used as asynchronous message consumers. When a message arrives at the destination, the EJB container invokes the message-driven bean automatically without an application having to explicitly poll the destination.
- Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources. We can configure message-driven beans as listeners on a JCA 1.5 resource adapter, such as the default messaging provider or the WebSphere MQ messaging provider in WAS.
- Deploy an enterprise application to use message-driven beans with listener ports. Listener ports are stabilized. For more information, read the article on stabilized features. You should only deploy the application against a listener port for compatability with existing message-driven bean applications. Otherwise, you should deploy the application against JCA 1.5-compliant resources.
Subtopics
- Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources
Message-driven beans can be configured as listeners on a JCA 1.5 resource adapter, such as the default messaging provider or the WebSphere MQ messaging provider in WAS.- Deploy an enterprise application to use message-driven beans with listener ports
Define the listener ports for the application. For each message-driven bean in the application, configure the deployment attributes to match the listener port definitions. Install the application, specifying the name of the listener port to use for late responses.
Related
Programming for interoperation with WebSphere MQ
Programming to use message-driven beans
Samples documentation