FlexNet Embedded Licensing Key Concepts
FlexNet Embedded Licensing
Software on a device controls the product feature set expressed on that particular device. If the device has Internet connectivity, it can connect directly to FlexNet Operations and receive the license for its particular product feature set. A device can also be activated offline or using a FlexNet Embedded license server.
FlexNet Embedded license technology can also be integrated with a producer’s software to make it capable of enforcing perpetual, subscription, or demo software license models.
FlexNet Embedded licenses are of two types:
| • | An uncounted license allows a customer to deploy an unlimited number of licenses. |
| • | A counted license restricts deployment to a limited number of licenses. The count is specified during the entitlement process. |
Linking multiple license models to a single product is permitted. If multiple license models are linked to a product, it must be specified, when an entitlement line is created, which license model applies to the entitlement line. If only a single license model is linked to a product, then it is used by default.
FlexNet Embedded SDK
To use FlexNet Embedded, FlexNet Operations works in conjunction with the FlexNet Embedded SDK, a licensing library. Before you continue, ensure that you have access to the following:
| • | FlexNet Operations Producer Portal |
| • | FlexNet Embedded SDK |
Installing and Configuring the FlexNet Embedded SDK
Install and configure the FlexNet Embedded SDK as explained in your FlexNet Embedded documentation. Consult the user guide and getting started guide for your FlexNet Embedded SDK. For example, if you are using the FlexNet Embedded C SDK, consult the FlexNet Embedded C SDK Getting Started Guide and the FlexNet Embedded C SDK User Guide.
Building Product Binaries
Using the FlexNet Embedded SDK, your development team must create Flex-enabled product binaries that are able to take advantage of the FlexNet licensing technology. Some sample license-enabled code is included in your FlexNet Embedded SDK. Consult the user guide for your FlexNet Embedded SDK for details.
Configuring the Device Servlet
The device request servlet handles incoming binary HTTP requests (capability requests) from FlexNet Embedded devices. The servlet URL is http://<fnoServer>:<httpPort>/flexnet/deviceservices/. This URL must be accessible to networked devices to obtain their licenses from FlexNet Operations. Your development team must configure the connection method using the device servlet.
Using the Capability Request Command Line Utility
The caprequestutil capability request utility, located in <FlexNet_Embedded_install_dir>\bin\tools, enables you to manually generate a capability request and save it as a file or send it to a back office server. This utility is intended for quick testing involving capability requests. It is implemented using Java, and uses a text file as a substitute for trusted storage. This command line utility works for all platforms.
Embedded Activation
A FlexNet Embedded entitlement can be activated online or offline.
| • | Online activation – The Flex-enabled application generates a capability request for entitled features, then sends the request to FlexNet Operations via the Internet. FlexNet Operations sends a capability response to the device, which processes the response and places the license into trusted storage. |
| • | Offline activation – The Flex-enabled application generates a capability request file, which is manually transferred to a connected system from which it can be uploaded to FlexNet Operations. The capability response is downloaded from FlexNet Operations and transferred to the Flex-enabled application for processing. |
Embedded License Support
The license lifecycle extends beyond activation; support is also an important part of the lifecycle. Embedded licenses can easily be added, deleted, or re-allocated in response to customer demands, maintenance, or market conditions.