UDDI registry problem reporting

This topic describes information, such as log files, that you should supply to IBM if you have performed problem determination on the UDDI registry component, but cannot resolve the problem. Before reporting a problem, perform problem determination as described in UDDI registry troubleshooting . If you report a problem with the UDDI registry component to IBM, supply the following information:

• A detailed description of the problem. For example, if you were using a UDDI client, describe the client error seen and the type of client program, and provide details of the request issued. If you were using the UDDI user interface, describe the exact sequence you followed, and the result.

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

  • In the profile_root/installedApps/cell subdirectory of the WebSphere installation location, you will find a subdirectory called UDDI_Registry.node.servername.ear, where node 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 tracing enabled for the UDDI component, you should find a trace entry in the WebSphere trace log that includes the strings "UDDIMessageLogger" and "UDDI Build :" followed by the build date and time, and the build system. Also include this information.

• Other environment information, such as:

  • Platform.

  • Database product.

  • Whether the database is local or remote, or for Cloudscape, whether it is embedded or networked.

  • Whether the server is in a standalone or a network deployment configuration.

  • If the server is in a network deployment configuration, whether it is in a cluster or not.

  • Whether the UDDI node is default or customized.

  • The language used, for example, Chinese.

• Any relevant log files and trace files.

  • If the problem occurred while setting up and installing the UDDI registry application using the setup script uddiDeploy.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 Setting up a customized UDDI node or Setting up a default UDDI node.) 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 the remove script, uddiRemove.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 a UDDI registry node.) The log file is written to the directory from which you ran the remove script.

  • 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 UDDI registry troubleshooting for details on how to enable UDDI tracing. The Trace string that is most useful for initial analysis of problems by IBM is "com.ibm.uddi.*=all".

  • 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 running the command versioninfo (Windows platforms) or versioninfo.sh (Linux and UNIX platforms) on the application server node and directing the output to a log file.

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

• UDDI utilizes First Failure Data Capture (FFDC) to capture data for unexpected UDDI errors.

  Run the WebSphere collector tool to collect the FFDC data and send the resulting jar to IBM. See Run the collector tool.

---

Related tasks
UDDI registry troubleshooting

 

---