In case of failure, check and consolidate the status as to in which environment what phenomenon occurred. The following table describes the items to be checked in case of failure:

Table 7-1 Items to be checked in case of failure

No.	Item to be checked		Machine on which error is detected
			Machine on which HCSC server is running	Machine on which operating environment is running	Machine on which service requester is running	Machine on which service component is running	Machine on which database is running
1	Basic points	Time when failure occurred	Confirm as to when (from when) the error occurred.
2		Operation executed just before failure occurrence	Confirm as to which operations were performed when the error occurred.
3		Machine on which error was detected	Confirm as to on which machine the error was detected. Machine on which HCSC server is running Machine on which operating environment is running Machine on which service requester is running Machine on which service component is running Machine on which database is running
4		Error contents	Specifically mention the type of phenomenon that occurred.
5	Operating environment	Version of Service Platform	Y	--	--	--	--
6		J2EE server product name and version	--	--	Y	Y	--
7		Database product name and version	--	--	--	--	Y
8		OS type and version	Y	Y	Y	Y	Y
9		Number of processors	Y	Y	Y	Y	Y
10		Memory	Y	Y	Y	Y	Y
11		Virtual memory	Y	Y	Y	Y	Y
12		Java version	Y	Y	Y	Y	Y
13		Patch applicable status	Y	Y	Y	Y	Y
14	Reproducibility	Reproducibility	Confirm whether it can be reproduced.
15		Occurrence frequency	In the case of reproducibility, confirm the frequency of error occurrence.
16	Configuration changes	Whether changed when occurred	Confirm whether the coding or environment was changed before occurrence of corresponding error.
17		Contents of changed places	If there are any changes, then specifically mention the changed contents.

Legend:

Y: Must be confirmed.

--: Confirmation not required.

The information described in Table 7-2 for each error type is required as data for investigations in Service Platform system.

Note that there are items that require settings for acquiring error information. For details about error information acquisition, see 7.3 Acquiring failure information. For details about the place where acquired error information is output, see 7.3 Acquiring failure information and 7.4 Types of error information.

The information for which the acquisition of error information is not set is the information that is not required for error investigations or inquiry. However, the acquisition of this information might be required depending on the status of error investigations. The information required for error investigations differ depending on the places of error occurrence.

Table 7-2 Information acquired for error investigation

No.	Information that can be acquired			Error type
				When error message or exception is output by user program	When error occurs in service component invoking request	When error occurs in operations (command operations or operations from screens of operating environment)
1	Material for the Service Platform	Message log		P	P	P
2		Request trace		P	P	--
3		Performance analysis trace		--	S	--
4		User message trace		S	S	--
5		Definition information	HCSC server configuration definition file	--	P	P
6			HCSC server setup definition file	--	P	P
7			HCSC server runtime definition file:	--	P	P
8			HCSC-Manager definition file	--	P	P
9			The HCSC-Manager command definition file	--	P	P
10			HCSC-Messaging command definition file	--	P	P
11			Service-information change definition file	--	S	S
12			User-defined reception runtime definition file	--	S	S
13			SOAP fault operation definition file	--	S	S
14			Client definition file	--	S	S
15	Material for J2EE server	Logs of J2EE server#, redirector, and server management commands		P	P	S
16		Logs of Administration Agent, Management Agent, and Management Server (Integrated log)		P	S	P
17		DABroker Library log		S	S	S
18		DB Connector (Activity log of resource adapter)		P	P	P
19		EJB client application log		P	P	--
20		User log		P	S	--
21		Definition information	Setup file of Component Container	S	P	P
22			Setup file of Manager	S	P	P
23			DB Connector property information setup in dbcon-xadisplayname	S	P	S
24			DB Connector property information setup in dbcon-nodisplayname	S	S	P
25	Material for Reliable Messaging	Start stop message log		--	S	P
26		Message log for J2EE server#		S	P	P
27		Method trace		S	P	P
28		Line trace		S	P	P
29		Definition information	Setup information of Reliable Messaging configuration property	S	P	P
30	Data of SOAP Communication Infrastructure	Trace		S	P	--
31		Application log		S	P	--
32		Definition information	Definition file (SOAP Communication Infrastructure)	S	P	--
33			Server definition files (SOAP Communication Infrastructure)	S	P	--
34	Data of JAX-WS engine	Trace		S	P	--
35		Application log		S	P	--
36		Definition information	Common definition file (JAX-WS engine)	S	P	--
37	Log and trace of HTTP Server			P	S	--
38	Error information of database	When HiRDB is used	HiRDB log (Including HiRDB definition information)	--	S	S
39			HiRDB client log and trace	--	S	S
40			Exception log and trace of HiRDB Type4 JDBC driver	--	S	S
41		When Oracle is used	Oracle log	--	S	S
42			Oracle JDBC Thin Driver log	--	S	S
43	Error information of JavaVM	JavaVM output message log		--	S	S
44		JavaVM thread dump		--	S	S
45		Log of garbage collection of JavaVM		--	S	S

Legend:

P: Primary material

S: Secondary material

--: Not required

#

The default directory to which the J2EE server outputs log data is Service-Platform-installation-directory\CC\server\public\ejb\J2EE-server-name\logs. Hereafter, this directory is called the J2EE server's log output directory.

You can change this directory by using the ejb.server.log.directory key in the usrconf.cfg file (option definition file for the J2EE server).