Manage cluster configuration, project deployment, security and options like failover, affinities, and high availability using configuration files and directories.
Name | Description |
---|---|
<base-directory> | Base directory to which managers in this
cluster deploy projects. Holds workspaces, project instances,
project working directories, and log stores. By default, the
base directory in a local (Studio) cluster is the same as the
workspace. See also workspace and project working directory.
|
cluster.log | Cluster node log. Captures node-level and
cluster-level errors and event messages; each node’s log is
unique to that node. Resides in the same directory as <node-name>.xml and
cluster.log.properties.
|
cluster.log.properties | Cluster node log configuration file.
cluster.log.properties
is a log4j properties file; it resides in the directory where
the the node is started and where <node-name>.xml is located.
|
csi_boe.xml csi_kerberos.xml csi_ldap.xml csi_native_nt.xml csi_native_unix.xml csi_role_mapping.xml csi_rsa.xml |
Security configuration files.
|
ESP_HOME | Represents the
Event Stream Processor installation
directory. ESP_HOME is
also an environment variable and a configuration file macro.
|
esp_server.log | Project log. Captures errors and events in a
running project. Resides in the working directory for the
project.
|
examples | Examples directory. Stores sample
configuration files including <node-name>.xml, policy.xml, persistence.xml, log properties
files, and authentication files.
|
Input files for projects | Anything a project needs at runtime—for
example, input CSV files, ODBC drivers, or queueing clients.
|
Log store | Log store. Saves project input and output
data in case of failover.
|
<node-name>.xml | Cluster node configuration file. Created
automatically for clusters configured at installation, manually
for clusters created after installation. Defines a node as a
manager, a controller, or both, and configures security, port
communication, and caching.
|
<persistence-directory> | Persistence directory. Saves project and
workspace information when a node shuts down. The cluster
configuration file, <node-name>.xml, sets the persistence
directory’s path. All managers in a cluster must use the same
persistence directory.
|
policy.xml | Policy file. Defines access control policies
that specify user roles, the actions available to each role, and
the resources on which the actions can be performed.
|
<project-name>.ccl | Definition of a project in Continuous
Computation Language. A project has one <project-name>.ccl file.
When you edit the project in Studio, you modify the CCL or an
ancillary file. (The ancillary files store information about the
visual presentation of the project in Studio.)
|
<project-name>.ccr | Project configuration or CCR file. An XML
file that contains runtime and deployment configuration for the
project, including adapter, parameter, and binding definitions,
A project can have multiple CCR files, allowing you, for
example, to specify different adapters in different deployment
environments, or to change run-time parameter values.
|
<project-name>.ccx | The compiled CCL file. You must supply the
path to the CCX file when you deploy a project to a remote
(non-Studio) cluster. You do not need to view or edit the CCX
file.
|
Project working directory | Contains files generated by the project. May
also contain input files the project needs. See also workspace.
|
stdstreams.log | Standard streams log. Captures output
written to stdout and stderr, including SySAM licensing
information and messages from third party applications. Resides
in the working directory for the project.
|
security | Security directory. Stores Java keystores
for RSA,
policy
files for access control, and the csi_cluster.xml file for specifying security
authentication on the local cluster server. All components in a
cluster are subject to the security rules defined in the cluster
configuration file. To easily maintain consistent security
configurations among all nodes, SAP recommends that multiple cluster
managers running in the same cluster share a security folder.
|
service.xml | Service configuration file. Contains
database service definitions, including all the properties and
parameters required for the database connections needed by the
projects that run on this node or in this cluster. Every node
needs access to a service configuration file.
|
workspace | Directory where
ESP Studio stores project
files. You set the location during installation. By default, the
workspace in a local (Studio) cluster is the same as the base
directory. See also <base-directory> and project working directory.
|