uCosminexus Service Platform, Overview

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

2.2.2 Relationship between user messages and WSDL when a service component is invoked

The relationship between user messages and the WSDL when a service component is invoked is different for standard reception and user-defined reception.

Organization of this subsection
(1) For standard reception
(2) For user-defined reception

(1) For standard reception

The following describes the relationship between user messages and the WSDL during SOAP communication (standard reception (Web Services)).

(a) When the SOAP Communication Infrastructure is used

The figure below shows the relationship between user messages and the WSDL during SOAP communication (standard reception (Web Services)) when the SOAP Communication Infrastructure is used as the communication infrastructure. You can also use a configuration in which the SOAP Communication Infrastructure is used at the service requester side or the service component side and the JAX-WS engine is used at the other side. For details about the side on which JAX-WS engine is used, see (b) When the JAX-WS engine is used.

Figure 2-10 Relationship between user messages and the WSDL during SOAP communication (standard reception (Web Services)) when the SOAP Communication Infrastructure is used

[Figure]

  1. When defining a service adapter, define the WSDL of the service component as the message format of the service component side (formats of the request message, response message, and fault message are defined in this WSDL). To create a WSDL, use the Java2WSDL command provided with the SOAP Communication Infrastructure.
  2. When invoking a service component by invoking standard reception (Web Services) from the service requester, use the WSDL provided with the HCSC server. You can create a stub by using the WSDL2Java command based on the WSDL provided with the HCSC server.
  3. When invoking standard reception (Web Services) from the service requester, create in advance a request message matching the message format of the service component side. Then, specify the created message in the parameters of standard reception (Web Services) (parameters of the user message) defined in the WSDL provided with the HCSC server, and then request execution of a service component.
  4. A request message for invoking a business process from the service requester is the message format defined in the receive activity of the business process. In the service requester, create a message in the message format of the request message defined in the receive activity of the business process. Then, specify the created message in the parameters of standard reception (Web Services) (parameters of the user message), and then request execution of a service component.
  5. For the response to the service requester, use the message format of the response message defined in the service adapter.
(b) When the JAX-WS engine is used

The figure below shows the relationship between user messages and the WSDL during SOAP communication (standard reception (Web Services)) when the JAX-WS engine is used as the communication infrastructure. You can also use a configuration in which the JAX-WS engine is used at the service requester side or the service component side, and the SOAP Communication Infrastructure is used at the other side. For details about the side on which the SOAP Communication Infrastructure is used, see (a) When the SOAP Communication Infrastructure is used.

Figure 2-11 Relationship between user messages and the WSDL during SOAP communication (standard reception (Web Services)) when the JAX-WS engine is used

[Figure]

  1. When defining a service adapter, define the WSDL of the service component as the message format of the service component side (formats of the request message, response message, and fault message are defined in this WSDL). The WSDL of a service component is acquired by accessing the URL prepared at the service component side.
  2. When invoking a service component by invoking standard reception (Web Services) from the service requester, use the WSDL provided with the HCSC server. You can create a service class by using the cjwsimport command based on the WSDL provided with the HCSC server.
  3. When invoking standard reception (Web Services) from the service requester, create in advance a request message matching the message format of the service component side. Then, specify the created message in the parameters of standard reception (Web Services) (parameters of the user message) defined in the WSDL provided with the HCSC server, and then request execution of a service component.
  4. A request message for invoking a business process from the service requester is the message format defined in the receive activity of the business process. In the service requester, create a message in the message format of the request message defined in the receive activity of the business process. Then, specify the created message in the parameters of standard reception (Web Services) (parameters of the user message), and then request execution of a service component.
  5. For the response to the service requester, use the message format of the response message defined in the service adapter.

(2) For user-defined reception

The following describes the relationship between user messages and the WSDL during SOAP communication (SOAP reception).

(a) When the SOAP Communication Infrastructure is used

The following figure shows the relationship between user messages and the WSDL during SOAP communication (SOAP reception) when the SOAP Communication Infrastructure is used as the communication infrastructure.

Figure 2-12 Relationship between user messages and the WSDL during SOAP communication (SOAP reception) when the SOAP Communication Infrastructure is used

[Figure]

  1. For a SOAP reception, a request message specified in the service requester is sent in a message format defined in the receive activity of the business process. (Create a WSDL matching the message format defined in the receive activity, and then define the WSDL in the SOAP reception.)
  2. A stub can be created by using the WSDL2Java command provided with the SOAP application development support functionality based on the user-defined WSDL. In contrast to standard reception (Web Services), you need not create an XML of the request message in the program at the service requester side. When the service requester sends a request to the stub, set a value in each parameter to request execution of a service component (create a SOAP message within the stub).
  3. A response to the service requester is sent in the message format of the response message defined in the reply activity of the business process. (Create a WSDL matching the message format defined in the reply activity, and then define the WSDL in the SOAP reception.)
(b) When the JAX-WS engine is used

The following figure shows the relationship between user messages and the WSDL during SOAP communication (SOAP reception) when the JAX-WS engine is used as the communication infrastructure.

Figure 2-13 Relationship between user messages and the WSDL during SOAP communication (SOAP reception) when the JAX-WS engine is used

[Figure]

  1. For a SOAP reception, a request message specified in the service requester is sent in a message format defined in the receive activity of the business process. (Create a WSDL matching the message format defined in the receive activity, and then define the WSDL in the SOAP reception.)
  2. You can create a service class by using the cjwsimport command based on the WSDL provided with the JAX-WS. In contrast to standard reception (Web Services), you need not create an XML of the request message in the program at the service requester side. When the service requester sends a request to the service class, set a value in each parameter to request execution of a service component (create a SOAP message within the service class).
  3. A response to the service requester is sent in the message format of the response message defined in the reply activity of the business process. (Create a WSDL matching the message format defined in the reply activity, and then define the WSDL in the SOAP reception.)

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.