Foglight Agent Manager 5.9.1 - Foglight Agent Manager Guide


	IMPORTANT: On Windows® 7 and Vista, you must run the command-line installer from an administrator version of cmd.exe or PowerShell (not just logged in as administrator) if you want the installer to install the Agent Manager as a service.

Run the installer executable by issuing the following command:

FglAM-<version>-<platform> --headless

Where <platform> and <version> reflect the platform of the machine on which the Agent Manager is about to be installed and its version number. Consult the matrix in Downloading the Agent Manager installer for more information.


	IMPORTANT: If you want to configure the Agent Manager to accept upstream HTTP connections during the installation, you must start the installer on the command line with the --allow-unsecured option: FglAM-<version>-<platform>.exe --headless --allow-unsecured


	NOTE: If you want to install the Agent Manager as a Windows service, or as a Unix deamon, the default values in the related installation steps, if selected, cause the Agent Manager Windows service or Unix deamon to start immediately after the installation. You can override these defaults during the installation, or by starting the installer executable with the --no-start-on-exit option: FglAM-<version>-<platform>.exe --headless --no-start-on-exit For more information about these options in the installation interface, see Step 8: Install init.d Script (Unix) and Step 9: Windows Service .

The command shell displays messages indicating that the installer files are being extracted to a temporary directory, and that the installer is starting up.


	TIP: To cancel the installation at any time, press Ctrl-C.

Step 1: Introduction

When the installer finishes loading, the Introduction step appears.

•

Review the information in the Introduction step and press Enter.

Step 2: License Agreement


	NOTE: You must accept the license agreement before you can install the product.

When the first part of the License Agreement step appears, press Enter to page through the license agreement.

At the prompt Do you accept the terms of the license agreement? [Y/N], type Y and press Enter to accept the terms, and to continue the installation.


	IMPORTANT: If you are running an AIX® operating system with IPv6 support enabled and the Agent Manager installer detects problems resolving IP addresses and host names, an AIX compatibility warning appears. This warning provides information about an alternate command-line option for running the installer and a URL that you can consult for more information. See Frequently asked questions for more information.

Step 3: Installation Directory

The Installation Directory step allows you to specify the directory where you want to install the Agent Manager.

•

Complete one of the following steps:

•

To accept the default installation directory, press Enter.

•

To specify a different installation directory, type it at the command prompt, and press Enter.

If the specified directory does not exist, the installer prompts you regarding whether or not you want it to be created. To create the directory, press Enter. To return to the Install directory prompt and specify a different directory, type N and then press Enter.

If the Agent Manager is already installed in the directory, you must specify a different directory. The installer informs you if the Agent Manager is already installed in the directory, provides information about performing upgrades, and prompts you to select a different directory.

Step 4: Host Display Name

The Host Display Name step allows you to configure the host name that the Agent Manager uses to identify itself. This is also the name under which the Agent Manager submits metrics to the Management Server.

By default, the Agent Manager uses the host name that is automatically detected for the machine on which it is being installed.

There are certain cases in which you should explicitly set the host name in this box: for example, if the host name is already in use by another machine. If necessary, you can replace the host name with a different (non-host name) value that suits the needs of your environment; for example, WebServer (Unix Cluster 1) or 12345.example.com (Databases).

Complete one of the following steps:

•

To accept the detected host name, press Enter.

•

To use a different host name, type the host name and press Enter.

The Log a warning if the detected host name changes prompt appears.

This allows you to configure the Agent Manager to log a warning message when it starts if the specified host name differs from the automatically detected host name. If logged, this message appears in the console when you start the Agent Manager and in the Agent Manager log file.

If you want the Agent Manager to log a warning, press Enter.

If you want to suppress warning messages, or the machine on which you are installing the Agent Manager is configured with multiple IP addresses or host names, type N and press Enter.

Step 5: Server URLs

