Set up the UDDI Registry to use Cloudscape within a deployment manager cell

If you plan to use Cloudscape for the database in which the UDDI Registry data will be held, use this task to create and load the UDDI Registry database using Cloudscape.

 

Please see the section "Choice of database product to be used as the persistence store" to decide which database product use as your persistence store before proceeding further with this step.

This task is part of the parent task and is described in Installing the UDDI Registry into a deployment manager cell. You should complete this task at the appropriate step in the parent task, then return to and complete the parent task.

If you plan to use Cloudscape for the database in which the UDDI Registry data will be held, use this task to setup and install the UDDI Registry application to use the supplied Cloudscape database.

This task configures Cloudscape on the host where you want to run the UDDI Registry. Cloudscape is supplied with WebSphere Application Server, so not need to install Cloudscape support.

In this task you will invoke a script called setupuddi.jacl, specifying the target node and appserver into which the UDDI Registry is to be deployed. Please note that if the target appserver is running when you invoke setupuddi.jacl, then the script will stop the server and will restart the server after it has completed its operations.

 

  1. Copy the UDDI20 directory tree from the bin subdirectory of the deployment manager tree into the bin subdirectory of the target application server's install tree.

  2. Create a JDBC driver and datasource to provide access to the UDDI20 Cloudscape database, and install the UDDI Registry application. This is done using the WSADMIN tool, using as input the setupuddi.jacl script from the UDDIReg/scripts subdirectory of the Deployment Manager. Note that this script must be run on the deployment manager node.

    You should either run this script from the UDDIReg/scripts subdirectory where it is located, or copy it to some other suitable directory. Note that the WSADMIN command is located in the bin subdirectory of the deployment manager node.The syntax for calling this script for Cloudscape is: 

    wsadmin -f setupuddi.jacl
             deploymgrpath
             servername
             nodename
             discoveryURLprefix
             pathtodb
             > setupuddi.log

    where

    • deploymgrpath is the fully qualified pathname of the deployment manager install directory, specified using forward slashes regardless of platform; e.g. for Windows, this might be C:/Progra~1/WebSphere/deploymentManager

    • servername is the name of the target server on which you wish to deploy the UDDI Registry, such as servername. Note the the server name entered is case sensitive.

    • nodename is the name of the WebSphere node on which the target server runs. Note the the node name entered is case sensitive.

    • discoveryURLprefix is the URL prefix to be used for discovery URLs. Typically this will be of the form http://<ip-address>:9080/uddisoap/ so an example of a discoveryURLprefix value might be http://nodename.mylocation.mycompany.com:9080/uddisoap/

    • pathtodb is the path to the UDDI20 database within the bin subdirectory of your WebSphere AppServer installation, specified using forward slashes regardless of platform; e.g. for Windows, this might be C:/Progra~1/WebSphere/AppServer/bin/UDDI20 and for Unix platforms, it might be $WAS_HOME/bin/UDDI20

    • > setupuddi.log is an optional parameter to direct the output to a log file as opposed to the default (which is to the screen)

    For example: 

    wsadmin -f setupuddi.jacl "C:/Progra~1/WebSphere/DeploymentManager/" servername MYRIAD "http://myriad.headoffice.xyz.com:9080/uddisoap/" "C:/Progra~1/WebSphere/Appserver/bin/UDDI20"
    will install the UDDI Registry application into the server servername running on node MYRIAD, and set it up to access the Cloudscape UDDI20 database located in the bin subdirectory of the appserver.

    The setupuddi.jacl script will

    1. Create a JDBC driver named UDDI.JDBC.Driver.<nodeName>.<server> and a datasource named UDDI.Datasource.<nodeName>.<server> (where <nodeName> is the name of the target node and <server> is the name of the target server>, and will replace any existing driver and datasource of that name.

    2. Check whether the UDDI Registry application is already installed and, if so, stop it and uninstall it.

    3. Update the uddi.properties configuration property file to configure the discoveryURLprefix value that you have specified and set the persister property as 'Cloudscape', and place this file into the location config/cells/<currentcell>/nodes/<nodename>/servers/<servername>/uddi.properties. You should make any further global configuration changes using this copy of the file.

    4. Place a number of files that are needed by the UDDI Registry into the WebSphere configuration repository, and update the ws.ext.dirs list to reference these files.

    5. Install the UDDI Registry.

    This script will deploy the UDDI Registry into the configuration under the deployment manager, and then do a Synch which causes it to get installed into the specified server.

 

What to do next

Return to the next step in the parent task Installing the UDDI Registry into a deployment manager cell.

Installing the UDDI Registry into a deployment manager cell

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.