WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources

Manage message-driven beans

We can manage the Java EE Connector Architecture (JCA) v1.5-compliant message-driven beans deployed as message endpoints, and we can manage the message listener resources for non-JCA MDBs deployed against listener ports.

Migrate WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. If the application runs on application servers earlier than WAS v7, do not migrate. For example, if we have an application server cluster with some members at v6.1 and some at a later version, you should not migrate applications on that cluster to use activation specifications until after you migrate all the application servers in the cluster to the later version.

To use MDBs with a messaging provider that does not have a JCA v1.5 or 1.6 resource adapter, we cannot use activation specifications. Configure beans against a listener port. Use listener ports if compatability with existing MDB applications is required. See Message-driven beans, activation specifications, and listener ports.

We can manage the following resources for MDBs:


Subtopics

Choose a messaging provider
Manage messaging with the WebSphere MQ messaging provider
Manage messaging with a third-party messaging provider
Manage messages with message endpoints
Configure an activation specification for a third-party JCA resource adapter
Configure an administered object for a third-party JCA resource adapter
Configure an activation specification for the default messaging provider
Manage messaging with the default messaging provider
Deploy an enterprise application to use message-driven beans with JCA 1.5-compliant resources
Deploy an enterprise application to use message-driven beans with listener ports


+

Search Tips   |   Advanced Search