Configuring Tivoli Directory Integrator 

---

Configure IBM® Tivoli® Directory Integrator to synchronize and exchange information between the Profiles database and your LDAP directory.

Before you begin

Ensure that you have installed all the required software, including a database server and LDAP directory, and that you have created the Profiles database.

Note:

The internal name of the Profiles database is PEOPLEDB.

About this task

Use Tivoli Directory Integrator to populate the Profiles database repository from an LDAP directory.

You can manually run various Profiles tasks by using the appropriate scripts in the TDI Solution directory. For more information about these tasks, see the Batch files for processing Profiles data topic.

To configure Tivoli Directory Integrator, complete the following steps:

Procedure

1. Install Tivoli Directory Integrator, if it is not already installed.
   
When prompted for the location of the Solution directory, select Do not specify. Use the current working directory at startup time.

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

After you have configured Tivoli Directory Integrator, update it with the recommended fix packs.

2. Make the database libraries available to Tivoli Directory Integrator by doing one of the following:
• 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 the jvm/jre/lib/ext subdirectory of Tivoli Directory Integrator.
For example, if you installed Tivoli Directory Integrator on a Linux® system in /opt/IBM/TDI/V7.0, the path would be /opt/IBM/TDI/V7.0/jvm/jre/lib/ext.

• Oracle: Copy the ojdbc14.jar file from the jdbc/lib subdirectory of the directory where you installed Oracle. Paste it into the jvm/jre/lib/ext subdirectory of the Tivoli Directory Integrator directory.
For example, if you installed Tivoli Directory Integrator on a Linux system in /opt/IBM/TDI/V7.0, the path would be /opt/IBM/TDI/V7.0/jvm/jre/lib/ext.

• SQL Server:
Download the SQL Server JDBC 2 driver from the Microsoft® web site and follow the instructions to extract the driver files. IBM Connections uses the sqljdbc4.jar file.

IBM recommends that you obtain this Microsoft hotfix for the JDBC 2 driver for production deployments.

For example: If you installed Tivoli Directory Integrator on a Windows® system in C:\Program Files\IBM\TDI\V7.0, the path would be C:\Program Files\IBM\TDI\V7.0\jvm\jre\lib\ext.

If the database is hosted on a separate system, copy the database JAR file to the system hosting Tivoli Directory Integrator.

3. Edit the ibmdisrv file to increase runtime memory and disable the JIT compiler. To increase the runtime memory, add the -Xms256M and -Xmx1024M arguments to the Java™ invocation command; to disable the JIT compiler, add the -Xnojit argument. The ibmdisrv file is stored in the TDI directory.:
• AIX® or Linux: ibmdisrv
After you add the new arguments, the Java invocation command is similar to the following text:



"$TDI_JAVA_PROGRAM" -Xms256M -Xmx1024M $TDI_MIXEDMODE_FLAG -Xnojit -cp "$TDI_HOME_DIR/IDILoader.jar" 

"$LOG_4J" com.ibm.di.loader.IDILoader com.ibm.di.server.RS "$@"



• Windows: ibmdisrv.bat
After you add the new arguments, the Java invocation command is similar to the following text:



"%TDI_JAVA_PROGRAM%" -Xms256M -Xmx1024M -Xnojit -classpath "%TDI_HOME_DIR%\IDILoader.jar" 

%ENV_VARIABLES% com.ibm.di.loader.IDILoader com.ibm.di.server.RS %*"  



4. (AIX or Linux only.) In the Solution directory, execute the following commands to ensure that the script files are executable:
   
chmod +x *.sh

chmod +x netstore

5. (AIX or Linux only.) Ensure that there is a localhost entry in the /etc/hosts file.
   
For example:



127.0.0.1    localhost



Introduction to IBM Tivoli Directory Integrator
IBM Connections uses IBM Tivoli Directory Integrator to transform, move, and synchronize data from your LDAP directories to the Profiles database.

Parent topic: Populating the Profiles database

Related tasks
Adding LDAP data to the Profiles database
Deleting or inactivating users in the Profiles database

Related reference
Report-to chains for Profiles
IBM Connections system requirements
Batch files for processing Profiles data
SQL Server 2005 JDBC 2 driver
Microsoft hotfix for the JDBC 2 driver