Oracle Application Server 10.1.3

Configuration

Before using an Oracle Application Server monitor, several of the Oracle Application Server jars must be installed in NeoLoad jmxlib/oas directory.

Copy the following files from the Oracle Application Server directory to <neoload>jmxlib/oas directory:

After copying the files, it is unnecessary to restart NeoLoad. The files are automatically synchronized with the Monitoring Agent once the changes have been made.

Supported versions

This monitor allows NeoLoad to access Oracle Application Server 10g 10.1.3 and higher.

Connection settings

Defining a connection to an Oracle Application Server requires the name or IP address of the machine to be monitored, as well as the connection port (the default port is 6003). The application server connection port is configured in the file: <Server>/opmn/conf/opmn.xml,

<notification-server> <port local="6100" remote="6200" request="6003" /> ... </notification-server>

A valid user account must be provided in addition to these settings (same as the one used for connecting to the Oracle Application Server Management Console).

  1. Connect to the server management interface. The default URL is: http://<server>:8888/em
  2. Select the instance to be monitored.
  3. Click on the Administration tab.
  4. Select the Security > Security Providers task.
  5. Click Instance Level Realm.
  6. Select the Realms tab.
  7. In the Security Provider Attributes section, click on the number of realm users.
  8. Select the user to be used for monitoring.
  9. In the available roles, select "ascontrol_admin" and "oc4j-administrators" and add them to the user.
  10. Click Apply.
  11. Re-start the application server.
Create an Oracle Application Server 10.1.3 monitor

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.

Available counters

Method calls for each EJB can be monitored.