Choose language:
» Personal Loan No Credit Check, Online Economics » Business process management » Topics begins with B » BPEL
The Businesses Process Execution LANGUAGE, briefly BPEL, is a XML based language for the description of business processes, whose individual activities are implemented by Web services.
In the year 2002 the language imported from IBM, BEA and Microsoft is used thereby for the description of Webservice Orchestrierungen so mentioned. The description is likewise made available in form of a Web service and can be used as such.
By abstraction by means of BPEL the interface of a Web service, which took part Web services in a process steers, can have to arrive to be described - for example in which order message. With the BPEL cannot the choreography by business processes be described; this task is taken over by specification languages such as WS-CDL.
The processing concept WS-BPEL, formerly BPEL4WS (English acronym for BPEL for Web services), develops on the service model of WSDL. Further the standards XMLSchema, XPath and WG-ADDR-sing used.
The language connects the ideas of the calculation-based language XLANG von Microsoft and for the graph-based language WSFL of IBM.
A goal from BPEL is to make possible a programming generally speaking. It is to be noted that BPEL does not support the direct interaction with humans. BPEL processes exclusively communicate with Web services. These can be an interface to humans, however not humans themselves.
BPEL represents a base, on which different columns can be built. The columns abstract business process and executable business process are already in the specification contained. Further columns are BPELJ () and BPEL4people ().
With BPELJ is the goal that activities can contain themselves also Java code, which accelerates the process it however dependent on the programming language Java making IBM have together with SAP a Whitepaper under the name BPEL4people published, which makes the demands for an interaction of humans against an extension of BPEL.
BPEL is block-structured, i.e. with the definition of local environments (Scopes) local variables can be introduced. In addition with the Scopes can be associated error handling (Handler putrefies), compensation treatment (Compensation Handler) and event treatment (Event Handler).
The BPEL standard does not define a diagram of the modelled processes. But the Businesses Process Modeling notation is intended, which describes the illustration from BPMN in the standard to BPEL.
Executable BPEL processes can be brought on a Workflowmaschine to the employment (English deployed) and are executable by it. Abstract processes serve the description of the behavior of the process ("behavioral interfaces"). They are used as view on an executable process and to serve to hide the internal behavior of the process e.g. from a business partner.
BPEL does not know Unterprozesse. It is so for example not always possible to schedule a Unterprozess if the main case is scheduled. This functionality can be made available by explicit operations of a Web services, which is however not prescribed by the BPEL standard.
By IBM and SAP was published a Whitepaper under the name WS-BPEL 2,0 Extensions for Sub Processes (BPEL SPE), in which an extension is described by BPEL for Unterprozesse.
Release 1,1 is current, in which further manufacturers participated such as SAP and Siebel. Up to this version the BPEL standard with BPEL4WS (Business Process Execution LANGUAGE for Web services) is designated.
The standard was handed over in April 2003 at OASIS for standardisation.
A 2.0-Release is in treatment, which contains detail improvements, to the 1.x-Versionen is however incompatible. The OASIS WS-BPEL committee decided on 14 September 2004 to call the specification WS-BPEL 2,0 in order to arrive in agreement with the other WS-*-Standards such as WSDL, WG-Security etc.
Basic Activities - these are the fundamental - as it were atomic - activities, which are not developed different activities:
Structured Activities - these activities contain other activities and permit so the recursive composition of complex processes.
Scopes - with the help of this Konstrukts activities can be bundled and be combined into a transaktionalen unit. By a Scope a group of activities a Fehlerbehandler ("putrefies more handler") knows, Ereignisbehandler ("event more handler") and a Kompensationsbehandler ("compensation more handler") to be assigned. Long-continuous transactions are made possible by the Kompensationsbehandler.
BPEL Engines permit an implementing of BPEL code. For this they must be fed with WSDL information and be become the BPEL process deployed.
We found here 9 articles.
We found here 3 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback
Printer Friendly Format
Bookmark this page
Back to "Business process management"
Back to top