# CodeMeter License Manager

# Introduction

Open iT supports CodeMeter usage reporting. If you have dongle license data, you only need to activate the CodeMeter dongle data collection and this will produce the following aggregated data types used for historical reporting:

• (117) Dongle Data Inventory
  
• (119) Dongle License Use

On the other hand, the following sections will guide you on the required configuration for license manager utility polling, log file parsing, and poll parsing.

# Configuring License Manager Utility Polling

Open iT supports CodeMeter usage reporting through the generic license type format. This will produce the following aggregated data types used for historical and real-time reporting:

• (49) Host User License Use
  
• (93) OLAP Raw Hourly
  
• (94) OLAP User Concurrency
  
• (95) Usergroup License Use v3.0
  
• (102) OLAP Total Use
  

The following sections will guide you in setting up the necessary configuration to collect and send the required data to the server.

# Requirements

• An Open iT Client connected to an Open iT Server or a coexistent Open iT setup
• Activated LicenseAnalyzer collection and license poller
• License server administrative rights
• Configured CodeMeter license server
• Valid URL with port number of CodeMeter WebAdmin page

# Configuring Data Collection

These are the required steps to activate and configure collection of CodeMeter usage data.

1. Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and back up the licpoll.xml configuration file.

2. Open a command prompt with Administrator level privileges.

3. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

   Command Syntax

    cd $BIN_DIR

   Example

    cd C:\Program Files\OpeniT\Core\bin

4. Once in the directory, copy the object node genericlicense-sample, run the command:

   Command Syntax

    openit_confinit -c "licpoll.license-types.genericlicense-sample=>licpoll.license-types.codemeter"

5. Activate the collection of CodeMeter data, run the command:

   Command Syntax

    openit_confinit -c "licpoll.license-types.codemeter.active=true"

6. Set the arguments to the status command, run the command:

   Command Syntax

    openit_confinit -c "licpoll.license-types.codemeter.status-command.arguments=CodeMeter <api_url>"

   where <api_url> is the corresponding valid URL with the port number of the CodeMeter WebAdmin page.

   Example

    openit_confinit -c "licpoll.license-types.codemeter.status-command.arguments=CodeMeter http://localhost:22352"

7. Update the configuration file, run the command:

   Command Syntax

    openit_confbuilder --client

   Make sure that there are no errors encountered.

Refer to the CodeMeter Data Collection Configuration table to learn more about CodeMeter configuration in licpoll.xml.

