Configuring high availability for the Resource Adapter for JMS with WebSphere Application Server in a third party application server
For XA connections, the 搭配 WebSphere® Application Server 的 Resource Adapter for JMS must always connect to the same messaging engine in a bus. High availability is therefore an important consideration.
About this task
If you 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 搭配 WebSphere Application Server 的 Resource Adapter for JMS to connect to the bus. It is recommended 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.
Procedure
- Make the messaging engine highly available by deploying it to a cluster. For further information, see 服務整合高可用性和工作量分散配置
- Ensure that you 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 Deploying the 搭配 WebSphere Application Server 的 Resource Adapter for JMS to a third party application server and Deploying inbound connections for the 搭配 WebSphere Application Server 的 Resource Adapter for JMS.