Browse Prior Art Database

Methodology for Incorporating Entries in a Software Inventory Database

IP.com Disclosure Number: IPCOM000113773D
Original Publication Date: 1994-Oct-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 106K

Publishing Venue

IBM

Related People

Garrison, M: AUTHOR [+2]

Abstract

Disclosed is a methodology for incorporating application information in a software inventory database. The job of a network administrator has been rapidly growing both in volume and in complexity. Among other tasks, LAN administrators need to be able to balance the workload across the managed systems in a LAN and be able to detect when problems occur. Network administrators also need to keep track of the software on all the managed systems across a LAN. The methodology presented in this disclosure can be used with any network management program to help store entries in a software inventory database.

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

Methodology for Incorporating Entries in a Software Inventory Database

      Disclosed is a methodology for incorporating application
information in a software inventory database.  The job of a network
administrator has been rapidly growing both in volume and in
complexity.  Among other tasks, LAN administrators need to be able to
balance the workload across the managed systems in a LAN and be able
to detect when problems occur.  Network administrators also need to
keep track of the software on all the managed systems across a LAN.
The methodology presented in this disclosure can be used with any
network management program to help store entries in a software
inventory database.

      The following three tables would be needed as part of the
database schema (as implemented with SQL):
  o  SYSTEMS - Stores information about the managed systems in a
     network, which includes the NETID, SYSID, and other
     attributes of a specific system.  Information on managing
     systems could be included in this table as well.
  o  APPLICATIONS - Stores information about the applications that
     the network administrator wants to monitor.  This information
     would include the "class" attributes of name, program name
     (what to look for), date and time stamp of the file,
     application type, and other information.
  o  APP_SYS - Stores "instance" information about the monitored
     applications found on the systems in the network.  Such
     information would include the full path name of the
     discovered monitored application.  This table links the
     SYSTEMS and APPLICATIONS tables together.

      In addition to monitored applications, unmonitored ones could
be collected as well and stored in the APP_SYS table with a special
designation.  For example, if all files with the *.EXE extension were
collected from workstation WORK1, 123.EXE may be a monitored
application and XXX.EXE may not be.  Instance information on 123.EXE
would be stored in the APP_SYS table, and if the administrator so
desired, the XXX.EXE application could be as well.  Information on
the XXX.EXE application would be returned as part of the report when
the user queried for all unknown applications on workstation WORK1.

      When files are inserted into the Software Inventory tables, the
following flow is followed for each file entry.  This flow provides
administrators with multiple levels of granularity.  The
administrator can match information from a collected application
against just the file name, or the administrator can match the entry
all the way down to the file's date and time.
  1.  Retrieve the SYSTEM_ID primary key from the SYSTEMS table
      for the row that ma...