Template contents

You can use several different types of templates to quickly implement IBM® Sterling Control Center Monitor.

IBM Sterling Control Center Monitor contains the following types of templates:

  • Duration Schedule Template
  • Email Template
  • Operating System Commands Template
  • Rules Template
  • Calendar Schedule Template
  • Standard SLC Groups Template
  • Wildcard SLC Groups Template

Duration schedule template

The duration.tmp file is used for SLC duration schedules. It contains the following fields:

Tag Description
<dMax>&dmax;</dMax> Maximum duration
<dMin>&dmin;</dMin> Minimum duration
<desc>&desc;</desc> Schedule description
<enabled>&enabled;</enabled> Enabled (true or false)
<id>&id;</id> Schedule Name
<name>&id;</name> Schedule Name

Email template

The email.tmp file is used for email address in actions. It contains the following fields:

Tag Description
<desc>&desc;</desc> Action description
<email>&email;</email> Email address
<id>&id;</id Action name
<smtpFromAddr>&fromEmailAddr;</smtpFromAddr> From email address
<emailSubject>&subject;</emailSubject> Email subject text
<emailText>&message;</emailText> Email body text
Note: The final statement for the email template must be ACTION.

Operating system command template

The opSys.tmp file is used for operating system commands in actions. It contains the following fields:

Tag Description
<desc>&desc;</desc> Action description
<id>&id;</id> Action name
<operation>&operation;</operation> Operating system command
Warning: The final statement for the operating system command template must be ACTION.

Rules template

The rule.tmp file is used for creating rules. It contains the following fields:

Tag Description
<actionId>&actionid;</actionId> Action name associated with the rule
<desc>&desc;</desc> Rule description
<enabled>&enabled;</enabled> Enabled (true or false)
<eventType>&eventtype;</eventType> The event type that generates the rules.
<id>&id;</id> Rule name
<match>&quot;/event[eventType = &apos;&eventtype;&apos; and messageId = &apos;&messageid;&apos;]&quot;</match> The event type and message ID to match.
  • &eventtype; is the event type code
  • &messageID; is the message ID

Calendar schedule template

The schedule.tmp file is used for creating calendar schedules. It contains the following fields:

Tag Description
<calendarId>&calendar;</calendarId> Calendar name associated with the schedule
<desc>&desc;</desc> Schedule description
<enabled>&enabled;</enabled> Enabled (true or false)
<id>&id;</id> Schedule ID
<name>&id;</name> Schedule ID
<day>&day;</day> Normal End Range day. 0 = NSR start day, 1 = NSR start day + 1, and so on.
<end>&nerend;</end> Normal End Range end time. Format hh:mm:ss.
<start>&nerstart;</start> Normal End Range start time. Format hh:mm:ss.
<end>&nsrend;</end> Normal Start Range end time. Format hh:mm:ss.
<start>&nsrstart;</start> Normal Start Range start time. Format hh:mm:ss.
<timeZone>&timezone;</timeZone> The time zone.

Standard SLC groups template

The slc_group.tmp file is used for creating standard SLC groups. It contains the following fields:

Tag Description
<desc>&desc;</desc> Schedule description
<duplicateFileNames>&duplicatefilenames; </duplicateFileNames> Allow duplicate file names (true or false)
<duplicateProcesses>&duplicateprocesses; </duplicateProcesses> Allow duplicate Process names or Batch IDs (true or false)
<enabled>&enabled;</enabled> Enabled (true or false)
<fileName>&filename;</fileName> File Name
<id>&id;</id> SLC ID
<missingEvent>&missingevent; </missingEvent> Generate notification if event has not occurred (true or false)
<monitorToleranceStart>&monitortoleranceStart; </monitorToleranceStart> The start monitor tolerance windows in hours
<monitorToleranceEnd>&monitortoleranceEnd; </monitorToleranceEnd> The end monitor tolerance window in hours
<name>&id;</name> SLC ID
<node>&node;</node> The servers selected for the SLC
<process>&process;</process> The Process name. or Batch ID
<remoteNode>&remotenode; </remoteNode> The remote node name
<schedule>&schedule;</schedule> The associated schedule
<serverGroup>&servergroup; </serverGroup> The server groups selected for the SLC
<submitter>&submitter;</submitter> The submitter ID

Wildcard SLC groups template

The slc_regex.tmp file is used for creating wildcard SLC groups. It contains the following fields:

Tag Description
<desc>&desc;</desc> Schedule description
<enabled>&enabled;</enabled> Enabled (true or false)
<fileName>&filename;</fileName> The file name expression
<fileNameRegex>&filenameregex; </fileNameRegex> Matches the file name using a Regex expression (true or false)
<id>&id;</id> SLC ID
<missingEvent>&missingevent; </missingEvent> Generate notification if event has not occurred (true or false)
<monitorToleranceStart>&monitortoleranceStart; </monitorToleranceStart> The start monitor tolerance window in hours
<monitorToleranceEnd>&monitortoleranceEnd; </monitorToleranceEnd> The end monitor tolerance window in hours
<name>&id;</name> SLC ID
<node>&node;</node> The servers expression
<nodeRegex>&noderegex;</nodeRegex> Matches the servers using a Regex expression (true or false)
<process>&process;</process> The Process name or Batch ID expression
<processRegex>&processregex; </processRegex> Matches the Process name or Batch ID using a Regex expression (true or false)
<remoteNode>&remotenode; </remoteNode> The remote node name expression
<remoteNodeRegex>&remotenoderegex; </remoteNodeRegex> Matches the remote node name using a Regex expression (true or false)
<schedule>&schedule;</schedule> The associated schedule
<serverGroup>&servergroup; </serverGroup> The server groups selected for the SLC
<submitter>&submitter;</submitter> The submitter ID expression
<submitterRegex>&submitterregex; </submitterRegex> Matches the submitter ID using a Regex expression (true or false)