Considerations When Using SUPERSEDE or SUPERSEDE_SIGN

This section explores issues to consider when using the SUPERSEDE keyword.

Server-based License Model to a Client-based License Model

An upgraded entitlement line item may refer to a different type of license model than the original line item; that is, server-based or client-based. For example, one line item could refer to a floating counted license model and a second line item could refer to a nodelocked uncounted model. As a result, the hosts necessarily are different. This operation is almost like rehosting the license from a server to a client.

Even if FlexNet Operations used the SUPERSEDE keyword in this case, it is not effective if the user chooses not to install the superseded license on the server. As a result, the SUPERSEDE keyword is not generated.

The same problem exists for upgrading from a client-based license model to a server-based license model.

Because SUPERSEDE overrides all features in that server ISSUED prior to the ISSUED date of the SUPERSEDE line, caution must be exercised when using it. Consider these situations before implementing SUPERSEDE.

Different Identifiers for the Same Host

A host can be identified using an IP address or a DNS name in FlexNet Operations, but there is no way to confirm that this is the same host. As a result, FlexNet Operations may not regenerate the licenses for certain fulfillments on that host, causing some features to be superseded inadvertently.

Using host ID policies can help mitigate this problem. Most publishers restrict how a host can be defined. For example, some of them may allow their users to use only DNS names.

Trusted Storage Licensing

Trusted storage licensing currently supports both returns and repairs. Currently, an upgrade operation is implemented as returning the previous license and activating a new one. As a result, FlexNet Operations cannot track that a new fulfillment was created due to upgrading another fulfillment and the SUPERSEDE keyword is not generated for trusted storage licenses.

Also, the SUPERSEDE solution depends on the fact that FlexNet Operations records all the licenses ISSUED for a particular host. If there is a trusted activation on that host, FlexNet Operations only has the Machine Identifier of that host (which is not the same as the host name). As a result, FlexNet Operations does not regenerate the trusted storage license and it can be superseded. Mixing trusted storage and certificate licenses on the same host can cause problems if the SUPERSEDE keyword is used.

Start Date of the Upgraded License

Note that the upgraded license is generated from a new entitlement line item. As a result, that entitlement line item can have a different start date than the original line item.

Original and Upgraded Fulfillment on the Same Day

If a user fulfills a license for a product and gets the upgraded license on the same day, the SUPERSEDE keyword does not override the original product license, as both license lines have the same ISSUED date.

If the host contains any fulfillments ISSUED on the same day with similar features, SUPERSEDE licenses need not be generated for these fulfillments.

HOSTID as ANY

If ANY (or DEMO) is used as the hostname, the license works on any machine. If such a license is upgraded, then regenerating all ANY licenses with the SUPERSEDE keyword is problematic. As a result, FlexNet Operations does not generate the SUPERSEDE keyword for ANY (or DEMO) host ids.

Multiple VCGs

If the publisher supports multiple VCGs, SUPERSEDE does not supersede feature lines from another vendor daemon. As a result, FlexNet Operations does not regenerate licenses belonging to another vendor daemon.

Different Organization Units (Accounts) Using the Same Host

A host is identified by its name and the organization unit (account) in FlexNet Operations. When a license is generated for the first time on a host, the organization unit of the logged-in user is set as the organization unit of the host.

Consider two users who belong to the same company and use the same machine to host their licenses, but identify themselves to FlexNet Operations using two different organization units. (This case is common with the channel sales model, when end customers buy from resellers and come to the publisher separately.) In this case, FlexNet Operations treats the host names defined by these two users as different hosts, but in reality, they may be the same machine. Licenses of one or the other user may become ineffective.

Self-Registered Users

Self-registered users are FlexNet Operations Portal users who do not belong to an organization unit (account). Internally, all self registered users belong to a dummy organization unit called PORTAL_ORG_UNIT. Because a self-registered user name is not used to identify the host, the SUPERSEDE keyword cannot be used if self-registered users are supported. Licenses may be accidentally inactivated if two self-registered users use the same hostname.

Signature Length

SUPERSEDE_SIGN supersedes previous increment lines on a host based on their signatures. As signatures are quite long, sometimes, when a number of signatures are included in the SUPERSEDE_SIGN setting, the limit of the license line length can be equaled or exceeded.

If this occurs, the VCG returns the following error: Feature <name> has count zero. Increase count for the feature or decrease superseded sign list, where <name> is the feature for which the license line length is reached.

To resolve this issue, click System > Configuration > FlexNet Operations > Override older fulfillments on the host using SUPERSEDE_SIGN keyword. This decreases the number of signatures being added to the increment line.