Upgrade, Upsell, or Renew a Fulfillment
You can upgrade, upsell, or renew one or more seats in a fulfillment. The new license is created for the currently defined server host.
This process is similar to activation of an upgrade, upsell, or renewal entitlement line item. The difference is that this process allows you to control which fulfillments are upgraded, upsold, or renewed.
Important:Before upgrading or upselling a fulfillment, you must upgrade, upsell, or renew the customer’s entitlement line item for the product that this fulfillment references.
Important:Some conflicts can prevent the successful activation of upgrade line items. See Avoiding the Creation of Upgrade Line Items with Incompatible License Models for details.
Tip:FlexNet Operations can automatically upgrade line items for qualifying products and line items with the Product Version Upgrade job. See FlexNet Operations Alert Types.
When you upgrade, upsell, or renew a fulfillment, the status of the original fulfillment is changed to Obsolete and the Support Type is changed to either UPGRADE, UPSELL, or RENEW accordingly. A new fulfillment is created and the Support Type is MASTER. If you upgrade or upsell only a portion of the total Count in a fulfillment, then two fulfillments are created. The status of the original fulfillment is changed to Obsolete and the Support Type is changed to either UPGRADE, UPSELL, or RENEW accordingly.
For example, F1-P1 is a fulfillment for ten seats of product P1 (the Count property equals 10). You upgrade only two seats from that fulfillment to product P2. The status of fulfillment F1-P1 is changed to Obsolete and the Support Type is changed to UPGRADE. Two new fulfillments are created:
| • | F2-P1 is a fulfillment for the remaining eight seats of product P1. |
| • | F3-P2 is a fulfillment for the two seats of product P2. |
If you are upgrading or upselling a product with a floating counted, floating uncounted, and nodelocked counted license model and the entitlement line item for the new product specifies a nodelocked uncounted license model, the user is prompted to define either the server host ID or the nodelocked host ID (see the following table for details).
For example, in case 3 of the following table, the license model changes from floating counted to nodelocked counted, the new fulfillment record requires that nodelocked host IDs be defined. The server host ID is obtained from the original fulfillment record, but the user is prompted to define the nodelocked host IDs. If there is no change in the license model type, then all the information is retained from the original entitlement line item.
|
|
Original License Model |
Upgrade or Upsell License Model |
User is prompted to define the following host IDs (Server or Nodelocked): |
|
1 |
FC |
FC |
None |
|
2 |
FC |
FU |
None |
|
3 |
FC |
NC |
Nodelocked host ID |
|
4 |
FC |
NU |
Nodelocked host ID1 |
|
5 |
FU |
FC |
None |
|
6 |
FU |
FU |
None |
|
7 |
FU |
NC |
Nodelocked host ID |
|
8 |
FU |
NU |
Nodelocked host ID Note:In this case, the SUPERSEDE keyword is not used in the upgraded license, even if you enabled the Use SUPERSEDE Keyword for Upgrade and Renewal Licenses property in the System > Configure > FlexNet Operations page. |
|
9 |
NC |
FC |
None |
|
10 |
NC |
FU |
None |
|
11 |
NC |
NC |
None |
|
12 |
NC |
NU |
Nodelocked host ID Note:In this case, the SUPERSEDE keyword is not used in the upgraded license, even if you enabled the Use SUPERSEDE Keyword for Upgrade and Renewal Licenses property in the System > Configure > FlexNet Operations page. |
|
13 |
NU |
FC |
Server host ID Note:In this case, the SUPERSEDE keyword is not used in the upgraded license, even if you enabled the Use SUPERSEDE Keyword for Upgrade and Renewal Licenses property in the System > Configure > FlexNet Operations page. |
|
14 |
NU |
FU |
Server host ID Note:In this case, the SUPERSEDE keyword is not used in the upgraded license, even if you enabled the Use SUPERSEDE Keyword for Upgrade and Renewal Licenses property in the System > Configure > FlexNet Operations page. |
|
15 |
NU |
NC |
Server and nodelocked host ID Note:In this case, the SUPERSEDE keyword is not used in the upgraded license, even if you enabled the Use SUPERSEDE Keyword for Upgrade and Renewal Licenses property in the System > Configure > FlexNet Operations page. |
|
16 |
NU |
NU |
None |
|
FC=floating counted; FU=floating uncounted; NC=node-locked counted; NU=node-locked uncounted. |
|||
The following steps describe the upgrade process:
| 1. | Upgrade Products for the Activation ID... page. |
If there are multiple products (or entitlement line items) that this product can be upgraded or upsold to, you are presented with a list of entitlement line items that you can choose from. If there is only one entitlement line item that meets this requirement, you are not prompted to select anything.
| 2. | In the <Upgrade/Upsell/Renew> Fulfillment... page, define the required properties. |
| 3. | Click: |
| • | Verify to check whether the values entered generate a valid license. |
| • | Generate <Upgrade/Upsell/Renew> License to create the new license and complete the process. |
Important:FlexNet Operations does not evaluate the count of available copies when an upgrade is created. Therefore, it is possible to create an upgrade count that exceeds the number of available copies; however, the count is evaluated at fulfillment time. On fulfillment, upgrades that exceed the available count are rejected. To avoid errors at fulfillment time, users can invoke the method getExactAvailableCount(), which returns the exact number of copies available for upgrade fulfillment. This method is available as a web service call and also as part of public API.
Avoiding the Creation of Upgrade Line Items with Incompatible License Models
Some license technology and license model conflicts can prevent the successful activation of upgrade line items. (FlexNet Operations does not prevent the creation of these upgrade line items, but the resulting line items cannot be successfully activated.) The following upgrade paths result in upgrade line items that cannot be activated:
|
Upgrading From |
Upgrading To |
Notes |
|
Custom licensing |
FlexNet Publisher Trusted Licensing |
Sharing counts between a license model from a custom license technology and retail activation license model is not supported. |
|
FlexNet Publisher Certificate Licensing |
FlexNet Publisher Trusted Licensing |
Sharing counts between a floating, counted license model and a retail activation license model is not supported. |
|
FlexNet Embedded Licensing |
FlexNet Publisher Certificate Licensing |
Sharing counts between an embedded counted license model and a node-locked, uncounted license model is not supported. |
|
FlexNet Embedded Licensing |
FlexNet Publisher Trusted Licensing |
Sharing counts between an embedded, counted license model and a retail activation license model is not supported. |