uCosminexus Service Platform, Overview

[Contents][Glossary][Index][Back][Next]

2.1.4 Identification information provided in the service component invocation process

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

(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

[Figure]