7.7.16 Troubleshooting when the JSON-XML transformation function is used for HTTP linkage

(a) Output format

Performance analysis traces are output to files in the same format as the performance analysis traces for the J2EE server. For details, see 7.3 Collecting the trace based performance analysis file by using Management Server in the Application Server Maintenance and Migration Guide.

(b) Output items

For details about the items that are output to performance analysis trace files, see the following sections:

• For the HTTP reception

  7.7.14(3) Performance analysis trace

• For the HTTP adapter

  7.7.15(3) Performance analysis trace

(c) Collection points of performance analysis traces

The collection points of performance analysis traces for the HTTP reception and those for the HTTP adapter are different as follows:

• For the HTTP reception

  The following figure shows the collection points of performance analysis traces for the HTTP reception.

  Figure 7‒123: Collection points of performance analysis traces (for the HTTP reception using the JSON-XML transformation function in HTTP linkage)

  The following table lists event IDs, trace collection points, and collection levels of performance analysis traces. The numbers in the Number in figure column correspond to the circled numbers in the preceding figure.

  Table 7‒149: Collection points of performance analysis traces (for the HTTP reception using the JSON-XML transformation function in HTTP linkage)

  Event ID	Number in figure	Trace collection point	Level
  0x9860	1	Entry to the custom reception framework	A
  0x9861	2	Exit from the custom reception framework	A
  0x9862	3	Point for invoking data transformation (request message)	B
  0x9863	4	Point for receiving a response from data transformation (request message)	B
  0x9864	5	Point for invoking HCSC message delivery control	A
  0x9865	6	Point for receiving a response from HCSC message delivery control	A
  0x9866	7	Point for invoking data transformation (response message)	B
  0x9867	8	Point for receiving a response from data transformation (response message)	B
  0x986E	9	Point for invoking JSON-XML transformation in the custom reception framework (request message)#1	B
  0x986F	10	Point for receiving a response from JSON-XML transformation in the custom reception framework (response message)#2	B
  0x9880	11	Entry to the HTTP reception	A
  0x9881	12	Exit from the HTTP reception	A
  0x9882	13	Point for invoking the custom reception framework	A
  0x9883	14	Point for receiving a response from the custom reception framework	A

  Legend:

  A: Indicates the Standard level.

  B: Indicates the Advance level.

  #1

  This trace collection point is used only when JSON-XML transformation is performed during processing of a request.

  #2

  This trace collection point is used only when JSON-XML transformation is performed during processing of a response.

• For the HTTP adapter

  The following figure shows the collection points of performance analysis traces for the HTTP adapter.

  Figure 7‒124: Collection points of performance analysis traces (for the HTTP adapter using the JSON-XML transformation function in HTTP linkage)

  The following table lists event IDs, trace collection points, and collection levels of performance analysis traces. The numbers in the Number in figure column correspond to the circled numbers in the preceding figure.

  Table 7‒150: Collection points of performance analysis traces (for the HTTP adapter using the JSON-XML transformation function in HTTP linkage)

  Event ID	Number in figure	Trace collection point	Level
  0x9818	1	Point for invoking a service component of a service adapter (custom adapter)	A
  0x9819	2	Point for receiving a response from a service component of a service adapter (custom adapter)	A
  0x982A	3	Point for invoking JSON-XML transformation in the custom adapter development framework (request message)#1	B
  0x982B	4	Point for receiving a response from JSON-XML transformation in the custom adapter development framework (request message)#1	B
  0x982C	5	Point for invoking JSON-XML transformation in the custom adapter development framework (response message)#2	B
  0x982D	6	Point for receiving a response from JSON-XML transformation in the custom adapter development framework (response message)#2	B
  0x9890	7	Entry to the HTTP adapter	A
  0x9891	8	Exit from the HTTP adapter	A
  0x9892	9	At the time of sending an HTTP request	A
  0x9893	10	At the time of receiving an HTTP response completely	A
  0x9894	11	At the time of receiving an HTTP response header	A

  Legend:

  A: Indicates the Standard level.

  B: Indicates the Advance level.

  #1

  This trace collection point is used only when JSON-XML transformation is performed during processing of a request.

  #2

  This trace collection point is used only when JSON-XML transformation is performed during processing of a response.

• Changing the collection level of performance analysis traces

  To collect Advance-level performance analysis traces, use the cprflevel command to change the collection level of performance analysis traces, and then restart the HCSC server. Change the collection level setting for the HCSC server, which can be accessed at the upper layer of the first digit of Index 2.

  cprflevel -PrfChangeLevel ,0x40000000

  For details about the cprflevel command, see the Application Server Command Reference Guide.

(a) Collection points of user message traces

