Browse Prior Art Database

Mechanism and system for deployment time web services discovery and binding selection to facilitate software component runtime invocation of web services

IP.com Disclosure Number: IPCOM000015849D
Original Publication Date: 2002-Jun-01
Included in the Prior Art Database: 2003-Jun-21
Document File: 3 page(s) / 88K

Publishing Venue

IBM

Abstract

Disclosed is a mechanism and systems for a software component to remotely invoke web services’ operations, where the binding of specific web services are determined at deployment time of the software component.

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 53% of the total text.

Page 1 of 3

  Mechanism and system for deployment time web services discovery and binding selection to facilitate software component runtime invocation of web services

   Disclosed is a mechanism and systems for a software component to remotely invoke web services' operations, where the binding of specific web services are determined at deployment time of the software component.

In this mechanism, a software component uses a web service proxy to invoke the target web service. A web service proxy is a client-side artifact that represents a remote web service port type. The web service proxy is binding neutral, which means it does not contain fixed access information of a specific web service implementation. A software component that consumes a web service is referred to have dependency on the web service. The software component exposes dependencies on web services in a software component deployment descriptor document. The deployment descriptor contains information about the web services interface group(s) the software component depends on and information of the corresponding proxies that the software component uses to invoke the web services. During the deployment process of the software component, the deployment descriptor will be read. Based on the web service dependency information, a set of steps will be performed to resolve the web service dependency as shown in Fig. 1.

Retrieve Web Services Dependency Info from Deployment Descriptor

Query UDDI Registries for Web Services Fulfilling Dependency

Select a Web Service from Query Results

Select a Binding Port from the Selected Web Service

[more dependencies]

[no more dependency]

Resolve Web Services Dependencies

Fig. 1 - UML activity diagram of Resolve Web Services Dependency action state

After the web service dependency resolution is performed, the deployment process will ensure the resolution information available for the software component by creating an instance of the proxy declared for this web service dependency, setting the resolution information to the proxy instance, and storing the instance such that the proxy instance i...