Skip to main content

ANSYS Elastic Vendor License Table Configuration

Introduction​

The elasticproducttable.map is used for ANSYS Elastic Unit calculation. This is for ANSYS Elastic Reporter (AER) only.

warning

Apply the configurations shown in the Open iT Core Server.

Configuring elasticproducttable.map​

  1. Open elasticproducttable.map in the Configuration directory, which is by default in C:\Program Files\OpeniT\Core\Configuration.

    Notice that it contains instructions on how to edit the file.

  2. Modify the mapping file.

    The mapping file has three sections:

    DEFAULT

    This section has three parts: Attributes, Rules, and General as shown below:

    Mapping Syntax
    DEFAULT
          @count=<count>
          @cost=<cost>
          @valid_from=<date>
          @expires=<date>
          rules:
             <method1> <details1>
             <method2> <details2>
             ...
             <methodN> <detailsN>
          general:
             <index_g1>=<value1>
             <index_g2>=<value2>
             ...
             <index_gN>=<valueN>

    • Attributes - are values defined by a keyword (attribute name), and each keyword is preceded by @.

      Attributes

      AttributeExampleDescription
      count@count=199Use this to specify the default maximum number of instances allowed for a group.
      cost@cost=36800Use this to specify the default cost for all groups. This could be overridden per group).
      valid_from@valid_from=2010-01-01Use this to specify the start date of the group validity. If no date is specified, it is valid from any date.
      expires@expires=2012-01-01Use this to specify the group's expiration date. If no date is specified, it does not expire.
      DEFAULT: Attributes

    • Rules - are only applied to the DEFAULT section. Rules are specified as methods with details attached.

      Rules

      MethodDetailsExampleDescription
      ignore<index> <operator> <value>ignore used_licenses < 1Use this to ignore records for which the Boolean test specified in the details fails (in the example, ignore any record without actual license use). Available operators are: <, <=, >, >=, == and !=.
      count<index>count used_licensesSince one group may include several instances of a single feature, you can use this to specify the record field that holds the feature count, this should always be the index used_licenses).
      key<index>key featuresUse this to specify the main key used to identify features and obtain which features are part of which sets (see feature=**%elements%** in the general assignments table).
      DEFAULT: Rules

      Note

      Key is only available in the DEFAULT section; it may not be specified for individual GROUPs.

    • General - is a set of value assignments (one per line) to a record field. The fields are indexed by name.

      Possible indexes are:

      General Assignments

      IndexDescription
      productVendor license name
      packageLicense package name
      featureLicense feature name
      feature_versionFeature version
      featuresetFeature set name
      featureset_versionFeature set version
      licensesMaximum available licenses
      used_licensesLicenses in use
      queued_licensesLicenses queued for use
      userUser name
      displayDisplay/tty
      hostName of host where license is used
      startRecord start time (not necessarily license start time)
      durationRecord duration (not necessarily license duration)
      var0-var9Internal (free) variables
      General Assignment's Possible Indexes

      The values may be fixed or variable. Variables are used by enclosing the variable name in "%". Possible variables are:

      Values

      NameExampleDescription
      countused_licenses=%count%Use this to specify the number of instances of the group in the current constellation.
      totalcountlicenses=%totalcount%Use this to specify the count value for each group (i.e., maximum possible group instances).
      costvar1=%cost%Use this to specify the cost value for each group.
      elementsvar2=%elements%The elements value contains a comma separated list of feature names that belong to the featureset (provided the key rule is set to feature)
      General Assignment Value's Possible Variables

      note

      The count and total count should be defined as in the above examples in the DEFAULT section. The cost is usually less interesting (and is currently not part of any filter sequences).

    GROUPS

    This section defines various groups, each consisting of a set of features forming a featureset. These are organized as follows:

    Note

    Rules may be applicable to GROUPS, but at present, there is no requirement for that.

    Mapping Syntax
    GROUP <name1>
          @count=<count>
          @cost=<cost>
          @valid_from=<date>
          @expires=<date>
          general:
             <index_g1>=<value1>
             <index_g2>=<value2>
             ...
             <index_gN>=<valueN>
          elements:
             <index_m1.1>=<value1.1> ... <index_m1.N>=<value1.N>
             <index_m2.1>=<value2.1> ... <index_m2.N>=<value2.N>
             ...
             <index_m3.1>=<value3.1> ... <index_m3.N>=<value3.N>

       GROUP <name2>
          ...

    The attributes are the same as described in the DEFAULT group. Then, there is a set of assignments under ‘general’, which is a value to a record field.

    Elements : This is a list of record indices (see “General assignments”) where the value must match the given, in order to be eligible for the group. (Values containing spaces and/or tabs must be enclosed in double quotes.)

    Each line defines a unique value set where all values must match. If a record matches any line, then it is eligible.

    Example
    elements:
          feature="Concentric Circles" feature_version=3.14
          feature=Squares
          product=Geometry

    If a record's feature name equals "Concentric Circles" and its version is 3.14, or its feature name is "Squares", or its product name is "Geometry", then it is eligible for this group.

    UNMAPPED

    As said earlier, any feature eligible for a featureset, but was not actually assigned to a set, will be assigned to the UNMAPPED set. This is the syntax and a simple example:

    Mapping Syntax
    UNMAPPED
      general:
             <index_g1>=<value1>
             <index_g2>=<value2>
             ...
             <index_gN>=<valueN>
    UNMAPPED
          general:
             featureset=unmapped
             used_licenses=1
             licenses=1

    Empty lines are allowed — any line beginning with # as the first non-white character is considered a comment.

    Example
    DEFAULT
            rules:
                    ignore used_licenses < 1
                    count used_licenses
                    key feature
            general:
                    used_licenses=%count%
                    licenses=%min_of_licenses%
                    ppu_licenses=%min_ppu%
                    feature_version=all
                    var4=%cost%

    GROUP "1"
    	@count=99999
    	@cost=5.0
    	general:
    		featureset="ANSYS 2D Extractor (includes Electronics Desktop Core)"
    	elements:
    		feature="si2d_solve"
    		feature="si2d_gui"
    		feature="electronics2d_gui"

  3. Save the changes.

This mapping may affect the following data types:

Next Steps?​

Proceed with data regeneration after configuring all the necessary mapping files to apply the changes in the real-time and historical reports.

For real-time reports:

Generating License Status Data

For historical reports:

Data Generation