Enabling multiple CHA servers on multiple Websphere Application Servers

Branch Transformation Toolkit allows you to deploy multiple EAR files that contain their respective CHA servers on multiple WebSphere(R) Application Server instances. To enable this feature, do the following:

  1. In the dse.ini file of each CHA server, set the value of supportMultipleCHAServers to true:
    <?xml version="1.0"?>
    <dse.ini>
      <kColl id="settings">
        <kColl id="cha-server">
          ...
          <field id=" supportMultipleCHAServers" value="true"/>
         </kColl>
      </kColl>
    </dse.ini>

    However, if you have only one EAR file deployed on the application server, enabling multiple CHA servers support becomes uneconomical because this feature will occupy extra resources. You can set the value of supportMultipleCHAServers to false to disable the feature and save system resources.

  2. In the dse.ini file of each CHA server, specify the location of the CHA server:
    <?xml version="1.0"?>
    <dse.ini>
      <kColl id="settings">
        <kColl id="cha-server">
          ...
          <field id="myLocation" value="iiop://hostname:2809"/>
         </kColl>
      </kColl>
    </dse.ini>
    This setting enables the toolkit to tell whether local or remote EJB reference should be used between CHA facades and the CHA servers.
  3. In the dse.ini file of the CHA server, set the value of rootLocation to true:
    <?xml version="1.0"?>
    <dse.ini>
      <kColl id="settings">
        <kColl id="cha-server">
          ...
          <field id="rootLocation" value="iiop://hostname:2809"/>
         </kColl>
      </kColl>
    </dse.ini>