Configure IBM® Tivoli® Directory Integrator (TDI)
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 TDI 7.1.1 with fixpack 3, a database server and LDAP directory, and that
you have created the Profiles database. Refer to this technote
for more information about TDI installation.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. It is assumed you are using the profiles population wizard,
as some of the following information pertains specifically to that
method.
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
- Install Tivoli Directory
Integrator, if it is not already installed.
When
prompted for the location of the TDI 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.
- Make the database available to Tivoli Directory Integrator by doing one of
the following, depending on the database software provider:
Note: The
following information assumes that 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 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.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.
Note: If you
only run the manual mode, you must copy the files.
- Oracle: Copy the ojdbc6.jar file from
the jdbc/lib subdirectory of the directory where
you installed Oracle. 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 the jvm/jre/lib/ext subdirectory
of Tivoli Directory Integrator.
- SQL Server:
Download the SQL Server JDBC 4.0 driver from the Microsoft web site and follow the instructions to
extract the driver files. IBM 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 the
jvm/jre/lib/ext subdirectory of Tivoli
Directory Integrator.
If the database is hosted on a separate system, copy the database
JAR file to the system hosting Tivoli Directory
Integrator.Note: As a result of this step, the database files are
placed in the jvm/jre/lib/ext TDI directory.
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 the jars\3rdparty\others TDI
directory.
- Edit the ibmdisrv file to increase runtime memory. To increase the runtime
memory, add the two -Xms1024M
-Xmx2048M space-separated arguments to the Java invocation command.
Note: On Linux systems the file name is ibmdisrv. On Windows systems the file
name is ibmdisrv.bat. On both systems the file is located in the main TDI
directory.
- AIX® or Linux:ibmdisrv
After you add the new arguments to increase runtime
memory, the Java invocation command might look like the
following
example:
"$TDI_JAVA_PROGRAM" -Xms1024M -Xmx2048M $TDI_MIXEDMODE_FLAG -cp
"$TDI_HOME_DIR/IDILoader.jar" "$LOG_4J" com.ibm.di.loader.ServerLauncher "$@" &
Note: Do
not copy and paste the example into your ibmdisrv file. Add the two arguments
without changing any of the other arguments.
- Windows: ibmdisrv.bat
After
you add the new arguments, the Java invocation command might
look like the following example:
"%TDI_JAVA_PROGRAM%" -Xms1024M -Xmx2048M -classpath "%TDI_HOME_DIR%\IDILoader.jar"
%ENV_VARIABLES% com.ibm.di.loader.ServerLauncher %*
Note: Do
not copy and paste the example into your ibmdisrv.bat file. Add the two
arguments without changing any of the other arguments.
- (AIX or Linux only.) In the TDI solution directory,
execute the chmod +x *.sh command to ensure that
the script files are executable.
- (AIX or Linux only.) Ensure that there is a localhost entry
in the /etc/hosts file. For example:
127.0.0.1 localhost