# Honeywell Unified License Manager (ULM)

# Introduction

Open iT supports Honeywell ULM usage reporting by collecting log files and converting them to Open iT format. This will produce the following aggregated data types used for historical reporting:

(89) Total License Use Licenseevents
(90) Individual License Use Licenseevents
(91) Usergroup License Use Licenseevents
(108) Host License Use Licenseevents
(109) Hostgroup License Use Licenseevents
(104) License Logfile Events v2.0
(107) Denied License Use Licenseevents

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.

Apply the configurations shown in the Open iT client.

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

Open a command prompt with Administrator level privileges.
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
```
Once in the directory, activate the collection of Honeywell ULM log data, run the command:
Command Syntax
```
 openit_oconfinit --update "C:/Program Files/OpeniT/Core/Configuration/scheduler/collect_license_honeywellulm-logs.root.scheduler.jobs.create_honeywellulm_printusagelog.general.active=true
```
Make sure that PrintUsageLog.exe is in C:\Program Files (x86)\Common Files\honeywell\simstation.

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

# Verifying Log Data Collection

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

Open a command prompt with Administrator level privileges.
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
```

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"

Run the command:

Command Syntax
 openit_logfilecollector -c "C:\Program Files\OpeniT\Core\Configuration\logfilecollector-honeywellulm.conf"

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