Reporting problems with the IBM WebSphere UDDI Registry

 

If you report a problem with the IBM WebSphere UDDI Registry component to IBM, please supply the following information:

  1. A detailed description of the problem.

  2. The build date and time of the version you are using. This can be obtained as follows:

    • In the installedApps subdirectory of the WebSphere install location, you will find a subdirectory called UDDI_Registry.<nodename>.<servername>.ear, where <nodename> is the name of the node into which the UDDI Registry application is installed, and <servername> is the name of the server. Within that subdirectory, you will find a file called version.txt. Please include the contents of this file as part of your information.

    • If the UDDI Registry has been started with tracing enabled for the UDDI component, then find a trace entry in the WebSphere trace log which includes the strings " getUDDIMessageLogger" and "UDDI Build :" followed by the build date and time, and the build system. Please also include this information.

  3. Any relevant log files and trace files.

    • If the problem occurred while setting up and installing the UDDI Registry application using one of the setup scripts, setupuddi.jacl or appserversetupuddi.jacl, then please supply the log output from running the script. (If you had not chosen to redirect the output from the script file to a log file, then please rerun the script, this time redirecting the output as described in the section 'Installing and Setting up a UDDI Registry'.) The log file will be in the directory from which you ran the setup script.

    • If the problem occurred while removing the UDDI Registry application using one of the remove scripts, removeuddi.jacl or appserverremoveuddi.jacl, then please supply the log output from running the script. (If you had not chosen to redirect the output from the script file to a log file, then please rerun the script, this time redirecting the output as described in the section 'Removing the UDDI Registry from a deployment manager cell' or 'Removing the UDDI Registry application from a single appserver'.) The log file will be in the directory from which you ran the remove script.

    • If the problem occurred while creating the UDDI Registry database using the UDDI DB2 Setup Wizard, then please supply the log file UDDIloadDB.log, which will be in the directory from which the wizard was run.

    • If the problem occurred while running the UDDI Registry, please enable UDDI tracing (if not already enabled) and supply the trace log from the logs directory of the appserver on which the UDDI Registry was running. Please refer to the section on 'Turning on UDDI Trace' for details on how to enable UDDI tracing.

  4. If appropriate, any application code that you are using and the output produced by the application code.

In addition to the above, it might be useful to run the WebSphere collector tool and send the resulting jar file(s) (two files if run from Base AppServer AND DeploymentManager) to IBM. Instructions on running the collector tool can be found at Running the collector tool

IBM WebSphere UDDI Registry

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.