# Configuring ANSYS Elastic Product Table

# Introduction

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

Apply the configurations shown in the Open iT server.

# Configuring `elasticproducttable.map`

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.

Modify the mapping file.

The mapping file has three sections:

DEFAULT

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

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

Attribute	Example	Description
count	`@count=199`	Default maximum number of instances allowed for a group
cost	`@cost=36800`	Default cost for all groups (could be overrode per group)
valid_from	`@valid_from=2010-01-01`	This group cannot be used before this date (if not specified, then valid from any date)
expires	`@expires=2012-01-01`	This group cannot be used on or after this date (if not specified, then no expiration)

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

Rules

Method	Details	Example	Description
ignore	<index> <operator> <value>	`ignore used_licenses < 1`	Used 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_licenses`	Since one group may include several instances of a single feature, count is used to specify the record field that holds the feature count (this should always be the index used_licenses)
key	<index>	`key features`	Use this to specify the main key used to identify features and obtain which features are part of which sets (see `feature`=`%elements%` in general assignments below)

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

General - This is a set of assignments (one per line) of a value to a record field. The fields are indexed by name, and the following are some possible indexes:

General Assignments

Index	Description
product	License product name
package	License package name
feature	License feature name
feature_version	Feature version
featureset	Feature set name
featureset_version	Feature set version
licenses	Maximum available licenses
used_licenses	Licenses in use
queued_licenses	Licenses queued for use
user	User name
display	Display/tty
host	Name of host where license is used
start	Record start time (not necessarily license start time)
duration	Record duration (not necessarily license duration)
var0-var9	Internal (free) variables

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

Values

Name	Example	Description
count	`used_licenses=%count%`	Number of instances of the group in the current constellation
totalcount	`licenses=%totalcount%`	The count value defined for each group (i.e. maximum possible group instances)
cost	`var1=%cost%`	The cost value defined for each group
elements	`var2=%elements%`	The elements value contains a comma separated list of feature names (provided the key rule is set to feature)

Note that 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, with each group consisting of a set of features forming a featureset. These are organized as follows:

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

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 are basically 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:

UNMAPPED
  general:
         <index_g1>=<value1>
         <index_g2>=<value2>
         ...
         <index_gN>=<valueN>

Example
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"

Save the changes.

Open elasticproducttable.map in the etc directory, which is by default in /var/opt/openit/etc.

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