Two types of use of BPEL4WS1.1
System integration requires not only the ability to simply interact by using standard protocols. Only when the application and business process can integrate complex interactions by using a standard process integration model, you can play all the potentials of the integrated platform. Therefore, BPEL4WS defines two models: business protocols and executable processes.
The BPEL4WS process can define a business protocol role. For example, in the supply chain protocol, the buyers and sellers are two different roles, both parties have their own abstract flow. Their relationship is usually simulated into partner links. Abstract flows use all BPEL4WS concepts but it reflects the extent required to describe the business protocol common part. Specifically, the abstract flow only processes data about the protocol. BPEL4WS provides a way to identify data identification of the relevant protocol as a message property. In addition, abstract flows use uncertain values to hide private parts of the behavior.
BPEL4WS can also be used to define executable processes. The logic and status of the process determine the nature and order of the web service interaction in each business partner, thereby determining the interactive protocol. Although the BPEL4WS process is not required from a private implementation point of view, BPEL4WS effectively defines the portable execution format for the business processes that depend on the web service resource and XML data.
The BPEL4WS1.1 specification mainly specifies the core module to be shared. The concept of two models is independently used as an extension in the specification, and each part is discussed only by one chapter.
