Run the uddiDeploy.jacl script as shown, from the app_server_root/bin
directory. This script
deploys the UDDI registry to a server or cluster that you specify.
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
is not running.
- '-profileName profile_name'
is the deployment manager profile. If you do not specify a profile, the default
profile is used.
- node_name is the name of the WebSphere Application
Server node on which the target server runs. The node name is case sensitive.
- server_name is the name of the target server on which
you wish to deploy the UDDI registry, for example, server1. The server name
is case sensitive.
- cluster_name is
the name of the target cluster into which you wish to deploy the UDDI registry.
The cluster name is case sensitive.
![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
For example, to deploy UDDI on node 'MyNode' and
server 'server1' on a Windows system, (assuming that server1 is already started):
wsadmin -f uddiDeploy.jacl MyNode server1
![[AIX HP-UX Linux Solaris Windows]](../../dist.gif)
To deploy
UDDI into cluster 'MyCluster' on a Windows system:
wsadmin -f uddiDeploy.jacl MyCluster
![[i5/OS]](../../iseries.gif)
For example, to deploy UDDI on node 'MyNode' and server
'server1', (assuming that server1 is already started):
wsadmin -f uddiDeploy.jacl MyNode server1
![[i5/OS]](../../iseries.gif)
To
deploy UDDI into cluster 'MyCluster':
wsadmin -f uddiDeploy.jacl MyCluster
![[z/OS]](../../ngzos.gif)
For example, to deploy UDDI on node 'MyNode' and server 'server1'
(assuming that server1 is already started):
wsadmin.sh -f uddiDeploy.jacl MyNode server1
![[z/OS]](../../ngzos.gif)
To deploy
UDDI into cluster 'MyCluster' :
wsadmin.sh -f uddiDeploy.jacl MyCluster
You can also deploy the UDDI application
(the uddi.ear file) using the administrative console, in the normal way. However,
if you use the administrative console, some steps that the uddiDeploy.jacl
script performs automatically do not occur. If you use the administrative
console to install the UDDI application, you must perform some actions manually.
To do this, use the following steps:
- Install the application.
- Click > uddi_application > .
- Ensure that Class loader order is set to Classes
loaded with application class loader first.
- Ensure that WAR class loader policy is set to Single
class loader for application.