Tivoli Identity Manager Installation

I have been working on the Tivoli Identity Manager for the last couple of months, and all things considered, without training, the learning curve has been steep. However, with time I have come to appreciate the power and features of this product, especially when combined with the Tivoli Directory Integrator.

INSTALLATION
The installation instructions seemed pretty straightforward when I read it. The only issues that came up were applying the fixpacks to all the components. The TIM Installer seems to be very particular in pointing out which components are not up-to-date. However, you can go ahead and install it anyway if you choose to ignore these warning messages. We didnt update the WebSphere as required, and TIM still worked fine.
We used the following components for our test bed:
IBM WebSphere App Server
IBM Directory Server
IBM DB2

IBM WebSphere Configuration
Fixpack was required as per our TIM documentation. However, as I mentioned earlier, we were able to run TIM without applying any fixpacks.

IBM Directory Server
Installed it. Then created a suffix entry in the DS. All user data (from TIM) is stored below this node. The easiest suffix to add is dc=com.
We used the DS Configuration Wizard (Start->Program Files->IBM Directory Server x.x). Selected manage suffixes. Added dc=com. (You can directly edit the ibmslapd.conf file (%DS HOME%/etc) and add the line ibm-slapdSuffix: dc=com where the suffixes are defined.)
Then, created a .ldif file with following entry:
dn: dc=com
dc: com
objectclass: top
objectclass: domain
Imported this file using the DS Configuration wizard.

IBM DB2
Installed DB2 and DB2 FP8. Ran the following commands.
db2 create db itimdb using codeset UTF-8 territory US
Used this Database (itimdb) in TIM configuration wizard.
No further configuration was necessary. However, one of the documents suggested the following configuration:
db2 update db cfg for itimdb using applheapsz 384
db2 update db cfg for itimdb using app_ctl_heap_sz 512
db2 connect to itimdb
db2 create bufferpool enrolebp size -1 pagesize 32k
db2set DB2_RR_TO_RS=YES
db2 force application all
db2stop
db2start
However, one of our test beds is running well without using the above commands.
This commands would probably help streamline TIM functioning and maybe used for tuning up the configuration.

Tivoli Identity Manager
Rebooted the system after completing the above steps.
Installed Tivoli Identity Manager.
After installation (but before it is complete) TIM asks for DB and LDAP details.
DB:
Database Name: itimdb
Admin ID: db2admin (this is the default DB2 admin id)
Admin password: (As specified during DB2 install)
User Id: enrole
User Password: @password123
NB: The TIM installation was supposed to create the user enrole. However due to some error, it was not created on our system, so we created it manually. If TIM had created it, the password would also have been enrole.
If the test does not succeed, check whether DB2 service is running. Also, if db2admin exists.

LDAP:
Principal DN: cn=root
Password: (As specified during DS installation)
Host Name: (Host name/IP address of system on which DS is installed)
Port: 389 (default for LDAP)

Number of hash buckets:1
Name of your Organisation: XYZ
Default Org Short Name: XYZ
Identity manager DN Location: dc=com

After a reboot, TIM was up and running. The first login was done using itim manager, password:secret.

Additionally we also used Tivoli Directory Integrator to setup agentless communication with the sytems being provisioned.