Reporting problems with the IBM WebSphere UDDI Registry

Before you begin

If you report a problem with the IBM WebSphere UDDI Registry component to IBM, 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 installation 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. Include the contents of this file as part of your information.
    • If the UDDI Registry has been started with Turning on UDDI trace for the UDDI component, you should find a trace entry in the WebSphere trace log that includes the strings "getUDDIMessageLogger" and "UDDI Build :" followed by the build date and time, and the build system. 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, supply the log output from running the script. (If you did not redirect the output from the script file to a log file, rerun the script, this time redirecting the output as described in the section 'Installing and Setting up a UDDI Registry'.) The log file is written to 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, supply the log output from running the script. (If you did not redirect the output from the script file to a log file, 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 is written to 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, supply the log file UDDIloadDB.log, which is written to the directory from which the wizard was run.
    • If the problem occurred while running the UDDI Registry, enable UDDI tracing (if not already enabled) and supply the trace log from the logs directory of the application server on which the UDDI Registry was running. See 'Turning on UDDI Trace' for details on how to enable UDDI tracing.
    • Also supply the WebSphere log files system.out and system.err.
    • Supply details of the version of IBM WebSphere Application Server you are running by executing the command versioninfo (Windows) or versioninfo.sh (Unix platforms) on both the application server and deployment manager nodes and directing the output to a log file.
  4. If appropriate, any application code that you are using and the output produced by the application code.

In addition to the above, it is useful to run the WebSphere collector tool and send the resulting jar file(s) (two files if run from base application server AND DeploymentManager) to IBM. See Running the collector tool


Related reference
Enabling Universal Description, Discovery and Integration (UDDI)



Searchable topic ID:   twsu_report
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsu_report.html

Library | Support | Terms of Use | Feedback