Deploy inbound connections for the Resource Adapter for JMS with WAS
When deploying inbound connections, configure message-driven beans to use the Resource Adapter for JMS with WebSphere Application Server. A JMS activation configuration associated with one or more message-driven beans provides the configuration necessary for them to receive messages.
We can deploy message-driven beans within the application with a JMS activation configuration to access the Resource Adapter for JMS with WAS connection factories and destinations. When the message-driven bean is started, it uses the resource adapter to connect to the service integration bus, provided that the required messaging engine is available in WAS.
The Resource Adapter for JMS with WAS supports full two-phase XA transactional connections but it might also be run using local transactions or no transaction connections.
Tasks
- Configure the following properties for the activation configuration:
- Destination
- ProviderEndpoints
- DestinationType
- BusName
The Destination property value is the name of the destination from which the message-driven bean will be receiving messages.
See Configuration properties for the Resource Adapter for JMS with WAS for a description of these property names and other properties that might also be configured.
- Configure the following additional properties if the message-driven bean will use XA resources over the Resource Adapter for JMS with WAS connection.
- TargetType must be set to "ME"
- TargetSignificance must be set to "Required"
- Target value must be the name of the required ME
See Configuration properties for the Resource Adapter for JMS with WAS for a description of these property names and other properties that might also be configured.
These properties permit the recovery of indoubt transactions, should this be necessary. For further information about indoubt transactions, see Resolving indoubt transactions.