IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Edit your environment configuration settings > Tivoli Enterprise Monitoring Server configuration settings
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Duper process for optimizing situations
The Tivoli Enterprise Monitoring Server has a mechanism called duper that optimizes the activation of multiple situations when they are evaluating the same data at the same sampling interval. This topic describes how the duper process works, how to identify situations that use it, why you might want to disable it, and how to configure the Tivoli Enterprise Monitoring Server environment file to disable it.
- Duper process
- A duper situation is created and runs on the agent to collect data from the attribute group once and upload it to the monitoring server. The monitoring server evaluates the multiple situations using the data collected by the duper situation. Because the situation evaluation is taking place at the monitoring server, when the agent is disconnected, these situations are no longer evaluated.
- If agents are routinely offline or disconnected from the monitoring server and running autonomously, they are probably sending events directly from the agent to an event receiver other than the monitoring server. It might be preferable to define private situations at the agent rather than using enterprise situations that are defined at the monitoring server.
- Duper eligibility
- For a situation to qualify for the duper process, it must have these qualities:
- Monitors the same attribute group on the same managed system and with the same monitoring interval as at least one other situation
- Uses only the VALUE formula function
- Does not specify persistence, an Until clause, or dynamic thresholding with expression override
- Defined to AutoStart
- Does not embed another situation
- Match another situation’s display item (applies only if display item is used)
- Reflex automation consideration
- In IBM Tivoli Monitoring V6.3, duper is automatically applied to situations with reflex actions. No additional configuration is required.
- If you have a large number of situations with reflex actions set in the Tivoli Enterprise Portal to Execute the Action at the Managed System (Agent), then you can set the monitoring server environment variable KMS_EVAL_REFLEX_AT_TEMS=Y in the KBBENV file to increase your level of duper optimization.
- Set the KMS_EVAL_REFLEX_AT_TEMS environment variable at each monitoring server in your environment to cause the evaluations of the actions to be handled by duper on the monitoring server, while the actions are still directed to the managed systems. To implement this variable, your managed systems must be connected to a monitoring server in order for the actions to execute.
- Use the KMS_EVAL_REFLEX_AT_TEMS environment variable with caution.
- The KMS_EVAL_REFLEX_AT_TEMS variable has no affect on your situation if you have set Execute the Action at the Managing System (TEMS).
- Duper situation _Z_ identifier
- You can verify that a duper situation is collecting data from the agent by examining the LG0 log on the agent, such as C:\ibm\ITM\TMAITM6\logs\Primary_IBM_MyComputer_NT.LG0. There will be an entry starting with _Z_ that shows the agent is starting a situation on the attribute group that the multiple situations monitor. Example: Starting _Z_WTSYSTEM0 <3207594896,3996125040> for KNT.WTSYSTEM.
- Disable duper
- By adding a parameter to the monitoring server, you can disable the duper process. This is done by adding this line to the KBBENV file: CMS_DUPER=NO
- When the monitoring server is recycled, the duper is skipped.
To edit the monitoring server environment variable file, KBBENV on Windows and KDSENV on z/OS, follow these steps:
- Use Manage Tivoli Enterprise Monitoring Services (Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Enterprise Monitoring Services) to edit environment files. Right-click the component you want to modify and click Advanced → Edit ENV File. You must recycle the component to implement the changes.
- Edit the environment file directly. Edit environment variables in the <install_dir>/config/ms.ini file and then reconfigure and recycle the monitoring server to implement the changes.
- See Configure the Tivoli Enterprise Monitoring Server on z/OS for more information.
Parent topic:
Tivoli Enterprise Monitoring Server configuration settings