Skip to main content
Version: 10.2

Parasoft License Manager

Introduction​

Open iT supports Parasoft usage reporting by collecting log files and converting 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 5 minutes. 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:

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​

  • 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

Configuring Log File Collection​

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

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

    Command Syntax
    openit_confinit -c "logfilecollector-parasoft.logfilecollector.source.dir=<parasoft_log_dir>"

    where <parasoft_log_dir> is the location of the Parasoft log files.

    Example
    openit_confinit -c "logfilecollector-parasoft.logfilecollector.source.dir=C:\ProgramData\Parasoft"
    Sample Log File Content
    <log_entry ver="1"><time>2012-12-05 13:36:29.668</time><ip>130.38.36.222</ip><type>GET_ENCODED_LICENSE</type><request><archName>WIN32</archName><validation>valid</validation><minor>2</minor><networkID>0</networkID><clientID></clientID><authorization>1</authorization><toolName>C++Test</toolName><machineID>1361338310</machineID><userID>0</userID><authentication>B**Udru38</authentication><hostName>A4808581</hostName><userName>m248602</userName><major>9</major></request><status>0</status><statusmsg>OK</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.558</time><ip>130.38.36.222</ip><type>GET_START_DEACTIVATED</type><request></request><status>0</status><statusmsg>OK</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.621</time><ip>130.38.36.222</ip><type>GET_KEY</type><request></request><status>0</status><statusmsg>OK</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.668</time><ip>130.38.36.222</ip><type>GET_ENCODED_LICENSE</type><request><archName>WIN32</archName><validation>valid</validation><minor>2</minor><networkID>0</networkID><clientID></clientID><authorization>1</authorization><toolName>C++Test</toolName><machineID>1361338310</machineID><userID>0</userID><authentication>B**Udru38</authentication><hostName>A4808581</hostName><userName>m248602</userName><major>9</major></request><status>0</status><statusmsg>OK</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.730</time><ip>130.38.36.222</ip><type>GET_INFO</type><request></request><status>0</status><statusmsg>OK</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.777</time><ip>130.38.36.222</ip><type>GET_ENCODED_MULTI_FEATURE_LICENSE</type><request><archName>WIN32</archName><validation>valid</validation><minor>2</minor><networkID>0</networkID><clientID></clientID><authorization>0</authorization><toolName>C++Test Coding Standards|,|C++Test BugDetective|,|C++Test Source Unit Testing|,|C++Test RuleWizard|,|C++Test Extended Command Line Mode|,|C++Test Embedded Support|,|C++Test Code Review|,|C++Test Application Monitoring|,|C++Test Runtime Error Detection</toolName><machineID>1361338310</machineID><userID>0</userID><authentication>B**Udru!Bnehof!Ru`oe`ser}-}B**Udru!CtfEdudbuhwd}-}B**Udru!Rntsbd!Tohu!Udruhof}-}B**Udru!StmdVh{`se}-}B**Udru!Dyudoede!Bnll`oe!Mhod!Lned}-}B**Udru!Dlcdeede!Rtqqnsu}-}B**Udru!Bned!Sdwhdv}-}B**Udru!@qqmhb`uhno!Lnohunshof}-}B**Udru!Stouhld!Dssns!Edudbuhno38</authentication><hostName>A4808581</hostName><userName>m248602</userName><major>9</major></request><status>0</status><statusmsg>OK</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.777</time><ip>130.38.36.222</ip><type>GET_ENCODED_LICENSE</type><request><archName>WIN32</archName><validation>valid</validation><minor>2</minor><networkID>0</networkID><clientID></clientID><authorization>0</authorization><toolName>C++Test Coding Standards</toolName><machineID>1361338310</machineID><userID>0</userID><authentication>B**Udru!Bnehof!Ru`oe`ser}-}B**Udru!CtfEdudbuhwd}-}B**Udru!Rntsbd!Tohu!Udruhof}-}B**Udru!StmdVh{`se}-}B**Udru!Dyudoede!Bnll`oe!Mhod!Lned}-}B**Udru!Dlcdeede!Rtqqnsu}-}B**Udru!Bned!Sdwhdv}-}B**Udru!@qqmhb`uhno!Lnohunshof}-}B**Udru!Stouhld!Dssns!Edudbuhno38</authentication><hostName>A4808581</hostName><userName>m248602</userName><major>9</major></request><status>0</status><statusmsg>OK</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.777</time><ip>130.38.36.222</ip><type>GET_ENCODED_LICENSE</type><request><archName>WIN32</archName><validation>valid</validation><minor>2</minor><networkID>0</networkID><clientID></clientID><authorization>0</authorization><toolName>C++Test BugDetective</toolName><machineID>1361338310</machineID><userID>0</userID><authentication>B**Udru!Bnehof!Ru`oe`ser}-}B**Udru!CtfEdudbuhwd}-}B**Udru!Rntsbd!Tohu!Udruhof}-}B**Udru!StmdVh{`se}-}B**Udru!Dyudoede!Bnll`oe!Mhod!Lned}-}B**Udru!Dlcdeede!Rtqqnsu}-}B**Udru!Bned!Sdwhdv}-}B**Udru!@qqmhb`uhno!Lnohunshof}-}B**Udru!Stouhld!Dssns!Edudbuhno38</authentication><hostName>A4808581</hostName><userName>m248602</userName><major>9</major></request><status>5</status><statusmsg>NO_FEATURE</statusmsg></log_entry>
    <log_entry ver="1"><time>2012-12-05 15:36:29.777</time><ip>130.38.36.222</ip><type>GET_ENCODED_LICENSE</type><request><archName>WIN32</archName><validation>valid</validation><minor>2</minor><networkID>0</networkID><clientID></clientID><authorization>0</authorization><toolName>C++Test Source Unit Testing</toolName><machineID>1361338310</machineID><userID>0</userID><authentication>B**Udru!Bnehof!Ru`oe`ser}-}B**Udru!CtfEdudbuhwd}-}B**Udru!Rntsbd!Tohu!Udruhof}-}B**Udru!StmdVh{`se}-}B**Udru!Dyudoede!Bnll`oe!Mhod!Lned}-}B**Udru!Dlcdeede!Rtqqnsu}-}B**Udru!Bned!Sdwhdv}-}B**Udru!@qqmhb`uhno!Lnohunshof}-}B**Udru!Stouhld!Dssns!Edudbuhno38</authentication><hostName>A4808581</hostName><userName>m248602</userName><major>9</major></request><status>5</status><statusmsg>NO_FEATURE</statusmsg></log_entry>

  5. Update the configuration file, run the command:

    Command Syntax
    openit_confbuilder --client

    Make sure no errors are encountered.

Advanced Configuration

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

Object NameAccepted ValueDescription
source.dirDirName (e.g., C:\ProgramData\Parasoft)Location of the Parasoft log files.
source.patternString (i.e., ls_access.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., parasoftevents)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.
Parasoft Log File Collection Configuration

Activating Log Data Collection​

These are the required steps to activate collection of Parasoft 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 Parasoft log data, run the command:

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

The collection runs every 5 minutes by default. To configure the intervals, locate the instances attribute under collect_parasoft_licenselogs, preprocess_parasoft_licenselogs-records, or transfer_parasoft_licenselogs in the same file and configure the attributes.

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

Attribute NameAccepted ValueDescription
max-instancesUint (e.g., 5, 8, 9)The number of instances allowed to run the 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.
Parasoft Log Job Scheduler Instances Configuration

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_logfilecollector -c "C:\Program Files\OpeniT\Core\Configuration\logfilecollector-parasoft.conf"

  4. Verify that there are *.data files created in the LogFileCollector directory, which is by default in C:\Program Files\OpeniT\Core\Log\temp\LogFileCollector.

Next Steps?​

Renaming Vendor License
Renaming Features
Create and Add Report
License Monitor