Before you begin
You can populate the Profiles database with the help of the population wizard, as described here, or manually as described in the Manually populating the Profiles database
topic. You might choose to use the population wizard to simplify the properties mapping process from your source to the target Profiles database.
Ensure that you have created a Profiles database, and installed and configured Tivoli
® Directory Integrator and an LDAP directory.
Run the population wizard on the system where Tivoli Directory Integrator is installed.
If you need to configure multiple systems with Profiles data, you can run the wizard in silent mode. For more information, see the Using the Profiles population wizard in silent mode topic.
The population wizard populates only those entries where the value for surname is not null.
You can run the population wizard before, during, or after installing IBM Connections.
Note: Additional and related information about configuration and mapping properties may be available in the Manually populating the Profiles database topic.
About this task
To populate the Profiles database, complete the following steps:
xhost + // Grant display authority to other users
If granting display authority to all users is a security concern for you, change the command to grant display authority to a specific user or users. For more information about this command, consult your AIX or Linux administrator guide.
echo $DISPLAY // Echo the value of DISPLAY under the root user
Important: Microsoft™ Windows™: If you are installing from disk or ISO, change the permissions for the Wizards folder from Read Only to Write or the population wizard will fail.
Note: This page is shown only if you have already used the wizard to populate the Profiles database.
Note: This page is shown only if the wizard cannot automatically detect your Tivoli Directory Integrator directory.
The name of the system that hosts the database.
The communications port for connecting to the database. Add a new port number or choose one of the following default port numbers:
The default name of the database is PEOPLEDB.
JDBC driver library path
Note: There is no default name for the Oracle database, Instead, enter the name of the database instance.
Enter the path to the JDBC driver on the host machine. For example: IBM/sqllib/java
You can find the db2jcc.jar and db2jcc_license_cu.jar files in the IBM/DB2/v9.7/SQLLIB/java directory.
You can find the ojdbc6.jar file in the oracle/product/11.2.0/db_1/jdbc/lib directory.
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.
Enter your user ID. This must be a database user who has write access to the Profiles database. For DB2, the default value is LCUSER. For Oracle and SQL Server, default value is PROFUSER. These user names are automatically created when you create the database.
Enter your password.
LDAP server name
The host name or IP address of the LDAP server.
LDAP server port
The default port is 389. If SSL is selected, the default port is 636.
Use SSL communication
Select the check box to enable SSL.
The Profiles population wizard can use the new truststore file to communicate with your LDAP server in SSL handshaking mode. It can also use the file when fetching data from your LDAP.
File where trusted server certificates are stored. Used when SSL handshaking is performed.
Password to access the keystore.
Format of the trusted server certificate. Currently only JKS and PKCS12 are supported in Java™.
If the LDAP server certificate is not in the truststore, an Accept permanently
message appears that asks you to permanently accept the certificate in the truststore file. If you do not accept it, the wizard cannot connect to the LDAP server with SSL and will not continue with the population task.
Ensure that the global.properties
file in Tivoli
Directory Integrator (TDI) is configured with the file trust store name, password and type you just created. See the Tivoli Directory Administrator’s Guide for Client SSL Configuration of TDI Components
for further instructions. The Understanding IBM Tivoli Directory Integrator for IBM Connections
white paper is also helpful.
Oracle 10gR2 is supplied with the ojdbc14.jar
JDBC driver while Oracle 11gR2 is supplied with ojdbc6.jar
Note: The Profiles population wizard does not support anonymous binding for LDAP. If you wish to populate the Profiles database using anonymous binding, you must populate the database manually.
For more information about each attribute and function, see Table 2
in the Mapping fields manually
The uid, guid, dn, surname, and displayName attributes are always required.
You can use the Group By filter in Metrics to categorize the metrics report by a particular user attribute. To do so, ensure correct mapping between the LDAP attribute and the Profiles database field. Metrics defines the Group By attributes by default as country, organization and title. See the Metrics documentation for more information.
Add country data to each profile.
Add department data to each profile.
Add organization data to each profile.
Add employee-type data to each profile.
Add location data to each profile.
if you want to mark the profiles of each manager.
Employee types task
Work locations task
For all the entries in this list (except Mark managers), you need to prepare corresponding CSV files with the required information. An Employee Types CSV file might include regular=IBM Employee and manager=IBM Manager. You can edit the profiles-config.xml file to specify whether you want to display the code or the value, where regular or manager are the employee type codes stored in LDAP and IBM Employee or IBM Manager are the values.
Examine the CSV files in the Wizards/TDIPopulation/TDISOL/OS/samples directory, where OS is your operating system, to see the input file format of the optional tasks:
Log into the system where Tivoli Directory Integrator is installed as the root user or system administrator.
(AIX and Linux only): Grant display authority to all users by running the following commands under the root user or system administrator:
Copy the Wizards directory from the IBM Connections installation media to the system where Tivoli Directory Integrator is installed.
Run the following script from the Wizards directory:
Note: If the wizard does not run correctly, you might need to edit the populationWizard.sh file and enter the correct JRE/JVM path for your system The populationWizard.sh file expects the path to be jvm/linux/jre/bin.
Microsoft Windows: populationWizard.bat
On the Welcome page of the wizard, click Launch Information Center to open the IBM Connections Information Center in a browser window. Click Next to continue.
Select Default settings or, if you are resuming an earlier session, click Last successful default settings and click Next.
Enter the location of Tivoli Directory Integrator and then click Next.
Select a database type and click Next.
Enter the following information about the database, and then click Next:
Enter the following properties for the LDAP server, and then click Next:
(Optional) Create an empty truststore file where you can store trusted LDAP server certificates. (Complete this step if you want to use SSL. If you already have a truststore file that contains your LDAP server certificates, you can skip this step.) The Profiles population wizard downloads the LDAP server certificates from your LDAP directory for you.
where TDI_Install_directory is the directory where Tivoli Directory Integrator is installed.
Note: On the Windows 7 and Windows 2008 operating systems, right-click ikeyman.exe and select Run as administrator.
Note: You need this password when you use the Profiles population wizard.
Start the iKeyman utility by running the following file:
AIX or Linux:TDI_Install_directory/jvm/jre/bin/./ikeyman
Click Key Database File from the menu bar and then click New.
Select JKS or PKCS12 as the key database type.
Save the new file to an appropriate location and click OK.
Enter a password in the Password Prompt dialog box and then confirm the password. Click OK.
Exit the iKeyman utility.
Optional: If you selected SSL when you entered the LDAP properties, you are asked to enter the following keystore properties:
Enter the authentication details for the Bind distinguished name (DN) and Bind password, and then click Next.
Enter the details of the Base distinguished name (LDAP user search base) and LDAP user search filter, and then click Next.
Map LDAP attributes or JS Functions to the Profiles database fields.
If you are prompted to supply a profile type value, see the Profile-types topic for available options.
Optional: You can choose to run the following additional tasks:
Review the Summary page to ensure that the information you entered in the previous panels is correct. Click Configure to begin populating the database.
Review the message on the Result page. If necessary, click View log to examine the log in detail. Click Finish to exit the wizard.
The Profiles population wizard has populated the Profiles database with data from your LDAP directory.
Parent topic: Adding source data to the Profiles database
Understanding how the sync_all_dns process works
Managing the Search index
Using the Profiles population wizard in silent mode
Manually populating the Profiles database
Mapping fields manually
Populating the Profiles database
Attribute mapping for Profiles
SQL Server 2005 JDBC 2 driver
Microsoft hotfix for the JDBC 2 driver
Tivoli Directory Integrator solution properties for Profiles
Supplemental user data for Profiles
Configuring the Manager designation in user profiles