Configure Tivoli Directory Integrator

Configure Tivoli Directory Integrator

Overview

Use Tivoli Directory Integrator (TDI) to populate the Profiles database repository from an LDAP directory.
Before starting...

Install Tivoli Directory Integrator
Install a database server
Install the LDAP directory
Create the Profiles database

The internal name of the Profiles database is PEOPLEDB.
We can use the profiles population wizard or we can manually run some Profiles tasks using scripts in the TDI Solution directory.

Install and configure Tivoli Directory Integrator
Review install instructions on InfoCenter
Verify 450 MB available in /tmp
Verify 595 MB available for TDI components
Disable Security Enhanced Linux (SELinux)
setenforce 0

After TDI is installed, to renable SELinux again:
setenforce 1

We can also enable and disable SELinux by editing...
/etc/selinux/config

The default settings resemble...
# SELINUX= 
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - SELinux is fully disabled.
SELINUX=enforcing
# SELINUXTYPE= 
#     targeted - Only targeted network daemons are protected.
#     strict - Full SELinux protection.
SELINUXTYPE=targeted
The TDI installer uses a JRE (install_dir/jvm) that cannot run with the SELinux default settings. The TDI installer makes an attemp to change the security permissions for the TDI JRE so that it can run by executing...
chcon -R -t textrel_shlib_t install_dir/jvm/jre

If the installer cannot issue the chcon command, or if there is an error when issuing the command, edit the permissions manually. Errors that resemble the following output indicate that the chcon command did not work:
[root@dyn9-37-225-164 V7.1.1]# ./ibmdisrv
Failed to find VM – aborting
[root@dyn9-37-225-164 V7.1.1]# ./ibmditk
Failed to find VM – aborting
[root@dyn9-37-225-164 V7.1.1]# bin/amc/start_tdiamc.sh
Failed to find VM - aborting
Kickoff the install program...
install_tdiv711_linux_x86_64.bin

If graphics is not enabled, installation defaults to console mode.
Here is an example response file: tdi_respfile711.txt
Select locale
Choose Locale...
----------------

    1- Deutsch
  ->2- English
    3- Español
    4- Français
    5- Italiano
    6- Português  (Brasil)

CHOOSE LOCALE BY NUMBER:
Select install location
Choose Install Folder
---------------------
Where would you like to install?

  Default Install Folder: /opt/IBM/TDI/V7.1.1

ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: /opt/IBM/TDI
Select features to install
Choose Install Set
------------------

  ->1- Typical
    2- Customize...

ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS  TO ACCEPT THE DEFAULT
   : 1
When prompted for the location of the TDI solution directory, select...
Do not specify. Use the current working directory at startup time.
Solutions Directory
-------------------
A Solutions Directory is a static directory where the IBM TDI Server and Configuration Editor look for your solutions.

  ->1- Use a subdirectory named TDI under my home directory
    2- Use Install Directory
    3- Select a directory to use
    4- Do not specify - use current working directory at startup time

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:: 4
Server Port Values
ServerPort: (DEFAULT: 1099):
System Store Port: (DEFAULT: 1527):
REST API Port: (DEFAULT: 1098):
System Queue Port: (DEFAULT: 61616):

Integrated Solutions Console Port Values
HTTPS port: (DEFAULT: 13101):
Action Manager API port: (DEFAULT: 13104):
HTTP port: (DEFAULT: 13100):

At the end of the installation process, clear the check box...
Start the Configuration editor

After install check logs under...
/opt/IBM/TDI/logs
/tmp

Update TDI with recommended fix packs.

Make the database available to TDI by doing one of the following, depending on the database software provider:
The following information assumes the database server is on a separate system.

DB2
Copy the db2jcc.jar and db2jcc_license_cu.jar files from the java subdirectory of the directory where you installed DB2. Paste the files into a temporary location on the system where TDI is installed. The wizard will prompt for this location and copy the files into...
TDI_HOME/jvm/jre/lib/ext

For example, if you installed TDI on a Linux system in...
/opt/IBM/TDI/V7.1.1

...the path would be...
/opt/IBM/TDI/V7.1.1/jvm/jre/lib/ext

This is the case regardless of the database provider.
If we only run the manual mode, copy the files.

Oracle
Copy...
ORACLE_HOME/jdbc/lib/ojdbc6.jar

...into a temporary location on the system where TDI is installed. The wizard will prompt for this location and copy the files into...
TDI_HOME/jvm/jre/lib/ext

SQL Server
Download the SQL Server JDBC 4.0 driver and extract the driver files. Connections uses the sqljdbc4.jar file.
Paste the files into a temporary location on the system where TDI is installed. The wizard will prompt for this location and copy the files into...
TDI_HOME/jvm/jre/lib/ext

As a result of this step, the database files are placed in...
TDI_HOME/jvm/jre/lib/ext

This directory is on the TDI classpath, but in rare circumstances may not be close enough to the beginning of the path. If TDI throws an exception that seems to be Java related, try putting the database JAR files in...
TDI_HOME/jars/3rdparty/others

Edit TDI_HOME/ibmdisrv to increase runtime memory and disable the JIT compiler.

To increase the runtime memory, we add -Xms256M -Xmx1024M
To disable the JIT compiler, we add -Xnojit argument.

You should end up with something like...
"$TDI_JAVA_PROGRAM" -Xms256M -Xmx1024M $TDI_MIXEDMODE_FLAG -Xnojit -cp "$TDI_HOME_DIR/IDILoader.jar" "$LOG_4J" com.ibm.di.loader.ServerLauncher "$@" &

For Windows you should have something like...
"%TDI_JAVA_PROGRAM%" -Xms256M -Xmx1024M -Xnojit -classpath "%TDI_HOME_DIR%\IDILoader.jar" %ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %*

Set script files to be executable.
cd TDI_HOME
chmod +x *.sh

Verify there is a localhost entry in /etc/hosts. For example:
127.0.0.1 localhost
Parent topic:
Populate the Profiles database

Related:
Introduction to IBM TDI
Delete or inactivate users in the Profiles database
IBM Connections system requirements
Batch files for processing Profiles data