This is where the BPEL (Business Process Execution Language for Web Services, also WS-BPEL or BPEL4WS) becomes important. BPEL allows composition of web services and is thus the top-down approach to SOA – the process oriented approach to SOA.
The goal of this project is to provide an open-source implementation of JBI compliant data mashup service engine which will give a single view of data from heterogeneous sources within the enterprise with ability to source data from static web pages and tabular data exposed as web services, join/aggregate them, cleanse the data and generate a response in a WebRowSet schema.
The Universal Services are a set of database operations, including insert, update, delete, and query, exposed as Web service operations. These services enable someone who has a pureXML™ column in a DB2® database to set up database Web service operations quickly, for example for prototyping. The services then allow users to query and modify XML data stored in the pureXML column through REST or SOAP, which can serve as a basis for further development of various applications, such as forms or SOA applications. This article gets you started with configuring, testing, and modifying the Universal Services. For even more details, see the step-by-step instructions in the readme file that accompanies the Universal Services download.
The uniform interface constraints describe how a service built for the Web can be a good participant in the Web architecture. These constraints are described briefly as follows
1.