立即与支持人员聊天
与支持团队交流

Foglight 5.9.7 - Installing Foglight on Windows with an External Oracle 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

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.

bin

Foglight executables for running the server and utilities.

cartridge

Installed cartridge files in their original form.

client

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

compat

Cartridge files: Core-HostServices-compatibility-5_9_x.car

and FTR-WS-1_0_0.car

config

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.

docs

HTML and PDF versions of the product documentation.

dtd

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

extension

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

fglam

Directories for the embedded Agent Manager.

jre

Version of the JRE (1.8) that Foglight uses.

lib

The Foglight JAR files.

license

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).

logs

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

Generated at runtime.

postgresql

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

scripts

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.

server

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

state

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.

support

Where support bundled archive information is stored.

tmp\cartridge.deployed

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.

tools

Various Foglight utilities.

UninstallerData

Files that the Foglight uninstaller uses.

upgrade

Directory that the installer uses.

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

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.

Enabling High Availability mode after installation

If you want to run Foglight in High Availability (HA) mode but did not select this option during installation, you can enable HA mode after installation by editing the file server.config. For more information, see the Foglight High Availability Field Guide.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级