## Description

The Opsview License Manager enables the licensed features of Opsview Monitor. Licenses are locked to the machine's hostname and its network MAC address - if any of those two change the system needs to be re-licensed.

## Dependencies

This component is required by Master Orchestrator server.

## Installation

This component is deployed on the Master server when installating Opsview Monitor and must not be moved to another server.

## Configuration

We ship the opsview-freshchecker with its default configuration, which can be modified or overridden by the user.

• **default setting** - /opt/opsview/licensemanager/etc/licensemanager.defaults.yaml

• **user settings** - /opt/opsview/licensemanager/etc/licensemanager.yaml

Default setting settings are restored on upgrade/installation, user settings are left as defined by the user.

The setting files follow the YAML file format, setting are stored on a <setting_name>: <value> format.

The **custom setting example** contains an example on how to override default value.

### Configuration options

• encoder_key: encryption key used for cross-component communication, if changed also update `/opt/opsview/coreutils/etc/opsview.conf`

## Management

### Configuration

#### DPKGs

Watchdog service files are now managed by the package, doing a remove would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package managed config files are as follows

• /opt/opsview/watchdog/etc/services/opsview-licensemanager.conf

#### RPMs

Watchdog service files are now managed by the package. Any modifications will be saved at upgrade and remove processes with the .rpmnew and .rpmsave extensions correspondingly.

• /opt/opsview/watchdog/etc/services/opsview-liecensemanager.conf

### Service Administration

As root, start, stop and restart the service using: