Reinstalling the UDDI Registry application
Overview
Perform this task if you want to continue providing UDDI services with your existing UDDI database, but require that the UDDI application code be changed.
Procedure
- Make a note of any changes that you have made to the installed UDDI application that you wish to keep, for example changes to security role mappings, changes to the deployment descriptor (web.xml) in v3soap,war, v3gui.war, v3soap.war, or soap.war, or customization of the UDDI user interface (GUI). All such changes will be lost during the reinstallation process; any changes that you wish to keep will need to be reapplied later.
- Run the wsadmin script uddiDeploy.jacl from the install_root/bin directory, as shown, noting that:
- You should not specify the default option even if you previously used this option to set up a default UDDI node using Cloudscape.
- If you are deploying the UDDI Registry into a network deployment scenario, ensure that the deployment manager is the target.
At a command prompt enter:
wsadmin [-conntype none] –f uddiDeploy.jacl node servernamewsadmin [-conntype none] –f uddiDeploy.jacl {node servername | cluster_name}
where
The output from this command can optionally be redirected to a log file by adding '> log_name.log' at the end of the command, where log_name.log is the name of the log file to be created.
The command removes the existing UDDI application and reinstalls it.
Note: Your existing JDBC provider, datasource and any J2C authdata entry will be unchanged by this procedure . Your existing UDDI Registry data, including UDDI entities as well as property and policy settings, will also be unaffected.