uCosminexus Service Platform, Setup and Operation Guide
The performance analysis trace (PRF trace) is trace information used to analyze the performance of the Service platform system. The performance analysis trace file is a text file in which the performance analysis trace is edited and output in the CSV format. The information that is output as the performance analysis trace is used to analyze performance bottlenecks throughout the system, including J2EE applications. It is used to troubleshoot and prevent such bottlenecks. For details on performance analysis trace functionality, see "7. Performance analysis using performance analysis trace" in "Application Server Maintenance and Migration Guide".
The format that is output in the performance analysis trace file is same as that of the performance analysis trace of the J2EE server. For details about the performance analysis trace file, see "7.3 Collecting performance analysis trace file using Management Server" in "Application Server Maintenance and Migration Guide".
Table 7-22 Table Contents output to the performance analysis trace file (messaging infrastructure)
| Item | Content | |
|---|---|---|
| Event ID | The Event ID of the collection point is output. For details, see the following points:
|
|
| Return code | The type of collection point is output.
|
|
| Interface name | Class name is output. | |
| Operation name | Method name is output. | |
| Option information | Message common ID | The request identification information (parent ID) is output. |
| Service request ID | The request identification information (child ID) is output. | |
| Additional information | The additional information specific to the output destination is output. | |
Table 7-23 Table Content output to the performance analysis trace file (business process infrastructure)
| Item | Content |
|---|---|
| Event ID | The Event ID of the collection point is output. For details, see "Table7-32 Performance analysis trace collection point (business process infrastructure)". |
| Return code | The type of the collection point is output.
|
| Interface name | Any of the following names is displayed:
|
| Operation name | Is not output. |
| Option information | Option information is output. For details, see"Table 7-32 Performance analysis trace collection point (business process infrastructure)". |
Table 7-24 Table Contents output to the performance analysis trace file (Database adapter)
| Item | Content | |
|---|---|---|
| Event ID | The Event ID of the collection point is output. For details, see the following points: |
|
| Return code | The type of the collection point is output.
|
|
| Interface name | Class name is output. Package name is not displayed. |
|
| Operation name | Method name is output. | |
| Option information | Message common ID | The request identification information (parent ID) is output. Value becomes null when the information is not set. |
| Service request ID | The request identification information (child ID) is output. Value becomes null when the information is not set. |
|
| Additional information | Individual information is output. | |
Table 7-25 Table Content output to the performance analysis trace file (Data transformation infrastructure)
| Item | Content | |
|---|---|---|
| Event ID | The Event ID of the collection point is output. For details, see the following points: |
|
| Return code | The type of the collection point is output.
|
|
| Interface name | Class name is output. | |
| Operation name | Method name is output. | |
| Option information | Message common ID | The request identification information (parent ID) is output. |
| Service request ID | The request identification information (child ID) is output. | |
| Additional information | The additional information specific to the output destination is output. | |
Table 7-26 Table Content output to the performance analysis trace file (component-common UOC)
| Item | Content | |
|---|---|---|
| Event ID | The Event ID of the collection point is output. For details, see the following points: |
|
| Return code | The type of the collection point is output.
|
|
| Interface name | Class name of UOC class is output. | |
| Operation name | Method name of UOC class is output. | |
| Option information | Message common ID | The request identification information (parent ID) is output. |
| Service request ID | The request identification information (child ID) is output. | |
| Additional information | Option information is output. For details, see "7.4.3(2)(e) For HCSC server (component-common UOC)". |
|
Performance analysis trace files are output at the following times, and the trace collection point for each time is different:
Figure 7-11 Figure Trace collection point of the performance analysis trace (when executing individual services)
Table 7-27 Table Performance analysis trace collection point (when executing individual services)
| Event ID | Number in figure | Trace collection point | Level |
|---|---|---|---|
| 0x9800 | 1 | Entry to standard reception (Web Services) | A |
| 0x9801 | 2 | Exit from standard reception (Web Services) | A |
| 0x9802 | 1 | Entry to standard reception (SessionBean) | A |
| 0x9803 | 2 | Exit from standard reception (SessionBean) | A |
| 0x9804 | 1 | Entry to standard reception (MDB(WS-R)) | A |
| 0x9805 | 2 | Exit from standard reception (MDB(WS-R)) | A |
| 0x9806 | 1 | Entry to standard reception (MDB(DB queue)) | A |
| 0x9807 | 2 | Exit from standard reception (MDB(DB queue)) | A |
| 0x9810 | 3 | Invocation of service components of SOAP adapter | A |
| 0x9811 | 4 | Point for receiving response from service components of SOAP adapter | A |
| 0x9812 | 3 | Invocation of service components of SessionBean adapter | A |
| 0x9813 | 4 | Point for receiving response from service components of SessionBean adapter | A |
| 0x9814 | 3 | Invocation of service components of MDB (WS-R) adapter | A |
| 0x9815 | 4 | Point for receiving response from service components of MDB (WS-R) adapter | A |
| 0x9816 | 3 | Invocation of service components of MDB (DB queue) adapter | A |
| 0x9817 | 4 | Point for receiving response from service components of MDB (DB queue) adapter | A |
| 0x9818 | 3 | Invocation of service components of service adapters(CUSTOM) other than those mentioned above | A |
| 0x9819 | 4 | Point for receiving response from service components of service adapters(CUSTOM) other than those mentioned above | A |
Figure 7-12 FigureTrace collection point of the performance analysis trace (when executing business process services)
Table 7-28 Table Performance analysis trace collection point(when executing business process services)
| Event ID | Number in figure | Trace collection point | Level |
|---|---|---|---|
| 0x9800 | 1 | Entry to standard reception (Web Services) | A |
| 0x9801 | 2 | Exit from standard reception (Web Services) | A |
| 0x9802 | 1 | Entry to standard reception (SessionBean) | A |
| 0x9803 | 2 | Exit from standard reception (SessionBean) | A |
| 0x9804 | 1 | Entry to standard reception (MDB(WS-R)) | A |
| 0x9805 | 2 | Exit from standard reception (MDB(WS-R)) | A |
| 0x9806 | 1 | Entry to standard reception (MDB(DB queue)) | A |
| 0x9807 | 2 | Exit from standard reception (MDB(DB queue)) | A |
| 0x9808 | 1 | Entry to SOAP reception | A |
| 0x9809 | 2 | Exit from SOAP reception | A |
| 0x9810 | 7 | Invocation of service components of SOAP adapter | A |
| 0x9811 | 8 | Point for receiving response from service components of SOAP adapter | A |
| 0x9812 | 7 | Invocation of service components of SessionBean adapter | A |
| 0x9813 | 8 | Point for receiving response from service components of SessionBean adapter | A |
| 0x9814 | 7 | Invocation of service components of MDB (WS-R) adapter | A |
| 0x9815 | 8 | Point for receiving response from service components of MDB (WS-R) adapter | A |
| 0x9816 | 7 | Invocation of service components of MDB (DB queue) adapter | A |
| 0x9817 | 8 | Point for receiving response from service components of MDB (DB queue) adapter | A |
| 0x9818 | 7 | Invocation of service components of service adapters(CUSTOM) other than those mentioned above | A |
| 0x9819 | 8 | Point for receiving response from service components of service adapters(CUSTOM) other than those mentioned above | A |
| 0x9840 | 3 | Invocation of business process services | A |
| 0x9841 | 4 | Point for receiving response from business process services | A |
| 0x9842 | 5 | Entry to business process reception | A |
| 0x9843 | 6 | Exit from business process reception | A |
Figure 7-13 Figure Performance analysis trace collection point (when executing database access)
Table 7-29 Table Performance analysis trace collection point(when executing database access)
| Event ID | Number in figure | Trace collection point | Level |
|---|---|---|---|
| 0x9850 | 1 | Invocation of DB connector | A |
| 0x9851 | 2 | Point for receiving response from DB connector | A |
| 0x9852 | 3 | Invocation of execution log of DB connector | B |
| 0x9853 | 4 | Point for receiving response from execution log of DB connector | B |
Figure 7-14 Figure Performance analysis trace collection point (when accessing files)
Table 7-30 Table Performance analysis trace collection point (when accessing files)
| Event ID | Number in figure | Trace collection point | Level |
|---|---|---|---|
| 0x9854 | 1 | Invocation of file access (before opening the file) | B |
| 0x9855 | 2 | Point for receiving response from file access (after closing the file) | B |
The following figure shows the performance analysis trace collection point:
Figure 7-15 Figure Trace collection point of performance analysis trace (business process infrastructure)
The following tables lists the event ID, trace collection point, and the performance analysis trace collection level, and indicates the output content of Interface name and Option information for each event ID. The numbers in the Number in figure column of the table correspond to the numbers in the above figure.
Table 7-31 Table Performance analysis trace collection point(business process infrastructure)
| Event ID | Number in figure | Trace collection point | Level | Interface name | Option information |
|---|---|---|---|---|---|
| 0x9900 | 1 | Invoking a request for business process execution from messaging infrastructure | A | Business process definition name |
|
| 0x9901 | 2 | Response to messaging infrastructure for the request to execute business process | A | Business process definition name |
|
| 0x9902 | 3 | Invoking after reply activity from messaging infrastructure | A | Business process definition name |
|
| 0x9903 | 4 | Response to invocation after reply activity from messaging infrastructure | A | Business process definition name |
|
| 0x9904 | 5 | Invoking the request to re-execute from messaging infrastructure | A | Business process definition name |
|
| 0x9905 | 6 | Response to invocation of the request to re-execute from messaging infrastructure | A | Business process definition name |
|
| 0x9906 | 7 | Invoking the user-created Java class | A | Java class name | None |
| 0x9907 | 8 | Response from the user-created Java class | A | Java class name |
|
| 0x9908 | 9 | Invoking data transformation request | A | "Data Transform" | None |
| 0x9909 | 10 | Response from data transformation request | A | "Data Transform" |
|
| 0x990A | 11 | Invoking from TimerService after the standby activity | A | Business process definition name |
|
| 0x990B | 12 | Response to invocation from TimerService after the standby activity | A | Business process definition name |
|
| 0x990C | 13 | When registering of TimerService | A | Business process definition name |
|
| 0x990D | 14 | In the case of TimerService timeout | A | Business process definition name |
|
| 0x9910 | 15 | Invoking a service component request to messaging infrastructure | A | Service name |
|
| 0x9911 | 16 | Response to the service component request from messaging infrastructure | A | Service name |
|
| 0x9912 | 17 | Invoking after reply activity from messaging infrastructure to asynchronous EJB | A | Business process definition name |
|
| 0x9913 | 18 | Response to the Invoking after reply activity from asynchronous EJB to messaging infrastructure | A | Business process definition name |
|
The trace collection point of performance analysis trace differs depending on whether you execute startup operations or service components.
Figure 7-16 Figure Trace collection point of performance analysis trace (when starting the DB adapter)
Table 7-32 Table Performance analysis trace collection point (when starting DB adapter)
| Event ID | Number in figure | Trace collection point | Level |
|---|---|---|---|
| 0x9B60 | 1 | Immediately before data source search | B |
| 0x9B61 | 2 | Immediately after data source search | B |
| 0x9B62 | B |
Figure 7-17 Figure Trace collection point of performance analysis trace (when executing DB adapter service)
Table 7-33 Table Performance analysis trace collection point(when executing DB adapter service)
| Event ID | Number in figure | Trace collection point | Level |
|---|---|---|---|
| 0x9B00 | 1 | Immediately after invoking a service component request from messaging infrastructure | A |
| 0x9B01 | 14 | Immediately before the response to the service component request from messaging infrastructure | A |
| 0x9B02 | A | ||
| 0x9B20 | 2#1#2, 12#1#2 | Immediately before invoking a data transformation request | A |
| 0x9B21 | 3#1#2, 13#1#2 | Immediately after invoking a data transformation request | A |
| 0x9B22 | A | ||
| 0x9B23 | 15#2#3 | Immediately before invoking a data replication request | A |
| 0x9B24 | 16#2#3 | Immediately after the response to the data replication request | A |
| 0x9B25 | A | ||
| 0x9B63 | 4 | Immediately before invoking a request to connect to database | B |
| 0x9B64 | 5 | Immediately after invoking a request to connect to database | B |
| 0x9B65 | B | ||
| 0x9B66 | 6 | Immediately before invoking an SQL request | A |
| 0x9B67 | 7 | Immediately after the response to the SQL request | A |
| 0x9B68 | A | ||
| 0x9B69 | 6 | Immediately before invoking an SQL request | A |
| 0x9B6A | 7 | Immediately after the response to the SQL request | A |
| 0x9B6B | A | ||
| 0x9B6C | 6 | Immediately before invoking an SQL request | A |
| 0x9B6D | 7 | Immediately after the response to the SQL request | A |
| 0x9B6E | A | ||
| 0x9B6F | 17 | When executing SELECT statement from DB adapter (only when ResultSet.next() is output for the first time) | A |
| 0x9B70 | 18 | A | |
| 0x9B71 | A | ||
| 0x9B40 | 8 | Immediately before storing SQL (SELECT) execution results | A |
| 0x9B41 | 11 | Immediately after storing SQL (SELECT) execution results | A |
| 0x9B42 | A | ||
| 0x9B43 | 9 | Immediately before collecting SQL (SELECT) execution results | B |
| 0x9B44 | 10 | Immediately after collecting SQL (SELECT) execution results | B |
| 0x9B45 | B |
The following table lists the event ID, trace collection point, and the performance analysis trace collection level.
Table 7-34 Table Performance analysis trace collection point (data transformation infrastructure)
| Event ID | Trace collection point | Level |
|---|---|---|
| 0x9A07 | Immediately before acquiring the value from XML | A |
| 0x9A08 | Immediately after acquiring the value from XML | A |
| 0x9A0C | Immediately before setting up the value in XML | A |
| 0x9A0D | Immediately after setting up the value in XML | A |
| 0x9A11 | Immediately before acquiring the node from XML | A |
| 0x9A12 | Immediately after acquiring the node from XML | A |
| 0x9A16 | Immediately before setting up the node in XML | A |
| 0x9A17 | Immediately after setting up the node in XML | A |
| 0x9A43 | Immediately before data transformation | A# |
| 0x9A44 | Immediately after data transformation | A# |
| 0x9A52 | Immediately before generating the data transformation template | A |
| 0x9A53 | Immediately after generating the data transformation template | A |
| 0x9A65 | Immediately before generating the XML schema instance | A |
| 0x9A66 | Immediately after generating the XML schema instance | A |
| 0x9A6A | Immediately before generating the XML schema instance | A |
| 0x9A6B | Immediately after generating the XML schema instance | A |
| 0x9A77 | Immediately before XML data analysis | A |
| 0x9A78 | Immediately after XML data analysis | A |
| 0x9A7A | Immediately before XML schema validation | A |
| 0x9A7B | Immediately after XML schema validation | A |
| 0x9A7C | Immediately before XML schema validation | A |
| 0x9A7D | Immediately after XML schema validation | A |
| 0x9A80 | Immediately before XML data analysis | A |
| 0x9A81 | Immediately after XML data analysis | A |
| 0x9A82 | Immediately before data transformation | A |
| 0x9A83 | Immediately after data transformation | A |
| 0x9A84 | Immediately before XML data analysis | A |
| 0x9A85 | Immediately after XML data analysis | A |
| 0x9A88 | Immediately before generating the XML schema instance | A |
| 0x9A89 | Immediately after generating the XML schema instance | A |
| 0x9A8D | Immediately before generating the XML schema instance | A |
| 0x9A8E | Immediately after generating the XML schema instance | A |
| 0x9A8F | Before invoking transformation function jar | A |
| 0x9A90 | After invoking transformation function jar | A |
The performance analysis trace when you use the Component-common UOC functionalityis output immediately before and after invoking the UOC class. The following figure shows the trace collection point of performance analysis trace when using component-common:
Figure 7-18 Figure Performance analysis trace collection point (when using component-common UOC)
The following table lists the event ID, trace collection point, and the performance analysis trace collection level. The "Number in figure" in this table corresponds to the numbers in "Figure7-18 Performance analysis trace collection point (when using component-common UOC)".
Table 7-35 Table Performance analysis trace collection point (when using component-common UOC)
| Event ID | Number in figure | Trace collection point | Level |
|---|---|---|---|
| 0x986C | 1 | Invocation of component-common UOC | A |
| 0x986D | 2 | Point for receiving response from component-common UOC | A |
The output format of the option information is as follows:
<Request identification information (parent ID)> <Request identification information (child ID)> Component type=<Component type (service adapter or reception)>, Component kind=<type>, Component ID=<Service ID of service adapter or reception ID#>, OP=<service operation name> |
In case of abnormal end, the option information is output in the following format:
<Request identification information (parent ID)> <Request identification information (child ID)> Component type=< Component type (adapter type or reception type)>, Component ID=< Service ID of service adapter or reception ID #>, OP=< service operation name >, Exception=<exception class name> |
| Component | Reception ID |
|---|---|
| Standard reception (Web services) (SOAP1.1,SOAP 1.1/1.2 combined mode is common) |
StandardReception_SOAP |
| Standard reception (SessionBean) | StandardReception_EJB |
| Standard reception (MDB(WS-R)) | StandardReception_WSR |
| Standard reception (MDB(DB queue)) | StandardReception_DBQ |
Settings are required to acquire performance analysis trace. For details, see "7.3.1(3) Performance analysis trace" and "7.3 Collecting performance analysis trace files using Management Server" in "Application Server Maintenance and Migration Guide".
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.