The following figure shows a business process as an example of how to use the connection-destination information file.

Figure 2-17 Example of a business process that uses the connection-destination information file

1. The service requester requests the business process to execute the service component.
2. The connection-destination URL is set in the header message of the request message that is sent from the service requester.
3. The business process receives the XML request message via the receive activity.
4. The business process generates header request data and request data.
5. The connection-destination URL of the header request data is set for the connection-destination URL variable in the data transformation activity or other activities.
6. The business process obtains the connection-destination URL from the connection-destination URL variable, and then calls the service component.
7. The business process configures an XML response message from the execution result of the service component, and returns it via the reply activity.
8. The response is returned to the service requester.
9. The XML response message is sent as the response to the service requester.

The following shows an example of creating a WSDL that generates a SOAP reception.

In this example, the URL of the connection-destination service component is sent contained in the SOAP header.

The following shows an example configuration of the data transformation activity that is used by the business process shown in Figure 2-17 Example of a business process that uses the connection-destination information file.

In this example, HeaderRequestData is specified as the source, and ConnectionDestinationInformation is specified as the target.

Figure 2-18 Example configuration of the data transformation activity

Define the transformation mapping as shown in the following figure.

Figure 2-19 Example configuration of transformation mapping

The following shows an example configuration of the connection-destination information that is used by the business process shown in Figure 2-17 Example of a business process that uses the connection-destination information file. Note that the connection-destination information must be set for the header-allocated variable of the invoke service activity. The information set here is the information that can be viewed on the service adapter.

Figure 2-20 Example configuration of connection-destination information (invoke service activity settings)

The connection-destination information files for individual service adapters are stored in the following locations:

• Storage location for the connection-destination information file for the DB adapter
  

   
  installation-directory-of-the-service-platform\CSC\schema\connection\connection_db_adapter.xsd.
   

• Storage location for the connection-destination information file for the SOAP adapter
  

   
  installation-directory-of-the-service-platform\CSC\schema\connection\connection_soap_adapter.xsd.
   

• Storage location for the connection-destination information file for the TP1 adapter
  

   
  installation-directory-of-the-service-platform\CSC\schema\connection\connection_tp1_adapter.xsd.

Note

When you dynamically change the connection-destination information of the service adapter, use the connection-destination information file provided by the service platform. If you do not use the provided connection-destination information file, operations are not guaranteed to work.