uCosminexus Service Platform, Overview
To differentiate each request through on an HCSC, a message common ID and a service request ID is allocated to each request message. These IDs are output in the message log, request trace, and the performance analysis trace.
By following the message common ID and service request ID, you can trace the flow of the service component invocation process. For information about tracing messages, see 7.7 Troubleshooting the requests to invoke a service component in the Service Platform Setup and Operation Guide.
In addition to the identification information allocated on an HCSC server, a client correlation ID is also set up in which the user can specify any value.
- Organization of this subsection
- (1) Types of identification information
- (2) Timing of allocation of identification information
(1) Types of identification information
- Message common ID
A message common ID is allocated automatically when a service component invocation request is received from a service requester. The same message common ID is used until a response is sent.
Even when a service requester invokes a business process, individual service component invocation processes within the business process can be identified as the same process. The format of the message common ID is as follows:
CSC_[server-name]_[reception-time (milliseconds)]_[serial-number]
|
- #: The serial number added at the end is a number allocated in a sequence starting from 1.
- Example: CSC_CSCServerName_2008-04-20_11:32:18.360_1
- Service request ID
The service request ID is identification information allocated to each individual service component invocation process within the HCSC server.
The service request ID is allocated not only when a service component invocation request from the service requester is received, but also when a service component invocation process from the business process is executed. The format of the service request ID is as follows:
MSG_[server-name]_[reception-time (milliseconds)]_[serial-number]
|
- #: The serial number added at the end is a number allocated in a sequence starting from 1.
- Example: MSG_CSCServerName_MDBWSR_2008-04-20_11:32:18.360_1
- Business process instance ID
The business process instance ID is identification information (process instance identifier) for identifying individual process instances of a business process. The business process instance ID is used when re-execution of a business process from a service requester is requested, and when the execution log of process instances is to be deleted.
(2) Timing of allocation of identification information
When the service adapter is invoked directly from standard reception, the message common ID and service request ID are inherited as the identification information on the HCSC server. When the service adapter is invoked from standard reception and user-defined reception via the business process, the message common ID is inherited as the identification information on the HCSC server. However, the service request ID is inherited as the identification information for each service component invocation process. Furthermore, the business process instance ID is allocated when the business process first receives a request.
The following figure shows the timing of allocation of message common IDs and service request IDs.
Figure 2-8 Timing of allocation of identification information
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.