Receiving SOAP Requests

ActiveMatrix BusinessWorks can implement a web service through a process definition. The SOAP Event Source process starter defines the concrete WSDL file for the web service. SOAP clients must retrieve the concrete WSDL file before sending a SOAP request to the service. The WSDL Palette allows you to locate and store existing concrete service definitions or create your own abstract service definition. If you use an existing concrete service definition, the concrete bindings are ignored, and you can configure the service to use different namespaces and input/output headers.

Note: Using the SOAP Event Source process starter allows you to use WSDL interface files that have only one operation. That is, you can only implement one operation in the process definition that has the SOAP Event Source. If you wish to implement a service with multiple operations, use the Service resource.

To create a web service, perform the following general procedure:

Procedure 

  1. Create XSDs to define the input, output, and fault messages for the web service.

  2. Create a WSDL File resource that defines the interface to the web service.

  3. Create a process definition that performs the work of the web service. Use the SOAP Event Source process starter for this process definition. Use the SOAP Send Reply activity to return a reply or the SOAP Send Fault activity to return a fault to the client.

  4. Create a process definition that retrieves the concrete WSDL file and sends it to web service clients. Use the HTTP Receiver process starter and the Retrieve Resources activity for this process definition.

See TIBCO ActiveMatrix BusinessWorks Palette Reference for more information about the resources in the SOAP palette.