Run the uddiDeploy.jacl script as shown below, from the install_root/bin
directory, with the deployment manager as the target.
This script deploys the UDDI registry to a server (or cluster) specified by you. If you are deploying into a cluster in WebSphere Application
Server Version 6.0.0, see the note at the end of the step first.
Note: If you are using either the UNIX or Linux operating
systems, add the .sh suffix to the wsadmin command.
![[Version 6.0]](../../v60.gif)
wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
node_name
server_name
![[Version 6.0.1 and later]](../../v601x.gif)
wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
{node_name server_name | cluster_name}
where
- '-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 will be used.
- '-conntype none' is optional, and is only needed if the application server
is not running.
- node_name is the name of the WebSphere node on which
the target server runs. Note that the node name is case sensitive.
- server_name is the name of the target server on which
you wish to deploy the UDDI registry, such as server1. Note the server name
entered is case sensitive.
cluster_name is
the name of the target cluster into which you wish to deploy the UDDI registry.
Note that the cluster name entered is case sensitive.
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
![[Version 6.0.1 and later]](../../v601x.gif)
To deploy UDDI into cluster
'MyCluster' on a Windows system:
wsadmin -f uddiDeploy.jacl MyCluster
You
are recommended to deploy the UDDI application using the uddiDeploy.jacl script,
but note that you can also use the administrative console to deploy the UDDI
registry application (the uddi.ear file) in the normal way. If you use the
administrative console you must ensure that the Classloader Mode for the application
is set to PARENT_LAST, and that the WAR class loader Policy is set to Application.
The uddiDeploy.jacl script in a command prompt will do this for you.
Note: To deploy the UDDI registry
into a cluster, perform one of the following tasks (this does not apply to
WebSphere Application Server versions 6.0.1 or later, as these versions have
a cluster option for the uddiDeploy.jacl script) :
- Deploy the UDDI registry application into a standalone server using the
uddiDeploy.jacl script as described above, and then create a cluster using
that server as a template for the other members.
- If you are deploying into a cluster that already exists, use the administrative
console or the wsadmin command to deploy the UDDI registry application (the
uddi.ear file), as described above, across the cluster members.