Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Accessing multiple database instances through URIs

IP.com Disclosure Number: IPCOM000019222D
Original Publication Date: 2003-Sep-05
Included in the Prior Art Database: 2003-Sep-05
Document File: 3 page(s) / 157K

Publishing Venue

IBM

Abstract

This paper discloses a technology for accessing data and metadata that is stored in one or more relational databases through Uniform Resource Identifiers (URIs)[1].

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 3

Accessing multiple database instances through URIs

  The technology is based on a listener program that is associated with one or more database instances, which accepts URI requests and supports a data transport protocol for data delivery.

The URI contains the following information:

- the database instance - the database name
- the requested data or metadata - the requested output format

Security information, such as data encryption and authorization or authentication, is managed by the underlying transport protocol.

Based on the information in the URI, the listener program uses a database communication protocol to connect to a database. The information about the requested data is transformed into an SQL statement and sent to the database. The returned result set is formatted based on the requested output format and is sent back to the requesting client.

The returned data is wrapped into a MIME[2] message which provides additional information to the client about the content, such as data type and format.

Figure 1:URI format

The URI format, as shown in Figure 1, consists of the following parts:

1. Protocol, server, port The first parts of the URI ( http://server:port ) define the protocol (in this case

[This page contains 1 picture or other non-text object]

Page 2 of 3

HTTP), the server name, and the TCP/IP port that is used by the listener program.

2. Listener root The listener root defines the listener to which the request should be forwarded. In the example in Figure 1, the listener root is the application that contains the HTTP listener.

3. Instance Every database instance that is enabled for URI access is mapped to a unique identifier string. The database instance name is a string that the listener program can use to determine the instance to which the request is forwarded.

4. Method The client can choose among several access methods to use. You must define the access method to use within the URI.

5. Database The database string specifies the name of the database that the client wants to access.

6. Method specific information Every method uses different notations to describe the requested data.

7. Formatting options The formatting options are not part of the URI. The options are given in the URI request part as parameters. The options beg...