IBM Tivoli Identity Manager Performance Tuning Guide Page 3
1 Introduction The IBM Tivoli Identity Manager product addresses the complex problem of identity management. Due to
the complexity of the problem, it can be challenging to optimize the use of resources by IBM Tivoli Identity
Manager – that is, to tune. This tuning guide provides a system administrator with the information needed
to tune the application for your environment. Other individuals (such as IBM DB2 or the LDAP Server
administrators) in your organization might offer differing advice. In our experience, your system
administrators know your environment better, and their advice may be more accurate for your
environment than this tuning document.
The IBM Tivoli Identity Manager product can be divided into four major components: IBM WebSphere
Application Server, the IBM Tivoli Identity Manager application, IBM DB2, and IBM LDAP Server. We will
address each of these separately in this document.
The IBM Tivoli Identity Manager server can be installed as either a single server or as clustered servers.
A clustered environment can be considered a group of single servers with regard to tuning.
This document is a working document. As more information is gathered settings may be added, removed
or changed in future editions. It is recommended that you check the IBM Web site for the most recent
version. To find the most recent version, go to http://www.ibm.com/support/us. Type “ITIM Tuning Guide”
in the search box under Search technical support, and click Search.
1.1 Vital tunings
There are several thousand different parameters that you can modify to tune WebSphere Application
Server, the IBM Tivoli Identity Manager product, directory servers, and database servers. This tuning
guide discusses a small subset of these parameters that have proven effective during performance
testing.
If you are setting up an acceptance or production environment, read each section and perform the
applicable tunings for your systems. If you are setting up a test environment and want to get started as
quickly as possible, focus on these areas:
• IBM DB2 - Buffer pools
• IBM DB2 - Reorg and Runstats
Note: The database statistics tunings are a vital part of the IBM Tivoli Identity Manager product
performance.
• IBM LDAP Server – Indexing
1.2 Initial tunings
Most of these tunings can be implemented in a newly deployed environment or an environment that is
already deployed.
It is recommended that you execute runstats each time you add significant numbers of users to your
databases. Failure to keep your database statistics up to date can cause IBM DB2 to use non-optimal
paths when accessing data. See the IBM DB2 - Reorg and Runstats section for more information.
1.3 Resource allocation
Tuning values are more complex to manage when more than one middleware component is running on a
given system; for example, having the IBM Tivoli Identity Manager server, IBM DB2, and IBM LDAP
Server all on the same server. Regardless of configuration, it is important to calibrate the following
resources so that they are not over-allocated.