5.1 Overview of automated actions

In JP1/IM, you can execute a command automatically when a specific JP1 event is received by a manager. This function is called automated actions.

By using automated actions, you can advise the system administrator, by executing a command that sends an email or makes a phone call, whenever a JP1 event reporting an error is received, for example.

Figure 5‒1: Overview of automated actions

By defining the following items, you can execute a specified command as an automated action under set conditions.

• Define the automated action to be executed:

  • Specify a condition for executing the automated action.

  • Specify the command to be executed as an automated action, the target host, the user account, and whether identical actions are to be suppressed.

    Note that actions can be suppressed by using either the automated action function or the function for suppressing repeated-event monitoring.

    This subsection describes how the automated action function suppresses actions. For an explanation of how the function for suppressing repeated-event monitoring suppresses actions, see 3.5.8 Suppressing the execution of automated actions triggered by a large number of events.

• Set the environment for executing the automated action:

  • Customize the automated action execution environment.

  • Set up user mapping on the target host.

JP1/IM provides the following functionality to enable early detection of any problems during processing of an automated action.

• Automated action execution monitoring

  • Monitoring for delayed automated actions

  • Monitoring of automated action status

The next section describes how JP1/IM manages the status of automated actions. The following sections describe how to define an automated action, and the processes of monitoring and executing automated actions.

To Page Top