Installing the Agent Manager from the command line

This section covers the following key areas:

The command-line installer prompts you for information and informs you of the progress of your installation. To install the Agent Manager from the command line:

  1. UNIX platforms only. If required, change the permissions for the installer file to make it executable.
  2. Launch a command shell on the target machine and navigate to the directory to which you downloaded the installer.

    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.

  3. Run the installer executable by issuing the following command: FglAM-- –headless Where and reflect the platform of the machine on which the Agent Manager is about to be installed and its version number.

    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 –allowunsecured option: FglAM--.exe –headless–allow-unsecured

    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--.exe –headless –no-start-on-exit

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

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

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.

  • Complete one of the following steps:
    • To accept the default settings, click Enter.
    • To edit the path to point to a different sudo executable, type that path and click Enter.
    • To edit the path to point to the executable for a sudo-like application, type that path and click Enter.

      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.

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.

The system calls the quest-fglam script when the host on which the Agent Manager is installed starts up or shuts down. 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.

  1. 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 click Enter. Then, continue to Step 10: Summary.
    • To apply customized configuration options, type N, and click Enter. Then, proceed to Step 2.
  2. Using the Select the Unix/Linux distribution menu, specify the number in the identifies your operating system.

    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, click Enter.
    • To specify a different operating system, type the number associated with it, and click Enter.
  3. 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, click Enter.
    • To specify a different user account, type its name and click 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, click Enter. To specify a different user, type N and click Enter.

At the prompt, specify the user name.

  1. Type the number that corresponds with a run level to select a run level and click Enter.
  2. Type 0 and click Enter.
  3. If you want the Agent Manager process to start immediately after the installation, click Y, and then Enter.

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

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.

If you intend to use gMSA authentication you must install the Agent Manager as a service.

  1. Complete one of the following steps:
    • To install the Agent Manager as a Windows service, click Enter.
    • If you do not want to install the Agent Manager as a Windows service, type N and click Enter.
  2. If you want the Agent Manager process to start immediately after the installation, click Y, and then Enter.

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