# Honeywell Unified License Manager (ULM)

# Introduction

Open iT supports Honeywell ULM usage reporting by collecting log files and converting them to Open iT format.

An Open iT client is installed on your license server, and the license server does not create license usage history logs for this collection. The data collector initiates the raw data collector to request license usage history logs from the license manager every hour, triggering the data collection process. Once the logs are received, the raw data collector passes them to the data collector. The collected data is then sent to a data preprocessor for processing. After preprocessing, the final preprocessed data is sent and stored in the Core Server.

Log File Parsing Workflow with Raw Collector

Log File Parsing Workflow with Raw Collector

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

Record Log Data:

Event Log Data:

Recommended reading: Determining Tokens within the Honeywell ULM Log Files

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
  • PrintUsageLog.exe in C:\Program Files (x86)\Common Files\honeywell\simstation\

# Activating Log Data Collection

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

    Command Syntax
     openit_oconfinit -u "collect_license_honeywellulm-logs.root.scheduler.jobs.create_honeywellulm_printusagelog.general.active=true"

The collection runs hourly by default, which triggers the data collection process. To configure the intervals, locate the instances attribute under create_honeywellulm_printusagelog, collect_honeywellulm_licenselogs, preprocess_honeywellulm_licenselogs-events, preprocess_honeywellulm_licenselogs-records, or transfer_honeywellulm_licenselogs in the same file and configure the attributes.

Refer to the Honeywell ULM Log Job Scheduler Instances Configuration table to learn the attributes used to configure Honeywell ULM 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.
Honeywell ULM Log Job Scheduler Instances Configuration

# Deactivating Record Log Data Collection

Turning on log data collection automatically aggregates record and event log data. If you want to collect event log data only, follow 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. Once in the directory, deactivate the collection of record log data, run the command:

    Command Syntax
     openit_oconfinit -u "collect_license_honeywellulm-logs.root.scheduler.jobs.preprocess_honeywellulm_licenselogs-records.general.active=false"
  4. Change the handling of event logs, run the command:

    Command Syntax
     openit_oconfinit -u "collect_license_honeywellulm-logs.root.scheduler.jobs.preprocess_honeywellulm_licenselogs-events.operations.arguments=--srcdir \"${OpeniT.directories.temp}/LogFileCollector\" --srcpattern raw-honeywellulm-license-LogFileCollector*.data --srcfilehandling rename --trgdir \"${OpeniT.directories.temp}/LogParserHoneywellulm\" --module license --datatype event --resolution PT1H --matchobjects \"${OpeniT.directories.conf}/matchobjects-event-honeywellulm.oconf\" --type event --disable-statlogging"
  5. Change the data transfer schedule, run the command:

    Command Syntax
     openit_oconfinit -u "collect_license_honeywellulm-logs.root.scheduler.jobs.transfer_honeywellulm_licenselogs.scheduling.start-triggers.trigger#1.job-name=preprocess_honeywellulm_licenselogs-events"

# 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_poll2log -p "C:\\Program Files (x86)\\Common Files\\honeywell\\simstation\\PrintUsageLog.exe" -o "C:\Program Files\OpeniT\Core\Log\temp\HoneywellULMDecoded\PrintUsageLog.log" -s "C:\Program Files\OpeniT\Core\Log\temp\honeywell_printusagelog.status"
  4. Run the command:

    Command Syntax
     openit_logfilecollector -c "C:\Program Files\OpeniT\Core\Configuration\logfilecollector-honeywellulm.conf"
  5. 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