5.11.1 Considering linkage with JP1/IM - Manager

If you link JP1/Service Support with JP1/IM - Manager, the following settings are required on the JP1/IM - Manager side:

Define the Item management server in the system configuration definition of JP1/IM - Manager.: To execute an automated action from JP1/IM - Manager, in the system configuration definition of JP1/IM - Manager, you must include the Item management server in the management targets of JP1/IM - Manager.
Define an automated action.: Define JP1 events that trigger automatic registration of Items as conditions of automated actions, and specify the jssitementry command as the execution command.

For details, see the JP1/Integrated Management - Manager Overview and System Design Guide.

Also, you must install JP1/Base on the Item management server. The necessary version of JP1/Base depends on the OS of the Item management server. For details about the supported versions of JP1/Base, see the Release Notes.

Organization of this subsection

(1) Examples of automated action definitions when linking with JP1 products
(2) Example automated action definitions when JP1/Service Support issues JP1 events
(3) Linkage with JP1/IM - Manager in a cluster environment

(1) Examples of automated action definitions when linking with JP1 products

If you use JP1/IM - Manager to register JP1 events issued by individual JP1 products in JP1/Service Support as Items, define automated actions referring to the example definitions described in Table 5-9 to Table 5-14. When the Item status automatically registered by JP1/IM - Manager becomes Close, you may want to use an automated action to issue a JP1 event from JP1/Service Support to change the response status to Processed. To do this, you need to use the -evt option to specify the host name of the destination JP1/IM - Manager and the serial number of the event in the event database. Note that a JP1 event specified as the condition in these definition examples is a JP1 event issued by the relevant JP1 product when something that might disturb normal operations occurs.

Table 5‒9: Example automated action definitions (JP1/AJS linkage)
Condition	Action definition
[Event ID] `00004104`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-jobnet-abnormally-ended` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -jobnet $EV"ROOT_OBJECT_NAME" -job $EV"OBJECT_ID" -aimJP1/AIM-server-name` `-cit HOST -ci $EV"B3" -evt $ACTHOST $EVSEQNO`
[Event ID] `00004108`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-jobnet-completed-with-warning` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -jobnet $EV"ROOT_OBJECT_NAME" -job $EV"OBJECT_ID" -aimJP1/AIM-server-name` `-cit HOST -ci $EV"B3" -evt $ACTHOST $EVSEQNO`
[Event ID] `00004107`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-jobnet-abnormally-ended` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -jobnet $EV"ROOT_OBJECT_NAME" -job $EV"OBJECT_ID" -aimJP1/AIM-server-name` `-cit HOST -ci $EV"B3" -evt $ACTHOST $EVSEQNO`
[Event ID] `00004109`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-jobnet-completed-with-warning` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -jobnet $EV"ROOT_OBJECT_NAME" -job $EV"OBJECT_ID" -aimJP1/AIM-server-name` `-cit HOST -ci $EV"B3" -evt $ACTHOST $EVSEQNO`

Table 5‒10: Example automated action definitions (JP1/NNMi or HP NNMi linkage)
Condition	Action definition
[Event ID] `00006100` [Extended event attributes] The severity is `Emergency`, `Alert`, `Critical`, or `Error`.	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-an-NNMi-error` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -snmp $EV"NNMI_SRC_NODE_NAME" -url` `information-about-the-device-where-an-error-occurred` `$EV"NNMI_PROTOCOL"://$EV"NNMI_SERVER":$EV"NNMI_PORT"/nnm/launch?cmd=showForm"&"objtype=Incident"&"menus=true"&"objuuid=$EV"NNMI_UUID"`

Table 5‒11: Example automated action definitions (JP1/IM - Manager (integrated scope) linkage)
Condition	Action definition
[Event ID] `00003FB0` [Extended event attributes] `MON_NODE_ID:monitor-ID-for-the-work` `MON_NODE_STATUS:800`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-an-error-in-the-monitored-node` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s Emergency -ipt` `impact-level` `-itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -node $EV"MON_NODE_NAME" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EV"JCS_B_EVHOST" -evt $ACTHOST $EVSEQNO`
[Event ID] `00003FB0` [Extended event attributes] `MON_NODE_ID:monitor-ID-for-the-work` `MON_NODE_STATUS:700`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-an-error-in-the-monitored-node` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s Alert -ipt` `impact-level` `-itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -node $EV"MON_NODE_NAME" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EV"JCS_B_EVHOST" -evt $ACTHOST $EVSEQNO`
[Event ID] `00003FB0` [Extended event attributes] `MON_NODE_ID:monitor-ID-for-the-work` `MON_NODE_STATUS:600`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-an-error-in-the-monitored-node` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s Critical -ipt` `impact-level` `-itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -node $EV"MON_NODE_NAME" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EV"JCS_B_EVHOST" -evt $ACTHOST $EVSEQNO`
[Event ID] `00003FB0` [Extended event attributes] `MON_NODE_ID:monitor-ID-for-the-work` `MON_NODE_STATUS:500`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-an-error-in-the-monitored-node` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s Error -ipt` `impact-level` `-itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -node $EV"MON_NODE_NAME" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EV"JCS_B_EVHOST"`
[Event ID] `00003FB0` [Extended event attributes] `MON_NODE_ID:monitor-ID-for-the-work` `MON_NODE_STATUS:400`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-an-error-in-the-monitored-node` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s Warning -ipt` `impact-level` `-itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -node $EV"MON_NODE_NAME" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EV"JCS_B_EVHOST" -evt $ACTHOST $EVSEQNO`

