UDDI registry problem reporting

This page describes information, such as log files, to supply to IBM if we have performed problem determination on the UDDI registry component, but cannot resolve the problem.

Before reporting a problem, perform problem determination

If we report a problem with the UDDI registry component to IBM, supply the following information:

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

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

  • In the $WP_PROFILE/installedApps/mycell subdirectory of the installation location for WAS, you will find a subdirectory called UDDI_Registry.mynode.myserver.ear, where mynode is the name of the node into which the UDDI registry application is installed, and myserver is the name of the server. In that subdirectory, you will find a file called version.txt. Include the contents of this file as part of the information.

  • If the UDDI registry has been started with tracing enabled for the UDDI component, there is a trace entry in the appserver 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 Apache Derby, 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 we did not redirect the output from the script file to a log file, rerun the script, this time redirecting the output as.

    See also: Set 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 we did not redirect the output from the script file to a log file, rerun the script, this time redirecting the output.

    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 and supply the trace log from the logs directory of the appserver on which the UDDI registry was running.

    The Trace string that is most useful for initial analysis of problems by IBM is "com.ibm.uddi.*=all".

  • Also supply the appserver log files system.out and system.err.

  • Supply details of the version of WAS we are running by running the command versioninfo (Windows platforms) or versioninfo.sh (Linux and UNIX platforms) on the appserver node and directing the output to a log file.

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

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

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

---

 

Related tasks

UDDI registry troubleshooting