Nested Suites

<< Click to Display Table of Contents >>

Navigation:  Modules > Asset Management > Software License Management > Managed Software List (MSL) > Suites >

Nested Suites

Suites allow users to group MSL Titles together for licensing purposes.  Suites can end up within other suites through two possible actions and it is imperative for suite processing that suites never become nested beyond a maximum depth level, in order to prevent infinite recursion when consolidate processes suites.

 

If a suite level title is defined as a component of another suite, a nested suite will be created.

 

If a component of a suite is given its own suite components and becomes a suite level title, then a nested suite will be created.

 

To manage the creation of nested suites through the user interface, logic has been put in place in the Suite Components area within the MSL record edit screen that prevents the creation of suites that are nested beyond the maximum nesting level.

 

Nested Suites Processing

 

If you have Nested Suites, consolidate will determine the overall component list and zero out the LUR’s for the component authorizations when an authorization for the top-level suite is found. This includes the component suites themselves. For example, if Suite A contains Suite B, and there is an authorization for Suite A, consolidate will zero out the LUR’s for all the components of Suite A, all the components of Suite B, and then for Suite B itself.   

 

If any suites are found that exceed the nesting level, consolidate will skip processing of all suites for that customer. You will need to resolve the nesting level issue before the suites will start processing again. You can see which suites are invalid by examining the consolidate log, or by examining the report called 'Suites and Components' that will show you what those nested suites are.

 

Setting: ConsNestedSuiteMaxDepth

 

The ConsNestedSuiteMaxDepth sets the maximum depth to which suites can be nested. A value of zero indicates that no nesting is allowed. Values greater than zero indicate the how deep the nesting can go beyond the top-level suite. For example, a value of 1 indicates that a suite may be added to a suite, but no further nesting is possible. The maximum permitted value is 100. Any value higher than 100 is treated as 100. Values less than zero are treated as zero.