Tivoli Directory Integrator is used to move data between our LDAP source (in this case Domino) and our DB2 (or SQL or Oracle) profiles database (PEOPLEDB). IBM supply a range of Wizards and batch files to achieve this and they all depend on having TDI installed somewhere.
Once the TDI installer is extracted we run ./launchpad.sh in Linux (or launchpad.exe in Windows) to start installing TDI.
On linux this may fail because there is a script that validates if a supported browser version is installed. The script is a bit old and only checks for Firefox numbers beginning 1x and 2x – we’re currently on Firefox 35 and growing. To workaround that validation modify the file browser.sh in the launchpad directory as follows
The regedit syntax using [1-9][0-9] should cover any version Mozilla release for a couple of years 🙂
Now launchpad.sh should run
I choose a custom install because we only need a limited set of features installed for our purposes.
In theory I only need the Server component – the CE (Configuration Editor) is for creating and managing AssemblyLines. In a simple install we don’t use it but I like to install it regardless and it’s very likely we will use it to customise our directory sync activity.
The working directory should not be a static choice. Each time one of our TDI scripts runs, the parameters for that script will come from the directory it exists in. By not setting a working directory we are able to run multiple scripts from different locations with different settings.
Once TDI 7.1.1 is installed we need to patch it to fixpack 5 before doing anything further. After downloading the fixpack (7.1.1-TIV-TDI-FP0005.zip) and extracting it there will be a file called UpdateInstaller.jar in the extracted directory.
Copy the new UpdateInstaller.jar file to /opt/IBM/TDI/V7.1.1/maintenance
Copy the extracted fix TDI-7.1.1-FP0005.zip to a convenient location – in this case I’m using the directory where I’m going to run the update from /opt/IBM/TDI/V7.1.1/bin
To apply the fixpack we run ./applyUpdates.sh -update <fixpackfilelocation>
Once the updates have been applied we can verify it ran successfully using:
which shows us both components installed and patch levels for each.
In our environment we are installing TDI on the same server where DB2 is installed but if we weren’t we would have to copy the DB2 library files over to the TDI server so the two can communicate.