The Server URLs step provides multiple ways to configure the connection between the Agent Manager and the Management Server. For example, you can specify the URL of a single Management Server to which you want the Agent Manager to connect, or configure multiple Management Server URLs for failover purposes. You can also specify the URL of an Agent Manager concentrator to which you want the Agent Manager to connect.


	NOTE: You can configure Management Server URLs at a later time using the Agent Manager configuration interface. See Configuring the Agent Manager for information about launching this interface post-installation.

Add a new Management Server URL.

Type 1 and press Enter.

Review the information on the screen about the available parameters. See also Configuring Management Server URLs from the command line for information about these parameters.

When prompted, type the URL of a Management Server or Agent Manager concentrator to which you want the Agent Manager to connect, followed by the applicable parameters. For example:

url=http://localhost:8080,address=127.0.0.1,proxy=http://proxy.server

Press Enter.

A message appears, indicating that the Management Server URL is added.

If you want this Agent Manager to connect to additional Management Server URLs, for example, for failover purpose repeat these steps.

To review a list of newly added URLs, type 4 and press Enter.

A numbered list of configured Management Server URLs appears on the screen.

To remove a URL, complete the following steps.

Type 7 and press Enter.

A numbered list of configured Management Server URLs appears on the screen.

Type the number identifying the URL that you want to delete and press Enter.

A message appears, indicating that the Management Server URL is deleted.

Test the connections between the Agent Manager and the Management Servers.

Type 3 and press Enter.

A message appears, indicating the test progress. When the test is complete, the menu options appear on the screen.

To see if the configured URLs passed the connectivity test, type 4 and press Enter.

A numbered list of configured Management Server URLs appears on the screen. Any URLs that fail the connectivity test are marked with an ‘x’ on the left. To find why a URL may fail the connectivity test, see Frequently asked questions .

The menu options appear on the screen.

If required, search for other Management Servers that are configured to be part of the same HA (High Availability) partition.


	IMPORTANT: You can specify URLs for both Management Servers and Agent Manager concentrators. However, only Management Servers can have HA (High Availability) peers, not concentrators. Searching for HA servers does not cause any concentrators to be added to the list of URLs.

To search for additional HA servers, type 3 and press Enter.

The installer searches for HA peers and tests the connections. A message appears informing you of the progress.

If you specify a localhost address at the URL prompt (described in Step 1), and then search for HA peers, a URL that shows the real machine name appears along with the localhost URL. See Frequently asked questions for more information.

When the search is complete, the menu options appear on the screen.

To verify if the installer found HA peers and added them to the list, type 4 and press Enter.

A numbered list of configured Management Server URLs appears on the screen. Any URLs that fail the connectivity test have an ‘x’ on their left. To find why a URL may fail the connectivity test, see Frequently asked questions .

The menu options appear on the screen.

You can also manage SSL Certificate CAs from the Server URLs menu. For more information, see Configuring the Agent Manager to use SSL certificates.

To view a list of all certificates currently in the certificate store, type 6 and press Enter.

To add a new SSL Certificate Authority (CA), type 2 and press Enter.

Type the alias and file names of the SSL CA certificate using the following syntax:

alias=file_name

Where

alias is the name that you want to associate with the certificate.


	NOTE: The alias must be unique.

file_name is the full path to the certificate file.

For example, on a Windows machine, you can type the following: NewCert1=C:\certificates\example_ca_certificate.crt

Press Enter.

To remove a certificate from the certificate store, type 8 and press Enter.

If you want to enable the Agent Manager to accept connections from the Management Server, or downstream Agent Managers that use it as a concentrator, configure the ports that you want to use to listen for these types of connections. For more information, see Configuring the Agent Manager to accept connections from the Management Server.

Type 9 and press Enter.

Specify the protocol type (HTTP or HTTPS) and the port number that you want the Agent Manager to listen on. Type them, as prompted, using the following syntax:

port=<port>,type=<http|https>

Press Enter.

To specify additional ports, repeat Step a through Step c.

