9.3.1 Sending rule startup requests to JP1/IM - Rule Operation
When JP1/IM - Rule Operation linkage is enabled, rule startup requests are sent to JP1/IM - Rule Operation automatically via automated actions.
|
|
![[Figure]](GRAPHICS/CS040400.GIF)
When JP1/IM - Rule Operation linkage is enabled, display items related to JP1/IM - Rule Operation appear in the Action Parameter Detailed Definitions window of JP1/IM - View. This allows you to set the conditions for notifying JP1/IM - Rule Operation.
Once a notification condition has been set, whenever a JP1 event triggers a rule startup request, JP1/IM - Manager automatically sends the request to JP1/IM - Rule Operation.
In JP1/IM - Rule Operation, if the received rule startup request is found to match a rule startup condition, the rule is judged valid and executed.
- Organization of this subsection
(1) Enabling and disabling JP1/IM - Rule Operation linkage
To enable or disable JP1/IM - Rule Operation linkage, use the jcoimdef command. For details, see jcoimdef in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
When you connect from JP1/IM - View to a JP1/IM - Manager with JP1/IM - Rule Operation linkage enabled, display items related to JP1/IM - Rule Operation linkage appear in the following windows:
- Additional setup items appear in:
-
-
Action Parameter Definitions window
-
Action Parameter Detailed Definitions window
-
- Additional display items appear in:
-
-
Action Log window
-
Action Log Details window
-
List of Action Results window
-
Search Events page
-
Settings for View Filter window
-
Severe Event Definitions window
-
Detailed Settings for Event Receiver Filter window
-
For details about these windows, see Chapter 3. Event Console Window in the manual JP1/Integrated Management 2 - Manager GUI Reference.
(2) Setting notification conditions for sending rule startup requests to JP1/IM - Rule Operation
As with standard automated actions, you can set conditions for sending rule startup requests to JP1/IM - Rule Operation in the Action Parameter Detailed Definitions window or in the automated action definition file (actdef.conf).
When setting a notification condition to send a rule startup request, include only the JP1 events specified as the rule startup conditions. This ensures that no more than the minimum necessary automated actions will be executed.
Perform the same settings as for a standard automated action, except for the parts shown in the figure below.
|
|
![[Figure]](GRAPHICS/CS040500.GIF)
The following items, although used when setting an automated action, must be set in a particular way when setting a condition for sending a startup request to JP1/IM - Rule Operation:
-
Execution user: Specify a JP1 user mapped to an OS user on the target JP1/IM - Rule Operation host. Set this user by the jcoimdef command.
-
Target host: Specify the target JP1/IM - Rule Operation host. Set this host by the jcoimdef command. Unlike automated actions, you cannot specify a host group.
-
Action: Fixed as <RULE>. When JP1/IM - Rule Operation receives a startup request, it executes an internal command using as arguments the JP1/IM - Manager host name, the serial number of the JP1 event that triggered the request, and the arrived time.
-
Environment variable file: You cannot specify an environment variable file.
For details about the Action Parameter Detailed Definitions window, see 3.33.1 Action Parameter Detailed Definitions window in the manual JP1/Integrated Management 2 - Manager GUI Reference. For details about the definition file, see Automated action definition file (actdef.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
(3) Flow of notification processing
As is usual with automated actions, notification processing for JP1/IM - Rule Operation is performed according to the system hierarchy (IM configuration) definition. The status transitions of the communication processing are the same as for a standard automated action.