Exposing a Service (Contract Last)
Using contract last to expose a service involves defining the process data that you want to receive and send, then generating a WSDL that defines the service contract.
Step | Task description | For more information, see... |
---|---|---|
1. | Define the process data that you want to receive from and return to the service consumer. | Defining Input and Output Data |
2. | Configure an activity to expose the web service. | Configuring a Task or Event to Expose a Web Service |
3. | Generate an abstract WSDL, then select the web service operation that you want to expose. | Using the Default Generated Web Service Operation |
4. | Map the input/output parameters required by the web service operation to corresponding data fields or parameters in the process. | Defining Input and Output Mappings |
5. | (If required) Review the configuration of the SOAP binding and endpoint. | System Participant Shared Resource Properties |
6. | Deploy the project to the BPM runtime. | Deploying a Process That Exposes a Web Service |
7. | (If required) Generate the concrete WSDL that will be used to expose the service on its SOAP binding. | Administrator interface documentation for your BPM runtime environment |
8. | Make the appropriate generated WSDL (abstract or concrete) available to the service consumer. | Calling a Service on a Virtualization Binding (Contract First)
or |
Copyright © Cloud Software Group, Inc. All rights reserved.