When you are finished adding Management Server URLs and managing SSL certificate CAs, type 0 and press Enter.


	IMPORTANT: If you did not configure any Management Server URLs, if there are URLs listed that have not been tested, or if there are URLs listed that failed the connectivity test, the installer prompts you to confirm that you want to continue.

Continue with Step 6: Downstream Connection Configuration.

Step 6: Downstream Connection Configuration

Foglight Agent Manager can accept incoming connections and be configured as a concentrator that acts as an intermediary connection to aggregates one or more downstream Agent Manager clients. A concentrator configuration provides a single connection through either a firewall or proxy for all downstream clients, or as an aggregated connection directly to the server.

Configuring the Agent Manager to act as a concentrator involves configuring queue and heap sizes to adequately support accepting and transferring data from one or more downstream connections. You can configure downstream connections when the Agent Manager needs to accept connections from the Management Server and enable reverse data polling. This is useful when the Agent Manager cannot connect to the Management Server due to its location.

Using this installer step, you can configure:

•

Downstream SSL connections, when a certificate host name and a password are provided.

•

Downstream non-SSL connections, but only if you started the installer on the command line with the
--allow-unsecured option (as instructed in Installing the Agent Manager using the installer interface ).

User-provided certificates or keystores are supported, but can be configured after the installation.

If you are configuring the Agent Manager as a concentrator in order to enable connections from the Management Server, additional setup is required. For more information about this procedure, or to find out to configure non-SSL connections and user-provided certificates, see Configuring the Agent Manager to accept connections from the Management Server .

To enable downstream connections, type Y, and press Enter.

To set the queue and memory sizes, type the number associated with the desired size of the queue and heap, and press Enter.

Type the port number that you want the Agent Manager to use to listen for downstream connections, and press Enter.

Type the SSL certificate password, and press Enter. Retype the password, and press Enter.


	NOTE: The passwords are not visible on the screen as you type them.

Type the name of the host on which you are installing the Agent Manager. The host name you specify here is added to the SSL certificate that is to be generated.

If you are installing the Agent Manager on Windows, proceed to Step 9: Windows Service . Otherwise, continue with Step 7: Secure Launcher and Step 8: Install init.d Script.

Step 7: Secure Launcher

UNIX platforms only.

The Secure Launcher step defines the external launcher used by the Agent Manager to provide certain Foglight agents with the required permissions to gather system metrics. See Configuring Agent Manager agent privileges for more information.

•

Complete one of the following steps:

•

To accept the default settings, press Enter.

•

To edit the path to point to a different sudo executable, type that path and press Enter.

•

To edit the path to point to the executable for a sudo-like application, type that path and press Enter.


	IMPORTANT: After the installation is complete, you must edit the sudoers file for your system. If you are using a privilege-escalation tool other than sudo (for example, setuid_launcher), you must make changes related to that application. Follow the appropriate set of instructions in “Using Sudo to Configure Secure Launcher Permissions” on page 88.

Step 8: Install init.d Script

UNIX platforms only.

The Install init.d Script step allows you to configure the Agent Manager to run as a daemon. You do that by instructing the installer to installing an init.d-style script called quest-fglam in the init.d directory on your system. See Locating the init.d script for the location of this directory on your operating system.

The system calls the quest-fglam script when the host on which the Agent Manager is installed starts up or shuts down. See Configuring the Agent Manager to run as a daemon for more information.

Installation as the root user only: The installer prompts you to specify whether you want to install the init.d script.

Installing as a non-root user only: The installer does not prompt you to specify whether you want to install the init.d script. However, the installer generates two scripts that perform the necessary setup for later use. See Configuring the Agent Manager to run as a daemon for more information.

In the UNIX init.d Script step, complete one of the following steps:

•

If you want to use the default configuration options, type Y, and press Enter. Then, continue to Step 10: Summary.

•

To apply customized configuration options, type N, and press Enter. Then, proceed to Step 2.

Using the Select the Unix/Linux distribution menu, specify the number in the identifies your operating system.


	IMPORTANT: Even if you choose not to install the init.d script, or if you are not performing the installation as the root user, it is recommended that you configure as many options as possible in this step, and in the subsequent Install UNIX/Linux init.d Scripts steps. These options are used when generating the two scripts for later use.

