7.1. Domain Mode

Engineering Knowledge Manager

Installation Guide | Chapter 7: JBoss Domain Mode and Configuration |

Chapter 7: JBoss Domain Mode and Configuration |  | 7.2. Configuration
Prev |  | Next

## 7.1. Domain Mode

In a JBoss domain, multiple instances of JBoss work together and are managed centrally by one JBoss instance which is called the “domain controller”. Other JBoss instances which are members of the domain are known as "slaves".

In an EKM server, the EKM cluster primary node is initially configured as the JBoss domain controller. Non-primary nodes are configured as slaves. The domain controller provides centralized configuration and management for all JBoss instances in the domain.

When a JBoss instance is operated in domain mode, it executes the following processes:

- JBoss Process Controller (“Process Controller”)

- JBoss Host Controller (“Host Controller”)

- JBoss Application Server (“Application Server”)

The Process Controller is a process that manages and starts/restarts other processes. This process and its configuration are simple; we do not need to be concerned with it.

The Host Controller process is more interesting; this process controls the domain membership of the JBoss instance, and launches a JBoss Application Server, which executes the EKM server application. In a JBoss domain, one host controller serves as the domain controller, and the other host controllers are slaves. The domain controller maintains the master copy of the JBoss Application Server configuration, and distributes it to all the host controllers in the domain. Each host controller has its own configuration file, which configures the network settings, domain membership, and defines which Application Servers to launch, and what applications to run on them.

JBoss Application Server processes are launched by the host controller, according to the configuration of the host controller. These Application Server processes execute applications under the management of the domain controller. The EKM server application is executed by all JBoss instances in the domain. A configuration called the “domain configuration” defines the configuration for the Application Servers where hosted applications, such as EKM sever, execute.

The JBoss domain controller provides the following centralized management services for all JBoss instances in the domain:

- Centralized management of the JBoss domain configuration.

- Centralized management of JBoss instances via the JBoss CLI.

- Centralized management of JBoss instances via the JBoss Web Management Interface.

Some of the management features include:

- Deployment of applications, such as the EKM Server web application.

- Access to JBoss logs.

- Access to runtime metrics and statistics.

The role of the JBoss domain controller is to provide centralized management functionality only. It is not necessary for the JBoss domain controller to be running for slaves to execute application servers, run deployed applications, and serve requests. In terms of EKM functionality, if the JBoss domain controller is unavailable for any reason, any slaves in the domain will continue to run (in the case of a multi-node EKM server) and serve EKM requests. In the event of failure of a domain controller, a slave can be promoted to domain controller to restore domain controller functionality.

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.