Administer listener ports
Listener ports each define the association between...
- connection factory
- destination
- message-driven bean
To use message-driven beans with a messaging provider that does not have a JCA 1.5 resource adapter, we cannot use activation specifications and therefore configure the beans against a listener port. There are also a few scenarios in which, although you could use activation specifications, we might still choose to use listener ports.
We can use the WAS admin console to administer listener ports.
If configured as enabled, a listener port is started automatically when a message-driven bean associated with that port is installed. You do not usually need to start or stop a listener port manually.
- Create a new listener port.
- Set a listener port.
- Start a listener port.
- Stop a listener port.
- Delete a listener port.
Related concepts
Message-driven beans - listener port components
Migrate a listener port to an activation spec for use with the WebSphere MQ messaging provider
Deploy an enterprise application to use EJB 2.0 message-driven beans with listener ports
Set message listener resources for message-driven beans