6.10 Flow of automated action execution

The following describes how the JP1/IM and JP1/Base functionality are inter-linked in automated action execution, taking as an example the flow of processing from the time a manager receives a JP1 event that triggers an automated action until the action is executed on an agent.

The description below assumes that the definition of the automated action has been completed. (For details on defining an automated action, see 6.3 Defining an automated action).

Figure 6‒8: Flow of processing for automated action execution (command executed on an agent by an automated action)

The flow of processing is described below, following the numbers in the figure:

A JP1 event that triggers an automated action occurs on the agent and is registered with the event service.
The registered JP1 event is forwarded to a higher-level host in accordance with the configuration management definitions, and is registered with that manager's event service.
JP1/IM - Manager (event base service) acquires the registered JP1 event from the event service.
The acquired JP1 event is compared with the automated action definitions, and is passed to the automatic action service if a match is found.
On receiving the JP1 event, the automatic action service passes a command execution request to JP1/Base on the manager.
On receiving the command execution request, JP1/Base on the manager references the configuration information and sends a command execution request to the target host.
JP1/Base on the agent that received the request references the user mapping definitions and then executes the command using the permissions of the mapped OS user.^#

#: User mapping (JP1/Base user management) is processed on the target host where the command is to be executed. Thus, user mapping must be set up in advance on the agent where the automated action is to be executed, or on the manager if the automated action is to be executed on the manager.
After the command has been executed, JP1/Base on the agent reports the result to the higher-level host defined in the configuration definitions.
On receiving the command execution result, JP1/Base on the manager records the result in a command execution log (ISAM) file, and then reports the result to the automatic action service.
The automatic action service outputs the execution result received from JP1/Base to a log, and then passes the execution result to the event base service.
The JP1 event information held by the event base service is displayed in JP1/IM - View through the event console service.

Automated actions are executed by the JP1/Base command execution function. See also 8.4.4 Managing command execution.

Important

If any of the following events occurs during the execution processing of an automated action, the action ceases to proceed through the usual status transition (this applies only to actions whose status is Wait, Send, Queue, Running, Wait (Canceling), Send (Canceling), Queue (Canceling), or Running (Canceling)):

The manager, action relay host, or action target host is shut down or otherwise stopped.
Network error
JP1/Base failure

In such cases, check the status of the automated actions as follows.

Using the JP1/Base jcocmdshow command (supported in version 07-51):

You can check the action status using this command if the automated action was being processed by JP1/Base (command execution management) on the target host.^#

#: If the processing request has not yet been received or if processing has ended, you cannot use this command to check the action status.

If an automated action ceases to progress and the jcocmdshow command cannot be used to check its status, evaluate whether it needs to be re-executed, and do so if necessary from the Execute Command window.

To Page Top