System for Automation of Grid Service-Data Creation
Original Publication Date: 2004-Feb-17
Included in the Prior Art Database: 2004-Feb-17
Grid services are defined by the current OGSA specification from the Global Grid Forum (GGF), and by a newer series of specifications known as OGSI 1.5. Grid services are built on web services, and as such, depend on a hosting environment such as WebSphere. One the features of stateful grid services is 'service data'. This invention describes a grid services tooling solution which automates the addition of both structured and non-structured service data to a grid service. This promotes grid services by lowering the development costs associated with creating grid services, particularly when based on existing web services or other applications.
System for Automation of Grid Service -Data Creation
This invention describes a grid services tooling solution which automates the addition of both structured and non-structured service data to a grid service. A Grid Service developer would no longer need the knowledge of how service data 'looks' because the internal representation of the service data would be generated by the tooling which is used in the development environment to build grid services. At the same time, this invention solves two main problems with tooling grid service data. The first problem is describing information that is specific to how a grid service's service data is linked with OGSI's query capability. The second problem is transferring that data to a deployable OGSI Instance (the hosting runtime environment for grid services) in a way that is understood by the OGSI Instance, but does not interfere with the runtime behavior of the grid service, as would be the case if such information were placed in the grid service's interface definition. One advantage of this form of grid services tooling is that the internal representation of service data as defined by the GS Spec needs only to be realized by an infrastructure that implements the GS Spec. Another advantage is that it also imposes no requirement on the grid service developer to change the source implementation of his grid service. All automated generation of service data is done outside the of the grid service source. Finally, grid services tooling serves to make grid service development simpler; providing service data is less disruptive and less intrusive for the developer. In addition, some tasks are automated, easing the developer workload, lowering the cost of developing grid services. At the core of this invention is a system in which a grid service's service data is
a) communicated to and understood by an OGSI instance
b) subsequently linked to OGSI's query capability.
c) tooled in a way that automates the creation and enablement of grid service data and hides the complexity of the former two points from a grid service developer (in a manner analogous to how a compiler hides details about machine language instructions). This invention for grid service tooling takes grid service developer input, in the form of source code for a bottom-up design, or in the form of interface WSDL for a top-down design. This ability to support design approaches is important, because it supports various etiologies of the application. Web Services Description Language (WSDL), when used extensions to support grid services (GSDL), describe a grid service. Interface WSDL describes the operations supported by the grid service as well as the OGSI interfaces that accompany the service. As an end result of grid service tooling built into the development environment, grid service resources are produced. These resources include a set of server code (current implementation is focused on *Java, but of course, other programming languag...