+

Search Tips   |   Advanced Search

Deploy the UDDI registry application


You deploy a UDDI registry application as part of setting up a UDDI node. Use either the supplied script, or the admin console.

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

Use this task as part of Set up a default UDDI node or Set up a customized UDDI node. We can deploy a UDDI registry application in two ways:

 

  1. To deploy a UDDI registry application using the supplied script:

    1. Run the uddiDeploy.jacl wsadmin script as shown, from the APP_ROOT/bin directory.

      Deploys the UDDI registry to a server or cluster specified.
      [AIX] [HP-UX] [Linux] [Solaris]

      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 | cluster_name}                           
      
      where:

      • -conntype none is optional, and is needed only if the appserver or deployment manager is not running.

      • -profileName profile_name is the dmgr profile. If we do not specify a profile, the default profile is used.

      • node_name is the name of the WAS 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 on a Windows system, assuming that server1 is already started:

      wsadmin -f uddiDeploy.jacl MyNode server1
      

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

      wsadmin -f uddiDeploy.jacl MyCluster
      

  2. To deploy a UDDI registry application using the admin console, use the following steps.

    1. Install the UDDI application (the uddi.ear file).

    2. Click Applications > Application Types > WebSphere enterprise applications > uddi_application > [Detail Properties] Class loading and update detection .

    3. Ensure that Class loader order is set to Classes loaded with local class loader first (parent last).

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

    5. Click Apply, then save the changes to the master configuration.

 

Results

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

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

 

Next steps

Continue setting up the UDDI node.

 

Related tasks


Set up a default UDDI node
Remove a UDDI registry node
Set up a customized UDDI node