Main Menu
Home
Open a Ticket
My Ticket History
Browse Knowledgebase
My Account

Login
 E-mail:
 Password:
Register | Forgot Password?

Knowledgebase
Search by keywords:


Contact Us

We always recommend that you open a new ticket describing your problem and your environment. You will receive an automated reply with a request ID and shortly thereafter further communication from Open iT support.

You can also call the support hotline 1-866-OPEN-IT-S (+1-866-673-6487) or your local Open iT office during office hours for phone support.


Knowledgebase
Howto: Feature-Mapping

Article ID: 000007
Rating: 5.0 / 5.0 (1 votes)
Views: 3349

Problem:

It is sometimes useful to find concurrent usage across at set of
features.

I.e say you have feature FEAT_A, FEAT_B and FEAT_C. A user will
only use one of these, and licensing could be done based on a max
concurrent use of all these feature.

This article describes how to set up this in pre 5.0 installation. After
5.0

/opt/openit/bin/config_license_filters

can be used to turn on and off feature and product mapping.




Solution:

Mapping feature into "super features" is possible using the same
mechanism that is used for creating "super products"
(product-mapping). Here is a general description of how this mapping
can be added to any license data type:

Add new filters to filter sequence
----------------------------------

Add in feature duplication and calculation right after the
"CalcSum:product" filter in the sequence, i.e

Duplicate:features()=""
{
CalcSum:feature()=""
{

and also add closing bracket

}
}

in the appropriate place.

Add filter definitions
----------------------

Add the new filters in the "filter-defs"

Duplicate:features()=""
{
filter(String)="Duplicate"{}
limited()=""
{
map-file(FileName)="${OpeniT.directories.conf}feature-mapping"{}
source(String)="feature"{}
target(String)="feature"{}
}
}
CalcSum:feature()=""
{
filter(String)="CalcSum"{}
compare(String)="product,package,feature,feature_version"
{
field(String)="signals"{}
positive(Bool)="false"{}
pattern(String)="1"{}
}
remove(String)="feature"{}
summarize(String)="licenses"
{
field(String)="signals"{}
positive(Bool)="true"{}
pattern(String)="1"{}
}
}

Add filter map file
-------------------

Add mapping file

/var/opt/openit/etc/feature-mapping

with appropriate map. Syntax is identical to product mapping
file. In our example this could be

MAP: FEAT_COMBINED

FEAT_A
FEAT_B
FEAT_C

or if there are no other features for this product

MAP: FEAT_COMBINED

FEAT_*


Please note that any additions to the filter sequence will add extra
time during data processing. This is why feature mapping is not a
default part of the filtering sequence.

<< back

Rating
Did you find this article helpful?

Related Articles
Howto: Setup Oracle Space Data Collection without Running as SYS/SYSTEM User
Howto: Activate Logging (Windows)
Howto: Complete Input Logging for Licpoll
Howto: Processing of FLEXlm Debug Logs