Change rule set parameters for the omegamon.rls rule set file

IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Situation event integration with Tivoli Enterprise Console
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Change rule set parameters for the omegamon.rls rule set file

The omegamon.rls rule set file has parameters that you can edit, according to your environment, to tune performance or to set your own customized values. Using these parameters, you can write and customize IBM Tivoli Enterprise Console rules. During installation, you can choose the location of the rule base. Otherwise, you can use the wrb -lscurrb -path to find the current rule base.
Here are some reasons why you might want to change the behavior of the rule:

For the omegamon.rls file, omegamon_admin is the name of the rule set but you can name your rule set after your administrator's name or some other value.

Similarly, the sit_ack_expired_def_action rule set name is set to REJECT by default. This setting means that whenever a situation event acknowledgement expires in the Tivoli Enterprise Portal and the event becomes OPEN in the portal, the IBM Tivoli Enterprise Console event server rejects this action and re-acknowledges the event in the portal. You have the option of accepting the change that was initiated by the portal and changing the status in the IBM Tivoli Enterprise Console instead.

The following user-configurable parameters are available:

omegamon_admin

Use this identifier when a rule defined in this rule set closes an event. This identifier is used to differentiate close operations that were originated automatically rather than initiated by the console operator.

omsync_timeout

This attribute sets the period in seconds that you must wait to distinguish between the synchronization of single or multiple events. The default timeout is 3 seconds.

omsync_maxentries

This attribute sets the maximum number of events allowed per batch. Default batch size is 100 events.
Warning: Setting this value less than 20 events might cause contentions within the IBM Tivoli Enterprise Console task process, causing poor performance of events that are synchronized back to the Tivoli Enterprise Monitoring Server.

sit_resurface_def_action

This attribute determines the default action of the rules in case a situation update event arrives from Tivoli Enterprise Monitoring Server to resurface or reopen an event that has already been acknowledged. The two possible values are ACCEPT and REJECT. The default is ACCEPT.

sit_ack_expired_def_action

This attribute determines the default action of the rules in case a situation update event arrives from the Tivoli Enterprise Monitoring Server to reopen an event that has already been acknowledged. This happens when a situation's acknowledgement in the monitoring server expires and the situation event is reopened. The two possible values are ACCEPT and REJECT. The default is REJECT.

sf_check_timer

This attribute specifies the interval at which the state of the situation update forwarder is checked. It reads events from the cache files and send them to the Tivoli Enterprise Monitoring Server using Web Services. The default is 10 minutes.

After modifying any configuration parameters and saving omegamon.rls, you must recompile and reload the rule base and recycle the event server. To recompile the rule base, enter the following command, where Rulebase_Name is the name of the actively loaded rule base containing the omegamon.rls rule set:
wrb -comprules Rulebase_Name
To reload the rule base, issue the following command:
wrb -loadrb Rulebase_Name
To stop the Event server, issue the following command:
wstopesvr
To restart the Event server issue the following command:
wstartesvr
For more information regarding the wrb, wstopesvr, and wstartesvr commands, see the Command and Task Reference at the Tivoli Enterprise Console Information Center .

Tuning considerations
Integration parameters supporting actions at the IBM Tivoli Enterprise Console event console that are reflected at the Tivoli Enterprise Portal event console provide good response times with a reasonable system resource investment.

Parent topic:
Situation event integration with Tivoli Enterprise Console

+
Search Tips | Advanced Search