Browse Prior Art Database

Scan optimization with bundle detection

IP.com Disclosure Number: IPCOM000244268D
Publication Date: 2015-Nov-27
Document File: 4 page(s) / 47K

Publishing Venue

The IP.com Prior Art Database

Abstract

Nowadays every industry has numerous IT machines (laptops, servers) on which are installed many software products. Those software products need to be managed properly. To manage them correctly, there is need to know what exactly is installed on which machine, on what kind of license and which products are communicating with each other. Our invention allows to very quickly verify what is installed on which machine and say with big probability which components are sold in a bundle with each other.

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

Page 01 of 4

Scan optimization with bundle detection

We are proposing adding small functionality to installer of every software product which

will be adding record to a specific file that it has been installed. Then during scan

machine on which software product has been installed will send this file and list of hosts

with which this machine is communicating to Licensing Server. Then on server, files are

checked and user can receive information about software installed on the machine

within seconds. Comparing those files between machines from the host list can give information, with great probability, that software installed on the machines were sold in one bundle. To make it more confident, we propose that user shall provide to Licensing Server list of components that came in the installed offerings.

The best way to explain how it could work would be on an example.

Offering 1 consists of 3 components:


· Program A
· Program B
· Program C

Offering 2 consists of 1 component:


· Program D

Programs A and B are planned to be installed on Machine X and Program C is to be installed on Machine Y. Program D is installed on machine Z. After installation customer sends Offering names to Licensing Server. Licensing Server utilizes Knowledge Database where the Offering Definitions are available.

The topology of our example would look like this:

Lines symbolize connection between machines, their ability to communicate.

1


Page 02 of 4

Lets define Program List file as a file with records of installed components.

When Program A is installed, we propose that installer will have functionality that will check if Program List file exists (in certain directory, e.g. /home/ProgramList/ProgramList.txt). If it does not exist it will be created. Then installer

will create record in this file with information about it. Such record could look for

example like this:

Name: Program A;

Version: 1.1;

IP: 10.10.10.10;

Host: Machine X;

Dir: /opt/Program_A; Instal_Date: 10/10/2015 12:34:23 User: user1

Explaining those information:


· Name - name of installed component
· Version - version of this component


· IP - IP of machine
· Host - hostname of machine
· Dir - directory where it was installed
· Instal_Date - day and hour when it was installed
· User - name of user who installed this

So when Program A is installed, installer puts such record in ProgramList.txt, than Program B is installed and puts similar record in ProgramList.txt. Also similar situation occurs on Machine Y where Program C is installed a...