LOGIN | REGISTER NOW | SUBSCRIBE
 
print Printable version 
Most Read Latest News Blog Resources
CouchDB brings peer-based data replication
This NoSQL database is now production ready for developers who want to spread data out wit...
Experts: UML is active, but the buzz is lost
Since widespread acceptance, there is little enthusiasm around the language even ahead of ...
Compuware intros new GUI for mainframe tools
Beyond the GUI are plug-ins for data and debugging tools, as well as an OEM edition of Sli...
Black Hat conference fields suggestions for software security
Attendees give a wide variety of ideas about the subject, with Rex Black adding in some of...
Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter


            iphoneapp GET THE APP!

Why BP Languages Don't Help B-to-B


By David Burdett
September 1, 2003 —  (Page 1 of 4)
Last year, two business process language specifications were published: Business Process Execution Language for Web Services (BPEL4WS, or BPEL for short) by BEA, IBM and Microsoft; and Web Service Choreography Interface (WSCI) by BEA, Intalio, SAP and Sun.

While these languages have gained attention as effective ways to link business processes together with Web services, they don't work for electronic data interchange or business-to-business integration.

Businesses that implement solutions based on these languages will find they are not enough to make their solutions interoperate with other businesses successfully. As a result, the adoption rate of Web services-based e-commerce will be slowed. Fortunately, the problem can be solved.

But first, what's the problem? Consider a typical EDI or B-to-B purchasing transaction. To make this work, you need purchasing software at the buyer and seller that can work together. If Web services are being used to implement the processes, then the interfaces to each process would be defined using the Web Services Definition Language (WSDL), while the messages flowing either within the buyer or seller or between them would be SOAP messages that comply to the WSDL definitions.

Although each of the processes at the buyer and seller could be self-contained Web services, it is more likely they will be implemented by wrapping one or more existing procurement and ERP applications in a Web services "wrapper" so they appear to be Web services.

It also is necessary to manage the processes. This can be achieved by the following two approaches: distributed, in which each Web service determines where each message is sent on its own; or centralized, in which process management software or a broker looks at the data flowing between services and determines what process to invoke or message to send next.

The latter is a better approach because it is easier to create, manage, update and control the rules if they are specified in one place. This is exactly what business process languages such as BPEL and WSCI are designed to do. They provide a runtime script that can be used by process management software to manage the information flows.

Pages 1 2 3 4 


Share this link: http://www.sdtimes.com/link/27387
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading



 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 8/1/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
Like Ruby n' Rails
Programming languages and Web frameworks go together like peas n carrots. Or Ruby n' Rails.
07/30/2010 04:36 PM EST

Adobe buys a Web-based IDE
Adobe looks to buy a rapid and agile Web development environment.
07/28/2010 03:49 PM EST

OpenStack opens up
OpenStack looks to be an intriguing new idea for running clouds.
07/28/2010 01:56 PM EST

 

Events calendar tab
SHARE
8/1/2010 to 8/5/2010
Boston
SHARE

VSLive
8/2/2010 to 8/6/2010
Redmond, Wash.
1105 Media

Agile 2010
8/9/2010 to 8/13/2010
Orlando
Agile Alliance

Delphi Live
8/23/2010 to 8/26/2010
San Jose
S&S Media

VMworld
8/30/2010 to 9/2/2010
San Francisco
VMware