Troubleshooting problems with Tivoli Directory Integrator 

If you experience problems when using IBM Tivoli Directory Integrator to work with Profiles data, explore the different trace areas available for Profiles to find information that might help to identify and resolve the problem.


About this task

The Tivoli Directory Integrator solution used to perform actions on your Profiles deployment is made up of several interconnected components. When you are trying to determine the cause of an error, you might first need to determine which architectural layer is likely to be involved in the error, before you enable tracing for a specific component to resolve the problem.

Profiles-specific output can come from the Tivoli Directory Integrator configuration (profiles_tdi.xml) or from the component JAR files that are part of the solution. The JAR files contain business-layer functionality that is shared by the Profiles web application as well the Profiles TDI solution. Adjusting trace levels for these back-end components is very similar to the process used for the web application, and the same class hierarchical subsets can be used to view different tracing level outputs.

For more detailed information about determining the cause of problems with Tivoli Directory Integrator, refer to the following web page: http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc_7.1/pdguide.htm


Procedure


Parent topic

Resolving a problem

Related concepts
Manage user data using Tivoli Directory Integrator scripts
Error codes


Related tasks


Enable traces in WAS

+

Search Tips   |   Advanced Search