- HP OpenView Event Correlation Services Standalone Engine
ecsd [-e filepath] [-F] [-i instance] [-L mask] [-m filepath] [-T mask] [-C mask] [option...] [-? |-h]
ecsd [-install |-remove | -console] [-e filepath] [-F] [-i instance] [-L mask] [-m filepath] [-T mask] [-C mask] [option...] [-? |-h]
ecsd is the HP OpenView Event Correlation Services (ECS) standalone correlation engine. ecsd uses the Event IO (EIO) API to receive events from and forward events to user applications.
The default behavior of ecsd is to run as a daemon.
ecsd is controlled with the ecsmgrcommand.
The configuration of ecsd including streams, circuits, data/factstores and their relevant state is automatically restored from the default startup configuration file (Unix: $OV_CONF/ecs/instance/config, Windows NT: %OV_CONF%\ecs\instance\config). If the file is not present, ecsd starts up in a reset state. See -restore_config for details.
The default policy of the correlation engine is to output events not selected for input by any of the enabled (running) correlation circuits. This policy can be controlled with the ecsmgr -policy command.
The following options can be used to influence the behavior ofecsd:
-install
ecsd as a Windows NT service. The ecsd service must be installed before it can be started. To install an ecsd service, use the following command:
ecsd.exe -install
Any additional options will be ignored.
-remove
ecsd service from a Windows NT system. To remove an ecsd service, use the following command:
ecsd.exe -remove
Any additional options will be ignored.
-console
ecsd should run as a foreground console application. To run ecsd as a background process, start it using the Services option in the Windows NT Control Panel. Note that the ecsd service must be installed using the -install option before you can start it. For information on installing the ecsd service, see the -install option above.
-e path/ed.conf
ed.conf file.
-F
ecsd to run in the foreground, rather than as a daemon process.
-I instance
instance uniquely identifies a correlation engine instance running on a machine. If this option is not specified, a default engine instance of 1 is used. If a duplicate correlation engine instance is specified, undefined behavior will result.
-L mask
ecsmgr -log option. See the ecsmgr reference page for further details. If this option is not specified, an engine log mask of 0x7 is used.
-m path/MDL_metadata
-reset
$OV_CONF/ecs/instance/config, Windows NT: %OV_CONF%\ecs\instance\config).
-restore_config [configfile]
configfile if specified or from the default startup configuration file (Unix: $OV_CONF/ecs/instance/config, Windows NT: %OV_CONF%\ecs\instance\config) otherwise.
This command assumes that circuits and data/factstores will be found in the same place as when the configuration was saved. If an error occurs during restoration, the engine will keep going to restore as much as possible.
-T mask
ecsmgr(1m) -trace option. If this option is not specified, an engine trace mask of 0 is used.
-C mask
-T option. The set of components is specified as a 32-bit mask. If this option is not specified, all components will be traced.
-? | -h
ecsd usage message.
ecsd returns 0 upon normal completion and >0 if an error occurred.
To start a standalone correlation engine as a daemon process:
ecsd
To start a standalone correlation engine in the foreground:
ecsd -F
To set the default logging level to DISASTER and ERROR messages only:
ecsd -L 0x3
ecsd outputs diagnostic messages to its error log. If the error logging subsystem cannot be initialized, then ecsd will report a message to the standard error output. If ecsd has been started as a daemon, stderr output may appear in the ecsd.stderr file specified below.
The environment variables below represent universal pathnames that are established according to your shell and platform requirements. See the ovenvvars(1) reference page for information on universal pathnames for your platform and shell. For Windows NT platforms, substitute the environment variables in Windows NT format. For example, substitute $OV_LOG with %OV_LOG%.
$OV_LOG/ecs/instance/ecsd.log*
instance.
$OV_LOG/ecs/instance/ecsd.trc*
instance.
$OV_LOG/ecs/instance/ecsd.stderr
instance number. This is only applicable if the correlation engine is running as a daemon.
$OV_LOG/ecs/instance/ecsin.evt*
instance.
$OV_LOG/ecs/instance/sname_sout.evt*
sname in engine instance instance.
$OV_LOG/ecs/instance/sname_sdis.evt*
sname in engine instance instance.
$OV_LOG/ecs/instance/cname_cout.evt*
cname in engine instance instance.
$OV_LOG/ecs/instance/cname_cdis.evt*
cname in engine instance instance.
$OV_LOG/ecs/instance/sname_pout.evt*
sname in engine instance instance.
$OV_LOG/ecs/instance/sname_pdis.evt*
sname in engine instance instance.
$OV_CONF/ecs/instance/config
instance that is restored by the engine on startup.
$OV_CONF/ecs/md/mdl/mdl.md
$OV_CONF/ecs/md/ber/ecs.*
$OV_CONF/ecs/ed/ed.conf
Valid encode/decode module abbreviations are:
MDL enables the ASCII/MDL encode/decode module.
SNMP enables the SNMP encode/decode module.
CMIP enables both the CMIP and SNMP encode/decode modules.
Use of these encode/decode modules requires that an appropriate license be available.
$OV_SOCKETS/ecs/instance/socket
ecsd standalone correlation engine instance instance.
ecsdwas developed by Hewlett-Packard.
ecsdes
ecsmgr
ecslogmsg(5)