Vendor Dictionary Data

Many of the following use cases use vendor dictionary data to define conditions for license allocation.

The vendor dictionary to send custom data in a capability request (in addition to the FlexNet Embedded–specific data) to the license server and vice-versa. Basically, the vendor dictionary provides a means to send information back and forth between the client and server for any producer-defined purposes, as needed; FlexNet Embedded does not interpret this data.

A common theme across the use cases in this appendix is that feature counts are shared between business units called Sales and Engineering. These business units would be identified by "business-unit" : ["engineering", "sales" ] entries in the vendor dictionary.

Tip:For an example that demonstrates a vendor dictionary condition that uses an array, see Use Case: Making Feature Counts Available to Multiple Business Units.