About Oracle Virtual Directory Basic Tuning Considerations

Oracle Virtual Directory Performance Tuning 23-7

23.3.7 Server Tuning

Table 23–5 describes some basic parameters used to tune the server: Keep Alive Default: False This option determines whether the LDAP connection should use TCP keep-alive. If enabled, the SO_KEEPALIVE socket option is used to indicate that TCP keepalive messages should periodically be sent to the client to verify that the associated connection is still valid. TCP No delay Default: True This option determines whether the LDAP connection should use TCP no-delay. If enabled, TCP_NODELAY socket option is used to ensure that response messages to the client are sent immediately rather than potentially waiting to determine whether additional response messages can be sent in the same packet. Read Timeout Default: 0 This option enablesdisables SO_ TIMEOUT with the specified timeout, in milliseconds. With this option set to a nonzero timeout, client connection to the Oracle Virtual Directory server can remain idle only for this amount of time. If the connection is idle for a period longer than the specified timeout, the client connection is terminated. A timeout of zero is interpreted as an infinite timeout. Warning: This option is equivalent to vde.soTimeoutFrontend system property in Oracle Virtual Directory version 10g. The vde.soTimeoutFrontend system property is not supported for 11g. Users must modify the value specified in system property The mapping of values from 10g to 11g are: .Enabled to 0 Disabled to nonzero amount of time in milliseconds Table 23–5 Server Parameters Parameter Value Notes Anonymous Search Limit Default: 1000 The maximum number of entries returned for an anonymous client. Table 23–4 Cont. Listener Parameters Parameter Value Notes 23-8 Oracle Fusion Middleware Performance and Tuning Guide Connection Timeout Default: 120 minutes The Connection Timeout system property is used to prevent service outages caused by clients that do not properly close connections. The value can be set in Oracle Enterprise Managers Server Properties page. Warning : Setting to 0 disables the enforcement and client connections can not be closed regardless of how long they are inactive. The system property is not enforced on IP addresses and subjects that are exempt from the quota limit or that have disabled quota enforcement. Logging Levels Default: Error:1 Severe By default, log messages are written to the access.log file only when logging is set to NOTIFICATION:1. To maintain performance, consider keeping the default log level or use WARNING:1 WARNING to limit the amount of information written to the access.log file. Table 23–5 Cont. Server Parameters Parameter Value Notes 24 Oracle Identity Federation Performance Tuning 24-1 24 Oracle Identity Federation Performance Tuning Oracle Identity Federation is a standalone, self-contained federation server that enables single sign-on and authentication in a multiple-domain identity network. It contains the following sections: ■ Section 24.1, About Oracle Identity Federation ■ Section 24.2, LDAP Tuning ■ Section 24.3, Database Tuning ■ Section 24.4, Oracle HTTP Server Tuning ■ Section 24.5, SAML Protocol Tuning

24.1 About Oracle Identity Federation

Oracle Identity Federation is a standalone, self-contained federation server that enables single sign-on SSO and authentication in a multiple-domain identity network. The federation single sign-on capabilities are based on the SAML 1.xSAML 2.0WS-Fed protocols. The server is a Java EE Application deployed in a WebLogic Managed Server. This enables users to federate in heterogeneous environments and business associations, whether they have implemented other Oracle Identity Management products in their solution set. For more information see Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation.

24.2 LDAP Tuning

This section provides configuration settings that can be used to tune LDAP such as: ■ Connection Pool Settings ■ Connection Settings ■ Federation Data Store Settings Note: The configuration examples and recommended settings described in this chapter are for illustrative purposes only. Consult your own use case scenarios to determine which configuration options can provide performance improvements.