RDBMS Compression Database Tuning

25-2 Oracle Fusion Middleware Performance and Tuning Guide Oracle Web Services Security provides a framework of authorization and authentication for interacting with a web service using XML-based messages.

25.2 Detecting General Performance Issues

This section offers some general guidelines on how to identify a performance bottleneck and how to approach addressing such problems. If you discover a performance bottleneck, you should first verify that you have addressed the expected traffic load throughout your Web services deployment. If there is a system in the critical path that is at 100 CPU usage, you may simply need to add one or more computers to the cluster. If there is a bottleneck in your deployment, it is likely to be within one of the following: ■ Traffic through a slow connection with an agent ■ Latency in connections to third-party queuing systems like JMS For any of these problems, check the following potential sources: ■ Problems with policy assertions that include connections to outside resources, especially the following types: – Database Repositories – LDAP Repositories – Secured Resources – Proprietary Security Systems ■ Problems with database performance If you identify one of these as the cause of a bottleneck, you may need to change how you manage your database or LDAP connections or how you secure resources.

25.3 Oracle Platform Security Services Tuning

This section provides the following basic tuning configurations for Oracle Platform Security Services OPSS: ■ JVM Tuning Parameters ■ LDAP Tuning Parameters ■ Authentication Tuning Parameters ■ Authorization Tuning Properties ■ OPSS PDP Service Tuning Parameters Note: The information in this chapter assumes that you have reviewed and understand the concepts and administration information for Oracle Fusion Middleware Security Services. For more information, see the Oracle Fusion Middleware Security and Administrators Guide for Web Services before tuning any security parameters. Oracle Fusion Middleware Security Performance Tuning 25-3

25.3.1 JVM Tuning Parameters

Tuning the JVM parameters can greatly improve performance. For example, the JVM Heap size should be tuned depending upon the number of roles and permissions in the store. At run time, all roles and permissions are stored in the in-memory cache. For more JVM tuning information, see Section 2.4, Tune Java Virtual Machines JVMs .

25.3.2 LDAP Tuning Parameters

This section covers Lightweight Directory Access Protocol LDAP tuning. Oracle supports the management of policies in file-based repositories: Oracle Internet Directory and Oracle Virtual Directory. If you encounter increased CPU usage due to high SQL execution times, see the following chapters for basic tuning configurations for large deployments: ■ Oracle Internet Directory configuration settings can impact performance. For more information, see Chapter 22, Oracle Internet Directory Performance Tuning . ■ In addition to being configured as a LDAP server, Oracle Virtual Directory can also be configured as a local storage adapter LSA. See Chapter 23, Oracle Virtual Directory Performance Tuning .

25.3.3 Authentication Tuning Parameters

For OPSS Authentication tuning, see Improving the Performance of WebLogic and LDAP Authentication Providers in the Oracle Fusion Middleware Securing Oracle WebLogic Server guide at the Oracle Technology Network http:download.oracle.comdocscdE12840_ 01wlsdocs103secmanageatn.htmlwp1199087 .

25.3.4 Authorization Tuning Properties

The following Java system properties can be used to optimize authorization: