サポートと今すぐチャット
サポートとのチャット

Foglight for JMX 5.9.8 - User Guide

Foglight for JMX System Requirements Installing Foglight for JMX Managing JMX Agents Managing MBean Server Models Monitoring and Investigating JMX Data

Creating and Activating a JMX Discovery Agent

Before attempting this procedure, ensure that you have successfully completed Deploying the JMX Discovery Agent Package.

2
In the HostSelector box, select the host to which you have deployed the JMXDiscoveryAgent. gar package, and then click Next.
3
In the Agent Type list, select JMXDiscoveryAgent, and then click Next.
To specify a custom name for the agent,select the Specify Name check box, and then type the name in the Name box.
5
Click Next.
6
View your selections in Summary, and then click Finish.
7
Locate the new agent in the Agents table and select it.
8
Click Activate.

Next, create the JMX Agent using local process discovery through the setup wizard on the Application Servers Administration dashboard.

Creating a JMX Agent Using Local Process Discovery

Before attempting this procedure, ensure that you have successfully completed Deploying the JMX Discovery Agent Package and Creating and Activating a JMX Discovery Agent.

1
On the navigation panel, under Dashboards, click Application Servers > Administration.
3
Select JMX (Discovery).
4
On the Discovery Hosts page of the JMX - Setup Agents using Discovery wizard, select one or more monitored hosts on which you want to discover processes.
Click Next.
5
On the Identifying Properties page, define the set of identifying system properties that must be matched to enable process monitoring.
Click Add Property to manually add a property.
Select the Use Reg Ex check box if you want to use regular expressions. By default, this option is disabled.
Click Property Lookup to retrieve a list of available system properties.
a
Select the host from the Discovery Host list.
c
The list of System Properties refreshes based on your selection.
e
Click Add. The System Property Lookup dialog box closes. Click Next.
b
Optional — To edit the agent naming scheme, click the edit icon at the bottom of the dialog box. The Edit Agent Naming Scheme dialog box opens, allowing you to change the naming scheme that is automatically assigned to agents whenever you use this configuration to create agents.
c
Click Next.
Click Next.
Select either Use the default or Assign the following Server Group. If you select Assign the following Server Group, you can either choose an existing group from the list, or define a new group.
Click Next.
Optional — To save the configuration for later reuse, click Save setup as Discovery Template. In the box that opens, type a name for the configuration. This option saves all your settings, including the agent naming scheme.
Click Finish.
Click the message in the Result column to open the Task Result dialog box and view the details of the task.
Use the JMX > Explorer dashboard to view the MBean data. For more information, see Monitoring and Investigating JMX Data..
View data collected by the agent in the Application Servers > Monitor dashboard. See the Monitoring Application Servers User and Reference Guide or help for more information.

Creating JMX Agents and Server Models from the Command-Line

As an alternative to creating and managing JMX agents and server models through the Foglight browser interface, you can use the fglcmd command-line scripts that are available on the Foglight Management Server. This allows you to automate the creation of a large number of agents or server models.

You can also access help for the scripts from the command-line by typing: fglcmd /h.

The following JMX-specific commands are available:

createagent

Creates an agent called <NAME> on <HOST> (or <remoteClientId>) using server model ID <ID> with the given configuration settings. Either <HOST> or <remoteClientId> must be specified, but not both.

 

<remoteClientId> is the Remote Client ID of the Agent Manager on which the JMX agent must be created.
<ENV PROPS> is a comma-separated list of "name=value" pairs. <CLASSPATH> is a comma-separated list of paths.
<ACTIVATE> is a boolean indicating whether the agent is automatically activated after creation, and defaults to true.

 

Example:

jmx:createagent -name <NAME> -host <HOST> -serverModel <ID> ‑jmxServiceUrl <URL> [-username <USERNAME>] [‑password <PASSWORD>] [-connectionRetryInterval <CONNECTION RETRY INTERVAL>] [-serverGroup <SERVER GROUP>] [-jvmDataPort <JVM DATA PORT>] [-envProps <ENV PROPS>] [‑classpath <CLASSPATH>] [-activate <ACTIVATE>]

Or:

jmx:createagent -name <NAME> -remoteClientId <remoteClientId> -serverModel <ID> ‑jmxServiceUrl <URL> [-username <USERNAME>] [‑password <PASSWORD>] [-connectionRetryInterval <CONNECTION RETRY INTERVAL>] [-serverGroup <SERVER GROUP>] [-jvmDataPort <JVM DATA PORT>] [-envProps <ENV PROPS>] [‑classpath <CLASSPATH>] [-activate <ACTIVATE>]

deleteagent

Deletes the agent specified by <NAME>.

Example:

jmx:deleteagent -name <NAME>

updateagent

Updates the agent specified by <NAME> with the given configuration settings.

Example:

jmx:updateagent -name <NAME> -jmxServiceUrl <URL> [-username <USERNAME>] [-password <PASSWORD>] [-connectionRetryInterval <CONNECTION RETRY INTERVAL>] [‑serverGroup <SERVER GROUP>] [-jvmDataPort <JVM DATA PORT>] [-envProps <ENV PROPS>] [-classpath <CLASSPATH>]

createservermodel

Creates a new server model with id <ID>, optionally setting its name to <NAME>, description to <DESC> and copying the configuration from server model <ID2>.

Example:

jmx:createservermodel ‑id <ID> [‑name <NAME>] [‑desc <DESC>] [‑copy <ID2>]

deleteservermodel

Deletes the server model specified by <ID>.

Example:

jmx:deleteservermodel ‑id <ID>

listservermodels

Prints a list of all defined server models.

jmx:listservermodels

updateservermodel

Updates the name and/or description of a specified server model.

Example:

jmx:updateservermodel ‑id <ID> [‑name <NAME>] [‑desc <DESC>]

exportservermodel

Exports the configuration for a server model as an XML file.

Example:

jmx:exportservermodel -file <file path> -serverModel <name>

importservermodel

Imports the server model configuration that was previously exported as an XML file.

Example:

jmx:importservermodel -file <file path> [-newName <new name>] [- replace <boolean> ]

2
Navigate to the <foglight_home>/bin directory. By default, the path is: C:\Quest_Software\Foglight\bin.
4
Type the following command to create an agent named OASAgent1, using the server model OracleAS_1:

Managing JMX Agents

After you create a JMX agent, you can manage it from the Application Servers Administration dashboard. Click the agent name to open a list of options.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択