Content deleted Content added
No edit summary |
|||
Line 7:
BPML, a superset of BPEL, was implemented by early stage vendors, such as Intalio Inc., but incumbents such as IBM and Microsoft did not implement BPML in their existing workflow and integration engine implementations (BizTalk, Websphere etc.). Hence, they pushed for a simpler language, BPEL. Today, open source implementations of BPML still exceed the capability of these commercial products. This led some to say that BPML versus BPEL was a case of [[VHS]] versus [[Betamax]]. The analogy is not quite correct. For VHS and Betamax both let you watch video - even if one implementation won out. That is not the case with BPML and BPEL. BPML was designed as a formally complete language, able to model any process, and, via a BPMS ([[business process management]] system), deployed as an executable software process without generation of any software code. This is not possible with BPEL, since BPEL is not a complete process language. To illustrate this, note that BPEL is often used in conjunction with Java to fill in the "missing" semantics. In addition, BPEL is often tied to proprietary implementations of workflow or integration broker engines. Whereas, BPML was designed, and implemented, as a pure concurrent and distributed processing engine.
ps to complete a core technology stack at the heart of their business model.
BPEL and BPML are examples of a trend towards [[process-oriented programming]]. BPEL and BPML herald the concept of a BPMS as an IT capability for management of business processes, playing a role similar to a [[Relational database management system|RDBMS]] for business data.
|