There are two types of receptions: standard receptions, which are provided as the HCSC server functions, and user-defined receptions, for which the user can define interfaces as desired.

The following table describes the types of receptions that can be used in the service platform.

Table 1-1 Types of available receptions

Category	Type	Purpose
Standard reception	Standard reception (Web service)	Used when a system using a Web service (SOAP communication) receives a call request for a service component.
	Standard reception (Session Bean)	Used when a system using Session Bean receives a call request for a service component.
	Standard reception (MDB (WS-R))	Used when a system using MDB (WS-R) receives a call request for a service component.
	Standard reception (MDB (DB queue))	Used when a system using MDB (DB queue) receives a call request for a service component.
User-defined reception	SOAP reception	Used when a system using a Web service (SOAP communication) receives a call request for a service component.
	TP1/RPC reception	Used to receive a call request for a service component, from a service requester in an existing OpenTP1 system.
	FTP reception	Used to receive an execution request from an FTP client via the FTP inbound adapter.#1
	HTTP reception	Used to receive a call request for a service component, from an HTTP client by using HTTP communication.
	Message Queue reception	Used to receive an execution request from a JMS provider (IBM WebSphere MQ system) via the MQ resource adapter.
	Custom reception	Used to receive an execution request via an arbitrary protocol.#2

#1

Linkage with the FTP adapter is required to perform file transfer between an FTP client and the FTP server on the service platform.

#2

To receive an execution request via an arbitrary protocol, the user-defined reception processing must be run on the custom reception framework.

To use standard receptions, you need to create a service requester suitable for each type of standard reception, and create and analyze a message that corresponds to the input/output format of the service component. For details about how to create a service requester and message when a standard reception is used, see Chapter 8. Creating Service Requesters in the Service Platform Basic Development Guide.

To use a user-defined reception, define an interface in the development environment, and deploy the interface to the HCSC server. After deploying the interface to the HCSC server, start the user-defined reception. Then, a request message from a service requester can be received.

For details about the definitions necessary for using user-defined receptions, see Chapter 2. Defining User-Defined Reception.