Abstract
Orchestration is currently presented as a way to coordinate Web services in order to define business processes. In this paper we revisit these concepts, showing the current limitation of workflow coordination of Web services, and we show that business process is different from Web service coordination. The paper presents how we have extended the capabilities of workflow for the orchestration and coordination of services (Web or not), and we show how business process and orchestration can collaborate in an application. We shortly describe our tool, Melusine, in which the different propositions have been integrated and experimented.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
