Use > Inventory Tools > Analysis Workbench Overview > License Relations and Application Suites

License Relations and Application Suites

Each identified file is categorized as either Main, Associated, or 3rd Party. The recognition library can contain any number of files in a particular version as belonging to either category.

When at least one Main file is identified on a machine, a license is required for the application, unless another application on the machine assumes license responsibility for the application.

License relations are part of the Application Library. When two interdependent applications are identified on a machine, one application can assume license ownership on that particular machine. The chain of license relations can be any number of levels deep.

License relations solve the problem of Suite licensing simply and effectively, and are applicable to license relationships outside what would normally be considered a software suite.

For example, MS Office 2000 licenses MS Access, Word, Excel, PowerPoint, Outlook and is a well known software suite. In addition Outlook 2000 licenses MS Data Access Components (ADO) 2.1 sp1 - if Outlook or another licensing application is not present on the machine, a license is required for the software, but if Outlook is installed on the machine, Outlook assumes license ownership. Different versions of Outlook license different versions of MS Data Access Components.

License relations are also useful when an application has a complex component structure. If application components can be installed on their own, they should be treated as independent applications, but the connection with the application should be reflected in license relations for that application.

The SAI Editor allows license relationships to be established and immediately be applied to the application data loaded. This application is available via the Analysis Workbench User Interface or as a stand-alone utility from the Start menu.