Oracle 9i Jsps Test

This test reports the performance metrics related to the JSPs deployed in an Oracle9i application server instance. In order to enable users to easily manage and monitor the JSPs deployed on an Oracle 9i application server, the eG Enterprise provides the Click Here hyperlink, which when clicked allows users to add, modify, or delete groups of JSPs. Note that by default eG Enterprise monitors only those JSPs that are part of a group.

Target of the test : An Oracle 9i Application Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every JSP group monitored or for every JSP auto-discovered (as the case may be).

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


In the Port text box, it is recommended that you provide the port at which the OPMN (Oracle Process Manager and Notification) process of the Oracle application server instance listens. To know at which port OPMN listens, click on the Ports tab in the following URL: http://<oraHttpServerIP>:<OraHttpServerport>. This tab lists the port numbers that were assigned to the services executing on the Oracle application server. The port number displayed against the Oracle notification server request port entry is the OPMN port, and the same should be specified in the Port text box.


The absolute path of the directory in which the Oracle 9i application server has been installed.


By default, eG Enterprise allows administrators to configure JSP groups using the eG administrative interface, and reports metrics pertaining to every group so created. Accordingly, by default, AutoDiscovery is set to No. If you want JSPs to be discovered and monitored automatically, then select the Yes option against AutoDiscovery. When this is done, the eG agent automatically discovers all the JSPs on the server, and reports one set of measures for every JSP so discovered.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Threads serving JSPs

Indicates the current number of active requests for the JSP.


If a majority of the threads/processes are in use simultaneously to serve requests for a specific JSP, this may be indicative of a problem with the design of this page. Further investigation is needed to determine the cause of the bottleneck - whether it is the processing of the JSP, whether it is a bottleneck in the database tier, whether the database query (ies) are non-optimal etc. Alternatively, a slowdown of the application server may also cause the requests that are simultaneously executing to increase.

Requests completed

Indicates the rate at which requests were processed by this JSP.


Comparing this metric across JSPs can indicate which pages are most accessed. Optimizing the most heavily accessed pages can result in a significant improvement in the user-perceived performance of that web application. 

Avg request process time

Indicates the average time spent in servicing the JSP during the last measurement period.


An increase in this value may be indicative of a problem in the application server/JSP logic. 

Max request process time

Indicates the maximum time spent servicing a JSP since the server started.