Chat now with support
Chat with Support

Foglight 6.3.0 - Installing Foglight on Windows with an External Microsoft SQL Server Database

Before Installing Foglight Installing Foglight
Preparing to install Installing a new version of the Management Server Installed directories Foglight settings HP patch checking tool Uninstalling Foglight Upgrading the Management Server Installing Foglight FAQ
Running the Management Server Installing and Upgrading Cartridges Installing Agents

Configuration about SQL Server Failover

If you want to use the SQL Server Failover function on the Foglight Management Server, perform the following configurations:

Store the username, sid, and password_hash for later use.
NOTE: The value of <databasename> is the db instance that you create during the installation of the Foglight Management Sever.
Locate <FMS_HOME>\config\server.config, update value to the FMS DB's Availability Group Listener IP.
NOTE: For HA environment, both HA peers' value should be updated.

Next steps

If you performed a Custom Install and you did not install a license in Step 14: Add Foglight license file, follow the instructions in Importing a license file after installation to provide a license file to the Management Server after installation.

IMPORTANT: See the Administration and Configuration Guide for information about license requirements, managing licenses, and the different categories of cartridges (based on their license requirements).

If you did not select the Run Now option in the Foglight Server Startup step of the installer, start the Management Server by following the instructions in Starting and stopping the Management Server.

To log in to Foglight, see Logging in to Foglight.

To set up an encrypted database connection, see Setting up an encrypted database connection.

Embedded Agent Manager

An instance of the Agent Manager is automatically installed with new installations of the Management Server. This embedded Agent Manager instance runs on the Management Server machine. You can deploy agents to the embedded Agent Manager if you want to monitor the machine on which the Management Server runs.

In certain environments, Foglight starts and stops the embedded Agent Manager along with the Management Server by default. For more information about running the embedded Agent Manager, see the Agent Manager Guide.

You can run the embedded Agent Manager in tandem with the server or not. For more information, see the Agent Manager Guide.

Installed directories

The following table describes the directories that are created under your target installation folder. They may vary, depending on the product features that you selected and the components installed for your platform.


Foglight executables for running the server and utilities.


Installed cartridge files in their original form.


Files that client programs (such as the command-line client) use for remote access to Foglight.


Cartridge files:



Configuration files and subdirectories.

The files in the config directory contain settings that are most likely to require editing. Files at the next level are less likely to need changing. Files at the lowest level contain settings that are unlikely to need changing except in special circumstances.


HTML and PDF versions of the product documentation.


Descriptors for configuration files that can be imported into Foglight (for example, by installing a cartridge).


Directory for extension cartridges (optional cartridges that are not installed by default).


Directories for the embedded Agent Manager.


Version of the JRE (1.8) that Foglight uses.


The Foglight JAR files.


The Foglight license file you install.

NOTE: See the Administration and Configuration Guide for information about license requirements, managing licenses, and the different categories of cartridges (based on their license requirements).


Default location of the log files that Foglight generates when it runs.

Generated at runtime.


Default location for the embedded PostgreSQL® library.

If the embedded database is selected during installation, then the database is created, populated, and used for Foglight runtime.

To start the embedded database separately, without running Foglight, use these parameters:
[run|shutdown]Db.bat in <install-dir>/bin


SQL scripts and examples of the two types of Script Agents.

scripts\agent contains sample Type 1 and Type 2 Script Agent files. See the Administration and Configuration Guide for more information about Script Agents.

scripts\sql-templates contains SQL scripts to drop/create schema, or create/populate the database. The scripts included in this directory are specific to the type of database that you selected when installing Foglight.


JAR files and data files that a particular Foglight server variant uses (such as default).


Where the running state of Foglight is kept.

It includes the following sub-directories:

cartridge.exploded. A working directory for deploying cartridges. It contains files extracted from installed cartridges. This is the same data as in the corresponding CAR files, just unzipped. The contents change on cartridge redeployment, but should not change on server restart. Users should not modify this data (even if the server is not running).
postgresql-data. Default location for the embedded PostgreSQL® data.


Where support bundled archive information is stored.


A working directory for deploying cartridges. This directory contains files extracted from cartridges for the current Management Server run. Contents may change on restart or cartridge redeployment.

This data can be deleted if the server is not running. The server re-creates what is necessary on restart.


Various Foglight utilities.


Files that the Foglight uninstaller uses.


Directory that the installer uses.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating