Devices: Advanced Topics
For more information about these topics, refer to Administering Device and License Server Setup.
Activations of Entitlements Across Multiple Accounts on a Single Device
Producers with the FlexNet Advanced Organization module that use FlexNet Embedded licensing technology can take greater advantage of their account hierarchies and channel partner sets during entitlement mapping operations. This capability also supports producers who want end users to be able to activate entitlements on any device.
FlexNet Operations enables accounts, other than the device owner, to map entitlements to a device. Producers can map entitlements from the device owner's sub-accounts to any device, and End-User Portal users can map entitlements from their account, or its sub-accounts, to any device visible to them.
Activate Remaining Available Copies of an Entitlement
The FlexNet Embedded client API has a “partial” option when specifying activation IDs for a capability request intended for the back office. It is now possible to request, if there are insufficient copies of the entitlement to satisfy the request, that the back office instead activate the remaining available copies. Without this option, such a request would fail with a message indicating that the number of copies requested exceeds the available copies. With the option, the request succeeds with a status message indicating that the request was only partially fulfilled.
This partial option can be added for each activation code requested. For example,
-activate activation-id [copies] [partial]
Note:The partial option does not take into consideration optional limits imposed by the device series.
Refer to your FlexNet Embedded API documentation for details.
Device Series and Device Models
A device series is a collection of device models that are physically identical but can be upgraded in the field through license changes and products that are added on. The device series sets the maximum limits for device capabilities.
A device model is a basic configuration for which a producer creates a pre-installed license defining a set of capabilities within the maximum limits for the device series. The device model with that particular pre-installed license represents a purchasable configuration for the device. The capability of the model can be increased to the maximum for the series.
In the following example, producer ABC Networks, Inc. has a VPN 5000 device series that includes three device models: VPN 5005, VPN 5020, and VPN 5050. Each model represents a different basic configuration.
In the VPN 5000 device series, all device models can have up to 10,000 simultaneous users, up to 100 Mbps of throughput, and redundancy enabled or disabled.
The VPN 5050, the device model in the series with the highest basic capabilities, has a basic configuration of 5,000 simultaneous users, 50 Mbps of throughput, and redundancy enabled.
Two VPN 5000 series products that can be added on are an additional 1,000 simultaneous users and an additional 10 Mbps of throughput. All device models in the series can be upgraded by a customer to the maximum limits for devices in the VPN 5000 series.
Claiming an Unknown Device
If unknown device support is enabled for their site, a customer can claim an unknown device—a device that was not created using the Producer Portal—in one of the following ways:
| • | The device makes a capability request to FlexNet Operations. |
| • | The customer uses the device ID to claim the device through the End-User Portal. The device is no longer unknown because it is associated with an account. |
Mapping an Entitlement to a Device Using an Activation ID
Devices often include pre-installed products, but also permit the optional addition of new products. When the current owner of a device is entitled to additional products, the additional products can be mapped programmatically to the device using an activation ID.
Viewing Device Details and History
Use the FlexNet Operations Producer Portal to view details about a device such as device ID, status, host type, as well as details about any pre-installed or additional products. You can also view the history specific to a single device. The device history page lists all the device events including device creation, changes, and activation requests.
Associating a Device with an End User
A FlexNet Operations device can be associated with an end user or contact called the Device User. Associating a device with a Device User allows an End-User Portal administrator to communicate with someone regarding the licenses on that device. For example, if the End-User Portal administrator needs a license for a new device but there are no licenses available, the administrator can search for all existing devices using that license and request that one of those Device Users return their license so it can be used on the new device.
With the proper combination of system configuration and user permission settings, a Device User can be added, edited, or deleted via capability request, sync request, the End-User Portal, the Producer Portal, or Web Services. The same Device User can be associated with multiple devices, but a device can only be associated with one Device User.
Removing Licenses from a Device
A license for a device’s added-on product can be manually removed in the Producer Portal via the device’s default view.
Moving a Device
A device that has not yet been assigned to a customer account can be moved to a related account in the Producer Portal via the device’s default view. For example, a parent account can move a device from one of its child accounts (a regional division, for instance) to another child account.
When a device is moved, entitlements that belong to that device are moved as well. The result of such a move is to either create new entitlements for the receiving account or to increment the count of that account’s existing (and matching) entitlements by the count on the device that was moved.
Returning a Device
A device can be returned in the Producer Portal via the device’s default view. Returns are irreversible actions intended for devices that will no longer receive a capability response or license file.
When customer returns a malfunctioning device to a manufacturer or reseller, the customer has the option of moving all of that device’s licenses to a replacement device. Licenses that are not moved are returned to the pool of unused licenses and can be allocated to another device later.
Upgrading a Device
An upgrade is defined as moving a customer from a specified version of a product to an improved version with new or expanded capabilities. First, in the Producer Portal, create a product with additional features, configure FlexNet licensing for that product, and create an entitlement to the product for the customer account.
Note:The customer must remove the device’s previous licenses before mapping an entitlement for the new version of the product.
Managing Hardware Returns
When FlexNet Embedded is used to license hardware, the Return Material Authorization (RMA) process is used to return a malfunctioning device to a producer or reseller and replace it with a new one. Some or all of the licenses can be moved to the replacement device. If a license is not moved, it is returned to the pool of unused licenses and can be allocated to another device.
Making a Device Obsolete
An active device can be made obsolete from its default view on the Producer Portal. When a device is made obsolete, its licenses are removed and returned to the pool, and it becomes unable to acquire new license rights. Obsolete devices cannot be re-activated. Obsolete status is permanent.
Offline Activation
Some devices use an offline activation model in which the device generates a binary license request file for an additional product license. The request file can be manually uploaded on the FlexNet Operations End-User Portal.
FlexNet Operations processes the request file to generate a license. If the license request is for an existing device, FlexNet Operations generates a regenerative license. This means that each response contains the complete state of capabilities for the device and that calling the FlexNet Embedded library to process the response overwrites the existing state. Each capability response completely replaces the previous response.
If the request is made for a new device, FlexNet Operations enters the device into the system, adds the corresponding additional product, and generates a license for it.
Vendor Dictionary
The FlexNet Embedded capability request allows a device to send producer-specific information called a vendor dictionary. A vendor dictionary is a collection of name value parameters that are defined by the producer, such as GPS coordinates, time zone, and region. The vendor dictionary provides an interface for an implementer to send custom data in addition to the FlexNet Embedded-specific data from the device to server or vice versa. This data can be used in license-enabled code and the back office server to send information back and forth for any producer-defined purposes, as needed.
Rehosting a License
Rehosting licenses is defined as the process of transferring licenses from one device to another.
Note:The customer must remove a device’s licenses before they can be transferred to another device.
Generating a Trial License
A trial license enables a customer to demonstrate a product for trial purposes. The license expires after a short period of time.