Analysis of Grid Service Composition with BPEL4WS
AINA '04 Proceedings of the 18th International Conference on Advanced Information Networking and Applications - Volume 2
Analysis of interacting BPEL web services
Proceedings of the 13th international conference on World Wide Web
Compatibility Verification for Web Service Choreography
ICWS '04 Proceedings of the IEEE International Conference on Web Services
Web services: a process algebra approach
Proceedings of the 2nd international conference on Service oriented computing
JOpera: An Agile Environment for Web Service Composition with Visual Unit Testing and Refactoring
VLHCC '05 Proceedings of the 2005 IEEE Symposium on Visual Languages and Human-Centric Computing
Encoding Abstract Descriptions into Executable Web Services: Towards a Formal Development
WI '05 Proceedings of the 2005 IEEE/WIC/ACM International Conference on Web Intelligence
Validating feature-based specifications: Research Articles
Software—Practice & Experience
FORTE'05 Proceedings of the 25th IFIP WG 6.1 international conference on Formal Techniques for Networked and Distributed Systems
A rigorous approach to orchestrating grid services
Computer Networks: The International Journal of Computer and Telecommunications Networking
Rigorous development of prompting dialogues
Journal of Biomedical Informatics
Hi-index | 0.00 |
Grid services and web services have similarities but also significant differences. Although conceived for web services, it is seen how BPEL (Business Process Execution Logic) can be used to orchestrate a collection of grid services. It is explained how CRESS (Chisel Representation Employing Systematic Specification) has been extended to describe grid service composition. The CRESS descriptions are automatically converted into BPEL/WSDL code for practical realisation of the composed services. This achieves orchestration of grid services deployed using the widely used Globus Toolkit and ActiveBPEL interpreter. The same CRESS descriptions are automatically translated into LOTOS, allowing systematic checks for interoperability and logical errors prior to implementation.