Home
Altair Monitor Administrator Guide
Command Line Operations
Load the Database
A need may arise to manually load checkout or denial data into the database. This will be required if importing historical checkout data that is obtained from parsing a debug log, or if reloading data for checkouts and/or denials. It can also be helpful in debugging database loading problems.

Welcome
What's New
View new features for Monitor 2025.1.0.
Monitor Overview
A real time software license monitoring and management tool.
Monitor Tutorials
Currently there are no Monitor tutorials available.
Getting Started Guide
This manual describes the web user interface and provides instructions on common uses and best practices for users. It also provides the basic setup, installation and management practices for administrators. For both administrators and users, it functions as a getting started guide.
Altair Monitor User Guide
Altair Monitor is a software license tracking tool that reports current and historical license utilization. The license managers that Monitor supports includes FlexNet Publisher, Reprise, LUM, and many others. The primary user interface for accessing Monitor is a web interface.
Altair Monitor Administrator Guide
- Altair Monitor Overview
  This document describes how to configure and manage Altair Monitor.
- Enable CLI Access on UNIX
  This section explains how to set up a UNIX user's shell environment to have a proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- Enable CLI Access on Windows
  This section explains how to set up a Window user's command prompt environment to have the proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
- Use Monitor Help
  Monitor documentation is available in HTML and PDF format.
- Server Operation
- Failover Server Candidates
  If a server crashes suddenly, VOV has the capability to start a replacement server on a pre-selected host. This capability requires that the pre-selected host is configured as a failover server.
- Daemon Operation
  Although the Monitor daemons are started automatically upon startup, there may be times where a daemon should be restarted. This section describes how to control the Monitor daemons.
- Daemon Manager Utility
  Although the Monitor daemons are started automatically upon startup, there may be times where a daemon should be restarted. This section describes how to control the daemons from the command line (CLI).
- Database
  Monitor stores historical information about jobs in a relational database. As of version 2015.09, the database is fully integrated and managed as part of Monitor. This section provides an overview of the components that run and manage the database.
- Configuring Monitoring
- License Server Management
- Other Configurations
- Command Line Operations
  - Sample a License Server
    The Monitor CLI provides the ability to manually sample a license server to gather availability and utilization data. This can be helpful in debugging problems with the connectivity to a license server, or the data that is returned from the license manager status command.
  - Parse a Debug Log
    A need may arise to manually parse a debug log to gather denial and/or utilization data. This can be helpful in debugging problems with the data obtained from the file, or with parsing the file itself.
  - Load the Database
    A need may arise to manually load checkout or denial data into the database. This will be required if importing historical checkout data that is obtained from parsing a debug log, or if reloading data for checkouts and/or denials. It can also be helpful in debugging database loading problems.
  - Set Feature Capacity
    Monitor tracks the capacity of licenses in addition to utilization data. This is done so automatically with a periodic job, via the SNAPSHOT_CAPACITY task by loading a snapshot of the capacity of all features every hour by default, comparing the values against what is in the database and if they differ, inserting a new capacity value for each feature. In parallel, a data file also maintains a history of the capacity changes. This data file is useful for multi-site situations to aggregate capacity data to a parent site.
  - Update Summary Table
    Monitor utilizes summary tables for providing fast, high-level statistics for certain reports. The summary tables are automatically with a periodic job, via the UPDATE_SUMMARIES task by executing statistics gathering queries against the checkouts table and populating the results in the summary tables.
  - VovUserGroups
    VovUserGroups are an access control mechanism. They are internally-defined groups of users that are utilized to make the job of allocating access easier within Altair Accelerator tools.
  - Query the vovserver
    The vovselect command provides a way to retrieve specific data from the vovserver, with filtering done on the server side. This method is differs from some of the VTK calls, which get all data and require processing on the client side to get the data of interest.
- Reference

Load the Database

A need may arise to manually load checkout or denial data into the database. This will be required if importing historical checkout data that is obtained from parsing a debug log, or if reloading data for checkouts and/or denials. It can also be helpful in debugging database loading problems.

To manually load the database, first setup the CLI:
```
% vovproject enable licmon
```
Change to the directory that contains the data that is to be loaded. This data is stored in the checkouts/denials data files, located in licmon.swd/data under a respective subdirectory for each data type. The data is organized into files that are named for each day that contains data.
After setting up the CLI, the database loader command must be executed. The available commands are:
- vovsql_load_checkouts
- vovsql_load_denials
Click the links above to learn the arguments required and options supported for each command.