Operations Guide
|
Monitoring data collection services for UM are provided by MCS.
See Monitoring Collector Service (MCS).
There are two executables for MCS, each with it's own man page:
Note that these executables are not in the same "bin" directory as the platform native UM executables. Since it is a Java program, it has its own directory sub-tree, "MCS", with sub-directories "bin" and "lib". For example, the MCS executables are under "UMS_6.17/MCS/bin". For instructions on using a different directory structure, see the "Usage Notes" sections in MCS Man Page and Mcsds Man Page.
Note also that the MCS uses the underlying platform-specific UM library, so your proper paths should be set up.
Unix and Windows command-line interface.
Usage: MCS [options] [configfile] Available options: -h, --help help -p, --property-keys dump the list of supported property keys to stdout and exit -v, --validate validate config file and exit -V, --verbose be verbose about each message -x, --xsd dump the configuration XSD to stdout and exit
MCS
command runs the Monitoring Collector Service (MCS). It can be run interactively from a shell or command prompt, or from a script or batch file. (For use as a Windows Service, see Mcsds Man Page.)When shutting down a Unix-based MCS Process, use a SIGINT to trigger a clean shutdown, which attempts to cleanly finish outstanding IO requests before shutting down.
Given how the MCS was implemented, there are scripts, binary executables, and Java JAR files associated with the service. By default, the scripts and executables assume a certain directory structure, with the scripts and executables stored in a "bin" sub-directory, and JAR files stored in a "lib" sub-directory. This corresponds to how the UM package installation structures the files.
Starting with UM version 6.17, the user can use their own directory structure. To assist the scripts and executables in finding the JAR files, the user can define an environment variable, "UM_MCS_DIR", which contains the full path for the directory containing the JAR files.
Windows Service interface.
See UM Daemons as Windows Services for general information about UM daemons as Windows Services.
Usage: mcsds [options] mcs_cfgfile_name Available options: -h, --help display this help and exit -l, --service-log=FILE set a logfile name for the service log. -p, --process-log=FILE set a logfile name for the mcs process output. -s, --service=request Install, remove or add a configuration file. Examples: '-s install' to install the service with no config file '-s install cfgfile.xml' to install the service with a configuration file of cfgfile.xml '-s remove' to remove the service '-s config cfg2.xml' to change or add a configuration file -e, --event-log-level Update/set service logging level. This is the minimum logging level to send to the Windows event log. Valid values are: NONE - Send no events INFO WARN - default ERROR -E, --env_var_file update/set the environment Variable File -f, --flatdir specify that binaries and java libraries are in the same directory Note: This sets UM_MCS_DIR environment variable to the directory path of this executable -U, --noenv_var_file unset env_var_file (-E) entry Note: -U and -E are not supported on the same command line
mcsds
command has two functions: When installing the MCS as a Microsoft Windows service, use only local disk devices and fully qualified path names for all filenames. This is because Windows services run by default under a Local System account, which has reduced privileges and is not allowed access to network devices.
Given how the MCS Windows service was implemented, there are binary executables and Java JAR files associated with the service. By default, the executables assume a certain directory structure, with the executables stored in a "bin" sub-directory, and JAR files stored in a "lib" sub-directory. This corresponds to how the UM package installation structures the files.
Starting with UM version 6.17, the user can use their own directory structure. To assist the executables in finding the JAR files, the user can define an environment variable, "UM_MCS_DIR", which contains the full path for the directory containing the JAR files. This environment variable can either be made at the system level, or can be defined in a disk file, specified by the "-E" command-line option to mcsds
.
Alternatively, if you plan to store the executables in the same directory as the JAR files, you can instead use the "-f" command-line option to mcsds
.