Getting Started
To get started, make sure the Foglight Management Server is running, and, if you are planning to access the server commands remotely, copy and extract the contents of the remotemonitor.zip file to your remote computer.
For more information about the Remote Monitor, see remotemonitor .
|
1 |
Copy the <foglight_home>/tools/remotemonitor.zip file from the computer that has a running instance of the Foglight Management Server to the remote computer. |
|
2 |
Extract the contents of the remotemonitor.zip file to a directory on the remote computer. For example, if you want to run the Remote Monitor on a Foglight Agent Manager computer, extract the remotemonitor.zip file to the <foglight_agent_mgr_home>/bin directory. |
|
3 |
Reference the directory that contains the Foglight Management Server commands, either <foglight_home>/bin or <foglight_agent_mgr_home>/bin, by completing one of the following steps: |
|
• |
If you want to use the command prompt, open a Command Prompt window (Windows®) or a terminal window (UNIX® or Linux®) and navigate to <foglight_home>/bin or <foglight_agent_mgr_home>/bin as required. |
|
• |
If you want to use a Foglight Management Server command in a script, ensure that your script references <foglight_home>/bin or <foglight_agent_mgr_home>/bin as applicable. |
From here, you can proceed to any of the following procedures as required:
Running the Server in Stand-Alone Mode
The fms command provides command-line interface to the Foglight Management Server process. It offers a set of options that allow you to perform any of the following operations as required:
|
• |
Configure JavaTM Virtual Machine (JVM) options and add entries to the Foglight classpath |
|
• |
fms
The fms command provides command-line interface to the Foglight Management Server process. It offers a set of options that allow you to perform any of the following operations as required:
|
• |
Configure JavaTM Virtual Machine (JVM) options and add entries to the Foglight classpath |
|
package.=debug_level |
For example, you can set the debug_level to one of the following values:
The period '.' following the package name is mandatory, otherwise the package is treated as a class. The package.=debug_level argument can be specified multiple times. | ||||||||
|
-Dquest.debug=debug_level |
Runs the Foglight Management Server in debug mode. For example, you can set the debug_level to one of the following values:
| ||||||||
|
Passes an option to the JVM, prefixed with -X or -D. For example: fms -Xdebug -Xrunjdwp:transport=dt_socket,server=y, suspend=n,address=1044 -Dquest.debug=2 | |||||||||
|
Removes a debug level associated with one or more packages. The period '.' following the package name is mandatory, otherwise the package is treated as a class. The package. argument can be specified multiple times. | |||||||||
|
Sets the global debug level. The debug_level argument must be a non-negative integer. Higher debug levels result in more detailed logging. For example, you can set the debug_level to one of the following values:
| |||||||||
|
Displays the version number, copyright, build number, and the installation directory. | |||||||||
|
Installs the Foglight Management Server as a Windows service. | |||||||||
|
Stops and removes the Foglight Management Server Windows service. | |||||||||
|
• |
Running the Server in High Availability Mode
The fmsha command provides a command-line interface to the Foglight Management Server process running in High Availability (HA) mode. Running Foglight in HA mode allows you to manage multiple instances of the Foglight Management Server in a JBoss® partition that supports the HA feature. For more information about the HA mode, see the Installation and Setup Guide.
This command offers a set of options that you can use to perform any of the following operations:
|
• |
Configure JavaTM Virtual Machine (JVM) options and add entries to the Foglight classpath |
[-p|--classpath class_path] [-v|--version] [-h|--help] [-t|--thread-dump]
|
NOTE: If you do not specify any options, fmsha uses the default option, s, and starts an instance of the Foglight™ Management Server in HA mode. |
|
package.=debug_level |
Specifies a debug level for one or more packages. Higher debug levels result in more detailed logging. For example, you can set the debug_level to one of the following values:
The period '.' following the package name is mandatory, otherwise the package is treated as a class. The package.=debug_level argument can be specified multiple times. | ||||||||
|
Passes an option to the JVM, prefixed with -X or -D. For example: fmsha -Xdebug -Xrunjdwp:transport=dt_socket,server=y, suspend=n,address=1044 -Dquest.debug=2 | |||||||||
|
Removes a debug level associated with one or more packages. The period '.' following the package name is mandatory, otherwise the package is treated as a class. The package. argument can be specified multiple times. | |||||||||
|
Sets the global debug level. The debug_level argument must be a non-negative integer. Higher debug levels result in more detailed logging. For example, you can set the debug_level to one of the following values:
| |||||||||
|
Displays the version number, copyright, build number, and the installation directory. | |||||||||
|
Installs the Foglight Management Server as a Windows service. | |||||||||
|
Stops and removes the Foglight Management Server Windows service. | |||||||||
|
• |