Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Administration Guide 11g Release 1 (11.1.1.5.0) |
Part I Directory Server Administration
2. Directory Server Instances and Suffixes
3. Directory Server Configuration
6. Directory Server Access Control
7. Directory Server Password Policy
8. Directory Server Backup and Restore
9. Directory Server Groups, Roles, and CoS
10. Directory Server Replication
13. Directory Server Attribute Value Uniqueness
15. Directory Server Monitoring
Part II Directory Proxy Server Administration
16. Directory Proxy Server Tools
17. Directory Proxy Server Instances
19. Directory Proxy Server Certificates
20. Directory Proxy Server Load Balancing and Client Affinity
21. Directory Proxy Server Distribution
22. Directory Proxy Server Virtualization
23. Virtual Data Transformations
24. Connections Between Directory Proxy Server and Back-End LDAP Servers
25. Connections Between Clients and Directory Proxy Server
26. Directory Proxy Server Client Authentication
27. Directory Proxy Server Logging
28. Directory Proxy Server Monitoring and Alerts
Retrieving Monitored Data About Directory Proxy Server
Retrieving Monitored Data About Data Sources
To Monitor a Data Source by Listening for Errors
To Monitor a Data Source by Periodically Establishing Dedicated Connections
Configuring Administrative Alerts for Directory Proxy Server
To Enable Administrative Alerts
To Configure Administrative Alerts to Be Sent to Syslog
To Configure Administrative Alerts to Be Sent to Email
To Configure Administrative Alerts to Run a Script
Retrieving Monitored Data About Directory Proxy Server by Using the JVM
To View the Heap Size of the JVM
To Monitor the Heap Size of JVM When Directory Proxy Server is Running
Part III Directory Service Control Center Administration
For a description of how Directory Proxy Server monitors the health of data sources, see Monitoring Data Sources in Oracle Directory Server Enterprise Edition Reference. This section describes how to configure the monitoring of data sources.
Note - In addition to LDAP data source, you can also monitor the health of JDBC data source using monitoring-inactivity-timeout, monitoring-interval, and monitoring-mode properties.
The proactive monitoring is implemented for LDAP data source as well as for JDBC data source. The implementation for both the data sources is not the same as the nature of the data sources is different.
In this type of monitoring, Directory Proxy Server listens for errors on the traffic between Directory Proxy Server and the data sources. This type of monitoring is called reactive monitoring because Directory Proxy Server reacts if an error is detected, but does not actively test data sources.
You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.
$ dpconf set-ldap-data-source-prop -h host -p port datasource monitoring-mode:reactive
Directory Proxy Server creates a dedicated connection to a data source if there have been no requests to or responses from the data source for a specified interval.
You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.
$ dpconf set-ldap-data-source-prop -h host -p port datasource monitoring-mode:proactive
$ dpconf set-ldap-data-source-prop -h host -p port datasource \ monitoring-bind-timeout:timeout monitoring-entry-dn:dn \ monitoring-search-filter:filter monitoring-entry-timeout:timeout
The following properties are used in the search request:
The length of time that Directory Proxy Server waits to establish a connection to the data source. By default, the value of this property is 5 seconds.
The DN of the target entry in the search request. By default, this property is the root DSE entry ("").
The search filter.
The length of time that Directory Proxy Server waits for the search response. By default, the value of this property is 5 seconds.
$ dpconf set-ldap-data-source-prop ldap-data-source \ monitoring-bind-dn:uid=user-id monitoring-bind-pwd-file:password-file
Replace the user-id with a valid dn such as uid=bjensen,dc=example,dc=com and password-file with a path to the file containing password.
By default, the bind is performed as anonymous, that is, both the monitoring-bind-dn and monitoring-bind-pwd attributes are set to none.
$ dpconf set-ldap-data-source-prop -h host -p port datasource \ down-monitoring-interval:interval
If a connection is down, Directory Proxy Server polls the connection at this interval to detect its recovery. If the interval is not specified, the value of monitoring-interval is used.
$ dpconf set-ldap-data-source-prop -h host -p port datasource monitoring-retry-count:count
In this type of monitoring, Directory Proxy Server performs a search on each connection to each data source at a regular interval. In this way, Directory Proxy Server detects closed connections and prevents connections from being dropped because of inactivity.
You can use DSCC to perform this task. For information, see Directory Service Control Center Interface and the DSCC online help.
$ dpconf set-ldap-data-source-prop -h host -p port datasource monitoring-mode:proactive
$ dpconf set-ldap-data-source-prop -h host -p port datasource \ monitoring-inactivity-timeout:time
By default, the inactivity timeout is 120 seconds.
$ dpconf set-ldap-data-source-prop ldap-data-source monitoring-bind-dn:uid=user-id monitoring-bind-pwd-file:password-file
Replace the user-id with a valid dn such as uid=bjensen,dc=example,dc=com and password-file with a path to the file containing password.
By default, the bind is performed as anonymous, that is, both the monitoring-bind-dn and monitoring-bind-pwd attributes are set to none.