# Reactis License Manager

# Introduction

Open iT supports Reactis 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 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

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

Reactis License Manager V2022
Full path to the reactisl_log.csv file
An Open iT Client connected to an Open iT Server or a coexistent Open iT setup

The collected data does not include the number of available licenses. To configure the available licenses for Reactis features, refer to the instructions in the Configuring available-licenses.map section.

# Configuring Log File Collection

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

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

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

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

Example: logfilecollector-reactis.xml
<Object>
	<Name>dir</Name>
	<Description>Directory containing the log files</Description>
	<Value type="DirName">C:\Program Files\Reactis License Manager V2022</Value>
</Object>

"01/25/06 11:27:34", "", "License Manager Started", 0, "", "n/a"
"01/25/06 11:27:59", "192.168.1.107", "License granted", 1, "Reactis", "5555"
"01/25/06 11:27:59", "192.168.1.107", "User: John Doe on XYZ", 1, "Reactis", "5555"
"01/25/06 11:28:03", "192.168.1.107", "License released", 0, "Reactis", "5555"

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 Reactis Log File Collection Configuration table to learn more about Reactis configuration in logfilecollector-reactis.xml.

Object Name	Accepted Value	Description
source.dir	DirName (e.g., `C:\Program Files\Reactis License Manager V2022`)	Location of the Reactis log files.
source.pattern	String (i.e., `.csv`)	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., `reactis`)	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.

Reactis Log File Collection Configuration

# Reactis Events Log File Collection Configuration

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

(104) License Logfile Events v2.0

# Activating Event Log Data Collection

These are the required steps to activate event log data collection.

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 Reactis event log data, run the command:

Command Syntax
 openit_oconfinit -u "collect_license_reactis_event-logs.root.scheduler.jobs.collect_reactis_licenselogs.general.active=true"

The collection runs every 5 minutes by default. To configure the intervals, locate the instances attribute under collect_reactis_licenselogs, preprocess_reactis_licenselogs-events, or transfer_reactis_licenselogs in the same file and configure the attributes.

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

Reactis Event Log Job Scheduler Instances Configuration

# Verifying Event 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_executor -r collect_license_reactis_event-logs

Verify that there are *.status and raw-reactis-license-LogFileCollector*.parsed files created in the LogFileCollector directory, which is by default in C:\Program Files\OpeniT\Core\Log\temp\LogFileCollector.

# Reactis Records Log File Collection Configuration

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

# Activating Record Log Data Collection

These are the required steps to activate record log data collection.

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 Reactis record log data, run the command:

Command Syntax
 openit_oconfinit -u "collect_license_reactis_record-logs.root.scheduler.jobs.collect_reactis_licenselogs-records.general.active=true"

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

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

Reactis Record Log Job Scheduler Instances Configuration

# Verifying Event 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_executor -r collect_license_reactis_record-logs

Verify that the system creates a LogParserReactis directory containing license-usage-reactis.temp and products-info-reactis.temp files in the temp directory, which is by default in C:\Program Files\OpeniT\Core\Log\temp.

# Sample Reports

# Max Available vs Max in Use

This sample report compares max in-use licenses against max available licenses.
It offers several key benefits:

Optimized License Allocation – helps ensure you are not over-purchasing licenses you don't need or under-provisioning.
Cost Savings – identifies opportunities to downgrade or redistribute licenses, reducing unnecessary expenses.
Usage Trends & Capacity Planning – shows peak usage patterns, allowing better forecasting for future needs.
Avoiding Service Disruptions – helps prevent situations where users cannot access software due to reaching the license limit.
Compliance & Audit Readiness – provides a usage record to ensure compliance with vendor agreements and avoid penalties.
Performance & Productivity Insights – helps assess whether certain teams or departments are under-utilizing or over-utilizing software.

Max Available vs Max in Use Licenses per Feature

# License Usage and Event Logs

This sample report shows the usage and event log of a feature.
It offers several key benefits:

Optimize Software Spend - Identify underutilized or overutilized licenses to right-size your license pool and reduce unnecessary costs.
Gain Real-Time Visibility - Track check-in/check-out events, user activity, and license usage in real-time for better operational insight.
Ensure License Compliance - Maintain audit readiness with detailed logs showing user, host, event type, and time.
Enhance Engineering Productivity - Pinpoint license bottlenecks that hinder development workflows and ensure critical tools are always available when needed.
Improve Decision-Making - Use usage data to forecast demand and plan renewals, upgrades, or reallocations with confidence.
User Accountability - Easily track individual user access to promote responsible software usage and identify training needs.

License Usage and Event Logs

# Feature Elapsed Time per User

This sample report gives you helpful insights into software use, performance trends, and user behavior.
It offers several key benefits:

User Efficiency Analysis – tracks how much time users spend on specific features to help assess productivity.
Identifying Workflow Issues – highlights any delays or inefficiencies in processes that could be improved.
Usability & UX Insights – points out features that take longer to use, which could indicate design or functionality improvements.
Training & Support Guidance – helps identify users who might need extra training to use a feature more effectively.
Compliance Tracking – makes sure users are spending the right amount of time on regulated tasks.
Resource & License Optimization – finds underused features or areas where too much time is spent, helping with better resource allocation.

Feature Elapsed Time per User