Browse Prior Art Database

Method and System for Organizational Control and Caching of Web Services Connection Information

IP.com Disclosure Number: IPCOM000016269D
Original Publication Date: 2002-Aug-17
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 58K

Publishing Venue

IBM

Abstract

Web Service Screen Overview Disclosed is a system for caching and controlling Web Service connection information. Traditionally there are 2 parts to using Web Services. First you have to find them in the UDDI registry and get the connection information (eg. WSDL Web Services Description Language) and second you use the connection information to use the service. This system, called a Web Service Screen, would allow an organization to control which Web Service is used by Web Service clients within the organization and also add logic to the search for a Web Service. This system could be implemented as a J2EE* application or a .NET** application and could be easily accessed by J2EE or .NET clients within the organization. In the case of a J2EE implementation any web client could use this system via HTTP. Technical Implementation

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

Page 1 of 2

  Method and System for Organizational Control and Caching of Web Services Connection Information

Web Service Screen Overview

Disclosed is a system for caching and controlling Web Service connection information. Traditionally there are 2 parts to using Web Services. First you have to find them in the UDDI registry and get the connection information (eg. WSDL - Web Services Description Language) and second you use the connection information to use the service. This system, called a Web Service Screen, would allow an organization to control which Web Service is used by Web Service clients within the organization and also add logic to the search for a Web Service. This system could be implemented as a J2EE* application or a .NET** application and could be easily accessed by J2EE or
.NET clients within the organization. In the case of a J2EE implementation any web client could use this system via HTTP.

Technical Implementation

There are two views to this application, the administrative view and the Web Service client view. The system would implement an administrative interface that would allow for the administrator to define his/her own categories to apply to the Web Services connection information that will be stored by the application. This allows the organization to create it's own categories for the Web Service clients within that organization to use when searching for a Web Service. Other control information stored by the application would also be customized by the administrative interface. The system includes a "organization-preference" rating system. This allows a company to encourage Web services clients within that organization to use certain Web Services over others. For instance, if a large company has an agreement to get a 15% discount on books from BookStore A, then it will want it's employees to use BookStore A. If the book the Web Service client is looking for is not available at BookStore A, then the system could also store a BookStore B that could be used in situations such as these. The administrative console would allow you to peruse a UDDI registry and then present the W...