1. Enterprise Architect, CNA
MGB 2003
Introduction to BPEL
June 7, 2004
Boris Lublinsky
Enterprise Architect, CNA
© 2003 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2. Process-Centric Enterprise
Business process serves as a decoupling layer between Customer facing and Enterprise applications.
Introduction of a process layer allows for the separation of business process logic from the application’s logic. Encapsulation of the business process logic (the most frequently changed part of the enterprise business logic) in a process layer leads to a significantly more agile enterprise architecture, due to the fact that enterprise business processes can be changed with minimal or no impact to the enterprise applications

3. SOA in a nutshell
Enterprise Service is an “invokable” software construct that makes business offering available for repeatable use.
Business Process is a set of activities carried out in a sequence, to realize a business objective or policy goal.
Service-Oriented Architecture (SOA) is an architectural style, promoting concept of enterprise business processes orchestrating execution of the enterprise services.

4. Business Process Services and components
At the design level services can be used as a decomposition technique – at a topmost level a system can be represented as business process orchestrating multiple service.
A service (compound) can be further decomposed using business processes and lower level services
On the lowest possible level service is implemented as an internal business process, orchestrating business components.
Business components can be either implemented natively as part of the service implementation all wrap existing applications

5. BPEL Design Goals Web Services as the Base XML is the Form
Common set of Core Concepts supporting both abstract and executable processes
Support for both hierarchical and graph-like control constructs
Provides only a limited data manipulation functions that are required for definition of process relevant data and control flow.
Properties and Correlation
Support for implicit creation and termination of process instances
Long-Running Transaction Model
Modularization
Composition with other Web Services Functionality

6. BPEL Core Concepts

7. Implementation Landscape
Standard adherence – varies. Everyone has there own differentiator.
Typical Implementation
J2EE – Process container
.Net – Biztalk
Underlying model – P Calculus
Design tools
Ad hoc – interoperability on the level of BPEL XML files
Standardized – based on Business Process Metamodel – OMG/MDA
Debugging – Ad-Hoc

8. Business Process Metamodel

9. What is BPEL good for?
Mechanism allowing for choreography of services in and between enterprises
Exposing of business process itself as a service
Specification of business protocols and interaction model
Programmer's tool for low-level service orchestration and integration-oriented tasks.
Artifact of high-level modeling and process design environments.

10. What is missing ? Manual Activities support
Hooks to business activity monitoring
Multi Transport Binding
Robust transactional support
Robust transformations support
Business rules integration
Rich invocation semantics

11. Notice
The foregoing material is not intended to and does not provide any advice or opinion, and should not be relied upon regarding the results or effects of the use by third parties of any system, equipment, process or protocol described. Information and descriptions in the foregoing material reflect only the authors’ assessment of conditions known to them and existing as of the date of the presentation. Forward-looking statements in the foregoing materials speak only as of the date of the presentation, and CNA and the authors disclaim any obligation to update or revise any such statements.
Statements, analysis and opinions in the foregoing material are those of the authors and/or other individual contributors and are not necessarily those of any third party, including CNA or its subsidiaries or affiliates. Neither CNA nor the authors make any representation, endorsement, or assurance as to the accuracy or reliability of any such statements, analysis or opinions.
CNA is a service mark and trade name registered with the U.S. Patent and Trademark Office.
© 2004, Continental Casualty Company. All rights reserved.