• For the HTTP reception

  In the case where the JSON-XML transformation function is used in the HTTP reception and the trigger to output user message traces is set to NORMAL, the following trace collection points are added:

  • Point before JSON-XML transformation is performed during the processing of a request (5 in the figure)

  • Point after JSON-XML transformation is performed during the processing of a response (6 in the figure)

  The following figure shows the collection points of user message traces for the HTTP reception.

  Figure 7‒125: Collection points of user message traces (for the HTTP reception using the JSON-XML transformation function in HTTP linkage)

  The following table lists trace collection points, types of output messages, and precise positions. The numbers in the Number in figure column correspond to the circled numbers in the preceding figure.

  Table 7‒151: Collection points of user message traces (for the HTTP reception using the JSON-XML transformation function in HTTP linkage)

  Number in figure	Trace collection point	Output message	Details of start of user message trace collection
  			Collection point	Protocol type	Precise position
  1	Entry to the custom reception framework	Requester-side message	URCP	CUSTM	IN
  2	Exit from the custom reception framework	Requester-side message	URCP	CUSTM	OUT
  3	Point for receiving a response from data transformation (request message)#1	Request message after data transformation	URCP	CUSTM	RQA
  4	Point for invoking data transformation (request message)#2	Response message after data transformation	URCP	CUSTM	RSB
  5	Point for invoking JSON-XML transformation in the custom reception framework#3	Request message before JSON-XML transformation	URCP	CUSTM	JCB
  6	Point for receiving a response from JSON-XML transformation in the custom reception framework#4	Response message before JSON-XML transformation	URCP	CUSTM	JCA

Legend:

The meanings of the symbols in the Collection point, Protocol type, and Precise position columns are as follows:

• URCP: User-defined reception

• CUSTM: Custom reception

• IN: Entry to the custom reception framework

• OUT: Exit from the custom reception framework

• RQA: Point for receiving a response from data transformation (request message)

• RSB: Point for invoking data transformation (response message)

• JCB: Point for invoking JSON-XML transformation in the custom reception framework (request message)

• JCA: Point for receiving a response from JSON-XML transformation in the custom reception framework (response message)

#1

This trace collection point is used only when data transformation is performed during the processing of a request.

#2

This trace collection point is used only when data transformation is performed during the processing of a response.

#3

This trace collection point is used only when JSON-XML transformation is performed during the processing of a request.

#4

This trace collection point is used only when JSON-XML transformation is performed during the processing of a response.

• For the HTTP adapter

  In the case where the JSON-XML transformation function is used in the HTTP adapter and the trigger to output user message traces is set to NORMAL, the following trace collection points are added:

  • Point before JSON-XML transformation is performed during the processing of a request (5 in the figure)

  • Point after JSON-XML transformation is performed during the processing of a response (6 in the figure)

  The following figure shows the collection points of user message traces for the HTTP adapter.

  Figure 7‒126: Collection points of user message traces (for the HTTP adapter using the JSON-XML transformation function in HTTP linkage)

  The following table lists trace collection points, types of output messages, and precise positions. The numbers in the Number in figure column correspond to the circled numbers in the preceding figure.

  Table 7‒152: Collection points of user message traces (for the HTTP adapter using the JSON-XML transformation function in HTTP linkage)

  Number in figure	Trace collection point	Output message	Details of start of user message trace collection
  			Collection point	Protocol type	Precise position
  1	Immediately before invocation of the service adapter	Service component message	SVC	CUSTM	CAL
  2	Immediately after response by the service adapter	Service component message	SVC	CUSTM	RET
  3	Point for invoking data transformation (request message)#1	Request message before data transformation	CNVST	CUSTM	RQB
  4	Point for receiving a response from data transformation (response message)#2	Response message before data transformation	CNVST	CUSTM	RSA
  5	Point for invoking JSON-XML transformation in the custom adapter development framework#3	Request message before JSON-XML transformation	CNVJS	CUSTM	JCB
  6	Point for receiving a response from JSON-XML transformation in the custom adapter development framework#4	Response message before JSON-XML transformation	CNVJS	CUSTM	JCA

Legend:

The meanings of the symbols in the Collection point, Protocol type, and Precise position columns are as follows:

• SVC: Invocation of a service component (in the service adapter)

• CNVST: Data transformation in the service adapter

• CNVJS: JSON-XML transformation (in the custom adapter development framework)

• CUSTM: Custom adapter

• CAL: Calling (of a business process or service)

• RET: Reception of a response (to invocation of a business process or service)

• RQB: Immediately before data transformation that is performed when the service adapter is requested

• RSA: Immediately after data transformation that is performed when the service adapter responds

• JCB: Immediately before JSON-XML transformation in the custom adapter development framework

• JCA: Immediately after JSON-XML transformation in the custom adapter development framework

#1

This trace collection point is used only when data transformation is performed during the processing of a request.

#2

This trace collection point is used only when data transformation is performed during the processing of a response.

#3

This trace collection point is used only when JSON-XML transformation is performed during the processing of a request.

#4

This trace collection point is used only when JSON-XML transformation is performed during the processing of a response.