Best Practices for Upgrading Entitlements
This topic describes best practices for upgrading entitlements in FlexNet Operations.
Upgrade Relationships
The following upgrade paths allow progression from lower versions to higher versions:
|
Upgrade From |
Upgrade To |
|
ProductA 1.0 |
ProductA 2.0 |
|
ProductA 1.0 |
ProductA 3.0 |
|
ProductA 1.0 |
ProductA 4.0 |
|
ProductA 2.0 |
ProductA 3.0 |
|
ProductA 2.0 |
ProductA 4.0 |
|
ProductA 3.0 |
ProductA 4.0 |
Possible Upgrade Paths
| • | 1.0 → 2.0 → 3.0 → 4.0 |
| • | 1.0 → 2.0 → 4.0 |
| • | 1.0 → 3.0 → 4.0 |
| • | 1.0 → 4.0 |
These upgrade relationships allow a direct progression between versions, including the possibility of upgrading directly from version 1.0 to 4.0 if required.
Avoiding Infinite Loops
Introducing an "upgrade from" relationship where a higher version can revert to a lower version could lead to an infinite loop, which is not recommended.
For example, adding the following upgrade path to the table above would create such a loop:
|
Upgrade From |
Upgrade To |
|
ProductA 4.0 |
ProductA 1.0 |
This would create a potential endless loop:
1.0 → 2.0 → 3.0 → 4.0 → 1.0 → 2.0 → 3.0 → 4.0 → 1.0 → forever ...
Such a setup could cause complications, particularly in automated upgrade processes. To ensure stability, upgrades should only progress forward without looping back to earlier versions.