Browse Prior Art Database

Monitoring Novell Navigator Installations using Buckslip File

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

Publishing Venue

IBM

Related People

Brock, SE: AUTHOR [+3]

Abstract

A mechanism for monitoring the success of LAN software distribution and installation using Novell's Network Navigator* is disclosed. A monitor is created that peeks at a shared file, called a buckslip, to which each installer appends the result of the installation. The monitor reports the result when all installs have been completed, or when a time limit has expired.

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

Monitoring Novell Navigator Installations using Buckslip File

      A mechanism for monitoring the success of LAN software
distribution and installation using Novell's Network Navigator* is
disclosed.  A monitor is created that peeks at a shared file, called
a buckslip, to which each installer appends the result of the
installation.  The monitor reports the result when all installs have
been completed, or when a time limit has expired.

      Every time an application is to be distributed, a new buckslip
file is created in the Navigator shared directory, and a monitor
program is started.  The name of the buckslip file is based on the
application name with an extension of '.nnb'.  The file contains an
entry for each target with space for a return code, and has one entry
per line.  Each target is identified by the userid of the target.

      Two executable files, called buckslip handlers, are provided to
the customer to make entries in the buckslip file.  The OS/2 buckslip
handler is called RECEIPT2.EXE and the DOS handler is called
RECEIPTD.EXE.  These reside in the path of the target machines,
either on a file server or on the target machine itself.  The
customer inserts a call to one of these buckslip handlers in the
installation script for the software being distributed, passing the
name of the application being installed and the return code of the
installation.  The buckslip handler uses the application name to
locate the correct buckslip.  The return code is posted to the
buckslip in the entry corresponding to the userid of the caller.

      The monitor program, which is started after the buckslip file
has been created, looks at the buckslip file at a user set time
interval and checks if all the installations have been performed.  If
so, the monitor program ends, reporting the results.

      The monitor program remains active until all the installations
have been performed, either successfully or unsuccessfully, or until
a user set timeout period has elapsed.  For example:
 1.  Distribution initiated for application ABC with a distribution
    list of DEPTTH0B (consisting of userids BROCK, DEMARIA, MELAHN)....