# Zetaware License Manager

# Introduction

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

An Open iT 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

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

(104) License Logfile Events v2.0
(107) Denied License Use Licenseevents

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
Full path to the debug log file

# Configuring Events Log File Collection

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

Go to the Components directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\Components, and open logfilecollector-zetaware.xml.

Locate object node dir and set its value to the location of the Zetaware events log files.

logfilecollector-zetaware.xml
<Object>
	<Name>dir</Name>
	<Description>Directory containing the log files</Description>
	<Value type="DirName">%ZETAWARELOGDIR%</Value>
</Object>

Example: logfilecollector-zetaware.xml
<Object>
	<Name>dir</Name>
	<Description>Directory containing the log files</Description>
	<Value type="DirName">C:\User\AppData\Local\Zetaware\1234</Value>
</Object>

You can add multiple directories by typing in a semi-colon-separated list.

Example: logfilecollector-zetaware.xml
<Object>
	<Name>dir</Name>
	<Description>Directory containing the log files</Description>
	<Value type="DirName">C:\User\AppData\Local\Zetaware\1234;C:\User\AppData\Local\Zetaware\2345;C:\User\AppData\Local\Zetaware\3456</Value>
</Object>

Save the changes.
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
```
Update the configuration file, run the command:
Command Syntax
```
 openit_confbuilder --client
```
Make sure no errors are encountered.

Refer to the Zetaware Events Log File Collection Configuration table to learn more about Zetaware configuration in logfilecollector-zetaware.xml.

Object Name	Accepted Value	Description
source.dir	DirName (e.g., `C:\User\AppData\Local\Zetaware\log.txt`)	Location of the Zetaware log files.
source.pattern	String (i.e., `*_log.txt`)	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., `zetaware`)	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.

Zetaware Events Log File Collection Configuration

# Activating Events Log Data Collection

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

Command Syntax
 openit_oconfinit -u "collect_license_zetaware_event-logs.root.scheduler.jobs.collect_zetaware_licenselogs.general.active=true"

The collection runs every midnight by default. To configure the intervals, locate the instances attribute under collect_zetaware_licenselogs, preprocess_zetaware_licenselogs-events, or transfer_zetaware_licenselogs in the same file and configure the attributes.

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

Zetaware Events Log Job Scheduler Instances Configuration

# Verifying Events Log Data Collection

After configuration, you can verify that the data is collected and sent to the server 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_executor -r collect_license_zetaware_event-logs

Verify that there are archiver*.in files created in the server in the archiver directory, which is by default in C:\ProgramData\OpeniT\Data\incoming\archiver.

# Sample Reports

# Denied Licenses per Feature

This sample report provides insights into how often users cannot access specific software features due to licensing limitations.
It offers several key benefits:

Identifies Licensing Gaps – reveals which features frequently run out of available licenses, indicating a need for adjustments.
Prevents Productivity Loss – helps minimize disruptions by ensuring critical users can access required features.
Optimizes License Procurement – guides purchasing decisions by showing where additional licenses may be necessary.
Improves Resource Allocation – ensures licenses are distributed efficiently based on demand.
Enhances User Experience – reduces frustration by identifying recurring access issues.
Supports Capacity Planning – helps forecast future licensing needs based on denial trends.
Aids in Compliance & Audits – provides documentation on license usage patterns for internal reviews or vendor negotiations.

Denied Licenses per Feature

# Events vs Features

This chart visualizes software license usage, helping organizations optimize resource allocation.
It offers several key benefits:

License Utilization Insights – shows how often licenses are checked out and returned, helping balance supply and demand.
Identifies Feature Demand – highlights frequently used and under-utilized features.
Detects Licensing Bottlenecks – reveals trends in denied license requests, indicating where additional licenses may be needed.
Optimizes Procurement Decisions – supports better budgeting by showing real-time license consumption.
Prevents Access Issues – helps IT teams proactively allocate licenses to ensure critical users aren’t blocked.
Enhances Compliance & Audit Readiness – provides a historical record of license activity for audits and vendor negotiations.

Events vs Features

# Next Steps?

Renaming Vendor License Renaming Features Create and Add Report