Correlation event generation system profile (egs_system.conf)
- Organization of this page
Format
VERSION=1 START_OPTION={cold | warm}
File
egs_system.conf (correlation event generation system profile)
egs_system.conf.model (model file for the correlation event generation system profile)
Storage directory
- In Windows
-
- For a physical host:
-
Console-path\conf\evgen\profile\
- For a logical host:
-
shared-folder\jp1cons\conf\evgen\profile\
- In UNIX
-
- For a physical host:
-
/etc/opt/jp1cons/conf/evgen/profile/
- For a logical host:
-
shared-directory/jp1cons/conf/evgen/profile/
Description
This file defines the start and stop operations for the Event Generation Service.
When the definitions are applied
The settings in the correlation event generation system profile take effect at the following times:
-
When JP1/IM - Manager starts
-
When the file is reloaded by the jco_spmd_reload command
Information that is specified
- VERSION=1
-
Specifies the file version. There is no need to edit this parameter. If this parameter is omitted or a numeric value other than 1 is specified, VERSION=1 is assumed.
- START_OPTION={cold | warm}
-
Specifies the startup option for the Event Generation Service.
Specify the value that corresponds to the operation to be performed during startup and stop processing. The permitted values are cold and warm. The default is warm. This value is not case sensitive. If the parameter is omitted or an invalid value is specified, warm is assumed.
The table below describes the operation of the Event Generation Service during startup and stop processing depending on whether cold or warm is specified. Change the value as appropriate to your operations.
Table 2‒33: Operation of the Event Generation Service during startup and stop processing depending on the start option Start option
Operation of Event Generation Service
Operation during startup processing#1
Operation during stop processing
cold
When the start option was set to cold during the previous stop processing:
JP1 events registered after the Event Generation Service started are subject to generation processing.
All correlation events under generation processing fail and are output to the correlation event generation history file.
When the start option was set to warm during the previous stop processing:
All correlation events under generation processing fail and the JP1 events acquired since the Event Generation Service started are subject to generation processing.
warm
When the start option was set to cold during the previous stop processing:
JP1 events are subject to generation processing beginning with the one that immediately follows the last JP1 event acquired by the Event Generation Service during the previous stop processing.
Information about the last JP1 event acquired before the service stopped, details of the generation processing, and the correlation event generation definition information are output to internal logs and saved.
When the start option was set to warm during the previous stop processing:
The correlation event generation processing performed during the previous stop processing is inherited, and JP1 events are subject to generation processing beginning with the one that immediately follows the last JP1 event acquired by the Event Generation Service during the previous stop processing.#2
- #1
-
When the Event Generation Service starts for the first time, it functions as follows, regardless of the start option value:
The Event Generation Service acquires JP1 events that are registered after the Event Generation Service starts.
The Event Generation Service loads the correlation event generation definition and starts processing according to the definition.
Note that the default is that correlation events are not generated because the correlation event generation definition has not been set.
- #2
-
If the correlation event generation definition used when JP1/IM - Manager stopped differs from the definition used the next time JP1/IM - Manager starts, all correlation events under generation processing fail. After the contents are cleared, JP1 events are subject to generation processing again starting with the one that immediately follows the JP1 event acquired during the previous stop processing.
If you run JP1/IM - Manager in a cluster system, change the setting to warm.
In the event of failover, products are stopped and started in the following order: stopping JP1/IM - Manager
stopping JP1/Base
starting JP1/Base
starting JP1/IM - Manager. If failover occurs while the parameter is set to cold, the system cannot acquire JP1 events that occur during the period of stopping JP1/IM - Manager
stopping JP1/Base and during the period of starting JP1/Base
starting JP1/IM - Manager. Therefore, if you leave the parameter set to cold, some JP1 events that are subject to generation processing might be missed.