Browse Prior Art Database

Programmble Configuration

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

Publishing Venue

IBM

Related People

Barrett, KM: AUTHOR [+1]

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 EXTD/2 Rel. 1.0's Communications Manager. 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.

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

Programmble Configuration

      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 EXTD/2 Rel. 1.0's
Communications Manager. 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 (,2,3) disclosures explain further the key
points of the Enabling Architecture.

      Programmable Configuration (PC) is an extension of the REXXSAA
programming language that is provided by the Enabling Architecture as
an alternative to Advanced Configuration Dialog.  It is a powerful
tool which encompasses full functionality of the panel-driven dialog,
allowing system administrators to generate or modify large numbers of
configuration files quickly and efficiently.  PC allows the user to
write a REXXSAA program to create, modify, delete and/or copy
configuration information.  It takes as input REXXSAA commands in a
designated syntax, and produces generic method calls to the C-API.
Where the configuration data is stored is handled by the Enabling
Architecture; the number of files supported and the format of those
files is not restricted.

      Programmable Configuration provides the user with an extendable
user interface for manipulating any object in the topology.  Just
what PC can access is determined by what is defined in the Enabling
Architecture topology. The topology can be expanded and contracted
dynamically, for example,...