WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Deploying 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 begin

Before you deploy a UDDI registry application, you must create the database and data source for the UDDI registry.

About this task

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.

[Version 6.0] This script deploys the UDDI registry to a server that you specify.

[Version 6.0] If you wish to deploy into a cluster, do one of the following:
  • Deploy the UDDI registry application into a standalone server by using the uddiDeploy.jacl script, then create a cluster, using that server as a template for the other members.
  • To deploy 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 later in this topic, across the cluster members.

[Version 6.0.1 and later] This script deploys the UDDI registry to a server or cluster that you specify.

[AIX] [HP-UX] [Linux] [Solaris]
Note: If you are using either the UNIX or Linux operating systems, add the .sh suffix to the wsadmin command.
[Version 6.0]
wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl 
               node_name 
               server_name
[Version 6.0.1 and later]
wsadmin [-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.
  • [Version 6.0.1 and later] cluster_name 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
[Version 6.0.1 and later] To deploy UDDI into cluster 'MyCluster' on a Windows system:
wsadmin -f uddiDeploy.jacl MyCluster

We recommend that you deploy the UDDI application using the uddiDeploy.jacl script. However, 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, 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 does this for you.

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
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsu_uddi_deploy.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)