Through the Multi-Server Manager, it is possible to view the servers that are active members of a cluster.

In this type of environment, servers exchange messages that can be informative or trigger actions for all active servers.

The API lumis.portal.cluster can be used to customize communication between servers, indicating the type of messages, type of operations, and in which directories these operations will be performed. These operations are responsible for the actions taken (positive or negative).

The product was implemented using the higher-level API lumis.portal.filesystem for performing operations that make changes to the filesystems of all active servers (more specifically in the following directories lumisdata/def, lumisdata/data, and www). Such operations can include: adding or removing files, cache clearing, memory synchronization, file copying, among others.

The fact that solution files are located in those directories does not mean they will be automatically replicated. In other words, files created manually in such directories will not be replicated unless it is implemented to do so.

The functionalities that are part of the product that support multi-server implement the necessary replications or communications for their proper functioning in this scenario. Customized services or other components executed in the portal must be implemented to support multi-server as needed.

Permissions

• Manage service instance: Allows management of all data of this service instance, including deleting it entirely.
• Edit service instance content: Allows management of all data of this service instance with publisher profile.
• View service instance: Allows viewing public data of this service instance.

Interfaces

• Cluster Members
• Configuration