Standard reception (MDB (WS-R)) of an HCSC server operates by using an MDB (Message Driven Bean) and monitors the local queue of the HCSC server side. When a message is sent to the local queue of the HCSC server side, standard reception (MDB (WS-R)) extracts the message and invokes the service component.

In the transmit queue of the service requester side, specify the destination address of the HCSC server and the queue name of the local queue of the transmit destination. From the service requester, send a JMS message to the transmit queue of the service requester side to invoke standard reception (MDB (WS-R)) of the HCSC server.

When invoking a service component, send the message to the transmit queue of the service adapter side. The transmit queue then sends the message to the local queue of the service component side defined in the Service Adapter Settings window in the development environment. (In this window, the transmit destination queue name is specified for the address in the Basic window and the destination URL is specified in the Details window.) By creating the service component by using an MDB, the process can be executed by extracting the message sent to the local queue of the service component side. The following figure shows the specification of the destination for an asynchronous service component (MDB (WS-R)).

Figure 2-33 Specification of the destination for an asynchronous service component (MDB (WS-R))

For details about how to create a transmit queue, see 8.5.2 Creating a transmit queue in the Service Platform Basic Development Guide. For details about how to create a JMS message, see 8.5.3 Creating a JMS message in the Service Platform Basic Development Guide.

When a service component is invoked from the service requester, the format of the JMS message to be sent to the transmit queue is the interface of standard reception (MDB (WS-R)).

The contents specified in the payload (the main data excluding the header) of the JMS message are transmitted to the service component as the user message. Therefore, when invoking standard reception (MDB (WS-R)) from the service requester, create a request message matching the message format of the service component side in advance, and then send that message set in the payload. The following figure shows the relationship between user messages and JMS messages when an asynchronous service component is invoked.

Figure 2-34 Relationship between user messages and JMS messages when an asynchronous service component is invoked

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, and then send the message set in the payload. The following figure shows the relationship between user messages and JMS messages when a business process is invoked.

Figure 2-35 Relationship between user messages and JMS messages when a business process is invoked