Deploy the UDDI registry application

 

You deploy a UDDI registry application as part of setting up a UDDI node. You can either use the supplied script, or use the administrative console. Before you deploy a UDDI registry application, create the database and data source for the UDDI registry.

 

Overview

Use this task as part of Setting up a default UDDI node or Setting up a customized UDDI node.

 

Procedure

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 specified.

If you are using either 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 | cluster}
                           

where:

• '-conntype none' is optional, and is needed only if the appserver 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 is the name of the target cluster into which you wish to deploy the UDDI registry. The cluster name 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

To deploy UDDI into cluster 'MyCluster' on a Windows system:

wsadmin -f uddiDeploy.jacl MyCluster

You can also deploy the UDDI application (the uddi.ear file) using the console, in the normal way. However, if you use the console, some steps that the uddiDeploy.jacl script performs automatically do not occur. If you use the administrative console to install the UDDI application, perform some actions manually. To do this, use the following steps:

1. Install the application.

2. Click Applications > Enterprise Applications > uddi_application > [Detail Properties] Class loading and update detection .

3. Ensure that Class loader order is set to Classes loaded with application class loader first.

4. Ensure that WAR class loader policy is set to Single class loader for application.

 

Results

The UDDI application is deployed. If you see the following error message, check that you ran the uddiDeploy.jacl script using the deployment manager profile.

WASX7017E: Exception received while running file "uddiDeploy.jacl"; exception in formation: com.ibm.ws.scripting.ScriptingException: WASX7070E: The configuration
 service is not available.

 

What to do next

Continue setting up the UDDI node.

---

 

Related tasks

Setting up a default UDDI node
Removing a UDDI registry node
Setting up a customized UDDI node