Set up the UDDI Registry to use Cloudscape in a single application server

This task configures Cloudscape on the host where you want to run the UDDI Registry.

 

Overview

To decide which database product use as your persistence store, see "Choice of database product to be used as the persistence store".

If you plan to use Cloudscape for the database in which the UDDI Registry data is held, use this task to set up and install the UDDI Registry application to use the supplied Cloudscape database.

 

Overview

This task, to configure Cloudscape for the UDDI Registry database, is part of a parent task Installing and Setting up a UDDI Registry. You should complete this task at the appropriate step in the parent task.

  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. Copy the uddicloudscapeuserfunc.jar file from the lib subdirectory of the deployment manager install tree to the lib subdirectory of the target appserver's install tree.

  3. Ensure that the persister property in the uddi.properties file is set to persister=Cloudscape

  4. Copy the appserversetupuddi.jacl script from the UDDIReg/scripts subdirectory of the deployment manager install tree to the WebSphere Application Server bin subdirectory.

  5. Change directory to the WebSphere Application Server bin subdirectory.

  6. Start the appserver on which the UDDI Registry is to run.

    For example, enter: 

    startServer server1             for Windows

    startServer.sh server1

  7. Create a JDBC driver and datasource to provide access to the UDDI20 Cloudscape database, and install the UDDI Registry application.To do this run the wsadmin tool with the script appserversetupuddi.jacl as input, on the target appserver, using the following command syntax:

    (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 tool is located in the WebSphere /AppServer/bin subdirectory.)

    wsadmin -f appserversetupuddi.jacl 
        uddi-ear-location
        servername
        nodename
        WebSphere-lib-subdirectory
        cloudscapedbname
        > setupuddi.log

    Where:

    • uddi-ear-location is the fully-qualified path to the uddi.ear file in the installableApps subdirectory, specified using forward slashes regardless of platform.

      For example on Windows:

      : 

       C:/Progra~1/WebSphere/AppServer/installableApps/uddi.ear

      and on Unix platforms: 

      /opt/WebSphere/AppServer/installableApps/uddi.ear

    • servername is the name of the appserver on which the UDDI registry is to run; for example: server1. Note that the server name entered is case sensitive.

    • nodename is the name of the WebSphere node on which the application server, servername, is running. Typically this is the machine name. Note that the node name entered is case sensitive.

    • WebSphere-lib-subdirectory is the fully-qualified path to the WebSphere Application Server lib subdirectory, specified using forward slashes regardless of platform.

      For example on Windows:

      C:/Progra~1/WebSphere/AppServer/lib

      and on Unix platforms: 

      /opt/WebSphere/AppServer/lib

    • cloudscapedbname is the fully-qualified path to the UDDI20 database within the bin subdirectory of your WebSphere AppServer installation, specified using forward slashes regardless of platform. For example on Windows: 

      C:/Progra~1/WebSphere/AppServer/bin/UDDI20

      and on Unix platforms 

      /opt/WebSphere/AppServer/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)

    The appserversetupuddi.jacl script completes the following actions:

    1. Creates 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. Checks whether the WebSphere UDDI Registry application is already installed and, if so, stop the application and uninstall it.

    3. Installs the WebSphere UDDI Registry, then starts it.

    Note: The setup script, appserversetupuddi.jacl, cannot be used to install the UDDI Registry application into a clustered application server. It is possible to cluster the UDDI Registry application by installing UDDI into an unclustered appserver using the setup script, and then clustering that appserver.

 

What to do next

Return to the next step in the parent task Installing the UDDI Registry into a single appserver.

Related tasks
Installing and setting up a UDDI Registry