WAS v8.5 > Administer applications and their environment > Administer web services - UDDI registry > Administer the UDDI registry > Set up and deploying a new UDDI registry > Set up a customized UDDI node

Deploy the UDDI registry application

You deploy a UDDI registry application as part of setting up a UDDI node. We can use a supplied script, the dmgr console, or wsadmin scripting commands.

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

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

• We can use a script that performs all the necessary steps.

  This script deploys the UDDI registry to a server specified.

• We can use the dmgr console. You deploy the UDDI registry application, the uddi.ear file, then complete additional steps, as described later in this topic. Alternatively, we can follow the same procedure using wsadmin.sh commands.

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

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

      Note: For the UNIX or Linux operating systems, add the .sh suffix to wsadmin.

      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 we 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 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

2. Optional: To deploy a UDDI registry application using the dmgr console, use the following steps.
   1. Install the UDDI application (the uddi.ear file) to the server that you require.

   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 your changes to the master configuration.

Continue setting up the UDDI node.

Related

Set up a default UDDI node
Remove a UDDI registry node
Install enterprise application files with the console
Install enterprise applications using wsadmin.sh
Modify class loader modes for applications using wsadmin.sh
Modify WAR class loader policies for applications using wsadmin.sh

+

Search Tips   |   Advanced Search