Browse Prior Art Database

Application Interface to Objects and Methods on Objects

IP.com Disclosure Number: IPCOM000122638D
Original Publication Date: 1991-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 6 page(s) / 246K

Publishing Venue

IBM

Related People

Barrett, KM: AUTHOR [+2]

Abstract

The Enabling Architecture is a general, modular, and flexible software architecture. It is the result of a task force that investigated alternative design strategies for Communications Manager EXTD/2 Release 1.0. The initial goal was to eliminate some of the fundamental limitations of Communications Manager configuration; however, the software architecture described here is applicable to other products as well. Characteristics of the new Enabling Architecture include: o Unification of redundant architectures. o Support for a vertical team organization. o Facilitation of code reuse. o Support for multiple configuration files and configuration file

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

Application Interface to Objects and Methods on Objects

      The Enabling Architecture is a general, modular, and
flexible software architecture. It is the result of a task force that
investigated alternative design strategies for Communications Manager
EXTD/2 Release 1.0. The initial goal was to eliminate some of the
fundamental limitations of Communications Manager configuration;
however, the software architecture described here is applicable to
other products as well.  Characteristics of the new Enabling
Architecture include:
  o   Unification of redundant architectures.
  o   Support for a vertical team organization.
  o   Facilitation of code reuse.
  o   Support for multiple configuration files and configuration file

      formats.
  o   Separation of the user interface from the configuration data.
  o   Support for new function.
  o   Implementation of an open architecture.
  o   Preparation for later convergence with AIX*.

      The Enabling Architecture is an architecture designed to meet
most or all of these goals.  It is an object-oriented architecture
consisting of two main pieces: a TOPOLOGY GRAPH showing the
relationships between objects, such as hardware information, user
data, configuration files, and the communications features installed
by the user, and a C-API implementing the methods used to access the
objects in the topology.

      The architecture is not tailored for use only by configuration;
it can be used by runtime or by any code that needs to access the
objects without regard for how or where they are stored.  In fact,
the architecture does not even assume that the context is
Communications Manager;  it was designed to be generic, for
application in other areas as well.

      This article and (1,2,3) explain further the key points of the
Enabling Architecture.
C-API FOR MANAGED OBJECTS

      The C-API is, as its name implies, a formal interface between a
C program and the configuration files.  The C-API is provided in
order to prevent the user from having to learn the structure and
organization of the configuration files of every feature he may want
to install and configure.

      In previous CM releases, access to the .CFG file was handled by
a module called Profile Services/Record Services (PS/RS).  Any
program wanting to read or write configuration data would issue the
appropriate PS/RS function call, which would then access the .CFG
file.  Beginning with EXTD/2 Release 1.0, configuration data for CM
will be distributed among several files.  In order to protect the
user from having to learn a different syntax for each configuration
file he wishes to access, the C-API was designed to provide one
consistent syntax.  The user specifies a generic operation name (such
as get or put), the object in the topology to be operated on, and the
parameters associated with the operation.  The C-API then uses the
topology information to identify the object, de...