IBM G210-1784-00 manual Tuning database server performance, Indexing LDAP attributes

Models: G210-1784-00

1 131
Download 131 pages 28.82 Kb
Page 113
Image 113

4.There are several user attributes that are used quite often when searching for users (first name, last name, organization, etc.). For a faster response, you can index these attributes in the LDAP server’s database.

Indexing LDAP attributes

Every vendor provides different ways on how to index the information in their LDAP directory. In the case of Lotus Domino, for example, you just need to create a full text index on the address book (names.nsf) of the Domino server hosting the LDAP process. This can boost the performance significantly.

With IBM Directory Server 5.1, you can indicate which fields you want to index, using the Web administration interface. IBM Directory Server 4.1 does not provide this feature in the administration interface. There you will have to create the index manually using DB2 utilities.

Deferring the IsManager lookup

As described above, in some cases you need to defer the IsManager lookup to speed up login and rostering processes. You can advise LMS to do this by setting the value of the deferIsManagerLookup field in the settings.xml and the ds-settings.xmlfrom Disabled to Enabled. After the change you will need to restart the applications.

The settings.xml is located in the Learning Server installation directory at:

<WAS_install_path>\installedApps\<NODENAME>\LMSLMM.ear\lms-lmm-complete- 23.war\WEB-INF\classes\settings.xml

The ds-settings.xmlis located in the Delivery Server installation directory at:

<WAS_install_path>\installedApps\<NODENAME>\LMSDS.ear\lms-ds- complete23.war\WEB-INF\classes\ds-settings.xml

When the deferral is enabled, the IsManager attribute will not be updated during login and rostering processes. For newly rostered users, it will be set to zero (false). For users that logged on before, the value of the last IsManager lookup is used.

The server thread that performs the IsManager lookups in the background works with a FIFO queue (first-in, first- out). This means that the IsManager field of users that logged on first will be updated first.

If the deferral of IsManager lookups is enabled and an LMS administrator rosters a huge list of users at once, the lookup thread’s queue might overrun and could produce an error. In this case, you should not defer the IsManager lookup.

Tuning database server performance

Tuning parameters vary according to the type of database and operating system you are using. There are no specific LMS-related performance adjustments that should be applied to the database server. Nevertheless, keep the following general advice in mind:

Ensure that the database server is set up to support the maximum number of connections from the connection pool defined in the WebSphere Application Server.

If you are using the same database server for the Learning Server and the Delivery Server database, you can increase the performance by creating the databases on physically different hard disks on the database server.

There are additional resources on the Internet that cover database performance tuning for the database servers supported by LMS. For your convenience, some of them are listed here:

IBM DB2 Performance Problem Determination http://www-3.ibm.com/cgi- bin/db2www/data/db2/udb/winos2unix/support/tutorial_performance.d2w/toc

106 IBM Lotus LMS Release 1 Installation Guide

Page 113
Image 113
IBM G210-1784-00 manual Tuning database server performance, Indexing LDAP attributes, Deferring the IsManager lookup