Tasks Tables Physical Data Placement

25 Tuning Application Server Performance 25-1 25 Tuning Application Server Performance This chapter describes how to tune Oracle WebLogic Server for Oracle Identity Manager to improve performance in the following sections: ■ JVM Memory Settings ■ JDBC Connection Pool ■ Number of Message Driven Beans ■ User Interface Threads ■ Disable Reloading of Adapters and Plug-in Configuration ■ Changing the Number of Open File Descriptors for UNIX Optional ■ Tuning the JVM Garbage Collection for Solaris Sparc T3 or T4

25.1 JVM Memory Settings

To change the JVM memory setting: 1. Open the DOMAIN_HOMEbinsetSOADomainEnv.sh or setSOADomainEnv.cmd file. 2. Change the value of DEFAULT_MEM_ARGS and PORT_MEM_ARGS from the default value. 3. Save the setSOADomainEnv.sh or setSOADomainEnv.cmd file. Note: ■ All tuning parameter suggestions and values in this section are for reference purposes only. Values should be modified based on your requirement, application usage patterns, loads, and hardware specifications. ■ Changing any of the settings may require you to restart the server. See Also: Oracle® WebLogic Server Performance and Tuning documentation for more information about tuning Oracle Application Server 25-2 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager

25.2 JDBC Connection Pool

Oracle Identity Manager uses the oimOperationsDB and oimJMSStoreDS datasources deployed on Oracle WebLogic Server. By default, maximum connections is set at 50. You may have to increase this based on the requirement. To increase the capacity of the JDBC connection pools: 1. Open the WebLogic Server Administration Console. 2. For JDBC Datasource xlXADS:

a. Click Services, JDBC, Data Sources, oimOperationsDB, and then click the

Connection Pool tab. b. Adjust the Initial Capacity and Maximum Capacity based on requirement. For JDBC Datasource xlDS:

a. Click Services, JDBC, Data Sources, oimJMSStoreDS, and then click the

Connection Pool tab. b. Adjust the Initial Capacity and Maximum Capacity based on requirement. 3. Save and activate the changes.

25.3 Number of Message Driven Beans

Oracle Identity Manager uses Message Driven Beans MDBs for processing all offline activities, such as reconciliation, auditing, requests, attestation, and for its internal kernel operations. By default, total of 80 MDB instances concurrently serve requests. However, based on the requirement, this can be increased by modifying the OIMMDBWorkManager configuration. To do so: 1. Login to WebLogic Administrative Console.

2. Navigate to Environment, Work Managers, and then to

MaxThreadsConstraint-1 . 3. Change the count from 80 to a higher number per your requirement.

25.4 User Interface Threads

By default, Oracle Identity Manager provides 20 front-end thread configurations. These threads are used for serving front-end requests. To change the number of front-end thread configurations: 1. Login to WebLogic Administrative Console. Note: Add the following option to prevent StringIndexOutOfBoundsException error: -XX:-UseSSE42Intrinsics This parameter is required only for Sun JDK. Note: Ensure that any increase in number of connections on the application server connection pools are compensated by database configuration changes. You might have to increase the MAX SESSIONS settings on Oracle Database.