An Introduction to BPEL standard and its extentions - SoberIT

More documents

Recommendations

Info

Traditional business integration and process automation methodsExpensive to make changesWeb servicesWProprietary EAI and BPMToo expensiveImplementation of Internet transportprotocols (HTTP, SMTP)Data model (XML)Message exchanged (SOAP)Description of service operations andspecifications (WSDL)Publishing and discovery of services(UDDI)Unable to fill the need themselvesBPELFigure 2.1: Development of process integration and process automation [1, 5]2.3 DevelopmentBPEL 1.0 was initially developed by Microsoft, IBM and BEA as BPEL4WS in August 2002. In April2003, BPEL 1.1 was first submitted to OASIS to obtain broader acceptance and open standardization [3,6]. The OASIS WS-BPEL technical committee voted on 14 September 2004 to name their specificationWS-BPEL 2.0, and approved it as OASIS standard on 12 April 2007 [2, 7].2.4 What can BPEL do?BPEL makes it possible to keep internal business processes separated from external enterprise processes.Hence, changing of internal processes will not affect data exchange between enterprises [3].BPEL provides enterprise with a standard for business orchestration and execution. It specifies how tosend/receive XML messages, exchange message with partners, implement parallel or sequential process,manipulate data between partner interactions, define parallel/sequential execution, etc [6].By using BPEL it Makes integration with business partners easier and more effective Stimulates enterprises to further define their business processes, Leads to further optimizing the business process
3. BPEL4PEOPLE3.1 Limitation of BPEL4WS and demand for BPEL4PeopleBPEL permits orchestration of web services, while the obvious business activity of a human interactionwithin a process is not covered by BPEL [8], and this means that vendors will most probably create theirown proprietary extention to BPEL, and this will result worse interoperability between products, thereforeit makes sense to standardize this part of the process too. However the activities that make up generalbusiness processes are broader than this, because people often participate in the execution of businessprocesses. To support a broaden range of scenarios involving people within business processes, a BPELextension is required [9, 10]. An additional group of syntax and semantics which focus on the descriptionhas to be added to BPEL.3.2 Development of BPEL4PeopleIBM and SAP recognized the importance of extending BPEL for people and jointly published a whitepaper in July 2005 [13, 14, 15, 19]. It addresses various BPEL4People requirements and scenarios.In June 2007, Active Endpoints, Adobe, BEA, IBM, Oracle and SAP published the BPEL4People andWS-HumanTask specifications, which define an approach for integrating human interactions using WS-BPEL 2.0 [9-12]. The authors of BPEL4People plan to submit the specifications to OASIS (Organizationfor the Advancement of Structured Information Standards) in the near future [12].3.3 BPEL4People specificationA BPEL language contains features needed to describe complex control flows. Since human interactionsare usually involved in business process, BPEL process should define people as another type ofparticipants.BPEL4People is now comprised of two specifications [12]: WS-BPEL Extension for People (BPEL4People) Version 1.0, which features lay on top of WS-BPELto describe human tasks as activities that may be incorporated as first-class components in WS-BPEL process definitions. Web Services Human Task (WS-HumanTask) Version 1.0, which introduces stand-alone human tasks.Web Services Human Task may be utilized by Web services-based applications beyond WS-BPELprocesses.BPEL specification focus on the business activities which interact with Web services. BPEL4Peoplespecification extends BPEL elements and enables the modeling of human interaction patterns [12].Complete specifications of BPEL4People 1.0 and WS-HumanTask 1.0 can be found at [13, 14].3.3.1 People integrationTo achieve best possible interact between people and process, it is essential to understand people roles inthe process and how process identifies the people to interact with.
Page 1 and 2: An Introduction to BPEL standard an
Page 3: 2. BPEL AND ITS APPLICATION IN BUSI
Page 7 and 8: 3.3.2.3 Managing processIn a long-r
Page 9 and 10: 4.3 Sub-processAs a fragment of BPE
Page 11 and 12: Parent processRequest operationResp
Page 13 and 14: 5. EU PROJECT SUPERIt happens quite
Page 15 and 16: Message is stored in containers to
Page 17: Besides excluding people action, BP

An Introduction to BPEL standard and its extentions - SoberIT

Create successful ePaper yourself

Delete template?

Save as template?