Embedded Agent Manager
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.
|
NOTE: Although the Foglight Agent Manager Adapter cartridge is installed by default with the embedded Agent Manager, you must install an Agent Manager cartridge that contains installers for your supported platforms, in order to deploy the Agent Manager to remote hosts. See the Agent Manager Guide for information about selecting an Agent Manager cartridge, downloading installers, and installing, configuring, and running the Agent Manager. |
Installed directories
|
Files that client programs (such as the command-line client) use for remote access to Foglight. | |||||
|
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. | |||||
|
Directory for extension cartridges (optional cartridges that are not installed by default). | |||||
|
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. | |||||
|
Default location for the embedded PostgreSQL® library. To start the embedded database separately, without running Foglight, use these parameters: | |||||
|
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:
| |||||
Foglight settings
Foglight can run with its default settings. Edit these settings if you need to change run-time parameters such as settings for running the Management Server in High Availability (HA) mode or the ports that the Management Server uses. Many Foglight settings can be changed by editing the file <foglight_home>/config/server.config, which contains settings.
For more details, see these topics:
Editing the server.config file
The <foglight_home>/config/server.config file contains parameters for port settings, virtual memory, command-line options, and server federation. You can edit the file using a text editor. Values within quotation marks can be edited.
The server.config file includes properties for individual database connection parameters like host name, port, etc. The Management Server uses those parameters to construct a JDBC URL at runtime. In some complex cases, like connecting to the Oracle RAC, these basic parameters are insufficient and a custom JDBC URL had to be manually entered into the oracle-ds.xml file.
Starting with Foglight 5.7.5.3, the server.config file allows you to specify the full JDBC URL (by editing the server.database.url property, which is by default commented out), removing the need for users to edit *-ds.xml files.