4.1.1 Registering Items via automated action

JP1/IM - Manager receives JP1 events from JP1/Base on the same host. If a received JP1 event satisfies conditions for executing an automated action, JP1/IM - Manager automatically executes commands as defined for the automated action. The execution conditions and processing to be executed are defined in JP1/IM - Manager.

Using the JP1/IM - Manager automated action functionality, JP1/Service Support executes the jssitementry command to register incidents in the Item management database.

For details about the jssitementry command, see jssitementry (registers an Item) in Chapter 12. Commands.

The following figure shows how JP1/Service Support registers incidents in the Item management database by using the JP1/IM - Manager automated action functionality.

Figure 4‒2: Incident registration by automated action

The steps in the above figure are described below.

JP1/IM - Manager receives JP1 events that have passed through the event acquisition filter from the JP1/Base event database on the integrated manager.
The JP1/IM - Manager automated action functionality determines whether the received JP1 events satisfy conditions for executing an automated action. If there are JP1 events that satisfy those conditions, JP1/IM - Manager sends command (action) execution requests to the appropriate hosts (where the commands are executed) according to the action definitions.

In this example, a request to execute the jssitementry command is sent to the Item management server.

After an incident (Item) is automatically registered in JP1/Service Support, JP1/IM - Manager can receive a JP1 event from JP1/Service Support when the status of that Item changes to Close. For JP1/IM - Manager to receive such a JP1 event, the JP1/IM - Manager host name and serial number must be specified for the -evt option of the jssitementry command.
In response to an execution request from the integrated manager, JP1/Service Support executes the jssitementry command on the Item management server.
An incident (Item) is registered in the Item management database.

Note: The JP1/IM - Manager automated action functionality can execute commands only on hosts managed by JP1/IM - Manager. In this example, the Item management server must be added to JP1/IM - Manager's management beforehand.

The following briefly explains the execution conditions and definitions of automated actions. For detailed information, see the JP1/Integrated Management - Manager Overview and System Design Guide and the JP1/Integrated Management - Manager Command and Definition File Reference.

Organization of this subsection

(1) Conditions for executing automated actions
(2) Definitions of automated actions

(1) Conditions for executing automated actions

In JP1/IM - Manager, you can use IDs, messages, and attribute values of JP1 events as conditions for executing automated actions. JP1/IM - Manager determines whether to execute automated actions based on these conditions.

To enable JP1/Service Support to execute automated actions, specify JP1 events that report matters that hinder normal operations as execution conditions.

To Page Top

(2) Definitions of automated actions

An automated action in JP1/IM - Manager is defined with information such as the execution host (host on which the action will be executed), the command to be executed, and the user who will execute the action. JP1/IM - Manager executes the automated action based on this information.

To use linkage with JP1/IM - Manager so that incidents are automatically registered in JP1/Service Support, specify the name of the Item management server as the execution host, and the jssitementry command as the command to be executed.

Note: JP1/IM - Manager can embed JP1 event attributes in arguments of the jssitementry command. For example, if you specify $EVSEV as the value of the -s option, which specifies the severity level, the value of the severity level for the Item to be registered changes according to the JP1 event's severity level.

To Page Top