Server Operation
Start Altair Monitor Manually on UNIX
- Ensure that the license license key file is in place (or for customers using a RLM-based licensing environment, ensure that the RLM server is running and Altair licenses are being served).
-
If starting from a UNIX shell, setup the environment
to include the Altair Accelerator commands:
- UNIX: source the shell-specific vovrc script found in the Altair Accelerator product installation, in the common/etc directory.
lmmgr
Altair Monitor management script. Execute on the server. Some commands require enablement by first typing "vovproject enable licmon". If a project name other than licmon is used, use that name instead.
lmmgr: Usage Message
DESCRIPTION:
Altair Monitor management script. Execute on the server. Some commands
require enablement by first typing "vovproject enable licmon".
If a project name other than licmon is used, use that name instead.
USAGE:
% lmmgr <COMMAND> [OPTIONS]
COMMANDS:
deobfuscate -- Deobfuscated checkout data that was obfuscated
due to license violation. Requires enablement and
a valid license file with a proper user count for
the dates that contain obfuscated data.
loaddb -- Fully load the database. Requires enablement.
loadremotedata -- Load data that was copied in from remote instances
into the database. Requires enablement.
reset -- Resets LM. Requires enablement.
start -- Starts LM. The project name is the -name option
value if present. Otherwise, licmon.
stop -- Stops LM. The project name is the -name option
value if present. Otherwise, licmon.
START OPTIONS:
-block -- Do not return to the shell or command prompt
after starting. This is only useful, and required,
when starting Monitor as a Windows service.
-dbhost <host> -- Host for database.
-dbport <port> -- Port of the database to listen for connections.
-dbroot <path> -- Path, local to database host, for database files.
If either -dbhost or -dbroot is left unspecified,
the database and historical reporting will be
unavailable until configured in the admin UI.
-dir <dir> -- Choose top directory (it must exist).
Default $VOVDIR/../../licmon
-h, -help -- Print this usage message.
-name <name> -- Name of the Monitor server project name. Used
by the start and stop commands.
-port <port[:port]> -- Colon separated port list wherein each element
may be of the form:
N - An integer specifying the exact port
number to use.
automatic - Calculates hash of project name to
derive a single port number.
any - Calculates hash of project name to
derive starting port number. Ports
are checked sequentially up to
30000.
Projects will not start if all specified ports
are unavailable (default 5557).
-product <product> -- Product type, one of: lm (default) or lms.
-removelockfile -- Delete server lock file if it already exists.
-roport <port> -- Web interface guest access port (default 5556), or
0 if no anonymous guest access port should be
enabled.
-v -- Increase verbosity.
-webprovider <prov> -- Web provider: internal or nginx. Default: internal.
-webport <port> -- Colon separated port list wherein each element
may be of the form:
N - An integer specifying the exact port
number to use.
automatic - Calculates hash of project name to
derive a single port number.
any - Calculates hash of project name to
derive starting port number. Ports
are checked sequentially up to
30000.
(Default 5555).
-inport <port[:port]> -- ignored
-eventport <port[:port]> -- Colon separated update port list wherein each
element may be of the form:
N - An integer specifying the exact port
number to use.
automatic - Calculates hash of project name to
derive a single port number.
any - Calculates hash of project name to
derive starting port number. Ports
are checked sequentially up to
30000.
Projects will not start if all specified ports
are unavailable (default 5559).
-pubkey <key> -- Specify the public VOV security key to be added
to a new project. If -pubkey is not specified,
the public key listed in ~/.vov/userkey or
%PROFILE%/.vov/userkey is added.
STOP OPTIONS:
-f, -force -- Suppress shutdown confirmation prompt.
-name <name> -- Name for the server (default licmon).
LOADDB OPTIONS:
-start -- Start time for loading data, (default 1y).
EXAMPLES:
% lmmgr -- For this usage message
% lmmgr start
% lmmgr start -dir ~/MYFTLM -port 7777
% lmmgr loaddb
% lmmgr stop
% lmmgr stop -force -name licmon833
% lmmgr deobfuscate
% lmmgr reset
Start Altair Monitor Manually on Windows
- Download the lm-win64.exe program from the release area of the Altair website and save it into a permanent directory, such as c:\rtda.
- Run lm-win64.exe.
-
Fill out the information to match the desired installation configuration.
Figure 1.
Monitor can now be controlled manually via the Start and Stop buttons.
First Startup
The following actions are performed upon first startup:
- The server working directory (licmon.swd) is created at the default location of $VOVDIR/../../licmon/licmon.swd, including default configuration files, as well as maintenance tasks for database loading, etc.
- The server process (vovserver) is started.
When the startup process is complete, the web interface will be accessible at the default URL of http://<HOSTNAME>:5555/cgi/ftlm.cgi.
Start Monitor Automatically at System Startup - Windows
Note: If upgrading from a version less than 2015.03, first stop and uninstall the old
service before installing the new service. See the Installation Guide for the specific version for instructions on doing this.
- Download the lm-win64.exe program from the Altair website and save it into a permanent directory, such as c:\rtda.
- Run lm-win64.exe as administrator by right-clicking it and choosing the Run as administrator option.
-
Fill out the information to match the desired installation configuration:
Figure 2.
- If not using an legacy license key file, make sure to specify the location of the ALM license server or file.
- Use the Windows Services area to setup and manage a service for controlling Monitor.
Reset Altair Monitor
Resetting Monitor consists of clearing all monitoring data, removing the data collection jobs, and recreating them from the configuration files. This may be required if disk-full or network outage situations occur while Monitor is running.
- To reset Monitor via the web interface, navigate to the System page under the Admin tab and click on the reset button.
-
To reset using the CLI, use:
% lmmgr reset
Stop Monitor
-
To stop Monitor, use:
% lmmgr stop
- To stop without prompting for confirmation, use the option -force.