Evaluating Performance on UNIX and Windows Systems Obtaining Recommendations by Using the Tuning and Sizing Wizard

22-22 Oracle Fusion Middleware Performance and Tuning Guide orclskewedattribute dn: cn=dsaconfig,cn=configsets,cn=oracle internet directory changetype: modify add: orclskewedattribute orclskewedattribute: my_attribute Restart the server after changing orclskiprefinsql or orclskewedattribute.

22.13 Setting Garbage Collection Configuration Attributes

The attributes orclpurgetargetage and orclpurgeinterval reside in the changelog purging configuration entry. You can change them with ldapmodify or Oracle Directory Services Manager.

22.13.1 Modifying Changelog Purging Attributes by Using ldapmodify

The following example is an LDIF file used to configure change log purging. This example configures time-based purging for 120 hours 5 days. Use an LDIF file similar to this: dn: cn=changelog purgeconfig,cn=purgeconfig,cn=subconfigsubentry changetype:modify replace: orclpurgetargetage orclpurgetargetage: 240 To apply the LDIF file mod.ldif, type: ldapmodify -D cn=orcladmin -q -p port -h host -D dn -q -f mod.ldif

22.13.2 Modifying Changelog Purging in Oracle Directory Services Manager

You can modify orclpurgetargetage and orclpurgeinterval by using the data browser in Oracle Directory Services Manager. You cannot navigate to the changelog purging configuration entry directly in the data tree, but you can get to it by using an advanced search as follows:

1. On the Data Browser tab, click Advanced.

2. Expand Garbage Collection in the left pane, then select changelog purgeconfig.

The Garbage Collector Window appears in the right pane.

3. In the right pane, enter the changes you want to make to the Purge Target Age

and Purge Interval. 4. Choose Apply. See Also: Change Log Purging in Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory for a description of change log purging. See Also: Configuring Time-Based Change Log Purging in Oracle Fusion Middleware Administrators Guide for Oracle Internet Directory. 23 Oracle Virtual Directory Performance Tuning 23-1 23 Oracle Virtual Directory Performance Tuning This chapter provides tuning tips for Oracle Virtual Directory. It contains the following sections: ■ Section 23.1, About Oracle Virtual Directory ■ Section 23.2, Basic Tuning Considerations ■ Section 23.3, Advanced Tuning Configurations

23.1 About Oracle Virtual Directory

Oracle Virtual Directory is an LDAP Version 3-enabled service that provides an abstracted view of one or more enterprise data sources. Oracle Virtual Directory consolidates multiple data sources into a single directory view, enabling you to integrate LDAP-aware applications with diverse directory server data stores. The information in this chapter assumes that you have reviewed the concepts and administration information in the Oracle Fusion Middleware Administrators Guide for Oracle Virtual Directory.

23.2 Basic Tuning Considerations

The tuning considerations in this section apply to most deployments and usage scenarios. It is highly recommended that you review these configurations and implement those that are appropriate for your use case scenarios. The tuning information is summarized in Table 23–1 . ■ Increase the ping interval to 60 seconds or more as needed in the opmn.xml file. When the system is busy, a ping from the Oracle Process Manager and Notification Server OPMN to Oracle Virtual Directory may fail. As a result, OPMN will restart Oracle Virtual Directory after 20 seconds the default ping interval. To avoid this, consider increasing the ping interval to 60 seconds or more. Note: Oracle Virtual Directorys out of box configuration may not be optimal for many production and test deployments. You are encouraged to incorporate the recommendations listed in Basic Tuning Configurations to achieve optimal performance and availability. 23-2 Oracle Fusion Middleware Performance and Tuning Guide The ping interval can be modified in the ORACLE_ INSTANCEconfigOPMNopmnopmn.xml as shown below: process-type id=OVD module-id=OVD module-data category id=start-options data id=java-bin value=ORACLE_HOMEjdkbinjava data id=java-options value=-server -Xms2056m -Xmx2056m -Dvde.soTimeoutBackend=0 -DdisableECID=1 -Didm.oracle.home=ORACLE_HOME -Dcommon.components.home=ORACLE_HOME..oracle_common -Doracle.security.jps.config=ORACLE_INSTANCEconfigJPSjps-config-jse.xml data id=java-classpath value=ORACLE_ HOMEovdjlibvde.jar:ORACLE_HOMEjdbclibojdbc6.jar category module-data stop timeout=120 ping interval=60 process-type ■ Tune the number of worker threads based on the number of central processing units CPU available for Oracle Virtual Directory Server on the system. The Threads configuration parameter in the Oracle Virtual Directory Listener settings should be set to an appropriate value. The default out of box value for Threads in the Admin Gateway listener and DSML Gateway listener should be generally optimal and need not be changed. The number of Threads for the LDAP Listeners are typically the threads that need to be tuned since typically it is the LDAP Listeners that take on concurrent traffic from applications. A common configuration is to have 10 threads per CPU. For example, if there are 4 central processing units on the system, then there would be 40 threads. For more information, see Managing Listeners in Oracle Fusion Middleware Administrators Guide for Oracle Virtual Directory. ■ Tune the Work Queue Capacity based on the expected maximum number of concurrent clients to a given LDAP Listener. The WorkQueueCapacity configuration parameter in the Oracle Virtual Directory Listener settings should be set to an appropriate value. This ensures that the connection requests from LDAP clients are not rejected due to a lack of work queue capacity. Work elements are allocated on demand only, therefore a value higher than the actual estimate can be used. The Fusion Middleware Control Performance Monitor provides a historical report which contains the maximum number of connections. Use this report to determine how to adjust the connection value based on production data. If Oracle Virtual Directory needs to support high number of concurrent clients, then set the ulimit nofiles descriptor parameter to the number of LDAP Clients expected. For example, in the command window where OPMN is started, set the following ulimit when 8000 concurrent clients are expected: ulimit -n 8192 This change requires restart of OPMN and Oracle Virtual Directory to take effect. For more information, see Managing Listeners in Oracle Fusion Middleware Administrators Guide for Oracle Virtual Directory. ■ Tune the size of the LDAP connection pool in Oracle Virtual Directory LDAP Adapter to be at least as high as the total number of Threads configured in the Oracle Virtual Directory Listeners that actively use the LDAP Adapter.