To define the connection to an Oracle Application Server using this monitor requires that the DMS (Dynamic monitoring System) library be activated. By default, it is activated on OC4J (Oracle Container 4 Java) servers version 10g.
The following procedure can be used to make sure the server metrics are accessible through the DMS library:
<server>is the server hostname.
<port>is the server port.
For example: http://oc4jserver.com:8888/dms0/Spy?format=xml.
For more information about monitoring Oracle Application Server servers through DMS, refer to the Instrumenting Applications With DMS documentation in the Oracle website.
This monitor supports Oracle Application Server 9 and later.
Defining a connection to an Oracle Application Server requires a server (defined in the Server section of the Virtual Users) tab and a path. The server to be used can be created, or a server created during a recording can be used.
NeoLoad makes it possible to create a new monitor either using the monitored machine creation wizard, as described in Create and configure a monitored machine, or from an existing monitored machine, as described in Create and configure a monitor.
NeoLoad displays a list of the EARs (Enterprise Archive) and WARs (Web Application archive) deployed on the configured server. It then automatically selects the most appropriate counters for each of the selected applications.
The counter advanced settings are available for all the HTTP counters. For more information, see Advanced Settings.
The Oracle Application Server counters are automatically calculated based on all the available managed objects. As the list of Oracle Application Server counters is dynamic, calculating the total number of counters may take several seconds. For certain counters, a description allows access to its documentation. Here are some of the most common sections.