{"id":82,"date":"2006-09-27T14:45:02","date_gmt":"2006-09-27T22:45:02","guid":{"rendered":"http:\/\/www.formtek.com\/blog\/?p=82"},"modified":"2006-09-27T14:45:02","modified_gmt":"2006-09-27T22:45:02","slug":"82","status":"publish","type":"post","link":"https:\/\/formtek.com\/blog\/82\/","title":{"rendered":"BPEL 2.0 Available for Public Comment"},"content":{"rendered":"

In an earlier Formtek\u00a0blog<\/a> I described and compared BPEL and BPMN 2.0 technologies and discussed how both are important to BPM.\u00a0\u00a0BPEL is a language that describes the flow and coordination of interactions between published business component\u00a0interfaces.\u00a0 BPMN is a notational language that can graphically describe business processes.\u00a0 In the current spirit of all-things 2.0, Ismael Ghalimi<\/a> even suggests<\/a> that the next generation of BPM is a combination of these two: BPMN + BPEL = BPM 2.0.<\/p>\n

Now, after three years of redesign, from September 10th through November 9th, an updated WS-BPEL 2.0<\/a> specification is out and available<\/a> for public review and comment.\u00a0 John Evedon, co-chair of the OASIS specification group and architect at Microsoft, has a list<\/a> of relevent links related to the new WS-BPEL 2.0 spec.<\/p>\n

What’s new with WS-BPEL 2.0?\u00a0 Quite a lot.\u00a0 BPEL 1.1 had a lot of unfilled holes that vendors filled in ways that best matched their own product architectures.\u00a0 The result\u00a0was that BPEL 1.1 did not live up to the goal of avoiding vendor lock-in — vendors did not implement the specification consistently.<\/p>\n

Because of that, moving up to BPEL 2.0, a lot of syntactic and semantic\u00a0changes were made to the specification so that it is not backwards compatible.\u00a0 The unpleasant side effect of these mid-course corrections are that upgrading from 1.1 to 2.0 versions of BPEL will not be without pain.<\/p>\n

It’s unlikely though that the incompatibility problems of the\u00a0version 2.0\u00a0release will stop the momentum behind BPEL.\u00a0\u00a0The upside is that long-term\u00a0the changes\u00a0should realize the originally envisioned inter-operability of BPEL engines.<\/p>\n

Microsoft, BEA, Oracle and IBM\u00a0have been involved with the BPEL specification as editors and have shown strong support of BPEL with their products.\u00a0 Of interest is IBM’s recent purchase of FileNet because it further reinforces their investment in BPEL.\u00a0 FileNet was also an active participant in the BPEL spec and used BPEL for the support of their workflow processing.<\/p>\n

Many people think that BPEL will power the infrastructure of SOA by allowing business processes to be composed from Web Service interactions.\u00a0\u00a0BPEL, Web Services and SOA will enable BPM.\u00a0 If done right, SOA-based BPM could lead to significant ROI.<\/p>\n

One missing\u00a0piece of the puzzle,\u00a0even with the BPEL 2.0 specification,\u00a0is how human interaction\u00a0can be\u00a0drawn into a BPEL-automated business process.\u00a0 But BPEL 2.0 is clearly a step forward.<\/p>\n

\"Digg<\/a><\/div>
\"Reddit<\/a><\/div>
\"Stumble<\/a><\/div>
\"Buzz<\/a><\/div>
\"Vote<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Kick<\/a><\/div>
\"Shout<\/a><\/div>
\"Share<\/a><\/div>
\"Bookmark<\/a><\/div>
\"Post<\/a><\/div>
\"Google<\/a><\/div><\/div>","protected":false},"excerpt":{"rendered":"

In an earlier Formtek\u00a0blog I described and compared BPEL and BPMN 2.0 technologies and discussed how both are important to BPM.\u00a0\u00a0BPEL is a language that describes the flow and coordination of interactions between published business component\u00a0interfaces.\u00a0 BPMN is a notational…<\/span><\/p>\n

Read more ›<\/a><\/div>\n

<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,32,38,39],"tags":[],"class_list":["post-82","post","type-post","status-publish","format-standard","hentry","category-business-process-management","category-soa","category-web-services","category-workflow"],"_links":{"self":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/82","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/comments?post=82"}],"version-history":[{"count":0,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/posts\/82\/revisions"}],"wp:attachment":[{"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/media?parent=82"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/categories?post=82"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/formtek.com\/blog\/wp-json\/wp\/v2\/tags?post=82"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}