4.6 Managing Existing Jobs

Once you have implemented your core Knowledge Scripts and have established a data-collection strategy, you might need to manage existing jobs by adjusting job properties, adding new servers, or expanding your core set of Knowledge Scripts.

When adding new systems to your environment, plan to run your core Knowledge Scripts to validate event thresholds before including them in a monitoring policy.

4.6.1 Changing Job Properties

After you implement your core Knowledge Scripts for monitoring and data collection, the job properties might need adjustment. Changes are propagated automatically to policy-based jobs. For one-time jobs or those not associated with a monitoring policy, you must manually propagate changes to job properties.

When manually propagating job properties, make sure the Knowledge Script is configured with the same action as the running job, if applicable. For more information about manually propagating job properties, see the Control Center User Guide for AppManager, available on the AppManager Documentation page.

If you want to monitor additional systems or applications with a one-time job, manually add the additional server(s) to the existing parent job by right-clicking the parent job, clicking Add Child Jobs, and selecting the objects you want to monitor. (A monitoring policy does this for you automatically.)

In the Operator Console, when working with different views that display policy objects, it can be difficult to identify the view where a monitoring policy was created or the Knowledge Script Groups that compose the monitoring policy. In the Extended Support section of the NetIQ Technical Support Web site, the AppManager Knowledge Depot features an Operator Console plug-in and a report that provide information about all existing monitoring policies, such as the view where the policy was created and the Knowledge Script Group members:

  • The Operator Console plug-in, MonitorPolicies.vbs, adds two Extensions menu commands to display monitoring policy information in a dialog box or write the information to a text file.

  • The ReportAM_PolicyInfo Report Knowledge Script creates a report about monitoring policies with hypertext links to the parameter values of each Knowledge Script Group member.

Use your myNetIQ Account Login to access the Knowledge Depot at http://www.netiq.com/support/am/extended/knowledgedepot/default.asp.

In the Control Center console, it is easier to identify the monitoring policies that apply to a management group and the Knowledge Script Groups that the monitoring policies are based on. In the Enterprise Layout pane, right-click a management group and click Management Group Properties > Policies. The Policies tab of the Management Group Properties dialog box lists any Knowledge Script Groups assigned to the management group as a monitoring policy.

4.6.2 Checking Job Status with the JobInfo Report

The JobInfo report is useful for finding out when jobs are stopped, pending, or errored out. NetIQ Corporation recommends scheduling this report job to run in the morning and to email the report to your team for review.

When responding to:

  • Stopped jobs, restart them if necessary.

  • Pending jobs, run NetIQCtrl on the agent computer to verify that the job status is Pending. If the job is Pending on the agent computer, delete the job, or in the case of a policy-based job, stop and delete the job by removing the server from the monitoring policy.

  • Errored jobs, look at the error message and take an appropriate action.

    You can configure the number of times to restart errored jobs within the Properties dialog box of the monitoring policy or as a repository preference.

For more information about viewing and responding to job results, see the Control Center User Guide for AppManager, available on the AppManager Documentation page.