Table 5‒12: Example automated action definitions (JP1/PFM - Web Console linkage)
Condition	Action definition
[Event ID] All [Extended event attributes] The severity is `Emergency`, `Alert`, `Critical`, `Error`, or `Warning`. `PRODUCT_NAME:/PFM/ALARM_EVENT` `OBJECT_TYPE:ALARM`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `PFM-alert` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -alarm $EV"OBJECT_NAME" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EV"JPC_AGENT" -evt $ACTHOST $EVSEQNO`

Table 5‒13: Example automated action definitions (JP1/Software Distribution linkage)
Condition	Action definition
[Event ID] `00010403`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-the-instruction-abnormally-ended` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -job $EV"S1" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EVHOST -evt $ACTHOST $EVSEQNO`
[Event ID] `00010407`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-the-job-abnormally-ended` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -job $EV"S1" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EVHOST -evt $ACTHOST $EVSEQNO`
[Event ID] `00010401`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `report-when-the-server-is-down` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -job $EV"S1" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EVHOST -evt $ACTHOST $EVSEQNO`
[Event ID] `00010101`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-the-relay-down` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -job $EV"S1" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EVHOST -evt $ACTHOST $EVSEQNO`
[Event ID] `00010410` or `00010110`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `client-alert` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -job $EV"S1" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EVHOST -evt $ACTHOST $EVSEQNO`
[Event ID] `00010411` or `00010111`	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `client-alert` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -itmc FAL -isuc MID -det "$EVMSG" -jp1 $EV"PRODUCT_NAME" -job $EV"S1" -aim` `JP1/AIM-server-name` `-cit HOST -ci $EVHOST -evt $ACTHOST $EVSEQNO`

Table 5‒14: Example automated action definitions (JP1/NP linkage)
Condition	Action definition
[Event ID] All	[Target host] `name-of-the-Item-management-server` [Action] `jssitementry -b` `process-work-board-ID` `-t` `event-of-an-error` `-r` `login-ID-for-the-registrar` `-cht` `type-of-the-person-in-charge` `-ch` `ID-of-the-person-in-charge` `-s $EVSEV -det "$EVMSG[\r\n]JP1-event-source-host: $EVHOST[\r\n]event-ID-of-JP1-event: $EVIDBASE" -jp1 $EV"PRODUCT_NAME" -evt $ACTHOST $EVSEQNO`^#

#: You must edit the configuration file for character string substitution to register the character string [\r\n] as linefeed characters. For details about the configuration file for character string substitution, see Configuration file for character string substitution (jp1imss_replace_string_setting.conf) in Chapter 13. Definition Files.

Only the settings that need to be specified are described in the above tables. Any other settings that can be defined for condition and action definition in the above tables can be defined by users.

Note:

