Administer activation specifications and listener ports for MDBs
Overview
For message-driven beans that comply with Java EE JCA v1.5, use activation specifications. Do not use activation specifications if the MDB does not leverage a JCA v1.5 resource adapter. In this case, configure beans to use the message listener service, listener ports, and listeners.
- WAS v4 does not support deploying MDBs, so listener ports and activation specifications are not applicable.
- WAS v5 supports deploying EJB 2.0 (JMS only) MDBs deployed using listener ports.
- WAS v6 supports deploying...
- Default messaging (service integration bus) MDBs using activation specifications.
- WebSphere MQ MDBs using listener ports.
- Third-party messaging MDBs using either listener ports or activation specifications.
- WAS v7 supports deploying...
- Default messaging (service integration bus) MDBs using activation specifications.
- WebSphere MQ MDBs using listener ports or activation specifications.
- Third-party messaging MDBs using either listener ports or activation specifications
For WAS v7, listener ports are deprecated, so if possible, migrate MQ MDBs to activation specifications. For clusters with some v6.1 members, do not use activation specifications.
Related
Introduction: Messaging resources
Set a J2C activation specification
Set a J2C administered object
Set message listener resources for MDBs
Manage messaging with the MQ messaging provider
Migrate a listener port to an activation spec for use with the MQ messaging provider.
Manage messaging with a third-party or (deprecated) v5 default messaging provider
Secure messaging
Tuning messaging
Troubleshooting messaging
Programming to use asynchronous messaging
Migrate a listener port to an activation spec for use with the MQ messaging provider
Deploy an enterprise application to use MDBs against JCA 1.5-compliant resources
Deploy an enterprise application to use EJB 2.0 MDBs with listener ports
Manage messaging with the default messaging provider
Set an activation spec for the default messaging provider.
manageWMQ
Choose a messaging provider