|
To set-up the monitoring of a generic JMX client, right-click the main Monitoring Studio icon > KM Commands > New > Java MBean polling (JMX) and select the environment Generic from the drop-down list:
Java MBean Polling Wizard (Generic Environment) — Welcome Page
 The application server should be started with the option: -Dcom.sun.management.jmxremote.port=portNumber
Using the above option starts a dedicated JMX agent for this particular application. The Monitoring Studio generic JMX client needs to use this port number to establish a connection.
Step 1: Enter the generic environment connection information
Java MBean Polling Wizard (Generic Environment) — Connection Information Page
| • | Host: Name of host server where the generic JMX application server is installed. |
| • | Port: Enter the port number. |
| • | Server name: Enter the server name |
| • | Protocol: Select the relevant protocol: RMI / IIOP |
| The Monitoring Studio generic client connects to the JMX agent using the protocol RMI or IIOP. If you use the protocol RMI the default server name is “jmxrmi” and if you use the IIOP protocol then the default server name is “jmxiiop”. |
Step 2: Enter the connection account credentials:
Java MBean Polling Wizard (Generic Environment) — Connection Account Credentials Page
| • | Principle: Enter the username |
| • | Credentials: Enter the password |
| • | Path to Java on the local server: Enter your java home path and ensure that all the settings are correct. |
| • | Connection timeout period: Default is set to 120 seconds; you can change this if you wish. When this timeout is reached, Monitor Studio considers the host to be unreachable and triggers an alert on the ExecutionStatus parameter. |
Click Next.
Step 3: Select domain
If the credentials entered are correct, Monitoring Studio connects to the application server and presents a list of domains for you to select from. Select the domain to monitor and click Next.
Java MBean Polling Wizard (Generic Environment) — Domain Selection Page
Step 4: Select the key property
Java MBean Polling Wizard (Generic Environment) — Key Property Page
Select the key property to monitor in this domain and click Next.
Step 5: Select the attribute
Java MBean Polling Wizard (Generic Environment) — Attribute Selection Page
Select the attribute to monitor and click Next.
You can only select one attribute at a time. To monitor several attributes of the same key property, you are required to go through the wizard each time.
Step 5a: Select parameters to collect
When you select a numeric attribute (boolean, integer, number) at the previous step, an additional panel is displayed to allow you to select the parameters to collect.
Java MBean Polling Wizard (Generic Environment) — Parameters Selection Page
| ▪ | Value: Reports the actual value collected upon data polling |
| ▪ | Delta: Calculates the difference between values collected during two consecutive polling. |
| ▪ | DeltaPerSecond: Reports the value resulting of the division of the Delta by the number of seconds elapsed between the collection times |
| • | Select the option "Discard negative Delta values" if you do not want negative values to be reported on the graph. |
| • | Use the Rescaling option to configure Monitoring Studio to rescale the value that is being extracted in order to have a more readable graph in the PATROL Console. The available rescaling options are: |
| ▪ | Divide the value by a value that then gives you the reading in terms best suited to you |
| ▪ | Multiply the extracted value by a constant factor |
This can be useful if you extract numeric values in bytes but prefer to show a graph in megabytes. In such a case, you would divide the values by 1048576 (1024*1024).
Step 6: Monitoring Studio settings
You arrive at the final step of the wizard that displays the object display name, ID and threshold options.
Java MBean Polling Wizard (Generic Environment) — Settings Page
Object display name: Label displayed in the PATROL Console for this generic JMX application monitoring.
Object internal identifier (ID): PATROL internal identifier.
What thresholds do you want to set for the newly created instance? A drop-down list allows you to select the mode of setting alert thresholds:
| • | Use default thresholds: Uses the default thresholds set by Monitoring Studio |
| • | Set custom thresholds: Allows you to customize the thresholds for all parameters of the instance |
| • | Use default thresholds and customize them: Sets the default Monitoring Studio thresholds on certain parameters (see list of parameters with default thresholds) and then allows you to customize any/all of them. This is mainly intended to help save time if you wish to customize the thresholds of just one of many parameters for the instance, and leave the default settings for the others. |
| If you select Use default thresholds and customize them; on clicking Finish, the Set Thresholds panel will appear, certain parameters for the instance may appear with an asterisk symbol - indicating that they already have thresholds. You can then customize (any/all) the thresholds of the parameters as per your specific needs. |
| • | Do not set any thresholds for now: No thresholds will be set on any parameter of the instance, and as a result no alerts will be triggered. Monitoring Studio will poll the object and return the output of the polling, but will not raise any alerts until you set thresholds. |
 | Thresholds can be set or modified at anytime by right-clicking on the instance > KM commands > Set Thresholds. |
Click Finish. An icon for the monitored instance will appear under the main Monitoring Studio icon bearing the name entered/displayed in the PATROL Label field; and at the next collect you will see values for the newly monitored object. You can add a string or numeric value search if you wish.
Generic JMX application objects are instances of the SW_JMX class.
See Also
Java MBean Polling (JMX)
JBoss
JOnAS
Numeric Value extraction
String Search
SW_JMX
WebLogic
WebSphere
| 
