Adding Features to Products
A feature is a discrete, separately licensed unit of functionality. A single feature can be a part of multiple products. FlexNet Manager for Engineering Applications tracks usage by feature. To enable usage reporting by product (which are composed of one or more features), you must associate licensed features with products.
You can also use the Assign Features page to assign unassigned features to products.
To associate features with products:
1. | From the Planner tab, under Products, click Products. |
2. | On the Products page, click the name of the product to which you want to add features. |
3. | On the bottom half of the View Product page, click the Features tab, then click Add Product Feature. |
4. | On the Add Product Feature page, specify the feature settings. Required settings are identified by a red asterisk (*) |
Setting |
Description |
Vendor Daemon |
Select the vendor daemon that serves the feature. The list contains all vendor daemons that are assigned to the software producer that makes this product. When you select a vendor daemon, the Feature Name list is populated with all of the features that are associated with the selected vendor daemon. If the list is empty, type the name of the vendor daemon name in the text field. Also, specify whether the vendor daemon serves features that use FlexNet or IBM LUM licensing. |
Feature Name |
Select the feature that you want to assign or map to this product. If the list is empty, you can specify a feature name in the text field. If you manually enter a feature name, the feature will be associated with the vendor daemon that is selected in the Vendor Daemon list. |
Minimum Feature Version |
Minimum feature version that is required for the product. This field accepts a string. This value can be used by the product usage aggregation process to fine-tune the association of feature usage to product usage. Some FlexEnabled (FlexNet-licensed) products specify a minimum version for the feature that is required to satisfy a checkout request. For example, the aggregation process may need to determine whether a checkout of version 1.0 should be included for a particular product. If the product definition requires that the minimum feature version is 2.0, then the version 1.0 checkout will not be grouped as usage for the product. |
Feature Licenses Per Product License |
Number of feature licenses, expressed as an integer, that are included in a single product license for the product. |
5. | Click Save. |
See Also