In this chapter, we've explained how you can describe executable business processes using BPEL. BPEL processes are composed with Web services and exposed as Web services. Activities in the process referring to inbound or outbound Web services specify the abstract interface.
We discussed the relationship of BPEL to other XML languages such as WSDL, XML Schema, and XPath, and you learned how BPEL is used to implement stateful Web services. We examined the following BPEL concepts in detail:
BPEL has helped SkatesTown reengineer its purchase order Web service with a business process. A major objective was achieved: the implementation of a Web service that is flexible with respect to changing business needs. The recursive Web service composition model enabled SkatesTown to incorporate both internal services and business-to-business interactions within the business process. The purchase order process is a stateful service that offers the additional capability to cancel running orders.
Like SkatesTown, a growing number of companies are exploiting Web services in similar ways. In the heterogeneous environment of B2B interactions, interoperability is an absolute must. The next chapter focuses on such aspects of Web services.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |