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

Method for Implementing Multiuser Database Manager Application Servers in Distributed Computing Environment

IP.com Disclosure Number: IPCOM000114780D
Original Publication Date: 1995-Jan-01
Included in the Prior Art Database: 2005-Mar-29
Document File: 2 page(s) / 77K

Publishing Venue

IBM

Related People

Hidalgo, DS: AUTHOR

Abstract

A multiuser or multi-database connection client-server database application that uses Distributed Computing Environment* (DCE) Remote Procedure Call (RPC) to support its service interface must create a separate server agent for each database connection. The reason for this is that a single server may not serve more than a single database connection at a time. This dynamic creation of database server agents presents a problem in a DCE RPC client-server implementation. This is due to the fact that for the client to make SQL RPC requests on the database connection held by the server agent, it must first get an RPC handle (must bind) to that server.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Method for Implementing Multiuser Database Manager Application Servers
in Distributed Computing Environment

      A multiuser or multi-database connection client-server database
application that uses Distributed Computing Environment* (DCE) Remote
Procedure Call (RPC) to support its service interface must create a
separate server agent for each database connection.  The reason for
this is that a single server may not serve more than a single
database connection at a time.  This dynamic creation of database
server agents presents a problem in a DCE RPC client-server
implementation.  This is due to the fact that for the client to make
SQL RPC requests on the database connection held by the server agent,
it must first get an RPC handle (must bind) to that server.  Since
the application client must not be dependent or be aware of the
server's process model and/or of its request transport method (DCE
RPC, vs sockets, etc), it is necessary to create a design that
resolves the dynamic connection server agent binding problem, while
at the time shielding the client from those details.

      The following is a method to implement an application database
client and server in a manner that resolves the above described
problem.
  1.  The application server is divided into a "Master Connection
       Server" and a "Connection Agent Server".
  2.  The Master server supports the connect and disconnect RPC's.
One
       instance of this server is started before any client attempts
a
       database connection.  The name of this server is "well known"
to
       clients, and is exported to the DCE cell name space when the
       server is started.
  3.  The connection server agent supports the Structured Query
       Language (SQL) request RPC's.  This agent is the actual
database
       application program.  It is started by the master server as
       result of a connection RPC call.  The server agent calls the
       Database Manager (DBM) database connection Application
       Programming Interface (API), if that call is successful then
the
       agent creates a uniq...