A. List of Snapshot Logs to Be Collected

This section describes the execution environment directories of the configuration software that are to be collected when you want to collect snapshot logs at the same time. Note that if you expand the collected ZIP file, the directories are extracted in the same directory configuration as that before collection.

When you collect all snapshot logs at the same time, the log files and definition files of the configuration software and libraries of a system built with the application server are collected. You can change the directory paths to be collected by editing the following files. For details about the settings for collecting the snapshot log, see the subsection 3.3.3 Settings for collecting snapshot logs (Systems for executing J2EE applications) or the subsection 3.3.4 Settings for collecting snapshot log (Systems for executing batch applications).

The following table describes the correspondence with the data required for troubleshooting and the snapshot log data type.

Table A‒1: Correspondence with the data necessary for troubleshooting and snapshot log data type

Data necessary for troubleshooting		Data type of snapshot log
Application Server log	Message log	Message log
	User log	Other logs
	Exception log	Other logs
	Maintenance log	Maintenance log
EJB client application system log	Message log	Message log
	User log	Other logs
	Exception log	Other logs
	Maintenance log	Maintenance log
Trace based performance analysis		Performance, error analysis trace
Thread dumps of JavaVM		Dump
GC logs of JavaVM		Other logs
Memory dump		Dump
JavaVM log file		Other logs
Error report files		Dump
OS state or log		Other logs
Statistical information of OS		Other logs
Definition information		Definition information
Operation directory		User data
Resource setting		User data
Web server log		Message log
		Other logs
		Access log
		Internal interface
JavaVM stack trace		Other logs
Event log of the Explicit Memory Management functionality		Other logs

Important note

The snapshot log is collected for directories created by default during installation of the configuration software in the default state. If the output destination and working directory of the log are changed, customize the collection destination.

Organization of this section

• A.1 Overview of the list of the snapshot log to be collected

• A.2 Cosminexus Component Container

• A.3 Cosminexus Component Transaction Monitor

• A.4 Cosminexus DABroker Library

• A.5 Cosminexus Developer's Kit for Java

• A.6 Cosminexus Performance Tracer

• A.7 Cosminexus Web Services - Security

• A.8 Cosminexus HTTP Server

• A.9 Microsoft Internet Information Service

• A.10 HCSC server

• A.11 HCSC server (FTP receipt)

• A.12 HCSC server (TP1 adapter)

• A.13 HCSC server (File adapter)

• A.14 HCSC server (Object Access adapter)

• A.15 HCSC server (Message Queue adapter)

• A.16 HCSC server (FTP adapter)

• A.17 HCSC server (SFTP adapter)

• A.18 HCSC server (file operation adapter)

• A.19 HCSC server (FTP inbound adapter)

• A.20 HCSC server (mail adapter)

• A.21 HCSC server (HTTP adapter)

• A.22 HCSC server (command adapter)

• A.23 HCSC server (file event reception)

• A.24 Audit log

• A.25 Other information

To Page Top