Use these tasks to manage resources used to support message-driven beans. These tasks are in addition to the tasks for administering resource adapters, JMS providers and the resources they provide.

Why and when to perform this taskYou can use the WebSphere administrative console to configure the following resources for message-driven beans:

• J2C activation specifications for JCA 1.5-compliant message-driven beans. Activation specifications must be provided when the application's resources are configured using the default messaging provider or any generic J2C Resource Adapter that supports inbound messaging.

• The message listener service, listener ports, and listeners for EJB 2.0 message-driven beans deployed against listener ports. Listener ports must be provided when using the JMS providers: V5 Default Messaging, WebSphere MQ, or Generic.

You can update the configuration data at any time, but some updates only take effect when the appropriate server is next started.

For information about administering support for message-driven beans, see the following topics:

• Configuring JMS activation specifications, default messaging provider

• Configuring a J2C activation specification

• Configuring a J2C administered object

• Configuring message listener resources for EJB 2.0 message-driven beans

For other information about administering JMS providers and the messaging resources they provide, see the list of related topics.

Related tasks
Deploying an enterprise application to use message-driven beans against JCA 1.5-compliant resources
Deploying an enterprise application to use EJB 2.0 message-driven beans with listener ports
Throttling of inbound message flow for JCA 1.5 message-driven beans
Configuring MDB throttling for the default messaging provider