When exposing a business process as a Web service, you work with a segment of an already deployed business process. Used exclusively in the context of exposing a business process as a Web service, business process segment refers to the portion of a business process that provides the functionality for a Request or Request-Reply type Web service. This consists of a sequence of consecutive activities within the business process beginning with a notification iface and ending with an end activity (in the case of a Request only service) or a one-way iface followed immediately by a normal end activity or another notification iface (in the case of a Request-Reply type web service).
Web service headers must be namespaced to meet SOAP 1.2 requirements. See namespaces.
In all cases, no other notification or one-way ifaces can exist between the beginning and end of the business process segment. Database or Web service activities can exist within the exposed business process segment.
A business process must have the following characteristics before it can be exposed as a Web service:
The selected ifaces represent a valid business process segment.
The notification and one-way operations are defined using one single XSD with a target namespace.
The notification and one-way operations are contained in the same service definition (the same WSDL file).
The following are examples of business process segments that can be exposed as a Web service:
Click here for an explanation of this process as a Web service.
Click here for an explanation of this process as a Web service.
Click here for an explanation of this process as a Web service.
