# Sentinel RMS License Manager

# Introduction

Open iT supports Sentinel RMS usage reporting. The following sections will guide you on the required configuration for license manager utility polling and log file parsing.

# 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. 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.

# Requirements

# Configuring Data Collection

These are the required steps to activate and configure collection of Sentinel RMS 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, activate the collection of Sentinel RMS data, run the command:

    Command Syntax
     openit_confinit -c "licpoll.license-types.sentinel-sample.active=true"
  5. Set the license server name used by the Sentinel RMS License Server, run the command:

    Command Syntax
     openit_confinit -c "licpoll.license-types.sentinel-sample.status-command.arguments=<hostname>"
    Command Syntax
     openit_confinit -c "licpoll.license-types.sentinel-sample.status-command.arguments=hou105win"
  6. Update the configuration file, run the command:

    Command Syntax
     openit_confbuilder --client

    Make sure that there are no errors encountered.

  1. Go to the Components directory, which is by default in /var/opt/openit/etc/Components, and back up the licpoll.xml configuration file.

  2. 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
  3. Once in the directory, activate the collection of Sentinel RMS data, run the command:

    Command Syntax
     ./openit_confinit -r /var/opt/openit/ -d /var/opt/openit/etc/ -c "licpoll.license-types.sentinel-sample.active=true"
  4. Set the license server name used by the Sentinel RMS License Server, run the command:

    Command Syntax
     ./openit_confinit -r /var/opt/openit/ -d /var/opt/openit/etc/ -c "licpoll.license-types.sentinel-sample.status-command.arguments=<hostname>"
    Command Syntax
     ./openit_confinit -r /var/opt/openit/ -d /var/opt/openit/etc/ -c "licpoll.license-types.sentinel-sample.status-command.arguments=hou105win"
  5. Update the configuration file, run the command:

    Command Syntax
     ./openit_confbuilder --client

    Make sure that there are no errors encountered.

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

Object Name Accepted Value Description
active Boolean (true or false) Setting this to true activates Sentinel RMS usage data collection.
type String (i.e., Sentinel) 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 vendor license name other than the default Sentinel=%server%;sentinel will be used.
end-trigger String (i.e., Enter to continue) The line that will be the end trigger.
status-command FileName (e.g., ${OpeniT.directories.bin}/lsmon) The binary used to obtain status from the license manager.
status-command.arguments String (e.g., hou105win) The arguments used for the status command.
Sentinel RMS 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.

  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_licpoll -# 1
  3. Verify that the temp directory, which is by default in /var/opt/openit/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 reporting:

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
  • License server administrative rights
  • Full path to the debug log file

# Configuring Log File Collection

These are the required steps to configure collection of Sentinel RMS 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-sentinel.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 Sentinel RMS log files, run the command:

    Command Syntax
     openit_confinit -c "logfilecollector-sentinel.logfilecollector.source.dir=<sentinel_log_dir>"

    where <sentinel_log_dir> is the location of the Sentinel RMS log files.

    Example
     openit_confinit -c "logfilecollector-sentinel.logfilecollector.source.dir=C:\Sentinel\home\logs"
  5. Update the configuration file, run the command:

    Command Syntax
     openit_confbuilder --client

    Make sure that there are no errors encountered.

Refer to the Sentinel RMS Log File Collection Configuration table to learn more about Sentinel RMS configuration in logfilecollector-sentinel.xml.

Object Name Accepted Value Description
source.dir DirName (e.g., C:\Sentinel\home\logs) Location of the Sentinel RMS 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 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.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., sentinel) 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.
Sentinel RMS Log File Collection Configuration
  1. Go to the Components directory, which is by default in /var/opt/openit/etc/Components, and back up the logfilecollector-sentinel.xml file.

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

    Command Syntax
     ./openit_confinit -r /var/opt/openit/ -d /var/opt/openit/etc/ -c "logfilecollector-sentinel.logfilecollector.source.dir=<sentinel_log_dir>"

    where <sentinel_log_dir> is the location of the Sentinel RMS log files.

    Example
     ./openit_confinit -r /var/opt/openit/ -d /var/opt/openit/etc/ -c "logfilecollector-sentinel.logfilecollector.source.dir=/root/Sentinel/home/logs"
  4. Update the configuration file, run the command:

    Command Syntax
     ./openit_confbuilder --client

    Make sure that there are no errors encountered.

Refer to the Sentinel RMS Log File Collection Configuration table to learn more about Sentinel RMS configuration in logfilecollector-sentinel.xml.

Object Name Accepted Value Description
source.dir DirName (e.g., /root/Sentinel/home/logs) Location of the Sentinel RMS 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 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.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., sentinel) 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.
Sentinel RMS Log File Collection Configuration

# Activating Log Data Collection

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

    Command Syntax
     openit_oconfinit --update "C:/Program Files/OpeniT/Core/Configuration/scheduler/collect_license_sentinel-logs.root.scheduler.jobs.collect_sentinel_licenselogs.general.active=true

The collection runs every 5 minutes by default, which triggers the data collection process. To configure the intervals, locate the instances attribute under collect_sentinel_licenselogs, preprocess_sentinel_licenselogs-events, preprocess_sentinel_licenselogs-records or transfer_sentinel_licenselogs in the same file and configure the attributes.

Refer to the Sentinel RMS Log Job Scheduler Instances Configuration table to learn the attributes used to configure Sentinel RMS 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:
  • 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-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.
Sentinel RMS Log Job Scheduler Instances Configuration
  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. Once in the directory, activate the collection of Sentinel RMS log data, run the command:

    Command Syntax
     ./openit_oconfinit --update "/var/opt/openit/etc/scheduler/collect_license_sentinel-logs.root.scheduler.jobs.collect_sentinel_licenselogs.general.active=true

The collection runs every 5 minutes by default, which triggers the data collection process. To configure the intervals, locate the instances attribute under collect_sentinel_licenselogs, preprocess_sentinel_licenselogs-events, preprocess_sentinel_licenselogs-records or transfer_sentinel_licenselogs in the same file and configure the attributes.

Refer to the Sentinel RMS Log Job Scheduler Instances Configuration table to learn the attributes used to configure Sentinel RMS 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:
  • 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-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.
Sentinel RMS 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_logfilecollector -c "C:\Program Files\OpeniT\Core\Configuration\logfilecollector-sentinel.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.

  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_logfilecollector -c "/var/opt/openit/etc/logfilecollector-sentinel.conf"
  3. 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

We value your feedback!

Please take a few minutes to complete our survey and share your thoughts on your recent experience with our documentation.

Take survey

Close