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 console, or wsadmin scripting commands.

Before you deploy 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:

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

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

• We can use the 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 commands.

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.

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

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

      (zos)

      wsadmin.sh [-conntype none] [-profileName profile_name] -f uddiDeploy.jacl
                 {node server_name | 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_name is the dmgr profile. If we do not specify a profile, the default profile is used.

      • node 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 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 to deploy the UDDI registry. The cluster name is case sensitive.

      (dist) 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

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

Results

The UDDI application is deployed. If the following error message is displayed, check that you ran the uddiDeploy.jacl script using the dmgr 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 JDBC provider and data source on individual cluster members to allow correct access to the shared database.

If the ports on which WebSphere Application Server listens to a value are modified from the defaults (9080 and 9443), you 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.

Related tasks

Set up a default UDDI node

Remove a UDDI registry node

Install enterprise application files with the console

Install enterprise applications

Modify class loader modes for applications

Modify WAR class loader policies for applications