8.3.4 Conversion to JP1 events
The message-mapping file is used to convert the log messages output with the Management Server, J2EE server, and user log functionality into JP1 events.
- Organization of this subsection
(1) JP1 events for Management Server
There are following two types of JP1 events for the Management Server:
-
JP1 events defined in Cosminexus
-
JP1 events specified in the message mapping file for the Management Server
(a) JP1 events defined in Cosminexus
Cosminexus issues JP1 events when the messages with the following message IDs are output:
|
Event ID |
Trigger |
Message ID |
|---|---|---|
|
0x00012050 |
Management Server startup |
KEOS10101-I |
|
0x00012051 |
Stopping the Management Server |
KEOS10102-I |
|
0x00012060 |
Addition of a Web system to the domain |
KEOS23301-I |
|
0x00012061 |
Deletion of a Web system from the domain |
KEOS23302-I |
|
0x0001206A |
Unit addition or deletion to the Web system and deployment or undeployment of a J2EE application (changing the Web system) |
KEOS23303-I |
|
0x00012070 |
Administration Agent startup |
KEOS21100-I |
|
0x00012071 |
Stopping the Administration Agent |
KEOS21101-I |
(b) JP1 events specified in the message mapping file for the Management Server
JP1 events are issued for the messages specified in the template file (mserver.jp1event.system.mapping.properties) of the message-mapping file for the Management Server.
The storage destination for the template file is as follows:
-
In Windows
Cosminexus-installation-directory\manager\config\templates\
-
In UNIX
/opt/Cosminexus/manager/config/templates
The following table describes the JP1 events for the Management Server that are issued based on specification of the message-mapping file:
|
Event ID |
Trigger |
Criticality of JP1 events specified by mapping |
|---|---|---|
|
0x00012000 |
Emergency-level failure of the logical server detected in the Management Server |
Emergency |
|
0x00012001 |
Alert-level failure of the logical server detected in the Management Server |
Alert |
|
0x00012002 |
Critical-level failure of the logical server detected in the Management Server |
Critical |
|
0x00012003 |
Error-level failure of the logical server detected in the Management Server |
Error |
|
0x00012004 |
Warning-level failure of the logical server detected in the Management Server |
Warning |
|
0x00012005 |
Notice-level failure of the logical server detected in the Management Server |
Notice |
|
0x00012006 |
Information-level failure of the logical server detected in the Management Server |
Information |
|
0x00012020 |
Emergency-level failure in the Management Server |
Emergency |
|
0x00012021 |
Alert-level failure in the Management Server |
Alert |
|
0x00012022 |
Critical-level failure in the Management Server |
Critical |
|
0x00012023 |
Error-level failure in the Management Server |
Error |
|
0x00012024 |
Warning-level failure in the Management Server |
Warning |
|
0x00012025 |
Notice-level failure in the Management Server |
Notice |
|
0x00012026 |
Information-level failure in the Management Server |
Information |
(2) JP1 events for J2EE server
JP1 events for the J2EE server are issued for the messages specified in the following template files:
-
Message mapping file for the shared J2EE servers (manager.jp1event.system.mapping.properties)
-
Message mapping file for the individual J2EE server (manager.logical-server-name.jp1event.system.mapping.properties)
The storage destination for the template file is as follows:
-
In Windows
Cosminexus-installation-directory\manager\config\templates\
-
In UNIX
/opt/Cosminexus/manager/config/templates
The following table describes the JP1 events for the J2EE server based on the specification of the message-mapping file:
|
Event ID |
Trigger |
Criticality of JP1 events specified by mapping |
|---|---|---|
|
0x00012080 |
Emergency-level failure of J2EE server |
Emergency |
|
0x00012081 |
Alert-level failure of J2EE server |
Alert |
|
0x00012082 |
Critical-level failure of J2EE server |
Critical |
|
0x00012083 |
Error-level failure of J2EE server |
Error |
|
0x00012084 |
Warning-level failure of J2EE server |
Warning |
|
0x00012085 |
Notice-level failure of J2EE server |
Notice |
|
0x00012086 |
Information-level failure of J2EE server |
Information |
|
0x00012090 |
Emergency-level failure of application detected in J2EE server |
Emergency |
|
0x00012091 |
Alert-level failure of application detected in J2EE server |
Alert |
|
0x00012092 |
Critical-level failure of application detected in J2EE server |
Critical |
|
0x00012093 |
Error-level failure of application detected in J2EE server |
Error |
|
0x00012094 |
Warning-level failure of application detected in J2EE server |
Warning |
|
0x00012095 |
Notice-level failure of application detected in J2EE server |
Notice |
|
0x00012096 |
Information-level failure of application detected in J2EE server |
Information |
(3) JP1 events for J2EE users
JP1 events for J2EE users are issued for messages output with the user log functionality. For details about the settings of JP1 events for user logs, see Chapter 13 in manual uCosminexus Application Server Operation, Monitoring, and Linkage Guide.
|
Event ID |
Trigger |
Criticality of JP1 events |
|---|---|---|
|
0x000120D0 |
Emergency-level failure of application |
Emergency |
|
0x000120D1 |
Alert-level failure of application |
Alert |
|
0x000120D2 |
Critical-level failure of application |
Critical |
|
0x000120D3 |
Error-level failure of application |
Error |
|
0x000120D4 |
Warning-level failure of application |
Warning |
|
0x000120D5 |
Notice-level reporting of application |
Notice |
|
0x000120D6 |
Information-level reporting of application |
Information |