Remove the existing UDDI application and reinstall it by running the uddiDeploy.jacl wsadmin script from the app_server_root/bin directory. Do not use the default option even if you used this option previously to set up a default UDDI node. If you use the default option, an error might occur during deployment, or, in some circumstances, existing UDDI data might be overwritten.If you deploy the UDDI registry into a Network Deployment configuration, ensure that the deployment manager is the target.
Enter the following command at a command prompt:
wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
node_name server_name
wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
{node_name server_name | cluster_name}
Note: This procedure does not change the existing JDBC provider, data source and any J2EE Connector Architecture (J2C) authentication data entry. Your existing UDDI registry data, including UDDI entities, property settings, and policy settings, are also unaffected.