The internal error information and the failure information of the business process when there is a failure while operating HCSC server is captured as exception log. Maintenance Service uses the exception log for analyzing the failure. The following table describes the contents output as exception log of Service Platform and the output destination:

Table 7-46 Table Output content and output destination of exception log

Type of exception log	Output contents	Output destination path of exception log file	Log file name
Exception log of HCSC-Manager	Acquires the internal exception information of HCSC-Manager.	Path specified in cscmng.log.dir parameter of HCSC-Manager definition file#1	exception<number of files>.log#1
Exception information when a J2EE server failure occurs	Acquires the internal exception information when a failure has occurred in the HCSC server.	Path specified in the output destination #2 of exception log of J2EE server (exception information at the time of failure occurrence)	For Wraparound mode cjexception<number of files>.log#1 For Shift mode cjexception.log
Exception log of HCSC server	Acquires the information of the exception (stack trace) that has occurred at the following locations: EJB invocation part of Custom reception framework, Custom adapter development framework Reception and service adapter using Custom reception framework, Custom adapter development framework HCSC server (standard reception, SOAP reception, message delivery control, SOAP adapter, SessionBean adapter, MDB (WS-R) adapter, MDB (DB queue) adapter.	Path specified in the methodtrace-filepath property of the HCSC server runtime definition file#3	For Wraparound mode cscmsgexp_<HCSC server name>_<number of files>.log#3 For Shift mode cscmsgexp_<HCSC server name>_.log
Exception log of DB adapter	Acquires the stack trace when a failure has occurred in DBadapter	Path specified in the methodtrace-filepath property of the HCSC server runtime definition file#3	For Wraparound mode cscdbaexp_<HCSC server name>_<number of files>.log#3 For Shift mode cscdbaexp_<HCSC server name>_.log
Exception log of TP1 adapter	Acquires the stack trace when a failure has occurred in TP1 adapter	<Working directory of J2EE server>\ejb\<J2EE server name>\logs\CSCADP\TP1ADP\maintenance\<Service ID>	For Wraparound mode exception< number of files>.log#4 For Shift mode exception.log
Exception log of Object Access adapter	Acquires the stack trace when a failure has occurred in Object Access adapter	<Working directory of J2EE server>\ejb\<J2EE server name>\logs\CSCADP\OAADP\maintenance\<Service ID>	For Wraparound mode exception<number of files>.log#5 For Shift mode exception.log
Exception log of Message Queue adapter	Acquires the stack trace when a failure has occurred in Message Queue adapter	<Working directory of J2EE server>\ejb\<J2EE server name>\logs\CSCADP\MQADP\maintenance\<Service ID>	For Wraparound mode exception<number of files>.log#6 For Shift mode exception.log
Exception log of FTP adapter	Acquires the stack trace when a failure has occurred in FTP adapter	Path specified in FTP adapter runtime-environment property file#7	For Wraparound mode cscftpadpexp_<HCSC server name>_<number of files>.log#7 For Shift mode cscftpadpexp_<HCSC server name>_.log
Exception log of file operations adapter	Acquires the stack trace when a failure has occurred in file operations adapter	Path specified in file operations adapter runtime-environment property file#8	For Wraparound mode cscadpfopexp_<HCSC server name>_<number of files>.log#8 For Shift mode cscadpfopexp_<HCSC server name>_.log
Exception log of mail adapter	Acquires the stack trace when a failure has occurred in mail adapter	Path specified in mail adapter runtime-environment property file#9	For Wraparound mode cscmailadpexp_<HCSC server name>_<number of files>.log#9 For Shift mode cscmailadpexp_<HCSC server name>_.log
Exception log of business process	Acquires the stack trace when a failure has occurred in business process	Path specified in the methodtrace-filepath property of the HCSC server runtime definition file#3	For Wraparound mode cscbpexp_<HCSC server name>_<number of files>.log#3 For Shift mode cscbpexp_<HCSC server name>_.log

Note#1

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

cscmng.log.exception.filesize=Exception log file size

cscmng.log.exception.filenum= Exception log file numbers

cscmng.log.dir= Exception log output destination directory path

For details on the HCSC-Manager definition file, see"HCSC-Manager definition file" in "Service Platform Reference Guide".

Note#2

Specify the output destination of exception log (exception information when a failure occurs) of J2EE server to usrconf.cfg (option definition file for J2EE server). Default output destination is<Installation directory of Service Platform>\CC\server\public\ejb\<J2EE server name>\logs.

For details on usrconf.cfg,see "2.3 usrconf.cfg (option definition file for J2EE server) " in "Application Server Definition Reference Guide".

Specify the size and number of exception log files in usrconf.properties (user property file for J2EE server). For details on usrconf.properties, see "2.4 usrconf.properties (user property file for J2EE server) " in "Application Server Definition Reference". For the details on settings of the rotation method of log files, see "Application Server Definition Reference Guide".

Note#3

For details on the specification of output destination path and numbers of the HCSC server runtime definition file, see "HCSC server runtime definition file" in "Service Platform Reference Guide".

Note#4

For details on the specification of numbers of the TP1-adapter runtime-environment property fileTP1, see "TP1 adapter execution environment property file" in "Service Platform Reference Guide".

Note#5

For details on the specification of numbers of the Object Access adapter runtime-environment property file, see "Object Access adapter execution environment property file" in "Service Platform Reference Guide".

Note#6

For details on the specification of numbers of the Message Queue adapter runtime-environment property file, see "Message Queue adapter execution environment property file" in "Service Platform Reference Guide".

Note#7

For details on the output destination path and numbers of the FTP-adapter runtime-environment property file, see "FTP adapter execution environment property file" in "Service Platform Reference Guide".

Note#8

For details on the output destination path and numbers of File operations adapter runtime-environment property file, see "File operations adapter execution environment property file" in "Service Platform Reference Guide".

Note#9

For details on the output destination path and numbers of the Mail adapter runtime environment property file, see "Mail adapter execution environment property file" in "Service Platform Reference Guide".

You can acquire the internal maintenance information of the HCSC-Manager internal as a maintenance log. The maintenance log is also used as a communication trace and message log between HCSC-Manager and external elements (such as Manager, HCSC management MBean, and the repository). The Maintenance Service uses the maintenance log for analyzing failures.

The following table lists and describes the content and the output destination that is output as the maintenance log:

Table 7-47 Table Content and the output destination of the maintenance log

Output content	Output destination path of the Maintenance log file	Log file name
Acquire the internal maintenance information of HCSC-Manager	Path specified in the cscmng.log.dir parameter of the HCSC-Manager definition file	maintenance<number of files>.log

If a failure occurs on a HCSC server and the cause is difficult to determine, you can acquire the required information as method trace. The Maintenance Service uses the method trace for analyzing failures.

The following table describes the output content and output destination of method traces.

Table 7-48 Table Output content and output destination of method trace

Method trace type	Output content	Output destination path of method trace	Trace file name
Method trace of HCSC server (messaging infrastructure)	Acquires the internal maintenance information of the HCSC server (messaging infrastructure).	Path specified in the methodtrace-filepath property of the HCSC server runtime-definition file. If the specified path does not exist, or if there is an error in the path, trace is output in the output destination of the omitted value.	For Wraparound mode cscmsgmtd_<HCSC server name>_<number of files>.log For Shift mode cscmsgmtd_<HCSC server name>_.log
Method trace of the HCSC server(business process infrastructure)	Acquires the internal maintenance information of the HCSC server(business process infrastructure). In the business process infrastructure, a trace is present when executing the trace and process instance related commands, when you execute the business process. This manual describes the trace when executing business processes. The trace at the time of executing process instance related commands is same as the trace output in Management Server. For details, see "Application Server Maintenance and Migration Guide".		For Wraparound mode cscbpmtd_<HCSC server name>_<number of files>.log For Shift mode cscbpmtd_<HCSC server name>_.log
Method trace of the HCSC server (DB adapter)	Acquires the internal maintenance information of the HCSC server (DB adapter). For details on the method trace of a service adapter other than DB adapter, see the description of each service adapter in "7.7 Troubleshooting during service component invocation request".		For Wraparound mode cscdbamtd_<HCSC server name>_<number of files>.log For Shift mode cscdbamtd_<HCSC server name>_.log