# Petroleum Experts (PetEx)

# Introduction

Open iT supports Petroleum Experts (Petex) usage reporting. The following sections will guide you on the required configuration for license manager utility polling and log file parsing.

Apply the configurations in the Open iT client.

# Configuring License Manager Utility Polling

Open iT supports Petex usage reporting through the generic license type format. This will produce the following aggregated data types used for historical and real-time reporting:

The following sections will guide you in setting up the necessary configuration to collect and send the required data to the server.

# Requirements

Configured Petex License Server
Host name of the valid IP Address of the Petex License Server
An Open iT Client connected to an Open iT Server or a coexistent Open iT setup
Activated LicenseAnalyzer collection and license poller

# Configuring Data Collection

These are the required steps to activate and configure collection of Petex usage data.

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.
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, copy the object node genericlicense-sample, run the command:
Command Syntax
```
 openit_confinit -c "licpoll.license-types.genericlicense-sample=>licpoll.license-types.petex"
```
Activate the collection of PetEx data, run the command:
Command Syntax
```
 openit_confinit -c "licpoll.license-types.petex.active=true"
```

Set the arguments to the status command, run the command:

Command Syntax
 openit_confinit -c "licpoll.license-types.petex.status-command.arguments=PetEx <servername>"

where <servername> is the host name of the valid IP Address of the Petex license server.

Example
 openit_confinit -c "licpoll.license-types.petex.status-command.arguments=PetEx hou150win"

Update the configuration file, run the command:
Command Syntax
```
 openit_confbuilder --client
```
Make sure that there are no errors encountered.

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

Object Name	Accepted Value	Description
active	Boolean (`true` or `false`)	Setting this to true activates Petex usage data collection.
type	String (e.g., `GenericLicense`)	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 product name other than the default `GenericLicense=%hosttype%` will be used.
license-server	String (e.g., `hou105win`)	The License Server name.
status-command	FileName (i.e., `${OpeniT.directories.bin}/genlicutil`)	The binary used to obtain status from the license manager.
status-command.arguments	String (e.g., `Petex hou150win`)	The arguments used for the status command. Use the format `PetEx <servername>`.

Petex Data Collection Configuration

# Verifying 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_licpoll -# 1
```
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.

Continue reading if you need to configure log file parsing. If not, here are some suggested readings.

# 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 and real-time 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

# 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 Petex log files.

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

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

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

Use semicolons(;) as separators to include multiple log file directories.

Example: logfilecollector-hasp2.xml
<Object>
	<Name>dir</Name>
	<Description>Directory containing the log files</Description>
	<Value type="DirName">C:\Users\user1\Petex\home\logs;C:\Users\user1\Petex\logs</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 that there are no errors encountered.

Refer to the Petex Log File Collection Configuration table to learn more about Petex configuration in logfilecollector-hasp2.xml.

Object Name	Accepted Value	Description
source.dir	DirName (e.g., `C:\Users\user1\Petex\home\logs`)	Location of the Petex 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 source files collected from before. Specify collect to collect from the start every time, specify ignore to never collect from the same file again, or specify tail 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., `haspevents2`)	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.

Petex Log File Collection Configuration

# Activating Event Log Data Collection

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

Go to the scheduler directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\scheduler, and open collect_license_hasp2_event-logs.oconf.
Locate and set root.scheduler.jobs.collect_hasp2_licenselogs_event.general.active to true to activate the collection of Petex event log data.
collect_license_hasp2_event-logs.oconf
```
 13|	}
 14|		general
 15|		{
 16|			active
 17|			{
 18|				type=bool
 19|				value=true
```
Save the changes.

The collection runs hourly using a 5-minute sample interval by default. The primary data is then transferred to the server every night according to the client timezone for processing. To configure the intervals, locate the instances attribute under collect_hasp2_licenselogs_event, preprocess_hasp2_licenselogs-events, or transfer_hasp2_licenselogs-event in the same file and configure the attributes.

Refer to the Petex Event Log Job Scheduler Instances Configuration table to learn the attributes used to configure Petex 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. Specify end-oldest to stop/kill the oldest instance and then start the new, specify end-all-old to stop/kill all running instances and then start the new, or specify end-new to not start the new instance.
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.

Petex Event Log Job Scheduler Instances Configuration

# Activating Record Log Data Collection

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

Go to the scheduler directory, which is by default in C:\Program Files\OpeniT\Core\Configuration\scheduler, and open collect_license_hasp2_record-logs.oconf.
Locate and set root.scheduler.jobs.collect_hasp2_licenselogs_record.general.active to true to activate the collection of Petex record log data.
collect_license_hasp2_record-logs.oconf
```
 13|	}
 14|		general
 15|		{
 16|			active
 17|			{
 18|				type=bool
 19|				value=true
```
Save the changes.

The collection runs hourly using a 5-minute sample interval by default. The primary data is then transferred to the server every night according to the client timezone for processing. To configure the intervals, locate the instances attribute under collect_hasp2_licenselogs_record, preprocess_hasp2_licenselogs-records, transfer_hasp2_licenselogs-record, or transfer_hasp2_licenselogs-raw in the same file and configure the attributes.

Refer to the Petex Record Log Job Scheduler Instances Configuration table to learn the attributes used to configure Petex 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. Specify end-oldest to stop/kill the oldest instance and then start the new, specify end-all-old to stop/kill all running instances and then start the new, or specify end-new to not start the new instance.
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.

Petex Record 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:

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_hasp2_event-logs

Run the command:

Command Syntax
 openit_executor -r collect_license_hasp2_record-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.

# Next Steps?

Renaming Vendor License Renaming Features Create and Add Report License Monitor