4.1.3 Internal control of JP1 events by JP1/IM - Manager

(1) JP1 event control when not using the integrated monitoring database

If you do not use the integrated monitoring database, JP1 events are collected from the JP1/Base event database by the JP1/IM - Manager's event base service and event generation service.

Figure 4‒4: Internal control of JP1 events by JP1/IM - Manager (when the integrated monitoring database is not used)

The JP1 events acquired by these two services are processed in various ways after they have been filtered by the event acquisition filter according to set conditions.

Processing of acquired JP1 events by the event base service

JP1/IM - Manager sends JP1 events from the event base service to the event console service, the automatic action service, and the central scope service. After the event base service receives notification from all of these services that they have received the JP1 events, it executes the next processing task. Therefore, if a large number of JP1 events are issued, the processing of JP1 events might be delayed. We recommend that you filter JP1 events and use only the necessary events for management.

Using the jcoimdef command, you can adjust the JP1 event acquisition and transfer processing performed by the event base service (for example, you can change the event acquisition start location, or the transfer timeout period and retry setting). For details, see jcoimdef in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

Processing of acquired JP1 events by the event generation service

This service performs correlation event issue based on issue definitions. For details, see 4.3 Issue of correlation events.

To Page Top

(2) JP1 event control when using the integrated monitoring database

When you use the integrated monitoring database, JP1 events are collected from the JP1/Base event database by the JP1/IM - Manager's event base service. The acquired JP1 events are stored in the integrated monitoring database.

Figure 4‒5: Internal control of JP1 events by JP1/IM - Manager (when the integrated monitoring database is used)

The event base service acquires JP1 events and executes various processing tasks.

If you execute the jcoimdef command with -1 specified for the -b option, the event base service acquires JP1 events from the next event after the event that has the oldest serial number (the event at which JP1/IM - Manager stopped last time) among the JP1 events processed before JP1/IM - Manager is stopped. -1 specified for the -b option, JP1 event is acquired depends on whether the event was processed before JP1/IM - Manager stopped.

For JP1 events that were processed before JP1/IM - Manager stopped:

JP1 events are acquired from the integrated monitoring database, where the event acquisition filter is not used.

For JP1 events that were not processed before JP1/IM - Manager stopped:

JP1 events are acquired from the JP1/Base event database.

These JP1 events have been filtered by the event acquisition filter. JP1 events acquired from the event database are stored in the integrated monitoring database.

Processing of acquired JP1 events by the event base service

In the event base service, JP1/IM - Manager generates a correlation event according to the correlation event generation definition. Then, JP1/IM - Manager sends JP1 events from the event base service to the event console service, the automatic action service, and the central scope service. After the event base service receives notification from all of these services that they have received the JP1 events, it executes the next processing task. Therefore, if a large number of JP1 events are issued, the processing of JP1 events might be delayed. We recommend that you filter JP1 events and use only the necessary events for management.

Using the jcoimdef command, you can adjust the JP1 event acquisition and transfer processing performed by the event base service (for example, you can change the event acquisition start location, or the transfer timeout and retry setting). For details, see jcoimdef in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

To Page Top