Skip to main content
Version: 10.2

CodeMeter License Manager

Introduction​

Open iT supports CodeMeter usage reporting via the following:

The following sections will guide you on the required configuration.

Dongle License Data Collection​

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:

note

Continue reading if you need to configure license manager utility polling or log file parsing. If not, here are some suggested readings.

Configuring License Manager Utility Polling​

Open iT polls the license servers at regular intervals to get the current status of its license use and availability.

For this collection, the data source is through an API. The data collector/preprocessor initiates the license status utility every hour using a 5-minute sample interval, triggering the data collection process. The license status utility requests the current license usage data from the license manager portal. After the license manager portal provides the requested data, the license status utility passes this information to the data collector/preprocessor. The data collector/preprocessor processes the data, preparing it for transmission. Finally, the preprocessed data is sent to the Core Server every night, according to the client's timezone, for further storage, completing the license usage data collection and processing.

License Manager Utility Polling Workflow through API

License Manager Utility Polling Workflow through API

This will produce the following aggregated data types used for historical reporting:

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

warning

Apply the configurations shown in the Open iT Core Client.

Requirements​

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 and rename it to your desired name. In this example, we will use codemeter. Run the command:

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

    Element names cannot contain parentheses ( or ) because they are not valid for XML element names.

  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 no errors are encountered.

Advanced Configuration

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

