High Availability Deployment and Architecture Considerations

2-28 Oracle Fusion Middleware Administrators Guide for Oracle Identity Federation

2.6.1.7 Tuning Servers

Take into account the presence of other servers in your production environment. Specifically, consider: ■ Tuning Oracle WebLogic Server and setting appropriate connection limits for Oracle Identity Federation. You can: – Tune Oracle WebLogic Server using typical configuration parameters such as memory used, number of processes, and so on. For details, see Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server. – Specify the maximum number of HTTPJDBC connections that Oracle Identity Federation uses when communicating with remote HTTP servers and RDBMS servers. For details, see Oracle Fusion Middleware Performance and Tuning Guide . ■ Tuning the Oracle HTTP Server, which is leveraged by Oracle Identity Federation.

2.6.1.8 HTTP Session Persistence

Oracle Identity Federation uses HTTP session state during request processing. To configure Oracle WebLogic Server session persistence see the chapter titled Using Sessions and Session Persistence in Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle. By default, memory-based storage is used. If you do not allow sufficient heap size when running Oracle WebLogic Server, your server may run out of memory under heavy loads.

2.6.1.9 Impact of Additional Security

Introducing additional security measures, such as fire walls, proxy servers, or using SSL authentication, can add extra steps in federated transactions and therefore impact performance.

2.6.2 Typical Deployment Scenario

Figure 2–11 illustrates a typical Oracle Identity Federation deployment architecture for a service provider, where Oracle Identity Federation relies on Oracle Access Manager as the back end access management system. The diagram illustrates multiple partners coming in through the DMZ and accessing a load-balanced pair of Oracle Identity Federation Proxy Servers, which are front-ending a pair of Oracle Identity Federation servers. See Also: The following provide tuning and performance guidelines: ■ Section 6.3.1, Configuring the LDAP Inactivity Setting ■ Section 6.4.2, Configuring the HTTP Session State SleepRetry Interval ■ Section 6.5.1, Configuring RDBMS Session Cache ■ Section 6.6.1, Storing Assertion Attributes of User Session ■ Chapter 7, Diagnostics and Auditing ■ Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server ■ Oracle Fusion Middleware Performance and Tuning Guide Planning Oracle Identity Federation Deployment 2-29 Figure 2–11 A Typical Federation Deployment Architecture

2.6.3 Reference Server Footprint

The following hardware and equipment is recommended for a baseline Oracle Identity Federation deployment, for an environment supporting up to 2000 concurrent users: ■ Any supported server-class machine and operating system for Oracle Identity Federation. See the certification matrix for a list of certified platforms for Oracle Identity Federation. Failover scenarios would double the number of machines required. Use a minimum of two Oracle Identity Federation servers, on separate machines, for redundancy. ■ Server footprint: – 2-4 GB memory 4GB recommended – Minimum of 2 CPUs per machine ■ If a proxy server is being used, follow the vendor-specific sizing recommendations.

2.6.4 Topology

Figure 2–12 shows the recommended topology for an Oracle Identity Federation deployment in SP mode in which Oracle HTTP Server serves up a provider application that is protected by a webgate.