(a) Output format

The following figure shows the output format of the request trace:

Figure 7-7 Figure Output format of request trace

(b) Output contents

The following table lists and describes the contents output to the request trace:

Table 7-17 Table Contents output to the request trace

Item		Content
Number		The request identification information (parent ID) is displayed.
Date		The trace record collection date (yyyy/mm/dd format) is output.
Time		The trace record collection time (hh:mm:ss.sss format) in milliseconds in local time is output.
Product ID		The "CSCMSG" that indicates the identifier messaging infrastructure to identify product is output.
pid		The ID to identify the process is output.
Tid		The ID to identify the thread is output.
ID		Not displayed.
Message common ID		The request identification information (parent ID) is output.
Service request ID		The request identification information (child ID) is output.
Collection point identification information	Collection location	The trace collection point (collection location) is output: RCP:Standard reception URCP:User-defined reception SVSND: Server-to-server transfer (sending) SVRCV: Server-to-server transfer (receiving) BPRCP:Business process request reception BPREQ:Invoking a business process SVC: Invoking Service components (within the service adapter) SVCGP: Invoking service group
	Protocol type	The trace collection point information (protocol type) is output. However, the information is not displayed if the collection location is BPRCP, BPREQ, or SVCGP. SOAP:Web Services EJB:SessionBean WSR:MDB (WS-R) DBQ:MDB (DB queue) CUSTM:Protocols other than those mentioned above
	Detailed location	The trace collection point information (detailed location) is output: IN:Reception OUT:Response CAL:Invoke (other components) RET:Receive response (other components) WRN:Exception
	Name	The trace collection point information (name) is output. However, the information is not displayed if the collection location is RCP, URCP, BPREQ, or SVRCV. Server name Service ID of service adapter Service ID of business process Service group name
	Adapter type	The trace collection point information (adapter type) is output. However, the information is not displayed if the collection location is RCP, URCP, BPRCP, SVCGP, SVSND, or SVRCV. SVA:Service adapter BP:Business process
Result		The response result type is output. However, if the detailed location is IN or CAL, this information is not displayed. Normal end: NORMAL Abnormal end: ERROR
Additional information		The additional information for the response result is output.
CRLF		Record end code is output.

Timing of request trace output is of following types and the collection point differs for each type:

• When executing individual services
• When executing business process services
• When checking the operating status

(a) When executing an individual service

The following figure shows the trace collection point of request when executing an individual service:

Figure 7-8 Figure Trace collection point of request (when executing individual services)

The following table lists trace collection points. The "Numbers in figure" in this table corresponds to the numbers in "Figure7-8 Trace collection point of request(when executing individual services)".

Table 7-18 Table Trace collection point of request (when executing individual services)

Number in figure	Trace collection point
1	Entry to standard reception (Web Services)
2	Exit from standard reception (Web Services)
1	Entry to standard reception (SessionBean)
2	Exit from standard reception (SessionBean)
1	Entry to standard reception (MDB(WS-R))
2	Exit from standard reception (MDB(WS-R))
1	Entry to standard reception (MDB(DB queue))
2	Exit from standard reception (MDB(DB queue))
3	Invocation of service components of SOAP adapter
4	Point for receiving response from service components of SOAP adapter
3	Invocation of service components of SessionBean adapter
4	Point for receiving response from service components of SessionBean adapter
3	Invocation of service components of MDB (WS-R) adapter
4	Point for receiving response from service components of MDB (WS-R) adapter
3	Invocation of service components of MDB(DB queue) adapter
4	Point for receiving response from service components of MDB(DB queue) adapter
3	Invocation of service components of service adapters(CUSTOM) other than those mentioned above
4	Point for receiving response from service components of service adapters(CUSTOM) other than those mentioned above

(b) When executing business process services

The following figure shows the trace collection point of the request trace when executing business process services:

Figure 7-9 Figure Trace collection point of request (when executing business process services)

The following table lists trace collection points. The "Numbers in figure" in this table corresponds to the numbers in "Figure 7-9 Trace collection point of request (when executing business process services)".

Table 7-19 Table Trace collection point of request (when executing business process services)

Number in figure	Trace collection point
1	Entry to standard reception (Web Services)
2	Exit from standard reception (Web Services)
1	Entry to standard reception (SessionBean)
2	Exit from standard reception (SessionBean)
1	Entry to standard reception (MDB(WS-R))
2	Exit from standard reception (MDB(WS-R))
1	Entry to standard reception (MDB(DB queue))
2	Exit from standard reception (MDB(DB queue))
1	Entry to user-defined reception
2	Exit from user-defined reception
7	Invocation of service components of SOAP adapter
8	Point for receiving response from service components of SOAP adapter
7	Invocation of service components of SessionBean adapter
8	Point for receiving response from service components of SessionBean adapter
7	Invocation of service components of MDB (WS-R) adapter
8	Point for receiving response from service components of MDB (WS-R) adapter
7	Invocation of service components of MDB(DB queue) adapter
8	Point for receiving response from service components of MDB(DB queue) adapter
7	Invocation of service components of service adapters(CUSTOM) other than those mentioned above
8	Point for receiving response from service components of service adapters(CUSTOM) other than those mentioned above
3	Invocation of business process services
4	Point for receiving response from business process services
5	Entry to business process reception
6	Exit from business process reception

(c) When checking the operating status

The following figure shows the trace collection point of the request trace when checking the operating status:

Figure 7-10 FigureTrace collection point of request (when checking the operating status)

The following table lists trace collection points. The "Number in figure" in this table corresponds to the numbers in "Figure 7-10 Trace collection point of request (when checking the operating status)".

Table 7-20 Table Trace collection point of request (when checking the operating status)

Number in figure	Trace collection point
1	Entry to standard reception (Web Services)
2	Exit from standard reception (Web Services)
1	Entry to SOAP reception
2	Exit from SOAP reception

Settings are required to acquire the request trace. For details, see "7.3.1(2) Request trace".

Following is the output destination of request trace:

 
Path specified in the request trace-filepath property of the HCSC server runtime definition file.
 

If the specified path does not exist, or in case of an incorrect path, trace is output in the output destination of the omitted value.

The following table shows the trace file name of request trace:

Table 7-21 Table Trace file name of request trace

Output mode of trace file	Trace file name
For Wraparound mode	cscmsgreq_<HCSC server name>_<number of files>.log
For Shift mode	cscmsgreq_<HCSC server name>_.log