Multiple CHA Servers for one application

Branch Transformation Toolkit allows you to use multiple CHA servers for your application, and share data among these CHA servers. This feature enables you to add a new EAR package for your application without having to stop those EAR files that are currently running.

As shown in the figure below, there are three EAR files deployed on the WebSphere(R) Application Server instance carrying out different tasks. Each EAR package has its own CHA server (and also Business Process Component, Single Action EJBs, and so on) and the CHA servers can share data between each other.

A chart showing how CHA servers on a single WebSphere Application Server instance work together

In this case, you can have the root CHA context residing on CHA server A, and when you dynamically deploy the EAR package for Business Task C, which contains CHA server C, you can chain the CHA session contexts residing on CHA server C to the root context residing on CHA server A. Note that you can have more than one CHA servers but the root context must reside on one single CHA server.

Here's how these CHA servers work together: