You deploy a UDDI registry
application as part of setting
up a UDDI node. You can use a supplied script, the administrative
console, or wsadmin scripting commands.
Before you begin
Before you deploy a UDDI registry application, you
must create
the database and data source for the UDDI registry.
If you are deploying a UDDI
registry application to a cluster, it is assumed that a single database
is used for all members of the cluster so that the cluster is displayed
as a single UDDI node.
About this task
Use this task as part
of setting up a default UDDI node or
setting up a customized UDDI node. You can deploy a UDDI registry
application in two ways:
Procedure
- Optional: To deploy a
UDDI registry application
using the supplied script:
-
Start a Qshell session by entering
the STRQSH command from the IBM® i
command line.
- Run the uddiDeploy.jacl wsadmin
script as shown, from the app_server_root/bin
directory.
wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
{node_name server_name | cluster_name}
The
attributes of the command are as follows:
- -conntype
none is
optional, and is needed only if the application server or deployment
manager 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 want 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 want to deploy the UDDI
registry. The cluster name is case sensitive.
For example, to deploy UDDI on the node MyNode
and the server server1, assuming that server1 is already started:
wsadmin -f uddiDeploy.jacl MyNode server1
To deploy
UDDI into the cluster MyCluster:
wsadmin -f uddiDeploy.jacl MyCluster
- Optional: To deploy
a UDDI registry application
using the administrative console, use the following steps.
- Install the UDDI application (the uddi.ear file)
to the server or cluster that
you require.
- Click .
- Ensure that Class
loader order is
set to Classes loaded with local class loader first (parent
last).
- Ensure that WAR
class loader policy is
set to Single class loader for application.
- Click Apply, then save
your changes
to the master configuration.
Results
The UDDI application
is deployed. If the following error message is displayed, check that
you ran the
uddiDeploy.jacl script using the
deployment manager profile.
WASX7017E: Exception received while running file "uddiDeploy.jacl"; exception
information: com.ibm.ws.scripting.ScriptingException: WASX7070E: The
configuration service is not available.
What to do next
Continue setting up the UDDI node.
If you deployed the UDDI registry
application to a cluster, you might need to update resources such
as the Java Database Connectivity
(JDBC) provider and data source on individual cluster members to allow
correct access to the shared database.
If the ports on which WebSphere Application Server
listens to a value are modified from the defaults (9080 and 9443),
you might also need to update the host aliases for the virtual hosts
of the UDDI application. You might need to do this for any configuration,
but the ports are more likely to change in a cluster environment.