Browse Prior Art Database

Transformer Rules Strategy for Software Distribution Mechanism-Support Products

IP.com Disclosure Number: IPCOM000112273D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 4 page(s) / 135K

Publishing Venue

IBM

Related People

Bunce, JL: AUTHOR [+3]

Abstract

Disclosed is a transformer rules strategy for programs that support a software distribution mechanism (SDM). This SDM-support product allows users to represent and configure workstation nodes within a network. Users can then define the attributes of applications on their nodes, as well as make functional connections between nodes. Afterwards, these nodes can be dragged and dropped onto a transformer object, which in turn, will create CID files, such as response, LAN CID Utility command, and/or NetView* DM/2 change files. (CID stands for IBM's approach to Configuration, Installation, and Distribution.) The strategy presented by this disclosure corresponds to a SDM-support product with an open design that allows users the ability to define their transformer rules on a per product basis.

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

Transformer Rules Strategy for Software Distribution Mechanism-Support
Products

      Disclosed is a transformer rules strategy for programs that
support a software distribution mechanism (SDM).  This SDM-support
product allows users to represent and configure workstation nodes
within a network.  Users can then define the attributes of
applications on their nodes, as well as make functional connections
between nodes.  Afterwards, these nodes can be dragged and dropped
onto a transformer object, which in turn, will create CID files, such
as response, LAN CID Utility command, and/or NetView* DM/2 change
files.  (CID stands for IBM's approach to Configuration,
Installation, and Distribution.)  The strategy presented by this
disclosure corresponds to a SDM-support product with an open design
that allows users the ability to define their transformer rules on a
per product basis.  This helps to satisfy the potentially unique
needs of each product.

      With the SDM-support product, users will be able to define the
attributes, events, and rules for their products.  Events are actions
that the SDM-support product will expect to run at certain times,
such as when connections are made.  The user can create any number of
rules that are associated with event actions.  These rules are run
when events are triggered.

      To allow products to work with transformers, there needs to be
a special event associated with each transformer type, such as
LCUTransform or NetViewDM2Transform.  These events will be activated
by the appropriate transformer type.  Off of each event, there will
be certain expected rules that the transformer will execute when
processing the products for the response file.  (If an expected rule
is not present, a default path, value, or rule will be taken.)
Alternatively, there can be one event named Transform with rules that
the transformer type will individually call if needed.  The event and
rules will be defined on a per product basis and stored in the
product's Class Definition File (CLD).

      Enumerating the set of possible base rules, the following can
be used both with the LCU and NetView DM/2 transformers:

o   Prereq - Returns a list of the products that must be installed on
    the workstation before the current product is.  The default is an
    empty list.

o   Coreq - Returns a list of the products that must be installed on
    the workstation within the same overall state that the current
    product is.  The default is an empty list.

      Temporary programs, such as semaint and lapsprep, can be
defined in the coreq section.  The LCU type of transformer will
correctly interpret the returned entries and know that these are
special programs that need to be incorporated into the generated LCU
command file.  LCU will also know to take the temporary products off
of the workstation when the installation is complete (via statements
in the command file).

      The same ...