Commuting Aggregate Licenses
Aggregate licenses of same feature-version combine to create additional hard and soft limit—benefiting users in the network during the peak usage period. However, this does not mean that all the tokens can be checked out for commuter use. The number of tokens that can be commuted at a point and the maximum duration of each commuted token depends upon:
>The hard limit of the underlying license.
>The expiration date of the underlying license.
In the diagram below, note the validity and hard limit of the three licenses:
The commuter licenses availability for the entire year will be as follows:
Periods (Months) | Tokens | Maximum Commuter Duration |
---|---|---|
1st Jan - 30th Apr | 5 | Can be commuted for use up to 31st Dec |
1st May - 31st May | 5+7 |
>1st five tokens - Can be commuted for use up to 31st Dec >Sixth to 12th tokens - Can be commuted for use up to 31st Aug |
1st Jun - 31st Jul | 5+7+3 |
>1st five tokens - Can be commuted for use up to 31st Dec >Sixth to 12th tokens - Can be commuted for use up to 31st Aug |
1st Aug - 30th Aug | 5+7 |
>1st five tokens - Can be commuted for use up to 31st Dec >Sixth to 12th tokens - Can be commuted for use up to 31st Aug |
1st Sep - 31st Dec | 5 | Can be commuted for use up to 31st Dec |
NOTE The same behavior is applicable to repository licenses that are aggregated.