Free 30 Day Trial
Find the root-cause of your cloud, hybrid-cloudor on-prem performance issues
How does eG Enterprise Monitor Sun Java System Application Server?
eG Enterprise is capable of monitoring the Sun Java System application server in both agent-based and agentless manners. Before attempting to monitor the server, first configure the server to work with the eG Enterprise. The procedure for achieving this is discussed in the below section.
Configuring the Sun Java System Application Server to work with eG
In order to ensure that the Sun Java System application server works smoothly with the eG product, the monitoring capability of a few key services has cputo be enabled. To achieve this, do the following:
Upon typing the URL, a dialog box requesting the User Name and Password of the administrator will appear (see Figure 1). Specify the same in the respective text boxes and click the OK button.
Upon successful login, the Sun Java System application server’s admin console will open (see Figure 2).
Now, select the ORB service as indicated by Figure 3.
Figure 3 reveals that by default the Monitoring Enabled check box displayed in the right pane is deselected for the ORB service. This capability has to be enabled for the eG agents to effectively monitor the ORB service. To enable this capability, click on the check box and click the Save button below. Upon clicking, a link named Apply Changes Required (see Figure 4) will appear in the top right corner of the window. To apply the changes made, first, click on this link.
Once the link is clicked, a page depicted by Figure 5 will appear. Click on the Apply Changes button in this page to register the changes made.
When this is done, the following confirmation message will appear (see Figure 6).
Repeat the procedure discussed above for the Transaction Service and the EJB Container, which can be seen in the left pane (see Figure 7). To view the EJB Container sub-node, expand the Containers node in the left pane (see Figure 7).
Configuring the eG Agent to Collect JVM-related Metrics from the Sun Java System Application Server 7.0
The jvm layer of the Sun Java System Application monitoring model is mapped to tests that report critical statistics related to the Sun Java System application server’s JVM. These statistics typically reveal the following:
These tests connect to the JRE used by the Sun Java System application server to pull out the above-mentioned metrics. For these tests to work, the eG agent should be configured to connect to the JRE and collect the required metrics, using one of the following methodologies:
Since both JMX and SNMP support are available for JRE 1.5 and above only, these tests will work only if the Sun Java System application server being monitored uses JRE 1.5 and above.
Version 7.0 of the Sun Java System Application server uses JDK 1.4 by default. Therefore, before enabling the optional JVM tests for this server, make sure you change to JDK 1.5.
If you choose to use JMX for pulling out the desired metrics from the JRE, then the following broad steps need to be followed:
If the JMX requires authentication (but no security), follow the steps below:
Edit the management.properties file that is used by the JRE of the target Sun Java System application server, and configure the following in it:
To know how to configure these, refer to the Monitoring Java Applications document.
When Figure 8 appears, click on the JVM Settings tab page. Then, click on the Path Settings link. In the Classpath Suffix text area, add a line indicating the full path to the crimson.jar file.
Save the settings and then, click he JVM Options link. In the JVM Option text box of Figure 9, specify the following:
-Dcom.sun.management.config.file=<Full path to the management.properties file of the JRE used by the target Sun Java System Application server>
To know how to enable SNMP support for the JRE, refer to the Monitoring Java Applications document.