Deploy the UDDI registry application

We deploy a UDDI registry application as part of setting up a UDDI node. Use a supplied script, the administrative console, or wsadmin scripting commands.

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

If we are deploying a UDDI registry application to a cluster, it is assumed that a single database is used for all members of the cluster so that the cluster is displayed as a single UDDI node.

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:

• Use a script that performs all the necessary steps.

  This script deploys the UDDI registry to a server or cluster specified.

• Use the administrative console. We 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.

Tasks

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

   1. (iSeries) Start a Qshell session by entering the STRQSH command from the IBM i command line.

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

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

      wsadmin [-conntype none] [-profileName profile] -f uddiDeploy.jacl
              {node server | cluster_name}             						  
      

      (ZOS)

      wsadmin.sh [-conntype none] [-profileName profile] -f uddiDeploy.jacl
                 {node server | cluster_name}             						  
      

      The attributes of the command are as follows:

      • -conntype none is optional, and is needed only if the application server or deployment manager is not running.
      • -profileName profile is the deployment manager profile. If we do not specify a profile, the default profile is used.
      • node is the name of the WebSphere Application Server node on which the target server runs. The node name is case sensitive.
      • server is the name of the target server on which we 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 we want to deploy the UDDI registry. The cluster name is case sensitive.

      (Dist) For example, to deploy UDDI on the node yNode and the server server1 on a Windows system, assuming that server1 is already started:

      wsadmin -f uddiDeploy.jacl MyNode server1
      

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

      wsadmin -f uddiDeploy.jacl MyCluster
      

      (iSeries) For example, to deploy UDDI on the node MyNode and the server server1, assuming that server1 is already started:

      wsadmin -f uddiDeploy.jacl MyNode server1
      

      (iSeries) To deploy UDDI into the cluster MyCluster:

      wsadmin -f uddiDeploy.jacl MyCluster
      

      (ZOS) For example, to deploy UDDI on the node MyNode and the server server1, assuming that server1 is already started:

      wsadmin.sh -f uddiDeploy.jacl MyNode server1
      

      (ZOS) To deploy UDDI into the cluster MyCluster:

      wsadmin.sh -f uddiDeploy.jacl MyCluster
      

2. Optional: To deploy a UDDI registry application using the administrative console, use the following steps.

   1. Install the UDDI application (the uddi.ear file) to the server or cluster 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 our changes to the master configuration.

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

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

What to do next

Continue setting up the UDDI node.

If we deployed the UDDI registry application to a cluster, we might need to update resources such as the Java Database Connectivity (JDBC) provider and data source on individual cluster members to allow correct access to the shared database.

If the ports on which WAS listens to a value are modified from the defaults (9080 and 9443), we might also need to update the host aliases for the virtual hosts of the UDDI application. We might need to do this for any configuration, but the ports are more likely to change in a cluster environment.

Set up a default UDDI node

Removing a UDDI registry node

Install enterprise application files with the console

Install enterprise applications

Modifying class loader modes for applications

Modifying WAR class loader policies for applications