Modifying parameter properties
The following process for modifying parameters employs the strengths of the KM and PATROL Configuration Manager:
- Make changes in one instance through the parameter property dialog boxes.
- Test the instance until satisfied that the changes operate as expected.
- Export the modified parameter changes to PATROL Configuration Manager.
- Deploy the modified parameter changes to other instances by using the PATROL Configuration Manager.
This method takes advantage of the validations performed by PATROL for DB2 UDB and gives you the opportunity to verify that the changes perform as expected before deploying those changes throughout your environment.
To modify parameter properties
- Navigate to the parameter properties for the parameter that you want to change:
- In the PATROL Console for UNIX, click Attributes and then Application Classes to open a list of the application classes. Select an application class, then click Attributes and then Parameters to open the list of parameters provided by the selected application class.
In the PATROL Console for Microsoft Windows, select the KM tree tab and expand the appropriate application class, then click Global and then on Parametersto open the list of parameters provided by the selected application class.
- Right-click (Windows) or click (UNIX) the parameter for which you want to access the parameter properties.
- To activate or deactivate a parameter, perform one of these actions:
- In Windows, select the General tab and select or clear Active .
- In UNIX, double-click the parameter, and select or clear Active .
- To change the interval between polling cycles, perform one of these actions:
- In Windows, select the Scheduling tab, and change the polling time.
- In UNIX, click on the parameter and change the polling time.
- To change the alarm thresholds and disable the alarms, perform one of these actions:
- In Windows, select the Border, Alarm1, and Alarm2 tabs, and make changes.
- In UNIX, click on Alarm Ranges, and double-click Border, Alarm1, or Alarm2, and make changes.
- Save the configuration by selecting File > Save Configuration.
- Test the changes on the instance over time to make sure that the changes are working as you expected.
- Using the PATROL KM for Event Management, convert the parameters in the instance to a rule set in PATROL Configuration Manager.
The rules that represent each parameter contain ANYINST for the instance name. The ANYINST designation works when applying parameter changes (although it does not work for instance configuration changes), and it allows you to apply these changes to any instance without adding a specific instance name. Drag and drop the rule set onto any other agent host name where you want to apply the changes.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*