7.10.1 Examples applicable for message tracking functionality

You can use message tracking anywhere if there is a performance analysis trace file when error occurs and if the machine has any of the Service Architect, or Service Platform installed. If there is a performance analysis trace file when error occurs, the error can be analyzed not only on the machine on which HCSC server is running where the error occurred but also from any other remote environment where the HCSC server on which error occurred is not running.

Usage examples of message ranking are as follows:

Organization of this subsection

(1) When error occurred in service component connection
(2) For investigating errors in the entire system
(3) For confirming the status of sent requests

(1) When error occurred in service component connection

When an error occurred while connecting to service component, analyze the performance analysis trace file and classify the places where error occurred and the reason for error. The following figure shows the flow of error analysis when error occurred while connecting to service component:

Figure 7‒138: Flow of error analysis when error occurred while connecting to service component

Access the machine on which HCSC server is running and acquire the performance analysis trace file.
Confirm the error information of Cosminexus J2EE server operation log and acquire the following information from error messages output to log:
- Time when error occurred
- Root application information
- Message common ID
The character string output after "RootApInfo =" is the root application information. Root application information is output to the "IP address/ process ID/ communication number" format.

The output format of Cosminexus J2EE server operation log is as follows:
Start message tracking.

Sort out the performance analysis trace files read when error occurred and start message tracking. For starting message tracking, see 7.10.2 Starting message tracking.
Display the performance analysis trace matching the root application information and analyze the error.

For details about displaying the performance analysis trace matching the root application information, see 7.10.3 Displaying performance analysis trace.

To Page Top

(2) For investigating errors in the entire system

When the requests are delayed due to hang-up, slowdown, or timeout of process, confirm the information about delayed requests from root application information of performance analysis trace file. Specify the places where error occurred from information about the delayed requests and investigate the errors in the entire system. The following figure shows the error analysis flow when investigating errors in the entire system:

Figure 7‒139: Error analysis flow when investigating errors in the entire system

Access the machine on which HCSC server is running where the error occurred and acquire the performance analysis trace file.
Start message tracking.

For details about starting the message tracking, see 7.10.2 Starting message tracking.
Display the root application information list of performance analysis trace file and confirm the information about requests that are delayed.

For details about displaying the root application information list of performance analysis trace file, see 7.10.4 List display of root application information.
Display the performance analysis trace matching the root application information confirmed in 3. and specify the delay places.

To Page Top

(3) For confirming the status of sent requests

When the sent requests are not returned or to confirm the progress status of requests, sort out the performance analysis traces to be analyzed in request sending time and confirm the status of the sent requests.

The following figure shows the error analysis flow when confirming the status of sent requests:

Figure 7‒140: Error analysis flow when confirming the sent requests

Access the machine on which HCSC server is running where the error occurred and acquire the performance analysis trace file.
Start the message tracking.

For details about starting the message tracking, see 7.10.2 Starting message tracking.
Sort the performance analysis trace to be analyzed in request sending time.

For details about sorting performance analysis trace to be analyzed, see 7.10.5 Sorting performance analysis trace.
Analyze the sorted performance analysis trace and confirm the status of send requests.

To Page Top