Home

 

Use the Profiles population wizard

 

+

Search Tips   |   Advanced Search

 

Use the Profiles population wizard to populate the Lotus Connections Profiles database with data from the LDAP

Before starting...

Notes


Populate the Profiles database

  1. (AIX or Linux.) Login or switch to root user.

  2. Copy the Wizards from the Lotus Connections installation media to the system where Tivoli Directory Integrator is installed.

    For 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.

  3. Run

      cd Wizards/Directory
      ./populationWizard.sh

    If the wizard does not run correctly, you might need to edit populationWizard.sh and enter the correct JRE/JVM path for your system. The populationWizard.sh file expects the path to be...

      jvm/linux/jre/bin

  4. On the Welcome page of the wizard, click Launch Information Center

  5. Select Default settings or, if you are resuming an earlier session, click Last successful default settings and click Next.

    This page is shown only if you have already used the wizard to populate the Profiles database.

  6. Enter the location of Tivoli Directory Integrator (TDI) and then click Next.

    This page is shown only if the wizard cannot automatically detect your TDI

  7. Select a database type and click Next.

  8. Enter the following information about the database, and then click Next:

      Host name The name of the system that hosts the database.
      Port The communications port for connecting to the database. Add a new port number or choose one of the following default port numbers:

        DB2 50000
        Oracle 1521
        SQL Server 1433
      Database name The default name of the database is PEOPLEDB.
      JDBC driver library path Enter the path to the JDBC driver on the host machine.

      DB2 IBM/DB2/v9.5/SQLLIB/java/db2jcc.jar
      IBM/DB2/v9.5/SQLLIB/java/db2jcc_license_cu.jar
      Oracle oracle/product/10.2.0/db_1/jdbc/lib/ojdbc14.jar
      SQL Server Download and extract SQL Server 2005 JDBC 1.2 driver

      User ID 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.
      Password Enter your password.

  9. Enter the following properties for the LDAP server, and then click Next:

      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.

  10. Optional: If you selected SSL in the previous step, you are asked to enter the following keystore properties:

      Truststore file File where trusted server certificates are stored. Used when SSL handshaking is performed.
      Keystore password Password to access the keystore.
      Keystore type Format of the trusted server certificate. Currently only JKS and PKCS12 are supported in Java.

    If the LDAP server's 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.

  11. Enter the authentication details for the Bind distinguished name (DN) and Bind password, and then click Next.

    The Profiles population wizard does not support anonymous binding for LDAP. If you wish to populate the Profiles database using anonymous binding, populate the database manually. However, if your LDAP server supports both anonymous and authenticated binding, you can use the wizard to populate the Profiles database.

  12. Enter the details of the Base distinguished name (LDAP user search base) and LDAP user search filter, and then click Next.

  13. Map LDAP attributes or JS Functions to the Profiles database fields.

    For each user in LDAP, Tivoli Directory Integrator will create a row in the database, mapping each LDAP attribute or JavaScript™ function to the corresponding column in the database. The wizard automatically validates each mapping. If you need to change the default mapping, select the required LDAP attributes or JavaScript functions and create or modify the field.

  14. Optional: You can choose to run the following additional tasks:

      Countries Add country data to each profile.
      Departments Add department data to each profile.
      Organizations Add organization data to each profile.
      Employee types Add employee-type data to each profile.
      Work locations Add location data to each profile.

    Select Yes if you want to mark the profiles of each manager.

    For all the entries in this list (except Mark managers), you need to prepare corresponding CSV files with the required information. An Employee Type CSV file might include...

    • regular=IBM Employee
    • 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.

  15. Review the Summary page to ensure that the information you entered in the previous panels is correct. To make changes, click Back to return to the relevant page and edit the information. Otherwise, click Configure to begin populating the database.

  16. Review the message on the Result page. If necessary, click View log to examine the log in detail. Click Finish to exit the wizard.

 

Results

The Profiles population wizard has populated the Profiles database with data from your LDAP

 

Related tasks

Add LDAP data to the Profiles database
Administer Profiles
Manually populate the Profiles database
Populate the Profiles database
Attribute mapping for Profiles
Population functions for populating ID into PROF_GUID