You can configure the message-driven beans deployment attributes for an enterprise bean, to override the deployment attributes defined within the application EAR file.
Listener ports are stabilized. For more information, read the article on stabilized features. You should only configure your application against a listener port for compatability with existing message-driven bean applications. Otherwise, you should configure your application against JCA 1.5-compliant resources.
If you have existing message-driven beans that use the WebSphere MQ messaging provider (or a compliant third-party JMS provider) with listener ports, and instead you want to use EJB 3 message-driven beans with listener ports, these new beans can continue to use the same messaging provider.
This task assumes that you have an EAR file that contains an enterprise application, developed as a message-driven bean, that can be deployed in WebSphere® Application Server.
You configure the deployment attributes of a message-driven bean application by using an assembly tool. Detailed steps given in this task are for Rational® Application Developer, but other tools have very similar steps.
In this information ...Related concepts
Related tasks
Related information
| IBM Redbooks, demos, education, and more(Index) |