The message log is output always.

The file size and number of files that are output by message log can be changed as and when required. For details about commands, see 7.4.1 Message log.

(a) HCSC-Manager log

Specify the following parameters in the HCSC-Manager definition file:

• cscmng.log.message.filesize=message-log-file-size
• cscmng.log.message.filenum=message-log-number-of-files

For details about the HCSC-Manager definition file, see HCSC-Manager definition file in the manual Cosminexus Service Platform Reference.

(b) Cosminexus integrated message log

Specify the file size and number of files for integrated message log in manager.cfg (Manager log setup file). For details about manager.cfg, see 10.10 manager.cfg (Manager setup file) in the manual Cosminexus Application Server Server Definitions.

(c) Cosminexus J2EE server activity log

Specify the file size and number of files for J2EE server activity logs in usrconf.properties (User property file for J2EE server). For details about usrconf.properties, see 2.4 usrconf.properties (User property file for J2EE servers) in the manual Cosminexus Application Server Server Definitions.

Specify whether the request trace can be collected in the following properties of HCSC server runtime definition file while acquiring request trace.

Furthermore, you can change the output destination path, file size, and number of files.

• requesttrace=whether-or-not-request-trace-is-to-be-collected (specify ON)
• requesttrace-filepath=path-of-request-trace-output-destination
• requesttrace-filesize=size-of-request-trace
• requesttrace-filenum=request-traces-count

For details about request trace see 7.4.2 Request trace.

The collection method and output destination of the performance analysis trace file are common to the entire Cosminexus system. For details about the performance analysis trace, see 7.4.3 Performance Analysis Trace. For details about how to acquire the performance analysis trace file and output destination, see 7.3 Performance analysis trace file in the manual Cosminexus Application Server Function Guide - Maintenance, Migration, and Compatibility.

Specify whether the user message trace can be collected in the following properties of HCSC server runtime definition file while acquiring user message trace:

• telegramtrace= Whether user message trace is collected or not (Set as ON)

The output destination path, file size and number of files can be changed in the following properties:

• telegramtrace-filepath= User message trace output destination path
• telegramtrace-filesize= User message trace file size
• telegramtrace-filenum= Number of user message trace files
• telegramtrace-trigger= Timing of user message trace output

For details about the user message trace, see 7.4.4 User message trace.

A definition set in Cosminexus Service Platform is required for error investigations. The following table describes about the definition file of Cosminexus Service Platform. For details about the definition, see 6. Definition Files in the manual Cosminexus Service Platform Reference.

This section describes how to acquire the maintenance information required to contact the system administrator or Maintenance Service. For details about the maintenance log and trace, see 7.4.5 Maintenance log and trace.

(a) Exception log

The exception log is output always. You can change the file size and number of files that are output.

For details about the exception log, see 7.4.5(1) Exception log.

(b) Maintenance log

The maintenance log is output always. You can change the file size and number of files that are output for maintenance log.

Specify the following parameters in the HCSC-Manager definition file:

• cscmng.log.maintenance.filesize=maintenance-log-file-size
• cscmng.log.maintenance.filenum=maintenance-log-number-of-files

For details about the HCSC-Manager definition file, see HCSC-Manager definition file in the manual Cosminexus Service Platform Reference.

(c) Installation log

Output always.

(d) Method trace

A method trace is output always. To perform method trace, you must determine its output destination, file size, number of files, and output level. Specify the following properties in the HCSC server runtime definition file:

Specify the following properties in the HCSC server runtime definition file:

• methodtrace-filepath=path-of-method-trace-output-destination
• methodtrace-filesize=size-of-method-trace-file
• methodtrace-filenum=number-of-method-trace-files
• methodtrace-level=method-trace-output-level

For details about the HCSC server runtime definition file, see HCSC server runtime definition file in the manual Cosminexus Service Platform Reference.

(e) Maintenance information

The following table describes the maintenance information required for error investigation:

Table 7-4 Maintenance information

Maintenance information	Output destination of data
HCSC server repository information	All the files and directories under Service Platform installation directory\CSC\repository#1
HCSC-Manager maintenance information	All the files and directories under Service Platform installation directory\CSC\config\manager
HCSC server maintenance information	All the files and directories under Service Platform installation directory\CSC\spool
	All the files and directories under Service Platform installation directory\CSC\system
	All the files and directories under the folder specified in hcscserver-data-filepath property of HCSC server setup definition file (When the hcscserver-data-filepath property is not specified, all the files and directories under the <Service Platform installation directory>\CSC\spool\msg\)#2

#1

When many operating and execution environments (Environment variable CSCMNG_HOME is set) are build on one machine, consider all the files and directories under %CSCMNG_HOME%\repository.

#2

This directory is required when HCSC server is setup in a configuration that does not use a database.