Configure message listener resources for message-driven beans
Overview
Use the following tasks to configure resources needed by the message listener service to support message-driven beans for use with a JMS provider that does not have a JCA 1.5 resource adapter.
For JMS messaging, message-driven beans can use a JMS provider that has a JCA 1.5 resource adapter, such as the default messaging provider that is part of WAS V6. With a JCA 1.5 resource adapter, you deploy EJB 2.1 message-driven beans as JCA resources to use a J2C activation specification. If the JMS provider does not have a JCA 1.5 resource adapter, such as the V5 Default Messaging and WebSphere MQ, configure JMS message-driven beans against a listener port (as in WAS V5).
If you want to deploy an enterprise application to use JMS message-driven beans with a JMS provider that does not have a JCA 1.5 resource adapter, use the following task descriptions:
- Configure the message listener service
- Add a new listener port
- Configure a listener port
- Delete a listener port
- Configure security for EJB 2.0 message-driven beans
- Administer listener ports
See also
Configure the message listener service
Create a new listener port
Configure a listener port
Delete a listener port
Configure security for message-driven beans that use listener ports
Administer listener ports
Message-driven beans - listener port components