Batch files for processing Profiles data 

---

IBM® Connections provides several batch files that automate the collection and processing of LDAP data for the Profiles database.

Batch file functions

Note: The name of each batch file ends with the .sh suffix for the IBM AIX® and Linux™ operating systems and with the .bat suffix for the Microsoft™ Windows™ operating system.

The following list describes each batch file and its functions. You can search for more information about these files in the help topics.

clearLock

Delete the lock file that is generated by the sync_all_dns batch file.

collect_dns

Create a file called collect.dns that contains the distinguished names from the LDAP directory. This batch file is used in the first step of the process to populate the Profiles database.

delete_or_inactivate_employees

Deactivate employee records in the Profiles database. The records are not removed from the Profiles database but are set to an inactive state and the employee login and mail address values are removed. These changes are propagated to the member and login tables in the databases of installed applications. The records to be deactivated are defined in the delete_or_inactivate_employees.in file. To remove users from only the Profiles database, change the value of the sync_delete_or_inactivate property in the profiles_tdi.properties file to delete.
Note: You must manually create the delete_or_inactivate_employees.in file. Use the following format for adding entries:

• • $dn:cn=Any User3,cn=Users,l=WestfordFVT,st=Massachusetts,c=US,ou=Lotus,o=Software Group,dc=ibm,dc=com uid:Any User3

dump_photos_to_files

Copy all the photos from the PHOTO table in the Profiles database to a folder on the local system called dump_photos. This batch file also creates a local file called collect_photos.in that contains the UID and URL of each photo.

dump_pronounce_to_files

Copy all the pronunciation files from the PRONUNCIATION table in the Profiles database to a folder on the local system called dump_pronounce. the local files. This batch file also creates a local file called collect_pronounce.in that contains the UID and URL of each pronunciation file.

fill_country

Populate the COUNTRY table in the Profiles database from the isocc.csv file.

fill_department

Populate the DEPARTMENT table in the Profiles database from the deptinfo.csv file.

fill_emp_type

Populate the EMP_TYPE table in the Profiles database from the emptype.csv file.

fill_organization

Populate the ORGANIZATION table in the Profiles database from the orginfo.csv file.

fill_workloc

Populate the WORKLOC table in the Profiles database from the workloc.csv file.

load_photos_from_files

Load all the photos from the dump_photos folder on the local system to the PHOTO table in the Profiles database. This batch file reads the collect_photos.in file and the dump_photos folder that you created with the dump_photos_to_files batch file. This batch file loads photos only for people who are already recorded in the database.

load_pronounce_from_files

Load all the pronunciation files from the dump_pronounce folder on the local system to the PRONUNCIATION table in the Profiles database. This batch file reads the collect_pronounce.in file and the dump_pronounce folder that you created with the dump_pronounce_to_files batch file. This batch file loads pronunciation files only for people who are already recorded in the database.

mark_managers

Set the PROF_IS_MANAGER field in the Profiles database, based on the value of the PROF_MANAGER_UID field in the employee records.

populate_from_dn_file

Populate the Profiles database from the source LDAP directory. This batch file reads the collect.dns data file that you created with the collect_dns batch file. The batch file also updates existing employee records in the Profiles database.

process_ad_changes

Synchronize LDAP directory changes with the Profiles database when your LDAP directory type is Microsoft Active Directory. This batch file is stored in the <solution-dir>/Samples directory. For more information, go to the Active Directory Change Detection Connector topic in the Tivoli Directory Integrator information center. For information about permissions, go to this How to poll for object attribute changes topic.
Note: The sync_all_dns script is recommended when you want to synchronize changes in the LDAP directory with the Profiles database.

process_draft_updates

Synchronize changes from the Profiles database back to the LDAP directory.

process_tds_changes

Synchronize LDAP directory changes with the Profiles database when your LDAP directory type is IBM Tivoli® Directory Server. This batch file is stored in the <solution-dir>/Samples directory.
Note: The sync_all_dns script is recommended when you want to synchronize changes in the LDAP directory with the Profiles database.

sync_all_dns

Update the Profiles database to capture changes to the LDAP directory. This synchronization process includes updates to employee records and additions and deletions of records.

tdienv

Set the correct environment for IBM Tivoli Directory Integrator. This batch file sets the path to the Tivoli Directory Integrator program, the Tivoli Directory Integrator host, and the Tivoli Directory Integrator port. If you installed Tivoli Directory Integrator to a custom location, modify the path to that location before using this batch file.

Parent topic

Manually populating the Profiles database

Related concepts
Populating a large user set

Related tasks
Configure Tivoli Directory Integrator
Add LDAP data to the Profiles database
Mapping fields manually
Update Profiles when changing LDAP directory
Synchronize IBM Tivoli Directory Server and Microsoft Active Directory LDAP changes
Delete or inactivating users in the Profiles database

Related reference
Tivoli Directory Integrator properties

+

Search Tips   |   Advanced Search