Browse Prior Art Database

Method of Enabling Automated Invocation of Web Services

IP.com Disclosure Number: IPCOM000015802D
Original Publication Date: 2002-Mar-19
Included in the Prior Art Database: 2003-Jun-21
Document File: 7 page(s) / 134K

Publishing Venue

IBM

Abstract

This invention disclosure publication describes a method and tooling by which an application can adapt when unrecognized web services are found. This involves use of established methods and procedures that, when aggregated as a whole, represents a unique and novel solution to the web service invocation problem. This includes user directed and program enabled functions that: invokes search services to dynamically discover service providers in service provider directories such as Universal Description Discovery and Integration (UDDI) creates an adaptive layer by mapping web services input and output parameters, as specified in Web Service Definition Language (WSDL), to application business object variables and methods stores adaptation information in an internal repository use to record and maintain discovered web services generates and compiles code modules that support run time invocation integrates web service invocation code modules into the application program The current lack of standardization around web service specification for each business process in each industry leads service providers to publish similar web services with different parameters and signatures. The implication of this is that when a requestor of a web service receives a WSDL specification for a web service from UDDI registry, developers may need to specially implement each web service call to support each service provider’s method. Further, the dynamic nature of UDDI registries poses several critical questions that an application working with the web services need to answer: can a program application know which service to invoke (based on its name in WDSL)? can a program application know which internal variables to use when invoking the service (based on the name and type of the interface specification in WSDL) ? can a program application know which internal variables to use when the service returns (again, based on the name and type of the interface specification WSDL)?

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

Page 1 of 7

Method of Enabling Automated Invocation of Web Services

This invention disclosure publication describes a method and tooling by which an application can adapt when unrecognized web services are found. This involves use of established methods and procedures that, when aggregated as a whole, represents a unique and novel solution to the web service invocation problem. This includes user directed and program enabled functions that: invokes search services to dynamically discover service providers in service provider directories such as Universal Description Discovery and Integration (UDDI) creates an adaptive layer by mapping web services input and output parameters, as specified in Web Service Definition Language (WSDL), to application business object variables and methods

stores adaptation information in an internal repository use to record and maintain discovered web services
generates and compiles code modules that support run time invocation integrates web service invocation code modules into the application program

The current lack of standardization around web service specification for each business process in each industry leads service providers to publish similar web services with different parameters and signatures. The implication of this is that when a requestor of a web service receives a WSDL specification for a web service from UDDI registry, developers may need to specially implement each web service call to support each service provider's method. Further, the dynamic nature of UDDI registries poses several critical questions that an application working with the web services need to answer:can a program application know which service to invoke (based on its name in WDSL)? can a program application know which internal variables to use when invoking the service (based on the name and type of the interface specification in WSDL) ? can a program application know which internal variables to use when the service returns (again, based on the name and type of the interface specification WSDL)?

The problem an application can encounter in working with the web services are as follows is described as follows. No industry-wide and category specific standards exist, which all service providers subscribe. Therefore, no standardized invocation convention for the use of service names, invocation parameters and return values. Applications that implement dynamic e-Business processes using web services may not be able to automatically make use of web services functions returned by UDDI search.

The issue of discovering web services and integrating it into an application may be exposed during two distinct phases: (1) application buildtime and, (2) application runtime. During buildtime, a business application is customized to meet the requirements of a given deployed solution. As part of this customization, an application administrator may want to search service provider directories such as UDDI for potential services to fulfill a given bu...