Reconfigure the Codar service

Reconfigure the Codar service to start, restart, and stop Codar using the standalone-fullha.xml configuration file.

Caution: You must stop the Codar service before reconfiguring it.
  1. Open a command prompt.
  2. Stop the Codar service by running the service codar stop command.
  3. Edit the <codar_home>/scripts/csa_env.conf (for Linux) or the <codar_home>\bin\service.bat (for Windows) file:

    For Linux:

    1. Locate the Toggle below two lines to run Codar in HA mode comment.

    2. Below this comment, comment out the export CSA_DEPLOY_MODE=standalone.sh # Standalone Mode line:

      #export CSA_DEPLOY_MODE=standalone.sh # Standalone Mode
    3. Uncomment the export CSA_DEPLOY_MODE="standalone.sh -c standalone-full-ha.xml -u [MULTICAST_ADDRESS]" # HA Mode line.

      where [MULTICAST_ADDRESS] is the UDP multicast address used by the JGroups subsystem on JBoss for communication between nodes. The JGroups subsystem establishes the cluster and manages membership of nodes in the cluster. Multicast addresses fall in the range between 224.0.0.0 and 239.255.255.255 (for example, 230.0.0.4). All nodes in a cluster must use the same multicast address. If you are configuring more than one cluster in your domain, use a different multicast address for each cluster.

      If the environment that you are using to set up the cluster does not support multicast messaging, the JGroups subsystem can be configured to use multiple TCP unicast messages. See "Configure the TCP Communication Channel on JGroups" below for more information. If you use multiple TCP unicast messages, do not specify the -u [MULTICAST_ ADDRESS] option in the csa_env.conf file.

    For Windows:

    1. Locate the two occurrences of standalone.bat.
    2. Insert the -c standalone-full-ha.xml command line option into the call standalone.bat > .r.lock >> run.log 2>&1 command line.
  4. Start the Codar service by running the service codar start command.