Reference

Reference information for IBM® Sterling Control Center Monitor.

engine.properties properties
engine.properties is stored as a row in the CC_FILES database table. When IBM Sterling Control Center Monitor event processors (EPs) start, EPs read engine.properties. Some of the system properties are used by IBM Sterling Control Center Monitor EPs and some are used by Java.
CCEngineService.xml properties
CCEngineService.xml is used to set IBM Sterling Control Center Monitor properties that are related to performance.
fgEventCodes properties
fgEventCodes contains a complete list of known Sterling File Gateway event codes.
sspConfig.properties
sspConfig.properties is used to set IBM Sterling Control Center Monitor properties that are related to SSP Server monitoring and Reporting functionalities.
Event type descriptions
This table describes all IBM Sterling Control Center Monitor event types.
Event type Sterling Connect:Direct statistic record ID cross-reference
You can use statistic record information to determine what Sterling Connect:Direct® activities produce associated IBM Sterling Control Center Monitor event types. If a statistic record ID is not listed, IBM Sterling Control Center Monitor does not use it.
Built-in actions and rules
IBM Sterling Control Center Monitor provides built-in actions and rules that can be used as is or modified to meet your needs.
Message IDs for rules
You can use message IDs when creating rules and SLCs.
Regular expressions
Regular expressions (or regex) can be used in wildcard SLCs and other IBM Sterling Control Center Monitor entities to match text or numeric strings that follow a particular pattern. They consist of normal characters and special characters. Normal characters are uppercase and lowercase letters and numbers. Special characters have specific meanings in the expression.
IBM Sterling Control Center Monitor variables
The following table lists IBM Sterling Control Center Monitor event elements that you can use as variables in operating system and server command actions, email actions, metadata actions, and workflow SLC correlators. A brief description of each element is also included.
Keys and fields
In IBM Sterling Control Center Monitor, you can specify a key to define the criteria for a report, rule, or SLC. You can also specify a key to act as a filter to limit the number of items that display in many IBM Sterling Control Center Monitor listings. A parameter consists of a key, an operator, and a value.
Data for third-party reporting tools
Data for third-party reporting tools is contained in IBM Sterling Control Center Monitor tables. The following tables are discussed here:
Application log field description
There is one field description for an application log.
Services field descriptions
You can use many fields to define services in IBM Sterling Control Center Monitor.
Engine connection field descriptions
There are two fields to define engine connections.
Console settings field descriptions
Console settings deal with how often activity monitors are refreshed, and inactivity timeout for console sessions.
File Agent field descriptions
You can use many fields to define a Sterling Connect:Direct File Agent.
Database FAQ
These topics contain frequently asked questions about databases.
RESTful APIs overview
IBM Sterling Control Center Monitor RESTful application programming interfaces (APIs) enable other applications to integrate with the IBM Sterling Control Center Monitor web client.
Posting Events

Parent topic: IBM Sterling Control Center Monitor 6.4.0