uCosminexus Service Platform, Overview
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
To invoke a service component, you basically require service requesters, reception, HCSC message delivery control, service adapters, and service components. A reception is used for receiving requests to invoke service components, and includes standard reception and user-defined reception.
Standard reception is the functionality (interface) used for receiving request messages from service requesters, and provided as standard by the HCSC server. User-defined reception is the functionality (interface) used for receiving execution requests from service requesters, and is deployed on the HCSC server after being defined by the user in the development environment. User-defined reception is able to communicate with interface which is defined by the user.
- Organization of this subsection
- (1) For standard reception
- (2) For user-defined reception
(1) For standard reception
The following figure shows the relationship between the structure and the development procedure when standard reception is used.
Figure 2-1 Relationship between the structure and the development procedure when standard reception is used
![[Figure]](FIGURE/ZC020100.GIF)
The relationship between the service requester that invokes service components, the HCSC server, and service components is as described below. This relationship is described according to the development procedure.
- Development procedure at the service component side
First, create the service component to be invoked. Next, create a message format and business process definition (BPEL) matching the type of service component to be invoked. Then define the service adapter based on the message format, and define the business process in the development environment. (Also define the message format for the business process.) The method of creating a message format matching the type of service component to be invoked differs depending on the protocol to be used (SOAP, RMI-IIOP, WS-R, or JMS). Deploy the defined service adapter and business process in the execution environment (HCSC server). For details about message formats, see the Service Platform Basic Development Guide, Chapter 4. Creating a Message Format. For details about the business process definitions (BPEL), see the Service Platform Basic Development Guide, Chapter 5. Defining a Business Process.
- Development procedure at the service requester side
After creating the service component, create a service requester for invoking the defined service adapters and business processes. The method of creating service requesters differs depending on the type of standard reception to be used. For details about creating service requesters, see the Service Platform Basic Development Guide, Chapter 8. Creating a Service Requester.
(2) For user-defined reception
The following figure shows the relationship between the structure and the development procedure when user-defined reception is used.
Note that the following uses an example of using Web Services (SOAP communication).
Figure 2-2 Relationship between the structure and the development procedure when user-defined reception is used
![[Figure]](FIGURE/ZC020200.GIF)
When you use Web Services (SOAP communication), the relationship between the service requester that invokes service components, the HCSC server, and service components is as described below. This relationship is described according to the development procedure.
- Development procedure at the service component side
First, create the service component to be invoked. Next, create a message format and business process definition (BPEL) matching the type of service component to be invoked. Then define the service adapter based on the message format, and define the business process in the development environment (also define the message format for the business process). Deploy the defined service adapter, business process, and user-defined reception in the execution environment (HCSC server). For details about message formats, see Chapter 4. Creating a Message Format in the Service Platform Basic Development Guide. For details about the business process definitions (BPEL), see Chapter 5. Defining a Business Process in the Service Platform Basic Development Guide.
- Development procedure at the reception side
After creating the service component, create a WSDL matching the message format of the business process to be invoked, and then define the user-defined reception in the development environment. For details about how to define a user-defined reception, see Chapter 2. Defining a User-defined Reception in the Service Platform Reception and Adapter Definition Guide.
- Development procedure at the service requester side
After creating a user-defined reception, create a service requester for invoking the defined user-defined reception. Generate a stub from the WSDL that is used when defining the user-defined reception, and then create a service requester for invoking the stub. For details about creating a service requester, see Chapter 8. Creating a Service Requester in the Service Platform Basic Development Guide.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.