Book Image

Business Process Execution Language for Web Services

Book Image

Business Process Execution Language for Web Services

Overview of this book

Web services provide the basic technical platform required for application interoperability. They do not, however, provide higher level control, such as which web services need to be invoked, which operations should be called and in what sequence. Nor do they provide ways to describe the semantics of interfaces, the workflows, or e-business processes. BPEL is the missing link to assemble and integrate web services into a real business process BPEL4WS standardizes process automation between web services. This applies both within the enterprise, where BPEL4WS is used to integrate previously isolated systems, and between enterprises, where BPEL4WS enables easier and more effective integration with business partners. In providing a standard descriptive structure BPEL4WS enables enterprises to define their business processes during the design phase. Wider business benefits can flow from this through business process optimization, reengineering, and the selection of most appropriate processes . Supported by major vendorsó including BEA, Hewlett-Packard, IBM, Microsoft, Novell, Oracle, SAP, Sun, and othersó BPEL4WS is becoming the accepted standard for business process management. This book provides detailed coverage of BPEL4WS, its syntax, and where, and how, it is used. It begins with an overview of web services, showing both the foundation of, and need for, BPEL. The web services orchestration stack is explained, including standards such as WS-Security, WS-Coordination, WS-Transaction, WS-Addressing, and others. The BPEL language itself is explained in detail, with Code snippets and complete examples illustrating both its syntax and typical construction. Having covered BPEL itself, the book then goes on to show BPEL is used in context. by providing an overview of major BPEL4WS servers. It covers the Oracle BPEL Process Manager and Microsoft BizTalk Server 2004 in detail, and shows how to write BPEL4WS solutions using these servers.
Table of Contents (14 chapters)
Business Process Execution Language for Web Services
Credits
About the Authors
About the Reviewers
Preface
Index

Architecture


BizTalk is a message-oriented middleware, which means that all the communication between BizTalk and any external system happens by exchanging messages. In BizTalk, all messages are internally converted to XMLthat adheres to the specified XML Schema Definition (XSD).

The architecture of BizTalk server 2004 can be broadly divided into the Messaging System and Business Processes (Orchestrations). While Messaging involves receiving, storing, and forwarding of messages and interacting with various external systems, Orchestration is where the business logic is executed.

The following figure describes the architecture graphically:

A message is received into BizTalk using a suitable Receive Adapter at one of the many possible Receive Locations of a defined Receive Port. Once the message is received, it is passed through a suitable Receive Pipeline where the message is processed in stages. The output of the pipeline can be one or more messages that are normalized and converted to XML format...