Flexnet License Generator

Overview

This document describes how to maintain the DDC-I FLEXnet License Generator.

The process for updating and/or building the License Generator requires the following steps

1. Use SVN to checkout the license generator source code
2. Make appropriate source code updates
3. Build the License Generator
4. Run the License Generator
5. Deploy the License Generator

We are currently using two versions of FLEXnet - 11.19.2 && 10.8.0.7 These are both checked in to CVS, but are currently checked out here:

\\ddsbuild\c$\FLEXnet_11.19.2 \\ddsbuild\c$\FLEXnet_10.8.0.7

Checkout the Source Code

1. Get the project onto your filesystem with "svn checkout"
   1. Choose where you want a copy of the project to go on your filesystem.
   2. "cd" into the directory just above where you want it to go.
   3. Make sure the folder you want it to end up in (typically called "LicenseGenerator") does NOT exist.
   4. Enter the following on the command line:
      • svn checkout https://deos.ddci.com/svn/DDCI/products/license-generator/branches/mainline LicenseGenerator
      • You can replace LicenseGenerator with any folder name you want.
      • The folder you created will contain all of the source code for the License Generator. Before you can run the License Generator, you have to build it (see below).
2. Updating your copy of the project to the latest version with "svn update":
   1. "cd" into the project directory.
   2. Enter this command:
      • svn update
   3. If all goes well, you should see "At revision ###" or "Updated to
      • revision ###" where the "###" is the version number.
3. Committing changes to the master repository with "svn commit":
   1. "cd" into the project directory.
   2. Enter this command:
      • svn status
      • - If you get no output, it means you don't have anything to commit.
      • - If you get some lines that start with '?', it means there are new files that may or may not belong in the master repository. If they don't belong in the master repository, either delete them or ignore them from here on. If they do belong, use the following command to mark them for inclusion:
      • svn add <path-to-file-or-folder>
      • - If you get some lins that start with 'M' or 'A', it means that these changes ('M' for modify, 'A' for add) are ready to be committed to the master repository.
   3. Once you know what changes will be committed, run the following command:
      • svn commit -m "PCR ### <description>"
      • Where "###" is the PCR number you're working on, and <description> is a description of the changes. This description shows up in bugzilla as a comment for the PCR you specify.

• TIP: see also `svn help` for convenience aliases to the above svn commands.

Updating Source Code

• Feature Set Updates
  • edit the file "features.properties". The syntax of each feature is:
    • <product>_<target>[_<moreInformation>]=<featureId>

   examples:
   DEOS_PPC=PC_WNT_DEOS_RTOS_PPC
   SCORE_1750A_CPP=PC_WNT_SCORE_CPP_1750A
 <product>:
   the product name. NOTE: this name appears in comments in the generated
   license for the user to see. example: "##DEOS###..."
 <target>:
   the target. All features of a particular target are given the same number
   of seats. If target is not relevant for a feature, convention is to say the
   target is "COMMON".
 [_<moreInformation>]:
   optional more specific qualifier(s). If a product has multiple features for
   a target (most do), then give more information after an "_". Any number of
   underscores are allowed; they are seperators for organizing features into
   the tree structure you see when running the license generator.
 <featureId>:
   This is the feature id that gets used in the generated license.
 NOTE:
   product and target names are case sensitive. Convention is to use all caps
   for everything to the left of the "=".

• Default Version Number Update
  • edit the file "versions.properties". The syntax of each line is:
    • <product>=<version>

 example:
   DEOS=1.13
 <product>:
   product name. Should match a product name from "features.properties".
 <version>:
   the version. When you include a feature in a license, this is the value
   that goes into the version textbox initially for the product.

Build the License Generator

1. Make sure the contents of the file "version.txt" contains the correct version number. Do not put any whitespace into the file, not even a newline at the end.
2. In Windows, use a desk maintainer environment.
3. run make. The build will be "LicenseGenerator_<version>". No installation necessary; just copy the folder and run it.

Run the License Generator

• Run "runme.bat".

1. if it doesn't work, make sure the LicenseGenerator is on a drive with a letter. If the path to the license generator starts with "\\" instead of a letter and a colon, then you need to map a network drive.
   1. Copy the path to the license generator and open explorer (a file browser).
   2. Tools -> Map Network Dirve...
   3. Choose your favorite letter from the "Drive" dropdown.
   4. Paste the path to the license generator into the "Folder" box. It should start with a "\\"
   5. Click "Finish".
   6. Now go to My Computer and look in the drive you just created. Try running the license generator again.
2. if it still doesn't work, see if a folder called "bin" exists next to "runme.bat". If it does not, then you're looking at an unbuilt checkout from svn. build the license generator and run the build.
3. if it still doesn't work, then seek help from a human such as:
   1. jsw
   2. lcj
   3. bh

Deploy the License Generator

1. Copy the new License Generator folder to \\nx3000\utils\flexnet
2. Update the LicenseGeneratorCurrent directory to contain the new license generator content.