Manage cluster configuration, project deployment, and persistence using cluster and project configuration files.
Cluster management uses these files and directories:
- <nodename>.xml – the cluster configuration file is created automatically for clusters configured at installation, and manually for clusters created after installation. The cluster configuration file contains all the parameters needed for defining nodes as either managers or controllers, setting security, enabling port communication, caching, high-availability projects, and persistence.
- <projectname>.ccr – the project configuration file contains parameters for deploying the project in high-availability mode (active-active), defining controller and instance affinities, and failover intervals. You can enable projects for Active-Active deployment only if high availability is enabled in the cluster configuration file for the node on which the project is running.
- <base-directory> – (optional) the cluster configuration file allows you to set the base directory where workspace and project instances are stored.
- <persistence-directory> – the cluster configuration file allows you to enable persistence and define the directory that persists application and workspace settings across starts and stops of the nodes of
the cluster. If one manager in a cluster is enabled for persistence, all managers in the cluster must be enabled for persistence, as well as share the same directory. The directory name varies.
- <security> – the cluster configuration file references the Event Stream Processor security directory. This directory stores Event Stream Processor security files, such as the Java keystore file for RSA-protected server instances, LDAP policy files for access control, and the csi_no_security.xml file, which provides open security to ESP Server in the absence of other authentication modes. All components in a cluster are subject to the security rules defined in the cluster configuration file.