WebSphere Application Server Version 6.1 Feature Pack for Web Services
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize 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

  1. [i5/OS] Start a Qshell session by entering the STRQSH command from the i5/OS command line.
  2. 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 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.
    [AIX HP-UX Linux Solaris Windows] [i5/OS]
    wsadmin [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
                   {node_name server_name | cluster_name}
                 						  
    [z/OS]
    wsadmin.sh [-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.
    • cluster_name is the name of the target cluster into which you wish to deploy the UDDI registry. The cluster name is case sensitive.
    [AIX HP-UX Linux Solaris Windows] 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
    [AIX HP-UX Linux Solaris Windows] To deploy UDDI into cluster 'MyCluster' on a Windows system:
    wsadmin -f uddiDeploy.jacl MyCluster
    [i5/OS] For example, to deploy UDDI on node 'MyNode' and server 'server1', (assuming that server1 is already started):
    wsadmin -f uddiDeploy.jacl MyNode server1
    [i5/OS] To deploy UDDI into cluster 'MyCluster':
    wsadmin -f uddiDeploy.jacl MyCluster
    [z/OS] For example, to deploy UDDI on node 'MyNode' and server 'server1' (assuming that server1 is already started):
    wsadmin.sh -f uddiDeploy.jacl MyNode server1
    [z/OS] To deploy UDDI into cluster 'MyCluster' :
    wsadmin.sh -f uddiDeploy.jacl MyCluster
    You can also deploy the UDDI application (the uddi.ear file) using the administrative console, in the normal way. However, if you use the administrative console, some steps that the uddiDeploy.jacl script performs automatically do not occur. If you use the administrative console to install the UDDI application, you must 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.



In this information ...


IBM Redbooks, demos, education, and more


Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Nov 25, 2008 2:35:59 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.wsfep.multiplatform.doc/info/ae/ae/twsu_uddi_deploy.html