立即与支持人员聊天

获得即时帮助
完成注册

登录

请求定价

联系销售人员

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

Before Installing Foglight

What is Foglight? Hardware requirements and guidelines Planning your installation

High Availability mode

Considerations for running the Management Server in HA mode

Using an external database Creating the database manually Planning for authentication with gMSA Licensing Installation modes

Console mode Silent mode

Installing Foglight

Preparing to install Installing a new version of the Management Server

Step 1: Introduction

Step 1: Introduction Step 2: Transaction Product Agreement Step 3: Select installation type Step 4: Choose installation folder Step 5: Choose shortcut location Step 6: Foglight service Step 7: Pre-installation summary Step 8: Installing Foglight Step 9: Foglight administrator password Step 10: Foglight mode Step 11: FIPS Compliance mode Step 12: Foglight repository database type Step 13: Foglight ports configuration Step 14: Add Foglight license file Step 15: Add Foglight to system service Step 16: Foglight server startup Step 17: Change service credentials [Optional] Step 18: Install complete

Foglight Server Startup page Configuration about SQL Server Failover Next steps Embedded Agent Manager

Installed directories Foglight settings

Editing the server.config file Enabling High Availability mode after installation Changing external database credentials Importing self-signed certificates to Foglight TrustStore

Non-FIPS mode FIPS-compliant mode

Setting up an encrypted database connection Setting up an encrypted LDAP connection with SSL Using encryption when sending email from Foglight Configuring ports Configuring the cluster multicast port used in High Availability mode Setting up Foglight server federation Setting memory parameters for the server

Process heap use

Adding command-line options Binding the Management Server to an IP address Configuring Foglight to use stronger encryption Configuring Foglight to use the HTTPS port

Importing a network security certificate Importing a PKCS #12 (pfx) format certificate

Setting the length of Foglight sessions

HP patch checking tool Uninstalling Foglight Upgrading the Management Server Installing Foglight FAQ

Running the Management Server

Manual database configuration

Option 1 - Run the Foglight database tool to configure the database Option 2 - Run SQL scripts to configure the database

Initializing the database Starting and stopping the Management Server

Starting the Management Server Running the Management Server as a Windows service

Using the Start Menu options Using the command line

Stopping the Management Server Starting and stopping the Management Server in High Availability mode

Logging in to Foglight

Monitoring the Management Server host Next steps

Running the Management Server FAQ

Installing and Upgrading Cartridges Installing Agents

Agent installers Remote agent installation

Configuration about SQL Server Failover

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

1

On the primary database instance, issue the following command:

select name, sid, password_hash from master.sys.sql_logins where name='<username>';

Store the username, sid, and password_hash for later use.

2

On the secondary database instance(s), issue the following command:


	NOTE: Variables contained within angle brackets should be changed to the values that you obtained in step 1. NOTE: The value of <databasename> is the db instance that you create during the installation of the Foglight Management Sever.

CREATE LOGIN [<username>]

WITH PASSWORD = <password_hash> HASHED,

DEFAULT_DATABASE = [<databasename>],

DEFAULT_LANGUAGE = [us_english],

CHECK_EXPIRATION = OFF,

CHECK_POLICY = OFF;

3

Locate <FMS_HOME>\config\server.config, update server.database.host value to the FMS DB's Availability Group Listener IP.


	NOTE: For HA environment, both HA peers' server.database.host 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.


	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

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.

Table 2. Installed directories

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: Core-HostServices-compatibility-6_0_0.car

and FTR-WS-1_0_0.car

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.

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.

Various Foglight utilities.

UninstallerData

Files that the Foglight uninstaller uses.

Directory that the installer uses.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级

© ALL RIGHTS RESERVED. 使用条款隐私 Cookie Preference Center