In order to monitor an Oracle HTTP server in Applications Manager, the
'/server-status' page must be configured on the target Oracle HTTP
server that needs to be monitored. This can be accomplished by following
these steps:
Step 1 - Enable the "mod_status.co" module in the Target Oracle HTTP server
Navigate to <ORACLE_HOME>/user_projects/domains/<domain_name>/config/fmwconfig/components/OHS/<server_component_name>/httpd.conf fileand uncomment the following line:
- LoadModule status_module "${PRODUCT_HOME}/modules/mod_status.so"
Step 2 - Add/Modify access handler for "/server-status" page
Add the following lines to the configuration file, and if it is already present, modify it according to the context given below:
- <Location /server-status>
SetHandler server-status
Require all granted
</Location>
Note that making the above changes will open the "/server-status" handler without any restriction. To restrict access to Applications manager alone, make the following changes to the configuration file:
<Location /server-status>
SetHandler server-status
Require host <hostname_of_apm_installed_machine>
Require ip <ip_of_apm_installed_machine>
</Location>
Step 3 - Enable Extended Status
Enabling ExtendedStatus is mandatory for monitoring metrics like
Request per second, bytes per second, bytes per request etc. If the ExtendedStatus is not enabled, then follow the below steps to enable the extended status.
- Locate the line starting with ExtendedStatus in the configuration file.
- Uncomment the line and set the status "On".
Step 4 - Restart the server
Restart the target Oracle HTTP server after performing the above mentioned steps and check if the below URL is accessible from Applications Manager installed machine.