Summary

This article outlines the steps required to build and import a Vendor Certificate Generator (VCG) into FlexNet Operations On-Premises.

Procedure

Preparing and Building the VCG

1. Prepare the VCG SDK
   1. Download the VCG Toolkit from the Product and License Center (in the Product List, click FlexNet Operations and select the desired version).
   2. Extract the contents into your designated working directory.
2. Configure the VCG Source Files
   1. Open machind\vcg_code.h.
   2. Enter your vendor daemon name and security seeds. These values can be found in machind\lm_code.h from your FLEXlm/FLEXnet Licensing installation.
   3. Save the file.
3. Update the Makefile
   1. Navigate to the platform-specific directory that has been created.
   2. Edit vcg.mak:
      • Replace VENDOR = demo with VENDOR = <your_vendor_daemon_name> (must match the name used in vcg_code.h).
4. Handle Seed Values for Version 11.5 and Later
   • Copy lmprikey.h from the Publisher Toolkit’s platform directory to the VCG platform directory.
   • Note: Earlier versions used LM_SEED values directly in vcg_code.h, but from 11.5 onwards, only lmprikey.h is used.
5. Build the VCG
   • Use your standard compiler to build:
     >nmake vcg.mak

After successfully building the VCG, you can proceed to import it into the GTlicensing or Operations system.

Importing the VCG into FlexNet Operations On Premises

For GTlicensing and Operations v6

1. Launch the GT/Operations interface.
2. Open to the Products tab.
3. From the top menu, select Products > Import > VCG.
4. In the dialog box, locate and select your compiled VCG file.
5. Click OK to complete the import.

For Operations v7 and Later

1. Copy the VCG file that you created to:
   <Install_dir>/custom/platform/bin
2. Run:
   flexnet site make
3. Start the system.
4. Navigate to Administer Operations > System Configuration.
5. On the left panel, select FLEXnet Licensing.
6. Enter your vendor daemon name in the VCG Configuration Name field.

Additional Notes for Building the V11.5 VCG

• Ensure lmprikey.h is copied to the machind directory.
• Edit both vcg_code.h and vcg.mak as described above.
• Follow the import steps relevant to your Operations version.