19.8 ESCALATIONS
The operator performs message escalation from the message browser. After a message is escalated, the message details contain information about the escalation, as shown in Figure 19.1. The configuration steps for message escalation are outlined in the next section.19.8.1 Process Steps to Create the Escalation Template
Add the escalation manager to the source manager's node bank as a message allowed node.Add the source manager to the escalation manager's node bank as a message allowed node.Add the escalation manager to a node group on the primary manager.Add the primary manager to a node group on the escalation manager.Copy the escmgr template from the tmpl_respmgrs directory to the work_respmgrs directory on the source manager.Edit the template; replace the name of their server "M1" with the name of the escalation manager.Use the opcmomchk utility to check the syntax of the escalation template.Move the escmgr template to the respmgrs directory.Restart the OVO session.Test the message escalation. Select a message in the browser, open the details or the pop-up menu, and select escalate. In the message details there is a new button, "Escalate." The message should appear on the escalation manager.19.8.2 Sample Escalation Template
The sample template escmgr in this example enables messages escalation a manager to a manager called tahiti. The managed node would also have a MoM configuration file that authorizes tahiti to perform actions and/or become a secondary manager.# Sample Escalation Template.
# This template allows Servers to escalate messages to
# the another system.
#TIMETEMPLATES
# None
# Responsible Manager Configurations
#
RESPMGRCONFIGS
RESPMGRCONFIG
DESCRIPTION "Responsible mgrs"
SECONDARYMANAGERS
ACTIONALLOWMANAGERS
MSGTARGETRULES
MSGTARGETRULE
DESCRIPTION "Management Server tahiti"
MSGTARGETRULECONDS
MSGTARGETMANAGERS
MSGTARGETMANAGER
TIMETEMPLATE "$OPC_ALWAYS"
OPCMGR IP 0.0.0.0 "tahiti"
|
لطفا منتظر باشید ...
