This section explains how to troubleshoot problems and describes any workarounds we can use.
If you receive connection errors when you try to run an AssemblyLine, verify that we have started the server associated with the project. This is usually the Default server unless it has been reconfigured to a different server. Also check the logs/ibmdi.log file in your server's working directory. This log file shows indications of server errors that prevent the Configuration Editor from running an AssemblyLine on that server.
Check the Error View in the Configuration Editor for error messages when your actions do not produce the expected results. Select Window in the main window toolbar, then select Show View > Error Log.
If the Configuration Editor by itself does not start, you may be able to pinpoint problems by looking at the very file this view represents; this file can be found in workspace/.metadata/.log, where workspace is the path to the workspace directory we have instructed TDI to use.
If you for some reason see the "Resource" perspective when you start the Configuration Editor, we should probably switch to the "TDI" perspective that shows the proper TDI views and functions. Use the Window -> Open Perspective -> Other... menu option and choose "Tivoli Directory Integrator" from the list of perspectives.
If you experience problems installing the TDI CE into a non-TDI Eclipse environment, you may have to add an additional update site where software update can access plugins for Eclipse version 3.4.1 prior to installing the TDI feature.