2.8 Command execution triggered by a JP1 event

If a JP1 event such as a failure notification is issued from an agent host, registered commands can be automatically executed from the agent host. This is called a local action. This functionality enables you to reduce the network load between managers and agents, and also enables you to execute commands even if an error occurs on the network between the managers and agents.

The following figure shows a comparison of JP1/Base local actions with JP1/IM - Manager automated actions.

Figure 2‒41: Comparison of JP1/Base local actions with JP1/IM - Manager automated actions

To execute a local action, you must create a local action execution definition file and specify which commands to execute when a JP1 event is generated. If a JP1 event specified in the local action execution definition file is generated, JP1/Base executes the command or commands corresponding to the JP1 event.

The local action functionality also enables you to issue an action start event and action end event. Therefore, by forwarding those events to the manager host, you can check the execution or result of the local action at the manager host. The action execution log is also output to the local action execution log file.

Organization of this section

• 2.8.1 Conditions required for executing local actions

• 2.8.2 Commands for local actions

• 2.8.3 Execution status of local actions

• 2.8.4 Pausing local actions

To Page Top