•

To accept the detected value, press Enter.

•

To specify a different operating system, type the number associated with it, and press Enter.

At the Enter the user the service will run as prompt, specify the user account that runs the Agent Manager daemon.

•

To accept the default (current) user, press Enter.

•

To specify a different user account, type its name and press Enter.

If you choose to have the Agent Manager run as a different user than the one who performed the installation, then that user account must already exist in the system. This user becomes the owner of the <fglam_home> directory and all files within it, including all state directories.

If the user specified at this prompt is not a local user, the installer displays a warning and prompts you to specify whether you want to continue.

To continue with the specified user, press Enter.

To specify a different user, type N and press Enter. At the prompt, specify the user name.

Type the number that corresponds with a run level to select a run level and press Enter.


	IMPORTANT: These numbers signify different run levels on different UNIX platforms. Consult your UNIX system administrator for more information.

Type 0 and press Enter.

If you want the Agent Manager process to start immediately after the installation, press Y, and then Enter.


	NOTE: The default answer to this question is Y (Yes). However, if you started the installer with the --no-start-on-exit option, the default answer to this question is set to N (No). For more information, see Installing the Agent Manager from the command line.

Continue with Step 10: Summary.

Step 9: Windows Service

Windows platforms only.

The Windows Service step allows you to specify if you want to install the Agent Manager as a Windows service. A Windows service operates in the background while the system on which it is installed is running. Installing the Agent Manager as a Windows Service causes the Agent Manager to start automatically on your system startup.

Complete one of the following steps:

•

To install the Agent Manager as a Windows service, press Enter.

•

If you do not want to install the Agent Manager as a Windows service, type N and press Enter.

If you want the Agent Manager process to start immediately after the installation, press Y, and then Enter.


	NOTE: The default answer to this question is Y (Yes). However, if you started the installer with the --no-start-on-exit option, the default answer to this question is set to N (No). For more information, see Installing the Agent Manager from the command line.

Step 10: Summary

The Summary step informs you that the installer has sufficient information to complete the Agent Manager installation.

•

Press Enter to complete the installation and exit the command-line installer.

The Agent Manager installer calculates the amount of disk space required to complete the installation, and copies the required to the machine on which it is being installed.


	NOTE: Unix platforms only. If the user account that you used to install the Agent Manager has no root privileges, the init.d-style script is not installed. Messages appear that inform you that the script is not installed due to insufficient user permissions and provide the path to the script installer and a copy of the script file.

If you choose to install it as a Windows service, the Agent Manager starts automatically.


	NOTE: The Agent Manager starts automatically when the installation is complete only when it is installed as a service on Windows. It does not start automatically at the end of an installation on a UNIX platform.

Configuring Management Server URLs from the command line

As described in Step 5: Server URLs of Installing the Agent Manager from the command line and Using the Agent Manager silent installer , you can configure the Foglight™ Agent Manager connection parameters using the fglam command and the arguments passed to its fms command option. For example:

fglam --headless --configure --fms url=http://localhost:8080, address=127.0.0.1,

proxy=http://proxy.server


	NOTE: For complete information about the fglam command, see “Managing the Foglight Agent Manager” in the Command-Line Reference Guide.

Syntax

