Show TOC

Cluster ConfigurationLocate this document in the navigation structure

The cluster database maintains configuration information for all nodes in the cluster.

The cluster database also holds policy configuration, and persists cluster cache data. There is one logical instance of the database per cluster.

The ESP installer creates a cluster database during installation, and prompts you to enter a user name and password for this database. This cluster database initially contains the configuration for a single ESP node. Because the database holds the configuration for a cluster, changes in database performance or function will directly impact the cluster. For this reason, consider a high availability configuration for the database.

A cluster must be running before you can deploy projects to it. To start a cluster, start manager nodes first, then controller-only nodes, using the streamingclusternode utility. The directory from which a node is started becomes the working directory for the node. The node looks for the cluster.log.properties file in the working directory. SAP recommends that you start each node from a separate working directory. You can also use streamingclusternode to deploy and retrieve cluster configuration files. For more information on streamingclusternode and its cluster options, see the SAP Event Stream Processor: Utilities Guide.


In this section:
    Role of the Installer in Cluster Configuration
    ESP uses a database-based cluster configuration, rather than a file-based cluster configuration. This database hosts configuration information for the cluster and is known as the cluster database. Several necessary components for the database-based configuration are installed during installation.
    Starting a Cluster
    Start a cluster by starting the cluster database and starting a node in the cluster. Starting a cluster is a prerequisite for running projects and logging into ESP Cockpit. In a test system, where you are running projects only on the Studio local cluster, you do not have to manually start a cluster.
    Cluster Persistence, Caching, and Multicast
    Cluster persistence, caching, and multicast are stored in the cluster database.
    Configuring Macros
    Macros are cluster-wide configuration file shortcuts for centralizing a repeated configuration, or for acquiring properties from the environment. You can edit or remove existing macros or create new ones.
    Configuring System Properties
    Edit, remove, and update cluster-wide system properties.
    Configuring Attributes
    Edit cluster-wide attributes, including Secure Sockets Layer (SSL), application heartbeat interval, multicast manager, and cluster persistence.
    Configuring High Availability Project Settings
    Edit, remove, and update properties for the High Availability (HA) project application type, with definitions for the base directory, host name, library directory, and security directory that the application uses.
    Configuring Project Settings
    Edit, remove, and update properties for the project application type, with definitions for the base directory, host name, library directory, and security directory that the application uses.
    Configuring Cluster-Managed Adapter Settings
    Edit, remove, and update properties for the toolkit adapter application type. Adapters that are cluster-managed are started and stopped independently of the project, and managed through the cluster.
    Configuring Key Store Settings
    Edit the key store settings for the cluster. The SAP ESP cluster key store is a repository of security certificates for accessing Event Stream Processor.
    Configuring Compiler Services
    Edit values for the compiler service if the node is a service provider.
    Configuring Discovery Services
    Edit values for discovery services if the node is a service provider.
    Configuring a Node
    Edit, remove, and update parameters of an existing ESP node.
    Configuring a Multinode Cluster
    Set shared locations and configure multiple nodes in a single cluster.
    File and Directory Infrastructure
    Use configuration files and directories to manage cluster configuration, project deployment, security and options like failover, affinities, and high availability.