7.3.3. JBoss Domain Controller – Failure and Promotion

Engineering Knowledge Manager

Installation Guide | Chapter 7: JBoss Domain Mode and Configuration | 7.3. Management |

7.3.2. Deploy the EKM Server Application |  | Chapter 8: Installing a Front-End Web Server
Prev |  | Next

### 7.3.3. JBoss Domain Controller – Failure and Promotion

In the event of failure of the JBoss domain controller, any JBoss slave can be manually promoted to assume the role of domain controller. Promotion of slave to domain controller is a manual process – automatic failover of the domain controller role is not currently supported in JBoss.

To promote a slave to domain controller, follow these steps on one cluster node:

1. Stop the EKM cluster node.

2. Edit the JBoss host controller configuration (see JBoss Domain Mode and Configuration).

   1. In the `domain-controller` element, replace the `remote` element (shown in bold):

          <domain-controller>
              <remote host="192.168.1.3" port="${jboss.domain.master.port:9999}"
                 security-realm="ManagementRealm" />
          </domain-controller>

      with a `local` element (shown in bold):

          <domain-controller>
              <local />
          </domain-controller>

   2. Under the `security-realms` element, remove the management user defined for this node (shown in bold):

          <management>
            <security-realms>
              <security-realm name="ManagementRealm">
                <server-identities>
                  <secret value="bm9kZTIhMTIz"/>
                </server-identities>

3. Locate the cached domain configuration and activate it. The cached domain configuration file is:

   `JBOSS_HOME/domain/configuration/domain.cached-remote.xml`

   Activate the domain configuration by renaming this file to: `ekm.xml`

4. Create management users on the new domain controller cluster node, following the instructions in Management, with these modifications:

   1. Create the admin user for accessing the JBoss Web Management Interface.

   2. For each slave cluster node, create a management user for the node.

      Save the output of the `add-user.(bat|sh)` script and note which user (cluster node) it is for. Specifically, you will need the secret element for the user, for example:

          <secret value="bm9kZTIhMTIz"/>

      If the slave cluster node is stopped, add the management user for the cluster node to the host controller configuration on the slave node as instructed in Management.

      If the slave cluster node is running, you will add the management user for the cluster node later.

5. Start the EKM cluster node.

The cluster node will now be running as a domain controller. The remaining slave cluster nodes must now be reconfigured to recognize the new domain controller.

On each slave cluster node, follow these steps:

1. Stop the EKM cluster node.

2. Edit the JBoss host controller configuration (see JBoss Domain Mode and Configuration):

   1. In the `domain-controller` element, update the `remote` element (shown in bold) to point to the IP address and port of the new domain controller:

          <domain-controller>
              <remote host="192.168.1.4" port="${jboss.domain.master.port:9999}"
                  security-realm="ManagementRealm" />
          </domain-controller>

   2. If you have not already done so in a previous step, add the management user for the cluster node.

3. Start the EKM cluster node.

The JBoss slaves should register with the new domain controller during startup.

Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.

Prev | Up / Contents | Next

Release 18.2 - © ANSYS, Inc. All rights reserved.