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

Strategy for Integrating and Analyzing Software Inventory Information

IP.com Disclosure Number: IPCOM000114407D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 2 page(s) / 84K

Publishing Venue

IBM

Related People

Garrison, M: AUTHOR [+2]

Abstract

Disclosed is a strategy to integrate and analyze the software inventory information collected from across a LAN. 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.

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

Strategy for Integrating and Analyzing Software Inventory Information

      Disclosed is a strategy to integrate and analyze the software
inventory information collected from across a LAN.  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.

      This disclosure discusses how the collected software inventory
information can be integrated (or stored) at the managing system and
how administrators can analyze the integrated information.  The
technique presented in this disclosure can be used with any network
management program.

      In the strategy presented by this disclosure, the network
management program running on the managing system would need to
detect that a software inventory file arrived and that the software
inventory integration program would need to be run.  This integration
program would be able to parse the data in the inventory file into an
inventory database that the administrator could query.

The inventory database would require three tables:
  1.  Systems, which stores information about the managed systems on
       the LAN, such as each system's workstation name and network
ID,
  2.  Applications, which stores attribute information on the files
       that should be monitored, and
  3.  App_Sys, which stores information about the instances of the
       applications that are slated for monitoring.

If the inventory database used a SQL database, the table definitions
could be as follows:
  CREATE TABLE SYSTEMS (
    SYSTEM_ID INTEGER NOT NULL,
    WRKSTATION VARCHAR(255) NOT NULL,
    NET_ID VARCHAR(512) NOT NULL,
    SYS_ID VARCHAR(1024) NOT NULL,
    OS2_DOS SMALLINT NOT NULL,
      PRIMARY KEY ( SYSTEM_ID ) )
  CREATE TABLE APPLICATIONS (
    APP_ID INTEGER NOT NULL,
    NAME VARCHAR(512) NOT NULL,
    TITLE VARCHAR(255) NOT NULL,
    FILE_DATE DATE,
    FILE_TIME TIME,
    SIZE INTEGER,
    TYPE SMALLINT,
    FILE_COMMENT VARCHAR(255),
      PRIMARY KEY ( APP_ID ) )
  CREATE TABLE APP_SYS (
    APP_ID INTEG...