Tivoli® Directory Integrator Solution commands
The following IBM® Tivoli® Directory Integrator Solution (tdisol) commands are available for managing profile data and performing user data synchronization tasks. These commands are also known as Assembly Lines.
Tivoli® Directory Integrator Solution commands
For related information, see Developing custom Tivoli® Directory Integrator assembly lines for Profiles.
Command | Description |
---|---|
AIX® and Linux™:
clearLock.sh Microsoft™
Windows™:
|
Deletes the lock file that is generated by the
sync_all_dns command. For more information, see Synchronizing source changes such as LDAP with Profiles. |
AIX® and Linux™: delete_or_inactivate_employees.sh Microsoft™
Windows™:
|
Deletes or inactivates users in the Profiles database. For more information, see Deleting or inactivating users in the Profiles database. |
AIX® and Linux™: dump_photos_to_files.sh Microsoft™
Windows™:
|
Reads existing photo files from the Profiles database and stores them on disk.
Used in conjunction with the load_photos_from_files command. For more information, see Populating Profiles with photos. |
AIX® and Linux™: dump_pronounce_to_files.sh Microsoft™
Windows™:
|
Reads existing pronunciation files from the Profiles database and stores them
on disk. Used in conjunction with the load_pronounce_from_files command. For more information, see Uploading pronunciation files. |
AIX® and Linux™: fixup_tdi_adapters.sh Microsoft™
Windows™:
|
Adds a reference to the profiles property store to your adapter files when you
are defining a custom assembly line to contain the logic used for the delete operation. For more information, see Customizing the logic used for the delete operation. |
AIX® and Linux™: load_photos_from_files.sh Microsoft™
Windows™:
|
Reads stored photo files from disk and populates the Profiles database with
them. Used in conjunction with the dump_photos_to_files command. For more information, see Populating Profiles with photos. |
AIX® and Linux™: load_pronounce_from_files.sh Microsoft™
Windows™:
|
Reads stored pronunciation files from disk and populates the Profiles database
with them. Used in conjunction with the dump_pronounce_to_files command. For more information, see Uploading pronunciation files. |
AIX® and Linux™: process_draft_updates.sh Microsoft™
Windows™:
|
Synchronizes changes from the Profiles database back to the LDAP directory.
The script initializes a daemon process that monitors the Profiles database for updates, formats
each update as a DSML request, and the transmits it to a configured DSML server. For more information, see Synchronizing user data between Profiles and the LDAP directory. |
AIX® and Linux™: process_ad_changes.sh Microsoft™
Windows™:
|
Processes changes made to a Microsoft™ Active Directory LDAP directory and propagates the changes to the corresponding
records in the Profiles database repository. For more information, see Synchronizing IBM® Tivoli® Directory Server and Microsoft™ Active Directory LDAP changes. |
AIX® and Linux™: process_tds_changes.sh Microsoft™
Windows™:
|
Processes changes made to an Tivoli® Directory Server LDAP directory and propagates the changes to
the corresponding records in the Profiles database repository. For more information, see Synchronizing IBM® Tivoli® Directory Server and Microsoft™ Active Directory LDAP changes. |
AIX® and Linux™: reset_draft_iterator_state.sh Microsoft™
Windows™:
|
Deletes the value of a database change record number tracked in a persistent
field by the process_draft_update command. For more information, see Synchronizing user data between Profiles and the LDAP directory. |
AIX® and Linux™: set_draft_iterator_count.sh Microsoft™
Windows™:
|
Resets the value of a database change record number tracked in a persistent
field by the process_draft_update command. For more information, see Synchronizing user data between Profiles and the LDAP directory. |
AIX® and Linux™: sync_all_dns.sh Microsoft™
Windows™:
|
Synchronizes LDAP directory changes with the Profiles database. For more information, see Synchronizing source changes such as LDAP with Profiles. |