6.1.2 Message monitoring
Application Server outputs a specific message to a log file when an error occurs. You can use and set up a monitoring application or monitoring system to monitor messages that are output, and to notify error occurrences when messages are output.
Messages are output to the log files shown in the following table. The table also shows keys that can be used for monitoring. Set the monitoring application or monitoring system to monitor these keys in log files.
|
Log file to which messages are output |
Key usable for monitoring |
||
|---|---|---|---|
|
Type |
Storage location |
File format/file switchover type |
|
|
Web server error log |
installation_directory_for_Application_Server/javaee/logs/nodes/node_name/server_instance_name/error.[n] |
WRAP2#1/ new file creation type#2 |
|
|
Java EE-server server instance message log |
installation_directory_for_Application_Server/javaee/logs/nodes/node_name/server_instance_name/je_message[n].log |
SEQ2#3 |
|
|
Domain administration server message log |
installation_directory_for_Application_Server/javaee/logs/domains/domain_name/das_message[n].log |
SEQ2#3 |
|
- #1:
-
File format for the JP1/Base log file trapping function. With this format, when log data is written to the end of the last log file, logging continues with the first log file, deleting the existing data in the file.
- #2:
-
Switchover type of monitoring-target files. The file to be monitored is switched in sequence within some files. Not all of these files exist when monitoring starts.
- #3:
-
File format for the JP1/Base log file trapping function. With this format, a new log file is created with the same name and logging continues with the new log file after the existing log file is saved with a different name or deleted.
- #4:
-
The XXXXX part indicates a unique five-digit message number managed by the program that outputs the message.