The following topics describe how you can tune Oracle Communications Delegated Administrator and related software to improve Delegated Administrator performance.
In addition to the guidelines described in this chapter, you can improve Directory Server performance by consolidating and reducing the number of default ACIs in the directory. See "Consolidating ACIs for Directory Server Performance" for information.
If an organization contains many users, the Delegated Administrator console may take time to display the User list page. If you try to create or edit a user while the page is still loading the existing users, an error occurs. Do not click any buttons or links until the page is ready.
Similarly, it can take time to open the Organization page or Group page if your directory contains many organizations or groups.
If these pages take too long to load, you can set wild-card search properties to a sufficiently low value to allow the pages to load quickly.
The properties are:
jdapi-wildusersearchmaxresults: Search property for users.
jdapi-groupsmaxsearchresults: Search property for groups
jdapi-wildorgsearchmaxresults: Search property for organizations.
The wild-card search property limits are as follows:
-1: Return all results. (Display all users, groups, or organizations.) -1 is the default value.
0: Do not search. (Display no users, groups, or organizations.)
n (>0): Return n (the specified number of results).
To display the user page more quickly:
Open the resource.properties file.
The resource.properties file is located in the following directory:
DelegatedAdmin_home/data/WEB INF/classes/sun/comm/cli/server/servlet
Set the value of jdapi-wildusersearchmaxresults to a low value. For example:
jdapi-wildusersearchmaxresults=50
Alternatively, you can set the value to 0 to display no users. In the Delegated Administrator console, use the Search drop-down list to search for specified users.
Redeploy the edited resource.properties file to the Web container used by the Delegated Administrator server.
Before the change can take effect, you must run the script that deploys the customized resource.properties file to your Web container.
See "Deploying a Customized Configuration File" for instructions on how to deploy a customized properties file to a particular Web container.
Open the resource.properties file.
The resource.properties file is located in the following directory:
DelegatedAdmin_home/data/WEB INF/classes/sun/comm/cli/server/servlet
Set the value of jdapi-groupsmaxsearchresults to a low value. For example:
jdapi-groupsmaxsearchresults=50
Alternatively, you can set the value to 0 to display no groups. In the Delegated Administrator console, use the Search drop-down list to search for specified groups.
Redeploy the edited resource.properties file to the Web container used by the Delegated Administrator server.
Before the change can take effect, you must run the script that deploys the customized resource.properties file to your Web container.
See "Deploying a Customized Configuration File" for instructions on how to deploy a customized properties file to a particular Web container.
Open the resource.properties file.
The resource.properties file is located in the following directory:
DelegatedAdmin_home/data/WEB INF/classes/sun/comm/cli/server/servlet
Set the value of jdapi-wildorgsearchmaxresults to a low value. For example:
jdapi-wildorgsearchmaxresults=10
Alternatively, you can set the value to 0 to display no organizations. In the Delegated Administrator console, use the Search drop-down list to search for specified organizations.
Redeploy the edited resource.properties file to the Web container used by the Delegated Administrator server.
Before the change can take effect, you must run the script that deploys the customized resource.properties file to your Web container.
See "Deploying a Customized Configuration File" for instructions on how to deploy a customized properties file to a particular Web container.
To improve the performance of common Delegated Administrator functions such as displaying pages and performing searches, you can increase the Java Virtual Machine (JVM) heap size used by the Web container to which Delegated Administrator is deployed. When the Web container's JVM heap size is too small, performance can be affected.
The JVM heap size is set by the following JVM option:
-Xmxnm
where <n> is the heap size in megabytes.
Typically, <n> is set to 256m.
The following tasks outline how to set a higher JVM heap size for Web Server and Application Server.
Log in to the Web Server Administration Server.
Under the Java tab, select JVM Options.
Edit the -Xmx256m option.
This option sets the JVM heap size.
Set the -Xmx256m option to a higher value, such as Xmx1024m.
Save the updated setting.
Web Server Documentation
See the Sun Java System Web Server Administration Guide and Web Server Performance Tuning, Sizing, and Scaling Guide for more information about using the Web Server Administration Server and setting JVM options.
Log in to the Web Server Administration Server.
Under the Configuration Tasks section, select Edit Java Settings.
Click the JVM Settings tab to display the JVM options.
Edit the -Xmx256m option.
This option sets the JVM heap size.
Set the -Xmx256m option to a higher value, such as Xmx1024m.
Save the updated setting.
Web Server Documentation
See the Sun Java System Web Server Administration Guide and Web Server Performance Tuning, Sizing, and Scaling Guide for more information about using the Web Server Administration Server and setting JVM options.
Log in to the Application Server Administration Server.
Navigate to the JVM options.
Edit the -Xmx256m option.
This option sets the JVM heap size.
Set the -Xmx256m option to a higher value, such as Xmx1024m.
Save the updated setting.
For more information about using the Application Server Administration Server and setting JVM options, go to the Sun Java System Application Server Documentation Center and select JVM Advanced Settings. Alternatively, see Tuning the Java Runtime System in Sun Java System Application Server Enterprise Edition 8.1 2005Q4 Performance Tuning Guide.
To improve performance of Delegated Administrator functions such as searching and displaying users, you can increase the threshold for indexes used by Directory Server to search the directory.
When Directory Server searches several LDAP objects, if the threshold is set to a low value, the index might run out of space before the search is completed. The remainder of the search is performed without indexing, which slows down the search operation.
Caution:
Perform this operation only if you are an experienced Directory Server administrator.To set the index threshold to a higher value, change the value of the nssldap-allidsthreshold option in the dse.ldif file.
This option might be set to a value such as the following:
nssldap allidsthreshold: 4000
Set nssldap-allidsthreshold to a higher value. For example:
nssldap allidsthreshold: 200000
For more information about the All IDs Threshold, see Managing Indexes in Indexing Directory Data in the Sun Java System Directory Server Administration Guide. For a definition of the nssldap-allidsthreshold option, see "Database Configuration Attributes" in Sun Java System Directory Server Administration Reference.
In some cases, when you are logged in as the Top Level Administrator and you click on the Advanced Search button, you may find that the search does not work for certain fields especially if there is a huge amount of data. To resolve this, you should reindex the backend on the root suffix for the particular field you are searching. By default mail and user name fields are indexed by dssetup so this problem does not occur for those attributes.
For example, to create an index for departmentNumber so that you can search for the department and get a list of the users, do the following:
dsconf create-index -h localhost -p 389 dc=idc,dc=oracle,dc=com departmentNumber dsconf set-index-prop -h localhost -p 389 dc=idc,dc=oracle,dc=com departmentNumber sub-enabled:on approx-enabled:on dsconf reindex -h localhost -p 389 -t departmentNumber dc=idc,dc=oracle,dc=com dsadm stop /var/opt/DS7Instance/ dsadm reindex -t departmentNumber /var/opt/DS7Instance/ dc=idc,dc=oracle,dc=com dsadm start /var/opt/DS7Instance/
If you need to index a different attribute, replace the attribute departmentNumber with another attribute that you need to index like city. Note that you will have to confirm the existence of the attribute in LDAP.