Object NameAccepted ValueDescription
activeBoolean (true or false)Setting this to true activates CodeMeter usage data collection.
typeString (e.g., GenericLicense)The license manager type.
intervalTimespan (e.g., P30S, P5M, P1H)The span of time between each polling round (it is recommended to set a value no less than P1M).
offsetTimespan (e.g., P30S, P5M, P1H)The span of time the aligned poll time decided by interval is shifted.
product-nameString (e.g., server;daemon)This object is defined if a vendor license name other than the default GenericLicense=%hosttype% will be used.
license-serverString (e.g., desktop123win)The license server name.
status-commandFileName (i.e., ${OpeniT .directories.bin}/ genlicutil)The binary used to obtain status from the license manager.
status-command.argumentsString (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.

note

Continue reading if you need to configure log file parsing. If not, here are some suggested readings.

Configuring Log File Parsing​

Open iT collects log files and converts them to Open iT format.

An Open iT Core Client is installed on your license server for this collection. The data collector monitors and gathers the license usage history logs from the license manager every midnight. Once the logs are collected, the data collection process triggers and the logs are passed to the data preprocessor. After the data is preprocessed, it is transferred to the Core Server for further storage, completing the history logs collection and processing.

Log File Parsing Workflow

Log File Parsing Workflow

This will produce the following aggregated data types used for historical reporting:

warning

Apply the configurations shown in the Open iT Core Client.

Requirements​

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

There are two methods for configuring log file collection:

Configuring Log File Parsing from a Single Directory​

Configuring Log File Collection​

These are the required steps to configure collection of CodeMeter log files from a single directory.

  1. Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and back up the logfilecollector-codemeter.xml 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, set the location of the CodeMeter log files, run the command:

    Command Syntax
    openit_confinit -c "logfilecollector-codemeter.logfilecollector.source.dir=<codemeter_log_dir>"

    where <codemeter_log_dir> is the location of the CodeMeter log files.

    Example
    openit_confinit -c "logfilecollector-codemeter.logfilecollector.source.dir=C:\Users\user1\CodeMeter\home\logs"
    Sample Log File Content
    2017-01-29T17:19:41 SignedLogfile FirmCode:5111696, PublicKey:b9019cb8ab0979f67c04f9cde93d3db754ad78769752b246107f0be4000000007195814def55d5fb7ebf17eb060100076c6a6f7829635fcd3e19342500000000, Runtime-Version:5.22.1514.502, LogfileId:8
    2017-01-29T17:19:41 Admin Server:"samplehost144.company.net" CodeMeter_started 2017-01-29T17:19:02
    2017-01-29T17:19:41 ListOfLicenses
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-16, SN:128-6129194, FC:5111696, PC:1, FM:1, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-17, SN:128-6129194, FC:5111696, PC:100, FM:7, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-18, SN:128-6129194, FC:5111696, PC:101, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-19, SN:128-6129194, FC:5111696, PC:102, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-20, SN:128-6129194, FC:5111696, PC:103, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-21, SN:128-6129194, FC:5111696, PC:104, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-22, SN:128-6129194, FC:5111696, PC:105, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-23, SN:128-6129194, FC:5111696, PC:106, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-24, SN:128-6129194, FC:5111696, PC:107, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521496-5111696-16, SN:128-6129196, FC:5111696, PC:1, FM:1, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521496-5111696-17, SN:128-6129196, FC:5111696, PC:100, FM:7, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521496-5111696-18, SN:128-6129196, FC:5111696, PC:101, FM:0, ET:never, LQ:1, PT:""

  5. Update the configuration file, run the command:

    Command Syntax
    openit_confbuilder --client

    Make sure no errors are encountered.

Advanced Configuration

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

Object NameAccepted ValueDescription
source.dirDirName (e.g., C:\Users\user1\CodeMeter\home\logs)Location of the CodeMeter log files.
source.patternString (i.e., *.log)The glob pattern identifying source files in the source directory.
source.seenString (collect, ignore, or tail)Seen files are the previously collected source files.
  • collect - Specify this option to collect from the start each time.
  • ignore - Specify this option to skip collecting from the same file again.
  • tail - Specify this option to continue collection from the end of the file last time (i.e., collect the ones added since last time).
source.cmplinesInteger (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.dirDirName (i.e., ${OpeniT .directories.temp}/ LogFileCollector)This is the location of the directory containing the collected log data.
target.moduleString (i.e., license)The target type of module (in general).
target.datatypeString (i.e., codemtr)The specific type of target data.
target.intervalTimespan (e.g., P30S, P5M, P1D)The span of time between collector runs.
target.rotation-sizeInteger (e.g., 6, 10, 20)The log file rotates if it goes beyond the number (in mb) defined.
target.rotation-globString (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. 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. Once in the directory, activate the collection of CodeMeter log data, run the command:

    Command Syntax
    openit_oconfinit -u "collect_license_codemeter-logs.root.scheduler.jobs.collect_codemeter_licenselogs.general.active=true"
Advanced Configuration

The collection runs every midnight by default. 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 NameAccepted ValueDescription
max-instancesUint (e.g., 5, 8, 9)The number of instances allowed to run at the same time.
max-handlingString (end-oldest, end-all-old, or end-new)The action done upon reaching the maximum number of instances:
  • end-oldest - Specify this option to stop/kill the oldest instance and start a new one.
  • end-all-old - Specify this option to stop/kill all running instances before starting the new one.
  • end-new - Specify this option to prevent a new instance from starting.
end-timeoutTimespan (e.g., P30S, P5M, P1H)The maximum waiting time before terminating a running instance.
quarantineTimespan (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 the LogFileCollector directory, which is by default in C:\ProgramData\OpeniT\Data\temp\LogFileCollector contains raw-codemtr-license-LogFileCollector-*.parsed and *.status files.

Configuring Log File Parsing from Multiple Subdirectories​

Configuring Log File Collection​

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

  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. Once in the directory, set the location of the CodeMeter log files directory, run the command:

    Command Syntax
    openit_oconfinit -u "core_config_codemeter-logs.root.scheduler.jobs.core_config_codemeter-logs.operations.arguments=<codemeter_log_dir>"

    where <codemeter_log_dir> is the location of the CodeMeter log files directory.

    note

    The default location is the directory generated platform dependently by the CodeMeter installer, C:\ProgramData\CodeMeter\Backup\Logs\LicenseTracking.

    Example
    openit_oconfinit -u "core_config_codemeter-logs.root.scheduler.jobs.core_config_codemeter-logs.operations.arguments=C:\ProgramData\CodeMeter\Backup\Logs\LicenseTracking"

    Make sure no errors are encountered.

    Sample Log File Content
    2017-01-29T17:19:41 SignedLogfile FirmCode:5111696, PublicKey:b9019cb8ab0979f67c04f9cde93d3db754ad78769752b246107f0be4000000007195814def55d5fb7ebf17eb060100076c6a6f7829635fcd3e19342500000000, Runtime-Version:5.22.1514.502, LogfileId:8
    2017-01-29T17:19:41 Admin Server:"samplehost144.company.net" CodeMeter_started 2017-01-29T17:19:02
    2017-01-29T17:19:41 ListOfLicenses
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-16, SN:128-6129194, FC:5111696, PC:1, FM:1, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-17, SN:128-6129194, FC:5111696, PC:100, FM:7, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-18, SN:128-6129194, FC:5111696, PC:101, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-19, SN:128-6129194, FC:5111696, PC:102, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-20, SN:128-6129194, FC:5111696, PC:103, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-21, SN:128-6129194, FC:5111696, PC:104, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-22, SN:128-6129194, FC:5111696, PC:105, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-23, SN:128-6129194, FC:5111696, PC:106, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521494-5111696-24, SN:128-6129194, FC:5111696, PC:107, FM:0, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521496-5111696-16, SN:128-6129196, FC:5111696, PC:1, FM:1, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521496-5111696-17, SN:128-6129196, FC:5111696, PC:100, FM:7, ET:never, LQ:1, PT:""
    2017-01-29T17:19:41 License Server:"samplehost144.company.net", LicenseID:224-9521496-5111696-18, SN:128-6129196, FC:5111696, PC:101, FM:0, ET:never, LQ:1, PT:""

  4. Activate the collection of CodeMeter log data, run the following:

    Command Syntax
    openit_oconfinit -u "collect_license_codemeter-logs.root.scheduler.jobs.collect_codemeter_licenselogs.general.active=true"

    Make sure no errors are encountered.

Verifying Log 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_executor -r core_config_codemeter-logs

  4. Verify that directories with the same name as the log directories are created in the LogFileCollector directory, which is by default in C:\ProgramData\OpeniT\Data\temp\LogFileCollector. It should contain raw-codemtr-license-LogFileCollector-*.parsed and *.status files.

Next Steps?​

Renaming Vendor License
Renaming Features
Create and Add Report
License Monitor