Wf-XML
From Wikipedia, the free encyclopedia
Wf-XML is a BPM standard developed by the Workflow Management Coalition.
Wf-XML is designed and implemented as an extension to the OASIS Asynchronous Service Access Protocol. ASAP provides a standardized way that a program can start and monitor a program that might take a long time to complete. It provides the capability to monitor the running service, and be informed of changes in its status. Wf-XML extends this by providing additional standard web service operations that allow sending and retrieving the “program” or definition of the service which is provided. A process engine has this behavior of providing a service that lasts a long time, and also being programmable by being able to install process definitions.
Wf-XML is offers a standard way for a BPM engine to invoke a process in another BPM engine, and to wait for it to completed. Why is a standard protocol needed for this? Because it is anticipated that process editing tools and process execution tools might be produced by different vendors. A standard way to retrieve process definitions and send definitions will allow a user to match the best process definition tool with the best process execution engine for their needs. Wf-XML completes the job by giving a standard way to pass the process definition between the design tool and the execution engine
The roots of the current effort began in 1997 with the Internet Engineering Task Force (IETF) effort named Simple Workflow Access Protocol (SWAP) lead by Netscape, Oracle Corporation and others. This was followed by the WfMC standard known as WfXML 1.0 and WfXML 1.1. Wf-XML was implemented by a number of commercial products. Because it was invented before SOAP, it does not use SOAP message structures. ASAP and WfXML 2.0 are efforts to move the same capability to be on top of SOAP messages, and to conform to other web standards that have come into existence in the mean time.
Wf-XML provides a standard way to retrieve a process definition from a BPM engine, and to provide an updated one to the BPM engine. A process design tool could used this standard web services based protocol to browse processes on remote BPM server. It provides an interface between such a design tool and the BPM engine; this is the traditional WfMC Interface 1 for getting and setting the process definition. There is no other effort known to be proposed for standardizing this interaction.
Wf-XML 2.0 is defined using WSDL, thus generally accepted as a standard web service. It should be known that services built using Wf-XML 2.0 and later are not backwards compatible with those using Wf-XML 1.1, as the earlier protocol was not based on SOAP messages.
[edit] See also
[edit] Bibliography
- Tom Spitzer, "WF-XML and Interoperability", WebTechniques / New Architect, August 2000, Archive
- Brian Schaffner, "Standardise workflow data with Wf-XML", Builder.au, Aug 16, 2002, Archive
- Clint Boulton, "Group to Wed Web Services Specs", Internet News, June 22, 2004, Archive
- Paul Krill, "ASAP spec proposed for delayed Web services", Infoworld, June 14, 2004, Archive
- Mark Brunelli, "New Web services standards connect competing systems ASAP", SearchWebServices.com, Jun 22, 2004, Archive
- David DeJean, "WfMC Brings Standard Protocols to BPM", InformationWeek, Jun 18, 2004, Archive
