Configuring the Embedded Agent Manager
Installing External Agent Managers
Understanding How the Agent Manager Communicates with the Management Server
Deploying the Agent Manager Cartridge
Downloading the Agent Manager Installer
Installing the Agent Manager
Configuring the Agent Manager
Installing the Agent Manager using the Installer Interface
Installing the Agent Manager from the Command Line
Using the Agent Manager Silent Installer
Installing the Agent Manager as a Windows Service
Starting or Stopping the Agent Manager Process
Frequently Asked Questions
How do I upgrade the Agent Manager?
How do I uninstall the Agent Manager?
Where can I find the Agent Manager installation log files?
Why does the message "Created system preferences directory in java.home" appear after I finish installing the Agent Manager on AIX?
Are the passwords that are stored in the configuration file, fglam.config.xml, encrypted?
How can I see what parameters are available for the silent installers?
Why are two URLs displayed for localhost when I search for HA peers?
I tested the connection between the Agent Manager and a Management Server, but the Management Server URL failed the connectivity test. Why did this happen?
When I try to install the Agent Manager using the installer interface on Solaris x86 VMware, it fails and a warning message related to fonts appears. Why does this occur?
Why does an AIX compatibility warning appear when I run the Agent Manager installer?
Operating System patches
Launching the Agent Manager Installation Interface
Configuring the Agent Manager from the Command Line
Configuring the Agent Manager to Use SSL Certificates
Configuring an Agent Manager Instance as a Concentrator
Advanced System Configuration and Troubleshooting
Configuring the Concentrator
Configuring Downstream Instances
Creating a Secure Connection with Downstream Instances
Excluding SSL Ciphers from Upstream or Downstream Connections
Configuring the Agent Manager to Accept Connections from the Management Server
Configuring Multiple Agent Manager Instances
Controlling the Polling Rate
Configuring Agent Managers to Work in High Availability Mode
Assigning Agent Managers to HA Partitions
Adding Cartridges to the HA Deployment Whitelist
About Agent Fail-Over
About Non-HA Deployments
Negotiating Agent Manager Resources at Runtime
How the Agent Manager Applies Configuration Settings
Configuration Example
Moving Existing Out-of-Process Agents to the Runtime Resource Negotiation
Disabling Runtime Resource Negotiation
Configuring Credentials
Troubleshooting
Configuring Windows Management Instrumentation (WMI)
Monitoring the Agent Manager Performance
Windows Firewall Interference
Minimum Requirements for Windows Management Instrumentation
Configuring Windows Remote Management (WinRM)
Promoting remote users to administrators on local machines through the Domain Controller
Granting required permissions to individual remote users
WMI Access Violation and OS Connectivity Verification Failure
WMI and Quota Violation Error
Known WMI Issues in Windows Server 2008
Modifying Registry Key Ownership on Windows Server 2008 R2
Configuring Registry Settings for Windows Server 2008 R2 and Windows 7
Resolving Access Denied Errors when Connecting to Windows XP Professional
OS Collection Fails with a Local_Limit_Exceeded Error
Access to DCOM Objects and Registry is Denied
Configuring Registry Settings for WinShell Access through DCOM
Enabling Agents to Connect from UNIX Machines
Enabling Agents to Connect Locally on Windows
Releasing a Locked MySQL Process
Generating a Configuration File Required for WinRM Negotiate Authentication
About the Cross-Realm Negotiate Authentication Behavior
About WinRM Authentication and the Agent Manager
Configuring the Target (Monitored) System
Configuring the Agent Manager (Monitoring) System
Configuring the Command-Shell Connection Settings
Available WinRM Connection Schemes when the Agent Manager Runs on AIX
About WinRM Connection Ports
Troubleshooting
UNIX- and Linux-Specific Configuration
About the Supported Remote Monitoring Protocols
Configuring the Agent Manager to Run as a Daemon
Configuring Agent Manager Agent Privileges
Using Sudo to Configure Secure Launcher Permissions
Using setuid_launcher to Configure Secure Launcher Permissions
Using the HP Patch Checking Tool
About Agent Manager Installations on AIX
Preventing Agent Manager Core Dumps on Linux
Investigating Agent Manager Diagnostics
Deploying the Agent Manager to Large-Scale Environments
Using Agent Manager Silent Installer Parameters
Example: Deploying the Agent Manager to Multiple UNIX Hosts
Example: Deploying the Agent Manager to Multiple Windows Hosts
Next Steps
Configuring the Embedded Agent Manager
This guide provides instructions for installing, configuring, and starting the Foglight™ Agent Manager. Before you begin, refer to the Foglight System Requirements and Platform Support Guide, and the Foglight Installation and Setup Guide set.
This guide provides installation instructions for both Windows® and UNIX® operating systems. Commands are listed separately for each OS. Generic examples follow the UNIX path structure that uses forward slashes '/' to separate directories; substitute the back slash where necessary for your operating system.
Getting Started
An instance of the Foglight™ Agent Manager is automatically installed with new installations of the Foglight 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.
|
• |
Foglight is installed in High Availability (HA) mode. If you want to run the Agent Manager on the Management Server machines in your HA cluster, you must install, configure, and run separate (non-embedded) Agent Manager instances on these machines. See Installing External Agent Managers for instructions. For more information about High Availability mode, see the High Availability Field Guide. |
|
• |
The Management Server is a Federation Master. The embedded Agent Manager does not start if you install Foglight as a Federation Master. See the Federation Field Guide for more information about federation. |
If you are running the Management Server as a Windows® service, the embedded Agent Manager continues to run when you log out of the machine on which the embedded Agent Manager and the Management Server are running.
An embedded instance of the Agent Manager automatically installs with the Management Server. You can deploy agents to the embedded Agent Manager. You can specify whether or not the embedded Agent Manager runs in tandem with the Management Server by changing the value of the server.fglam.embedded parameter in the server.config file.
|
2 |
On the Management Server machine, open <foglight_home>/config/server.config for editing. |
|
3 |
Set the parameter server.fglam.embedded to the desired value: |
|
• |
To have the embedded Agent Manager stop and start automatically with the Management Server, set server.fglam.embedded to true. |
|
• |
|
4 |
Save your changes to the server.config file. |
Interacting with the Embedded Agent Manager
You can run the configuration interface from the embedded Agent Manager installation directory, <foglight_home>/fglam/bin.
|
1 |
|
IMPORTANT: On UNIX® platforms, if you attempt to run the installation interface, and the DISPLAY environment variable is not set on the machine, the Agent Manager defaults to the command-line interface. |
|
4 |
Follow the appropriate set of instructions provided in To launch the Agent Manager Installation and Configuration interface: or To launch the Agent Manager configuration command-line interface: for proceeding through the configuration interface steps. |
Aside from setting the host name and port for the Management Server with which it communicates (described in Automatic Configuration of the Management Server Host Name and Port below), you can configure the embedded Agent Manager as you would a standalone Agent Manager.
Automatic Configuration of the Management Server Host Name and Port
When configuring the embedded Agent Manager, you do not need to set the host name and port number of the Management Server with which it communicates. The embedded Agent Manager automatically sets the host name and port number of the Management Server that starts it in its configuration file, fglam.config.xml, which is located in the <foglight_home>/fglam/state/default/config/ directory.