Report problems with the UDDI Registry

 

+

Search Tips   |   Advanced Search

 

 

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.
   • If you were using a UDDI client
   • Client error seen
   • Type of client program
   • Details of the request issued
   • Exact sequence
   • Result

2. The build date and time of the UDDI registry version...

   cd install_root/profiles/profile/installedApps/cell/UDDI_Registry.node.servername.ear
   cat version.txt

3. Platform type and version.

4. Database type and version.

5. Whether the database is local or remote.

6. Standalone or a network deployment configuration.

7. If ND, is it a cluster.

8. Is UDDI node default or customized.

9. The language used, for example, Chinese.

10. If the problem occurred while running uddiDeploy.jacl, supply the log output from running the script.

    See also: Setting up a default UDDI node.

11. If the problem occurred while removing the UDDI Registry application using the remove script, uddiRemove.jacl, supply the log output from running the script.

12. Enable UDDI tracing using...

    com.ibm.uddi.*=all

    In trace.log look for...

    getUDDIMessageLogger

    UDDI Build

13. Supply WebSphere log files system.out and system.err.

14. Supply details of the version of WAS you are running

    versioninfo.sh

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

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

---

 

---