If an argument for an option includes a half-width space character, enclose the argument in double quotation marks (").
The number of commands that can be executed at the same time on the Item management server can be changed by the JP1/Base setting (by using the jcocmddef command) (1 by default). For details about the jcocmddef command, see the JP1/Base User's Guide.

The maximum number of commands that can be executed at the same time on the Item management server is six.
If a large number of JP1 events defined as the condition of automated actions occur, a large number of Items are registered accordingly. Therefore, narrow down the conditions, and set up operations so that you can recognize the Items registered by automated action.
Also read Notes in 5.7 Considering automatic Item registration.
For an example of an automated action definition that registers JP1 events generated from JP1/AJS3 as JP1/Service Support incidents and then displays them in the Monitor window via a link to the Web GUI of JP1/AJS3 - Web Console, see 4.9.3 Example automated action definition when linking with the Web GUI for JP1/AJS3 - Web Console .
For an example of an automated action definition that registers JP1 events triggered by the hosts monitored by JP1/PFM as JP1/Service Support incidents and then displays them in the Select Report window via a link to JP1/PFM - Web Console, see 4.10.3 Examples of automated action definitions when linking with JP1/PFM - Web Console.

To Page Top

(2) Example automated action definitions when JP1/Service Support issues JP1 events

Whether to issue JP1 events from JP1/Service Support must be defined on the JP1/Service Support side. For details, see Configuration file for issuing JP1 events (hptl_jp1_imss_jp1event_setting.properties) in Chapter 13. Definition Files.

To use the JP1 events issued by JP1/Service Support and link with JP1/IM - Manager, define automated actions on the JP1/IM - Manager side. JP1/Service Support issues the following types of JP1 events:

Event ID: 00005F00 (JP1 event for completed-action linkage)

This event is issued when an Item that was automatically registered is closed. It changes the response status on the JP1/IM - Manager side to Processed.
Event ID: 00005F01 (status-change JP1 event)

This event is issued to notify that the Item status has been changed and execute an automated action.
Event ID: 00005F02 (consolidated JP1 event for completed-action linkage)

This event is issued to change the response status on the JP1/IM - Manager side to Processed when automatically registered Items are closed in a batch. This event is only issued if event consolidation is enabled. Note that a JP1 event for completed-action linkage will not be issued if a consolidated JP1 event for completed-action linkage is issued. A consolidated JP1 event for completed-action linkage is not issued if the batch operation only closes one Item. In this case, a JP1 event for completed-action linkage is issued instead. For details on the JP1 events issued when performing batch operations on Items, see 3.7 Batch operations on Items.

For details about JP1 events for individual IDs, see Appendix E.1 List of JP1 Events.

The following table describes example automated action definitions for individual JP1 events.

Table 5‒15: Example automated action definitions (Event IDs: 00005F00, 00005F01, and 00005F02)
Condition	Action definition
[Event ID] `00005F00` [Extended event attributes] `PRODUCT_NAME:/HITACHI/JP1/IM/SS`	[Target host] `$EV"ITEMENTRY_ACTHOST"` [Action] `jcochstat -h $EV"ITEMENTRY_ACTHOST" -n $EV"ITEMENTRY_SEQNO" -k PROCESSED`^#1
[Event ID] `00005F01` [Extended event attributes] `PRODUCT_NAME:/HITACHI/JP1/IM/SS` `STATUS:Close`	[Action] `teldial -p $EV"RESPONDENT_TEL"`^#2
[Event ID] `00005F02` [Extended event attributes] `PRODUCT_NAME:/HITACHI/JP1/IM/SS`	[Target host] `$EV"ITEMENTRY_ACTHOST"` [Action] `jcochstat` `-h` `$EV"ITEMENTRY_ACTHOST"` `-n` `$EV"ITEMENTRY_SEQNO"` `-k` `PROCESSED`^#3

#1: This example shows that when an automatically registered Item is closed, JP1/Service Support issues a JP1 event and changes the response status on the JP1/IM - Manager to Processed.
#2: This example shows that when the status of an Item is change to Close, JP1/Service Support issues a JP1 event, the teldial command of JP1/TELstaff defined by an automated action is executed, and then contact is made by telephone to the person in charge of answering inquiries about the Item.
#3: This example shows that when you close automatically registered Items in a batch operation, JP1/Service Support issues a JP1 event and changes the response status on the JP1/IM - Manager to Processed. This applies to an environment in which consolidation of JP1 events is enabled.

Notes:

For details about the statuses to be specified, see the JP1/Integrated Management - Manager Overview and System Design Guide.
Any other setting items that can be defined for Condition and Action definition in the above table can be defined by users. The conditions can be defined in the definition file for status-change JP1 events. For details, see Definition file for status-change JP1 events (hptl_jp1_imss_jp1event_status.properties) in Chapter 13. Definition Files.
Whether JP1 events are consolidated depends on settings in the configuration file for issuing JP1 events. For details, see Configuration file for issuing JP1 events (hptl_jp1_imss_jp1event_setting.properties) in Chapter 13. Definition Files.
A JP1 event is issued to the event server on the local host, and then forwarded to another host according to the definitions in the forwarding setting file. For details, see the JP1/Base User's Guide.

To Page Top

(3) Linkage with JP1/IM - Manager in a cluster environment

If you run JP1/Service Support on a cluster system and link JP1/Service Support with JP1/IM - Manager to automatically register Items, the JP1/Base instance on the Item management server must also run on the cluster system. The following shows the configurations when JP1/Service Support is running on a cluster system:

On the Item management server, configure the JP1/Base environment on the logical host on which JP1/Service Support is running (recommended configuration).

In this configuration, a failure in either JP1/Service Support or JP1/Base will cause the nodes for both JP1/Service Support and JP1/Base to switch.
On the Item management server, configure the JP1/Base environment on a logical host other than the logical host on which JP1/Service Support is running.

Use this configuration only when JP1/Base has already started linking with other JP1 products.

In this configuration, if a failure occurs in either JP1/Service Support or JP1/Base, only the node of the program with a failure is switch to another node. The node for the program without a failure continues running.

In this case (when JP1/Service Support is running on the secondary node and JP1/Base is running on the primary node on a server), Items can be automatically registered without any problems.

For details about the operation and configuration of JP1/Base on a cluster system, see the JP1/Base User's Guide.

If an automated action (automatic Item registration) is executed during failover, the execution might fail. If you want to detect this problem, enable the function of delay monitoring for automated actions in JP1/IM - Manager. If this function is enabled, a JP1 event is issued when a delay occurs. Therefore, you can start investigation on the JP1/IM - Manager side in response to the delay. For details, see the JP1/Integrated Management - Manager Overview and System Design Guide.

To Page Top