fglam --headless --configure [--fms url={http|https}://host:port

[proxy={http|https}://host:port [proxy-user=user_name] [proxy-pass=password]

[proxy-ntlm-domain=domain]] [address=IP_address]

[ssl-allow-self-signed={true|false}] [ssl-cert-common-name=name]

[compressed={true|false}]][[--downstream "<port=<port>,key-password=<password>>

[--deletedownstream <port>]|[--deletealldownstream]]

Table 3. Options and arguments
Option	Argument		Mandatory or Optional?	Description
Option	Name	Value	Mandatory or Optional?	Description
headless			Mandatory	Launches the Agent Manager and configuration interface on the command line, when used with the configure option.
configure			Mandatory	Launches the Agent Manager and configuration interface.
fms			Mandatory	Specifies the URL to the Management Server that you want to configure.
	url	http\|https://host:port	Mandatory	The URL to the Management Server, where host and port specify the host name of the machine on which the Foglight Management Server is installed, and the port number the server uses to communicate with the Foglight Agent Manager.
	proxy	http\|https://host:port	Optional	The URL to the proxy server needed to connect to the Management Server.
	proxy-user	user_name	Optional	The user name needed to connect to the proxy server.
	proxy-pass	password	Optional	The password associated with the user name needed to connect to the proxy server. The password is saved encrypted in the Agent Manager configuration file (<fglam_home>/state/<state name>/config/fglam.config.xml) the next time you start or restart the Agent Manager
	proxy-ntlm-domain	domain	Optional	The Windows domain to which the proxy server belongs.
	address	ip_address	Optional	The IP address of the Foglight Agent Manager that is used to connect with the Foglight Management Server.
	ssl-allow-self-signed	true\|false	Optional	Indicates if self-signed certificates are accepted (true) or not (false).
	ssl-cert-common-name	name	Optional	The common name of the expected certificate. Specifying this argument causes a certificate with a common (host) name, that is different than the one reported by the Management Server, to be accepted.
	compressed	true\|false	Optional	Indicates if HTTP compression is enabled (true) or disabled (false). HTTP compression is enabled by default. When enabled, it is applied to both request and responses, and used when connecting to either Agent Management concentrators or Management Servers.
downstream	port	port	Mandatory	When used with --configure, this option creates a downstream connection. The port argument specifies the number of the port the Agent Manager uses to listen for downstream connections.
	key-password	password	Mandatory	This argument specifies the password needed to access the private key contained in the keystore.
	host	host	Optional	Specifies the host name to be set in the certificate.
	type	http\|https	Optional	Specifies the type of the supported protocol.
	size	Small	Optional	Specifies the amounts of the disk and memory resources. Small allocates 10 MB for the disk queue and 512 MB of memory.
		Medium		Medium allocates 100 MB for the disk queue and 768 MB of memory.
		Large		Large allocates 500 MB for the disk queue and 1 GB of memory.
		Huge		Huge allows unlimited amounts of disk space for the queue, and up to 4 GB or 85% of system memory, whichever is less.
		Maximum		Maximum allows unlimited amounts of disk space for the queue, and 85% of available system memory.
deletedownstream	port	port	Mandatory	When used with --configure, this option deletes a downstream connection given its port number.
deletealldownstream				When used with --configure, this option deletes all downstream connections.

Removing Management Server URLs

In addition to managing connections to the Management Server from the command line, the fglam command also provides arguments for removing Management Server URLs, when required. You can delete one URL at a time, or all of them, as required. Deleting all Management Server URLs can, for example, be useful in situations when you need to migrate an Agent Manager from oneManagement Server to another.

To delete a single Management Server URL:

•

Issue the following command:

fglam --headless --configure --deletefms url=<http|https>://

To delete all configured Management Server URLs:

•

Issue the following command:

fglam --headless --configure --deleteallfms

In some configuration scenarios, after dissociating your Agent Manager from one or all of your Management Servers, you typically need to connect it to another Management Server. The fglam command is flexible enough to allow for multiple operations on a single command line, as long as you first specify the arguments to first delete the existing URLs, and then add a new one. For example:

fglam --headless --configure --deleteallfms --fms url=http://Host1:8080

Detecting HA Servers

The fglam command also allows you to detect High Availability (HA) failover servers (peers) using its detectha argument. When used with the configure option, this option instructs the installer to detect and test any available Management Server HA peers.

fglam --headless --configure --detectha

Using the Agent Manager silent installer

The Agent Manager silent installer allows you to install the Agent Manager non-interactively—for example, to install the Agent Manager from the command line onto a remote, headless machine.


	CAUTION: The silent installer is an advanced tool. It should be used cautiously and only by advanced Foglight administrators.Do not run the installer in silent mode unless you are an advanced Foglight administrator who is familiar with configuring the Agent Manager and you are certain what setup is required for your environment. If you are not certain which installation options you need, use the installer interface or command-line installer instead.

If you are running Foglight™ in High Availability (HA) mode, you can configure the Agent Manager to work with a set of primary and secondary Management Servers in an HA cluster.

To install the Agent Manager using the silent installer:

If you are installing the Agent Manager onto a remote machine, log in to the target machine (for example, using SSH).

Launch a command shell on the target machine and navigate to the directory to which you downloaded the installer.

On UNIX® platforms, if necessary, change the permissions for the installer file so that it is executable (as described in To download and run the Agent Manager installer using the Agent Managers or Agent Status dashboard: ).

Run the installer executable with the --silent option.


	IMPORTANT: On Windows® 7 and Windows Vista®, you must run the silent installer from an administrator version of cmd.exe or PowerShell (not just logged in as administrator) if you want the installer to install the Agent Manager as a service.


	IMPORTANT: The --silent option is an advanced option. It should be used cautiously and only by advanced Foglight administrators.

All desired installation parameters must be included in the command with the ‑‑silent option, using the following syntax:

fglam‑<version>‑<platform> --silent --installdir <install_directory_path>

[--fms <url_and_other_parameters>] [--noservice] [--host-display-name

<display_name>] [--spid <path_to_SPID>] [--certificate <alias=path>]

[--downstream "<port=<port>,key-password=<password>>[,type=<https|http>,

host=<host>,size=<Small|Medium|Large|Huge|Maximum>]"] [--allow-unsecured]

[--no-start-on-exit] [-h|--help] [-v|--version]

[<-j|--javavm> <path>] [--installer-properties <file_path>]

[--headless] [auth-token <token>] [--noservice] [--host-display-name <name>]

[--detectha]

Where:

•

silent prevents the installer from prompting for configuration options. It uses default values unless they are specified on the command line.

•

<version> is the version number of the Agent Manager.

•

<platform> is the appropriate installer name for your operating system. Consult the matrix in Downloading the Agent Manager installer for the installer name.

•

<install_directory_path> is the full path to the directory where you want to install the Agent Manager. The installdir option is mandatory.


	IMPORTANT: Ensure that there is no existing installation of the Agent Manager in the directory that you specify with the --installdir <install_directory_path> parameter. If there is an Agent Manager installation in the directory, you must specify a different directory or the installer fails. The installer aborts, to protect you from overwriting your existing installation. Consult the Foglight Upgrade Guide for upgrade instructions.

You can also include the following optional command-line options:

•

--fms <url_and_other_parameters>, where <url_and_other_parameters> is a comma-separated list of parameters for configuring the connection to a Management Server. See Configuring Management Server URLs from the command line for a description of the parameters for the --fms option.

If you are running Foglight in High Availability (HA) mode, add the --fms option once for each member of the HA cluster to which you want the Agent Manager to connect. You must do so to configure the connection to more than one Management Server (or Agent Manager concentrator) within the cluster.

•

--noservice (on UNIX) prevents an init.d-style script from being installed (that would automatically start the Agent Manager). On Windows®, this option causes the Agent Manager not to be installed as a service.

•

--host-display-name <display_name>, where <display_name> is the host display name that you want to set manually for the Agent Manager. This is the host name that the Agent Manager uses to identify itself and the name under which it submits metrics to the Management Server. By default, the Agent Manager uses the host name that it automatically detects for the machine on which it is being installed. There are certain cases in which you should explicitly set the host display name: for example, if the host name is already in use by another machine.

•

--spid <path_to_SPID>, where <path_to_SPID> is the path to an existing SPID installation. This allows you to (optionally) migrate agents from an existing SPID installation to the new Agent Manager installation. The Agent Manager automatically detects any agents managed by SPID from the old installation and copies the agent instances to the new Agent Manager installation.

•

--certificate alias=<path> allows you to add an SSL certificate, where <path> is the directory path to the SSL certificate file.

•

--downstream allows you to create a downstream connection.

•

port=<port> specifies the number of the port the Agent Manager uses to listen for downstream connections. This argument is mandatory.

•

key-password=<password> specifies the password needed to access the private key contained in the keystore.

•

type=<https|http> specifies the type of the supported protocol.

•

host=<host> specifies the host name to be set in the certificate.

•

size=<Small|Medium|Large|Huge|Maximum> specifies the amounts of disk and memory resources that are allocated to downstream connections.

•

--allow-unsecured enables the configuration of HTTP downstream connections.

•

--no-start-on-exit prevents the Agent Manager Windows service or Unix daemon from starting immediately after the installation.

•

-h or --help lists the arguments available with the installer executable and exits.

•

-v or --version display the Agent Manager version number and exits.

•

-j or --javavm sets the location of the Java virtual machine, for example, the directory that JAVA_HOME points to.

•

--installer-properties sets the path to the installer properties file. This file contains the default installer values used during installation. Its contents must be in a Java Properties format and can include a mix of installer arguments and arbitrary properties for use by the installer runtime. All installer options can be defined here but must be prefixed with “installer.” and have the “--” removed from the argument name. All other argument value setting constraints still apply. For installer arguments that can be declared multiple times, a numeric value must be appended to the end of the property name in order to make the key unique. For example:

•

installer.fms.0=url=https://localhost:8443,ssl-allow-self-signed=true

•

installer.fms.1=url=https://127.0.0.1:8443,ssl-allow-self-signed=true

•

installer.headless

•

installer.downstream=type=http,port=15872,size=Large

•

custom.property.one=true

If the --installer-properties argument is not declared, the installer runtime searches for a file named installer.properties in the root directory of the installer binary, or in the extraction root directory of the installer payload. When located, the properties file is automatically loaded during startup.

•

--headless launches the Agent Manager and configuration interface on the command line. If not specified, the graphical interface is displayed.

•

--auth-token registers an authentication token during the installation. The token is generated from the Management Server and provides authorization for this Agent Manager to connect.

•

--noservice prevents the Agent Manager service from being installed on Windows. On UNIX, it prevents the installer from installing an init.d script that automatically starts the Agent Manager.

•

--host-display-name specifies the display name used to identify this Agent Manager instance.

•

--detectha locates and configures additionally available high availability (HA) servers.

For example, in stand-alone mode:

FglAM-<version>-windows-x86_64.exe --silent --fms url=http://serverA:8080
--installdir C:\Quest\Foglight_Agent_Manager --noservice

./FglAM-<version>-linux-x86_64.bin --silent --fms url=http://serverA:8080
--installdir /opt/Quest/Foglight_Agent_Manager --noservice

In HA mode:

FglAM-<version>-windows-x86_64.exe --silent --fms url=http://serverA:8080/
--fms url=http://serverB:8080/ --installdir C:\Quest\Foglight_Agent_Manager

./FglAM-<version>-linux-x86_64.bin --silent --fms url=http://serverA:8080/
--fms url=http://serverB:8080/ --installdir /opt/Quest/Foglight_Agent_Manager

Messages appear in the command-line window while the installer starts. Installer files are extracted to the location you specified in the --installdir parameter and the installer runs.


	NOTE: Install the Agent Manager on each host that you want to monitor with local agents.

Installing the Agent Manager as a Windows service

If you did not install the Agent Manager as a Windows® service using the installer, you can do so from the command line after installing the Agent Manager.

To install theFoglight™ Agent Manager Windows service:

Launch a Command Prompt window on the Agent Manager host machine and navigate to the <fglam_home>\bin directory.


	IMPORTANT: On Windows 7 and Vista, you must issue the command to manually install the Agent Manager as a Windows service using an administrator version of cmd.exe or PowerShell (not just logged in as administrator).