Apama 10.7.2 | Deploying and Managing Apama Applications | Deploying Apama Components with Command Central | Administering Apama in Command Central | Configuration types that Apama components support | Configuration types that the Apama correlator supports
 
Configuration types that the Apama correlator supports
 
The correlator persistence properties
The correlator license key
The following table lists the configuration types that are specific to the Apama correlator component:
Configuration Type
Use to configure...
APAMA-ARGS
Use to configure command line arguments that are not represented by any other configuration type. For the correlator, the following properties are available:
*extraArgs. For more information, see Extra arguments.
*Logging properties. For more information, see Component logging.
*Persistence properties. For more information, see The correlator persistence properties.
COMMON-PORTS
Use to configure ports for Apama component instances. The available property for the correlator is port. For more information, see Component ports.
COMMON-LICENSE
Use to set the license key file assigned to the license key alias of the correlator run-time component. For more information, see The correlator license key.
COMMON-LICLOC
This configuration type contains the location of the license key file. After you set the license key file using the COMMON-LICENSE configuration type, the license key file information is available at APAMA_HOME/command-central/instances/correlator/instancename/ApamaCorrelatorLicense.xml. This license key location is stored in COMMON-LICLOC configuration type. This configuration type is read-only. This configuration type is not available in the web interface.
APAMA-ENVVAR
Use to define the environment variables. The defined variables are set when you start the instances. You must define the environment variables in the properties file. For more information, see Apama environment variables.
APAMA-ENGINE-CONNECT
Use to connect a source correlator (the sender) to a target correlator (the receiver). The target correlator will receive events from the specified channels of the source correlator. For more information, see Correlator connections.
APAMA-CORRELATOR-APP-MONITORING
Use to create, and monitor status and KPIs of an EPL application. The configuration values are a comma separated list of SUBCOMPONENT_ID strings. The SUMCOMPONENT_ID strings represent the EPL application names. The EPL files are injected into the correlator to publish the status and KPIs in Command Central. For more information, see Monitoring the KPIs for EPL applications and connectivity plug-ins.
APAMA-PROP-OVERRIDES
Use to override the properties that are set in correlator configuration files such as YAML configuration and properties files, JMS configuration files or distributed store configuration files.
For more information on YAML configuration, see Using YAML configuration files.
For more information on using properties files, see Using properties files.
For more information on distributed store configuration files, see Configuration files for distributed stores.
For more information on JMS configuration files, see Configuration files for JMS.
These properties will take precedence over any other correlator configuration properties. For more information, see Overriding correlator configuration.