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.
Procedure
- Optional: To deploy a UDDI registry application
using the supplied script:
- Run the uddiDeploy.jacl script
as shown, from the app_server_root/bin
directory.
Note: For the UNIX
® or Linux
® operating
systems, add the
.sh suffix to the wsadmin command.
wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
node_name server_name
The
attributes of the command are as follows:
- -conntype none is optional, and is needed
only if the application server 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 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.
For example, to deploy UDDI on the node
MyNode and the server server1 on a Windows
® system,
assuming that server1 is already started:
wsadmin -f uddiDeploy.jacl MyNode server1
- 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.
- Ensure that the Classloader Mode for the application
is set to PARENT_LAST, and that the WAR class loader policy is set
to Application. These are steps that the uddiDeploy.jacl script
completes automatically.
What to do next
Continue to set up the UDDI node.