6.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 6‒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^#

• Set the environment for executing the automated action:

  • Customize the automated action execution environment.

  • Set up user mapping on the target host.

# You can suppress identical actions in the following ways:

• Suppress automated actions to suppress identical actions.

  For details, see 6.4.4 Suppressing identical actions.

• Suppress the monitoring of repeated events to suppress actions.

  For details, see 4.5.8 Suppressing the execution of automated actions triggered by a large number of events.

In addition to identical-action suppression, you can also use the following ways to prevent automated actions from being executed:

• Use common exclusion-conditions to exclude events from action execution.

  For details, see 4.2.7 Common exclusion-conditions.

• Disable the action definition through the Action Parameter Definitions window in JP1/IM - View.

  For details, see 3.32 Action Parameter Definitions window in the manual JP1/Integrated Management 2 - Manager GUI Reference.

• Disable the action definition with the jcachange command.

  For details, see jcachange in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

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.

Important

• When the automated action function requests a large number of agents at once to execute a command, a heavy load might be applied on the manager host. To reduce the load, we recommend that you divide the agents into host groups and then execute the command for each group.

• It is recommended that you expand the number of records in the command execution log file because the conventional value (20,000 records by initial setting) is not enough in the case of using remote command or automated actions of JP1/IM - Manager when the number of the agents to be monitored is more than 1,024 after upgrade installation from JP1/Base 11-10 or earlier, and JP1/IM - Manager 11-10 or earlier.

• When more than 1,024 agent hosts are monitored in one JP1/IM - Manager, the boot-time of JP1/Base may increase depending on the size of the command execution log file. When the boot-time increases, please consider whether you reduce the number of records in the command execution log file or disable the function for automatically re-organizing the command execution log file of JP1/Base. When you run a JP1/IM - Manager host in a cluster system, the matter mentioned above may influences the time required for failing over the system. It is necessary to disable the function for automatically re-organizing the command execution log file or to reconsider the time-out value which is configured to the cluster software.

To Page Top