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 WebSphere® Application Server, 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 | cluster_name}
wsadmin.sh [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
{node_name server_name | cluster_name}
where:
- -conntype
none is
optional, and is needed only if the application server or deployment
manager is not running.
- -profileName profile_name is
optional, and is the name of the profile in which the UDDI application
is deployed. If you do not specify a profile, the default profile
is used.
- node_name and server_name are
the names of the WebSphere Application
server node and the application server in which the UDDI application
is deployed. These are the names that you specified when you ran the
uddiDeploy.jacl script to install the UDDI application.
- cluster_name is
the name of the WebSphere Application Server cluster
in which the UDDI application is deployed. This is
the name that you specified when you ran the uddiDeploy.jacl script
to install the UDDI application.
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.