The Service Modes pattern can also be used to specify service brokering components and their requirements or capabilities. The LTSA WS-Engineer + Modes tool provides transformations from service mode models to service brokering requirements and capability specifications. The transformations generate documents which are deployed on to a runtime broker. Thus, at runtime the requirements documents are used by service clients to create a new brokering session and trigger discovery of required services. Capabilities may also be registered with the service broker, which offers provided services and adds service capability to discoverable services.
Up to very recently, Web services messaging standards used to capture a different subset of non-functional parameters making even closely related standards incompatible with each other. Also the service developer had to specify service configurations at a very low technical level. To tackle these problems, we propose a model-driven approach to efficiently design and deploy standards-compliant service configurations with non-functional parameters.
From such engineering models, we automatically generate service descriptors (WSDL) and configuration descriptors for standard platforms like Apache Axis, including the definition of non-functional requirements, and server-side deployment artifacts. Our method is based on customizable model transformations which allow the developer to describe non-functional requirements in UML4SOA and generate different analysis and deployment code, also allowing an early estimation of the performability of a given middleware configuration.
BliteC is a software tool for supporting a rapid and easy development of WS-BPEL applications. BliteC translates service orchestrations written in Blite, a formal language inspired to but simpler than WS-BPEL, into executable WS-BPEL programs. The tool simplifies the task of developing WS-BPEL applications because Blite provides a textual programming notation and is equipped with an unambiguous semantics, while BliteC properly packages the produced files to be readily deployed and executed in a WS-BPEL engine.
