{"id":25,"date":"2004-07-23T05:04:50","date_gmt":"2004-07-23T11:04:50","guid":{"rendered":"http:\/\/www.khaitan.org\/blog\/2004\/07\/bpel-composing-webservices\/"},"modified":"2004-07-23T05:04:50","modified_gmt":"2004-07-23T11:04:50","slug":"bpel-composing-webservices","status":"publish","type":"post","link":"https:\/\/www.khaitan.org\/blog\/2004\/07\/bpel-composing-webservices\/","title":{"rendered":"BPEL: Composing WebServices"},"content":{"rendered":"<p><a href=\"http:\/\/www-106.ibm.com\/developerworks\/library\/ws-bpel\/\">Business Process Execution Language<\/a> (BPEL) is an XML-based standard for composing WebServices to create processes. In the stack of WebServices standards it sits on top of WSDL, SOAP and XML Schema. WSDL documents of a WebService defines the execution and behavior&#8211;parameters, types, returns, error conditions, invocation etc. BPEL interconnects two or more WSDLs. BPEL as a standard defines the notation and semantics of composing two or more individual services in order to create a process.<br \/>\nWhy a standard for composing WebService? Why not write a program in Java, C# to integrate two WebServices ?<br \/>\nThe answer is loose-coupling&#8211;the same reason why we have WSDL for fine-grained services. Its abstraction. The loose-coupling allows for run time typing and invocation from the WSDL to the fine-grained service. Same holds true for modelling the integration of services using BPEL. BPEL proposes the notations as to how the individual services could be executed.<br \/>\nOn a different note&#8211;While BPEL is being developed under <a href=\"http:\/\/www.oasis-open.org\/committees\/tc_home.php?wg_abbrev=wsbpel\">OASIS<\/a>, parallel efforts are underway:<\/p>\n<ul>\n<li><a href=\"http:\/\/www.w3.org\/TR\/2002\/NOTE-wsci-20020808\/\">WSCI<\/a>. Developed at W3C (Authored by HP, SUN, BEA, SAP, etc.)<\/li>\n<li><a href=\"http:\/\/www.w3.org\/TR\/2002\/NOTE-wscl10-20020314\/\">WSCL<\/a>. <a href=\"http:\/\/www.w3.org\/Submission\/2002\/02\/\">Submitted<\/a> by HP to W3C<\/li>\n<li>WSFL. Proposed by IBM (<a href=\"http:\/\/www-306.ibm.com\/software\/solutions\/webservices\/pdf\/WSFL.pdf\">pdf<\/a>)<\/li>\n<li><a href=\"http:\/\/www.bpmi.org\/bpml.esp\">BPML<\/a><\/li>\n<p>.Hosted at BPMI.org (Members&#8211;BEA, IBM, Fujistu, SAP, etc.)<\/p>\n<li>BPSS. Hosted at ebXML.org <\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Business Process Execution Language (BPEL) is an XML-based standard for composing WebServices to create processes. In the stack of WebServices standards it sits on top of WSDL, SOAP and XML Schema. WSDL documents of a WebService defines the execution and behavior&#8211;parameters, types, returns, error conditions, invocation etc. BPEL interconnects two or more WSDLs. BPEL as [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[],"_links":{"self":[{"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/posts\/25"}],"collection":[{"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/comments?post=25"}],"version-history":[{"count":0,"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/posts\/25\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/media?parent=25"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/categories?post=25"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.khaitan.org\/blog\/wp-json\/wp\/v2\/tags?post=25"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}