Common Vendor Daemon Mapping

FlexNet Publisher provides a common vendor daemon option to software publishers who want to deploy a single vendor daemon that serves features previously served by other vendor daemons. This scenario typically applies to software publishers who have acquired or merged with other companies, where the individual companies have previously sold FlexEnabled applications with their own vendor daemons.

For example, ABCware merges with DEFware, and begins to deploy the new vendor daemon abcdef. When the abcdef vendor daemon registers with FlexNet Manager for Engineering Applications, it receives usage information only about features served by the abcdef vendor daemon. Data received about features served by previously deployed abcware and defware vendor daemons is disregarded. To ensure that FlexNet Manager for Engineering Applications receives all relevant data for the merged publisher’s features, you must map the secondary vendor daemon names (abcware and defware) to the primary vendor daemon name (abcdef).

Use of a common vendor daemon enables the publisher to use one vendor daemon to serve features with different vendor names. A common vendor daemon configuration contains:

One primary vendor daemon—This is the vendor daemon for the acquiring company.
One or more secondary vendor daemons—These are the vendor daemons that were deployed prior to the merger or acquisition.

To configure common vendor daemon mapping:

1. Stop the Admin server if it is running.
2. Open a Command Prompt window and change to the following directory—

<fnmea_admin_install_dir>/release/manager/webapps/flexnet/WEB-INF/classes

3. Open the file secondaryVendors.properties. (This is an empty file.)
4. Add the common vendor daemon mappings to the .properties file in the following manner:

secondaryVendorName1=primaryVendorName

secondaryVendorName2=primaryVendorName

In the case of the previous example, the .properties file would contain the following:

abcware=abcdef

defware=abcdef

5. At the command prompt, change to the <fnmea_admin_install_dir> directory, then type the following command:

flexnet site make

6. Restart the Admin server.

See Also