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

Distributing SOMObjects Using Distributed Computing Environment

IP.com Disclosure Number: IPCOM000118265D
Original Publication Date: 1996-Nov-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 103K

Publishing Venue

IBM

Related People

Hahn, TJ: AUTHOR [+2]

Abstract

The Distributed Computing Environment (DCE) is used to distribute SOMObjects defined objects. The implementation allows the expressive power of object-oriented programming to benefit from the operational characteristics of DCE. The DCE specific processing to enable this function is encapsulated within a set of base classes from which specific objects are derived. DCE Naming and Security services are used to locate object instances, authenticate object "users" and "providers", provide for access control checking on a method basis, and allow for secure message communication between "user" and "provider".

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

Distributing SOMObjects Using Distributed Computing Environment

      The Distributed Computing Environment (DCE) is used to
distribute SOMObjects defined objects.  The implementation allows the
expressive power of object-oriented programming to benefit from the
operational characteristics of DCE.  The DCE specific processing to
enable this function is encapsulated within a set of base classes
from which specific objects are derived.  DCE Naming and Security
services are used to locate object instances, authenticate object
"users" and "providers", provide for access control checking on a
method basis, and allow for secure message communication between
"user" and "provider".

      The DCE offers a rich set of integrated services for enabling
the development of distributed computing applications.  These
services, however, are offered via procedural interfaces.  As object
technology exploitation becomes more widespread, it is inevitable
that the services  offered by DCE will be required for distributed
object processing.

      The fundamental problem is that of making use of the integrated
naming and security functions of DCE while offering the expressive
power of object oriented design and implementation.

      CORBA IDL (the language used to describe SOMObjects) is used to
define the set of objects that will be distributed.  In addition, a
DCE IDL specification is made for each method in the SOMObject.  All
DCE Remote Procedure Calls (RPCs) for a SOMObject are contained
within a single DCE interface specification.

      Two one-to-one mappings are made between SOMObject methods in
the CORBA IDL specification and the DCE RPC routines in the DCE IDL
specification.  One mapping occurs on the client side and maps a
client's SOMObject methods to RPCs in the DCE IDL specification.  The
second mapping occurs on the server side and maps RPCs in the DCE IDL
specification to SOMObject methods in the server.  The CORBA IDL
specification is used to define the SOMObject client object and the
SOMObject server object.  These are identical with the exception of
the base class they are derived from (mappings between CORBA IDL and
DCE IDL).

      The DCE specific processing to enable this function is
encapsulated within a set of base classes from which specific objects
are derived.  The DCEClientInterface SOMObject is the base class from
which specific client side SOMObjects are derived.  This base class
encapsulants the startup processing and name space lookup operations
for locating an object instance using the DCE Naming Service.  The
SOMObject derived from DCEClientInterface is implemented to act as a
proxy.  The implementation of each method is to invoke the associated
DCE RPC cal...