LDAP Listener Tuning Advanced Tuning Configurations

24-4 Oracle Fusion Middleware Performance and Tuning Guide orclfedproviderid=http:server2.example.com:7492fedidp orclfedfederationtype=1 orclfedfederationtype=3

24.3 Database Tuning

This section provides configuration settings that can be used to tune the database. See Additional RDBMS Configuration in Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation.

24.3.1 Data Sources

Oracle Identity Federation uses a Java EE data source to interact with a database for various operations, such as: ■ Locating a user record in the User Data Store ■ Retrieving attributes from a user record in the User Data Store ■ Locating, creating, or deleting an Oracle Identity Federation record from the Federation Data Store ■ Locating, creating, or deleting an Oracle Identity Federation transient record from the Session or Message Data Store. A transient record can be a user session, an artifact record, or federation protocol or session state. When creating a data source in the WebLogic Administration Console that can be used by Oracle Identity Federation, the maximum and minimum connection settings should be tuned for better performance. Consult your use case scenarios to determine what the connections settings should be to improve performance in your application.

24.3.2 RDBMS Session Cache

When Oracle Identity Federation is integrated with RDBMS for its Session Data Store, the server uses a caching mechanism to improve performance at run time. This enables the server to keep a reference to recently used session objects in memory to avoid read access to the database. To optimize RDBMS session caching, configure the following: ■ Number of session objects kept in memory at a given time ■ Length of time a specific session object is kept in memory See Configuring RDBMS Session Cache in Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation.

24.3.3 RDBMS Compression

To decrease the amount of data to be stored in an RDBMS, Oracle Identity Federation provides the capability to compress the data before storing it to the database.There are three kinds of data that can be compressed: Note: if Oracle Identity Federation is in High Availability HA mode with a load balancer, sticky sessions must be enabled to ensure that the cache is always reflecting accurate data. Oracle Identity Federation Performance Tuning 24-5 ■ AuthnRequest for SSO Artifact profile: when Oracle Identity Federation acts as an IdP for Liberty 1.x protocol, the server stores the AuthnRequest message in the RDBMS when the artifact profile is used. ■ Assertion Response for SSO Artifact profile: when Oracle Identity Federation acts as an IdP for SSO protocols, the server stores the Response message containing the Assertion in the RDBMS when the artifact profile is used. This must be enabled if attributes are contained in the assertion. ■ User Session Data: Oracle Identity Federation stores some session data related to the user at run time. If several attributes are stored in the User Session set by a custom Authentication Engine, or because the Attributes Assertion storage was enabled when Oracle Identity Federation was a service provider, then compression should be used. See Configuring RDBMS Data Compression in Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation.

24.4 Oracle HTTP Server Tuning