Universal description, discovery, and integration (UDDI) GUI does not start after renaming the Windows user account
 Technote (troubleshooting)
 
Problem(Abstract)
If you use the WebSphere® Application Server Network Deployment UDDI product on Windows® 2000, changing the name of the Administrator account results in errors during startup. In addition, after changing the user ID value in the Custom Properties for the UDDI server V4 DB2® data source in the administrative console, the UDDI GUI does not start.
 
Cause
The following error displays in the SystemOut.log:

Ý08/10/03 17:06:42:656 BST¨ 6533c2e0 ras A
com.ibm.uddi.gui.UddiActionServlet initOther UDUC0001I: IBM WebSphere
UDDI Registry user console starting initialization.
Ý08/10/03 17:06:45:734 BST¨ 6533c2e0 ras E
com.ibm.uddi.gui.UddiActionServlet initOther UDUC0013E: User console
initialisation failed to initialize tModels. Exception: <null>
 
Resolving the problem

There are two possible solutions for this problem:
  1. Run setupdb2uddi.jar.

    To set up the UDDI registry in DB2 you must run the setupdb2uddi.jar file in the $WAS_HOME/deploymentManager/UDDIReg /scripts directory. This opens a wizard that asks for the db2 user ID and password.
    1. Run setCmdLine.bat
    2. Run %JAVA_HOME%\bin\java -jar setupdb2uddi.jar -W db2info.userid= DB2 User ID -W db2info.password= DB2 Password -goto WindowsReplaceDB

      If you choose to run the setupdb2uddi.jar that allows the UDDI application to start with the new Windows account user ID, be aware that this step recreates the database used by UDDI with a schema name of newId. This results in the loss of all data about Web services previously published to that UDDI. You must republish all the Web services.
  2. Use the IBM WebSphere UDDI Registry user console to specify a user ID of user on the WebSphere Application Server UDDI.DataSource custom property. This user ID is different than the user ID used to create the UDDI20 database using the setupdb2uddi.jar script.

    Using this method, the existing DB2 data can be preserved. This method is suitable if you want to change the userid without recreating the database from scratch.

    This method is preferable if you already have an existing UDDI20 database containing published entries and you need to change the user ID used to access the database. This option eliminates the need to recreate the database and republish all your Web services.

    Use this method to create the UDDI20 database under a privileged user, then specify a less-privileged user on the WebSphere Application Server data source (in the UDDI setup script) to access the database.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Web Services (for example: SOAP or UDDI or WSGW or WSIF)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1143981
IBM Group: Software Group
Modified date: Aug 18, 2004