Specify the message ID list in the following format:

[Indicator]Message-ID

• Code one message ID in one line.
• An indicator wherein a hash mark (#) is specified is a comment.
• If you specify a plus (+) in the indicator or if you omit the indicator, the corresponding message ID is reported as the Management event.
• If you use a hyphen (-) in the indicator, the corresponding message ID is not reported as the Management event. You use this facility when the message ID mentioned in the default Management event issue message ID list is not to be sent as the Management event.
• Whitespaces at the beginning or end of the line and blank lines are ignored.
• When the same message ID is specified many times, the message ID coded in the end becomes valid.
• Always specify an indicator when the message ID starts with a plus (+) or a hyphen (-).

Any storage location and file name is possible. You can use the following characters in the file name:

Alphanumeric characters, periods (.), yen signs (), colons (:), plus signs (+), or hyphens (-)

Define the message IDs that are reported as Management events.

The following table describes the default message IDs that are reported as Management events:

Table 10-2 Message ID for Management issue (Default)

Functionality	Monitoring target	Message ID
Monitoring resource depletion	Memory usage status	KDJE34500-W
	Number of file descriptors	KDJE34520-W
	Number of threads	KDJE34540-W
	Number of thread dump files	KDJE34580-W KDJE34581-E
	HTTP request pending queue (pending queue of each Web application and the default pending queue)	KDJE34621-W
	Number of HTTP sessions	KDJE34640-W
	Connection pool utilization state	KDJE34660-W KDJE34661-W
Monitoring J2EE application execution time	J2EE application execution time	KDJE52702-W KDJE52703-W KDJE52705-W KDJE52713-E
Detecting connection failure	A timeout in connection failure detection	KDJE48602-W
	Connection managing threads	KDJE48603-W
Monitoring full garbage collection count	Full garbage collection count	KDJE53850-W
Monitoring the number of pending requests for each URL group	Upper threshold limit for the number of requests pending for each URL group	KDJE53860-W
	Lower threshold limit for the number of requests pending for each URL group	KDJE53861-I
Cluster connection pool	Connection pool status	KDJE49650-I KDJE49653-I KDJE49655-E KDJE49657-E KDJE49660-I KDJE49663-E KDJE49664-E KDJE49669-E
	Connection managing threads	KDJE49671-I

A sample is as follows:

When KDJE34580-W and KDJE34660-W are not reported as Management events:

# Monitoring of resources # : Status of memory (Java Heap) KDJE34500-W # : Number of file descriptors KDJE34520-W # : Number of threads KDJE34540-W # : Number of thread dump files -KDJE34580-W KDJE34581-E # : Number of HTTP requests in queue KDJE34621-W # : Number of HTTP sessions KDJE34640-W # : Status of connection pool -KDJE34660-W KDJE34661-W # Monitoring of execution time of user program KDJE52702-W KDJE52703-W KDJE52705-W KDJE52713-E

To create this file, see the following sample of the message ID list file for issuing Management events:

• In Windows
  Cosminexus-installation-directory\manager\config\templates\mevent.midlist.conf
  
• In UNIX
  /opt/Cosminexus/manager/config/templates/mevent.midlist.conf
  

• Management events are not issued for the following message IDs. If you specify these message IDs, the specification is ignored.
  
  • KDJE90001-E
  • KDJE90002-E
  • KDJE90003-E
  • KDJE90005-W
  • KDJE90006-W
  • KDJE90009-W
• The message IDs that you can specify include only the specific message IDs output by the J2EE server or batch server that are integrated with the functionality for issuing Management events. Even if you specify other system message IDs, message IDs output by J2EE applications or batch applications, the Management events are not issued.