Object Name	Accepted Value	Description
active	Boolean (true or false)	Setting this to true activates CodeMeter usage data collection.
type	String (e.g., GenericLicense)	The license manager type.
interval	Timespan (e.g., P30S, P5M, P1H)	The span of time between each polling round (it is recommended to set a value no less than P1M).
offset	Timespan (e.g., P30S, P5M, P1H)	The span of time the aligned poll time decided by interval is shifted.
product-name	String (e.g., server;daemon)	This object is defined if a product name other than the default GenericLicense=%hosttype% will be used.
license-server	String (e.g., hou105win)	The License Server name.
status-command	FileName (i.e., ${OpeniT.directories.bin}/genlicutil)	The binary used to obtain status from the license manager.
status-command.arguments	String (e.g., CodeMeter http://localhost:22352)	The arguments used for the status command. Use the format CodeMeter <api_url>.

CodeMeter Data Collection Configuration

# Verifying Data Collection

After configuration, you can verify that the data is collected by following these steps:

1. Open a command prompt with Administrator level privileges.

2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

   Command Syntax

    cd $BIN_DIR

   Example

    cd C:\Program Files\OpeniT\Core\bin

3. Run the command:

   Command Syntax

    openit_licpoll -# 1

4. Verify that the temp directory, which is by default in C:\ProgramData\OpeniT\Data\temp, contains a LicPoll directory containing .data and status-*.log files.

# Configuring Log File Parsing

Open iT collects log files and converts them to Open iT format. This will produce the following aggregated data types used for historical and real-time reporting:

• (104) License Logfile Events v2.0
  
• (107) Denied License Use Licenseevents

# Requirements

• An Open iT Client connected to an Open iT Server or a coexistent Open iT setup
• License server administrative rights
• Full path to the debug log file

# Configuring Log File Collection

These are the required steps to configure collection of CodeMeter log files.

1. Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and open logfilecollector-codemeter.xml.

2. Locate object node dir and set its value to the location of the CodeMeter log files.

   logfilecollector-codemeter.xml

    14|	<Object>
    15|		<Name>dir</Name>
    16|		<Description>Directory containing the log files</Description>
    17|		<Value type="DirName">%CODEMETERLOGDIR%</Value>
    18|	</Object>

   Example: logfilecollector-codemeter.xml

    14|	<Object>
    15|		<Name>dir</Name>
    16|		<Description>Directory containing the log files</Description>
    17|		<Value type="DirName">C:\Users\user1\CodeMeter\home\logs</Value>
    18|	</Object>

3. Save the changes.

4. Open a command prompt with Administrator level privileges.

5. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

   Command Syntax

    cd $BIN_DIR

   Example

    cd C:\Program Files\OpeniT\Core\bin

6. Update the configuration file, run the command:

   Command Syntax

    openit_confbuilder --client

   Make sure that there are no errors encountered.

Refer to the CodeMeter Log File Collection Configuration table to learn more about CodeMeter configuration in logfilecollector-hasp2.xml.

Object Name	Accepted Value	Description
source.dir	DirName (e.g., C:\Users\user1\CodeMeter\home\logs)	Location of the CodeMeter log files.
source.pattern	String (i.e., *.log)	The glob pattern identifying source files in the source directory.
source.seen	String (collect, ignore, or tail)	Seen files are source files collected from before. Specify collect to collect from the start every time, specify ignore to never collect from the same file again, or specify tail to continue collection from the end of the file last time (i.e., collect the ones added since last time).
source.cmplines	Integer (e.g., 6, 10, 20)	This is required if the value of source.seen is tail. This is the number of lines compared to source files collected before to determine where to start the collection. Note: If this number is too low, you can end up with an incorrect position, and duplicate data may be in the log files. Usually, it is better to have a few lines more than strictly necessary than even a single line too little.
target.dir	DirName (i.e., ${OpeniT.directories.temp}/LogFileCollector)	This is the location of the directory containing the collected log data.
target.module	String (i.e., license)	The target type of module (in general).
target.datatype	String (i.e., haspevents2)	The specific type of target data.
target.interval	Timespan (e.g., P30S, P5M, P1D)	The span of time between collector runs.
target.rotation-size	Integer (e.g., 6, 10, 20)	The log file rotates if it goes beyond the number (in mb) defined.
target.rotation-glob	String (e.g., *)	The glob pattern to match before the log file rotates.

CodeMeter Log File Collection Configuration

1. Go to the Components directory, which is by default in /var/opt/openit/etc/Components, and open logfilecollector-codemeter.xml.

2. Locate object node dir and set its value to the location of the CodeMeter log files.

   logfilecollector-codemeter.xml

    14|	<Object>
    15|		<Name>dir</Name>
    16|		<Description>Directory containing the log files</Description>
    17|		<Value type="DirName">%CODEMETERLOGDIR%</Value>
    18|	</Object>

   Example: logfilecollector-codemeter.xml

    14|	<Object>
    15|		<Name>dir</Name>
    16|		<Description>Directory containing the log files</Description>
    17|		<Value type="DirName">/root/user1/CodeMeter/home/logs</Value>
    18|	</Object>

3. Save the changes.

4. Go to the bin directory, which is by default in /opt/openit/bin, run the command:

   Command Syntax

    cd $BIN_DIR

   Example

    cd /opt/openit/bin

5. Update the configuration file, run the command:

   Command Syntax

    ./openit_confbuilder --client

   Make sure that there are no errors encountered.

Refer to the CodeMeter Log File Collection Configuration table to learn more about CodeMeter configuration in logfilecollector-codemeter.xml.

Object Name	Accepted Value	Description
source.dir	DirName (e.g., /root/user1/CodeMeter/home/logs)	Location of the CodeMeter log files.
source.pattern	String (i.e., *.log)	The glob pattern identifying source files in the source directory.
source.seen	String (collect, ignore, or tail)	Seen files are source files collected from before. Specify collect to collect from the start every time, specify ignore to never collect from the same file again, or specify tail to continue collection from the end of the file last time (i.e., collect the ones added since last time).
source.cmplines	Integer (e.g., 6, 10, 20)	This is required if the value of source.seen is tail. This is the number of lines compared to source files collected before to determine where to start the collection. Note: If this number is too low, you can end up with an incorrect position, and duplicate data may be in the log files. Usually, it is better to have a few lines more than strictly necessary than even a single line too little.
target.dir	DirName (i.e., ${OpeniT.directories.temp}/LogFileCollector)	This is the directory location containing the collected log data.
target.module	String (i.e., license)	The target type of module (in general).
target.datatype	String (i.e., codemeter)	The specific type of target data.
target.interval	Timespan (e.g., P30S, P5M, P1D)	The span of time between collector runs.
target.rotation-size	Integer (e.g., 6, 10, 20)	The log file rotates if it goes beyond the number (in mb) defined.
target.rotation-glob	String (e.g., *)	The glob pattern to match before the log file rotates.

CodeMeter Log File Collection Configuration

# Activating Log Data Collection

These are the required steps to activate collection of CodeMeter log data.

1. Go to the scheduler directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\scheduler, and open collect_license_codemeter-logs.oconf.

2. Locate and set root.scheduler.jobs.collect_codemeter_licenselogs.general.active to true to activate the collection of CodeMeter event log data.

   collect_license_codemeter-logs.oconf

    13|	}
    14|		general
    15|		{
    16|			active
    17|			{
    18|				type=bool
    19|				value=true

3. Save the changes.

The collection runs hourly using a 5-minute sample interval by default. The primary data is then transferred to the server every night according to the client timezone for processing. To configure the intervals, locate the instances attribute under collect_codemeter_licenselogs, preprocess_codemeter_licenselogs-events, or transfer_codemeter_licenselogs in the same file and configure the attributes.

Refer to the CodeMeter Log Job Scheduler Instances Configuration table to learn the attributes used to configure CodeMeter data collection and transfer.

Attribute Name	Accepted Value	Description
max-instances	Uint (e.g., 5, 8, 9)	The number of instances allowed to run at the same time.
max-handling	String (end-oldest, end-all-old, or end-new)	The action done upon reaching the maximum number of instances. Specify end-oldest to stop/kill the oldest instance and then start the new, specify end-all-old to stop/kill all running instances and then start the new, or specify end-new to not start the new instance.
end-timeout	Timespan (e.g., P30S, P5M, P1H)	The maximum waiting time before terminating a running instance.
quarantine	Timespan (e.g., P30S, P5M, P1H)	The waiting time before starting a new instance after a previous one.

CodeMeter Log Job Scheduler Instances Configuration

1. Go to the scheduler directory, which is by default in /var/opt/openit/etc/scheduler, and open collect_license_codemeter-logs.oconf.

2. Locate and set root.scheduler.jobs.collect_codemeter_licenselogs.general.active to true to activate the collection of CodeMeter log data.

   collect_license_codemeter-logs.oconf

    13|	}
    14|		general
    15|		{
    16|			active
    17|			{
    18|				type=bool
    19|				value=true

3. Save the changes.

The collection runs hourly using a 5-minute sample interval by default. The primary data is then transferred to the server every night according to the client timezone for processing. To configure the intervals, locate the instances attribute under collect_codemeter_licenselogs, preprocess_codemeter_licenselogs-events, or transfer_codemeter_licenselogs in the same file and configure the attributes.

Refer to the CodeMeter Log Job Scheduler Instances Configuration table to learn the attributes used to configure CodeMeter data collection and transfer.

Attribute Name	Accepted Value	Description
max-instances	Uint (e.g., 5, 8, 9)	The number of instances allowed to run at the same time.
max-handling	String (end-oldest, end-all-old, or end-new)	The action done upon reaching the maximum number of instances. Specify end-oldest to stop/kill the oldest instance and then start the new, specify end-all-old to stop/kill all running instances and then start the new, or specify end-new to not start the new instance.
end-timeout	Timespan (e.g., P30S, P5M, P1H)	The maximum waiting time before terminating a running instance.
quarantine	Timespan (e.g., P30S, P5M, P1H)	The waiting time before starting a new instance after a previous one.

CodeMeter Log Job Scheduler Instances Configuration

# Verifying Log Data Collection

After configuration, you can verify that the data is collected and sent to the server by following these steps:

1. Open a command prompt with Administrator level privileges.

2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

   Command Syntax

    cd $BIN_DIR

   Example

    cd C:\Program Files\OpeniT\Core\bin

3. Run the command:

   Command Syntax

    openit_executor -r collect_license_codemeter-logs

4. Verify that there are archiver*.in files created in the server in the archiver directory, which is by default in C:\ProgramData\OpeniT\Data\incoming\archiver.

1. Go to the bin directory, which is by default in /opt/openit/bin, run the command:

   Command Syntax

    cd $BIN_DIR

   Example

    cd /opt/openit/bin

2. Run the command:

   Command Syntax

    ./openit_executor -r collect_license_codemeter-logs

3. Verify that there are archiver*.in files created in the incoming directory in your defined data_dir ($ROOT_DATA_DIR) upon Open iT server installation.

# Configuring Poll Parsing

Open iT collects license usage data by polling through another utility from the license server. This will produce the following aggregated data types used for historical and real-time reporting:

• (117) Dongle Data Inventory
  
• (119) Dongle License Use
  

# Requirements

• An Open iT Client connected to an Open iT Server or a coexistent Open iT setup

# Configuring Data Collection

These are the required steps to activate and configure collection of CodeMeter data.

1. Go to the scheduler directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\scheduler, and open collect_license_codemeter-polls.oconf.
2. Locate and set root.scheduler.jobs.collect_codemeter_licensedongle.general.active to true to activate the collection of CodeMeter data.
   collect_license_codemeter-polls.oconf

    13|	general
    14|	{
    15|		active
    16|		{
    17|			type=bool
    18|			value=true
    19|		}

3. Save the changes.

The collection runs hourly using a 5-minute sample interval by default. The primary data is then transferred to the server every night according to the client timezone for processing. To configure the intervals, locate the instances attribute under collect_codemeter_licensedongle or transfer_codemeter_licensedongle in the same file and configure the attributes.

Refer to the CodeMeter Poll Job Scheduler Instances Configuration table to learn the attributes used to configure CodeMeter data collection and transfer.

Attribute Name	Accepted Value	Description
max-instances	Uint (e.g., 5, 8, 9)	The number of instances allowed to run at the same time.
max-handling	String (end-oldest, end-all-old, or end-new)	The action done upon reaching the maximum number of instances. Specify end-oldest to stop/kill the oldest instance and then start the new, specify end-all-old to stop/kill all running instances and then start the new, or specify end-new to not start the new instance.
end-timeout	Timespan (e.g., P30S, P5M, P1H)	The maximum waiting time before terminating a running instance.
quarantine	Timespan (e.g., P30S, P5M, P1H)	The waiting time before starting a new instance after a previous one.

CodeMeter Poll Job Scheduler Instances Configuration

# Verifying Data Collection

After configuration, you can verify that the data is collected and sent to the server by following these steps:

1. Open a command prompt with Administrator level privileges.

2. Go to the bin directory, which is by default in C:\Program Files\OpeniT\Core\bin, run the command:

   Command Syntax

    cd $BIN_DIR

   Example

    cd C:\Program Files\OpeniT\Core\bin

3. Run the command:

   Command Syntax

    openit_executor -r collect_license_codemeter-polls

4. Verify that there are archiver*.in files created in the server in the archiver directory, which is by default in C:\ProgramData\OpeniT\Data\incoming\archiver.

# Next steps?

   Renaming Vendor License    Renaming Features    Create and Add Report    License Monitor