Configure high availability for the Resource Adapter for JMS with WebSphere Application Server in a third party application server

For XA connections, the Resource Adapter for JMS with WebSphere Application Server must always connect to the same messaging engine in a bus. High availability is therefore an important consideration.

If we are using XA resources, a specific messaging engine must be targeted for connection to allow indoubt transactions to be recovered, if this becomes necessary. Therefore, the availability of the messaging engine is critical to the ability of the Resource Adapter for JMS with WebSphere Application Server to connect to the bus. IBM recommends that in this scenario the target messaging engine be made highly available by deploying it to a cluster so that in the event of a server failure the messaging engine will be failed over to an alternative server in the cluster.

This restriction does not apply to connections with no transactional context, or with local transactional context because in this case the transaction is always committed or rolled back immediately and there is therefore never an indoubt state.

1. Make the messaging engine highly available by deploying it to a cluster. For further information, see Service integration high availability and workload sharing configurations

2. Ensure that we have provided the connection factories with a list of provider endpoints for highly available bootstrap servers that the resource adapter can use to bootstrap to the required messaging engine. See also Deploy the Resource Adapter for JMS with WebSphere Application Server to a third party application server and Deploy inbound connections for the Resource Adapter for JMS with WebSphere Application Server.