You can use the population wizard to populate users from the LDAP server to the Profiles database. However, in this case, the manual process is explained. For more information on this manual population process, see:
http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/t_prof_populate_manual.html
The Profiles database must be populated with basic user information for Lotus Connections to function correctly. Before running the population wizard, you should ensure that IBM Tivoli Directory Integrator 6.1.1, including fix pack 6, is configured on the machine from where the profiles population task is run. For details, see the information center.
From the Lotus_Connections_Install directory, locate the TDISOL directory. In the TDISOL/linux directory, there are a number of files, which must be modified before starting this task. The following describes the minimum changes required to start this process. In the case where custom changes are required, it is recommended to review the information center link, and in particular the “
Mapping fields manually” section, which describes modifications that can be made at this point. In any case, it is recommended to study the information center on this topic and follow the guidance below only after you are knowledgeable about this process.
Open the file profiles_tdi.properties with a text editor and make the following changes:
- source_ldap_url=ldap://ldap.example.com:389
- source_ldap_user_login=uid=binduser,cn=users,l=location,c=US,dc=com
- {protect}-source_ldap_user_password=password
- source_ldap_search_base=l=location,c=US,dc=com
- source_ldap_search_filter=(&(uid=*)(objectclass=inetOrgPerson))
- dbrepos_jdbc_driver=oracle.jdbc.driver.OracleDriver
- dbrepos_jdbc_url=jdbc:oracle:thin:@oracle_server.example.com:1521:LSCONN.EMPINST
- dbrepos_username=PROFUSER
- {protect}-dbrepos_password=password
You can supply some optional properties at this point. A common optional property is setting the isManager field using a 1:1 mapping. To do this, ensure that you specified how to set the field in the map_dbrepos_from_source.properties file.
For example, if your LDAP has an "ismanager" field that is set to a value of Y or N, your map_dbrespos_from_source.properties file could specify the following:
- PROF_IS_MANAGER=ismanager
Notes:
If your source LDAP system uses a value other than Y or N to indicate whether the person is a manager, write a JavaScript™ function to map the value to a Y or N. Then provide a reference to that function here. If you are setting the PROF_IS_MANAGER field based on PROF_MANAGER_UID references in other employees' records, then you should run the mark managers script instead.
http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/r_report-to_chains_profiles.html
Now you can run the first task. This is to create a file containing the distinguished names (DN's) to be processed from the source LDAP Server directory. Before running this task, ensure that any custom changes are made to the profiles_tdi.properties file as required. Possible changes are discussed in the information center.
From the same directory, run the following command:
./collect_dns.sh
This creates a file called collect.dns and a log file called ibmdi.log in the /logs subdirectory of the TDI directory. Now you can begin the population of the profiles database. To do so, run the following command:
./populate_from_dn_file.sh
This task can take anywhere from a few minutes to many hours, depending on the number of users to be populated. TDI prints a message to the screen every 1,000 iterations to inform you of its progress.
If any failures or issues occur, please consult the information center. The information center also contains further instructions on how to run other optional tasks, such as mark managers, and populating the country, department, employee type, organization and work location codes to the profiles database.
Go to the next topic:
S2: Scenario environment
S2: Prerequisites
S2: Configuration diagrams
S2: Machine details
S2: Installing Lotus Connections in an Enterprise level deployment
S2: Starting Lotus Connections
S2: Configuring an administrative user for Blogs
S2: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal
S2: Enabling Sametime awareness on Lotus Connections
S2: Troubleshooting
Table of Contents:
Lotus Connections 2.5 Enterprise level deployment scenario