Browse Prior Art Database

Service MetaData, extended attributes and offer creation tool for Web serivces and Web applications Disclosure Number: IPCOM000010274D
Original Publication Date: 2002-Nov-14
Included in the Prior Art Database: 2002-Nov-14
Document File: 4 page(s) / 63K

Publishing Venue


This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 33% of the total text.

Page 1 of 4

  Service MetaData, extended attributes and offer creation tool for Web serivces and Web applications

   Disclosed is web hosting provisioning service metadata and offer creation tool which are used to create service offers in web hosting provisioning environment. The service metadata is a service definition XML file that describes service related information such as service name, description, service agent location, etc.. The service information can be loaded from this file to an offer creation tool. The service metadata can also define service specific attributes or other extended attributes. A typical example of extended attributes for a service is such as 'SLA (service license agreement) id', 'contract id' or any service specific configuration parameters. The offer creation tool can be used to load one or more service metadata definitions and extract all service related information including service specific attributes and other extended attributes, present the data as HTML forms.

As a web hosting provisioning system, it is important for this system to be able to host and provision the following three types of services, and they are:

a. Web Service - an anonymous service that can be invoked by using the web service invocation call.
b. Web Application - a web application that is run inside a web server
c. OGSA Service - a stateful service

The hosting provisioning service metadata should be able to describe all above services. For example, web services can be registered and published in a UDDI registry, therefore, the service metadata should be able to point to a location of the UDDI registry (e.g. IBM public UDDI registry, MicroSoft UDDI registry or a private UDDI registry) and dynamically load service information from UDDI. As a result, it is desirable to have a pluggable service lookup feature that can be used to load service related information from virtually anywhere (etc. UDDI, local file system, URL, or database).

Service MetaData Definition

Service MetaData XML file is an XML file that is provided by a service provider for a provisioned application or a set of web services. The service provider creates this service metadata XML file based on the service template that is provided in the Allegro product. This file describes the service related information such as service name, description or application agent location etc..

Service related information can be defined inside the MetaData XML file or defined in a UDDI registry. If service information is defined in a UDDI registry, a UDDI service lookup implementation class must be specified in this MetaData file (see the following service template for more detail).

If 'resourceLookup' is UDDI registry, user can specify '%' as a serviceName, all services that is registered in this UDDI registry which names have such a string pattern will be retrieved.

Service related extended attributes can be marked as delayed attributes . Then subscribers can pick up and reset these delayed attribu...