Setting 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, perform this task to setup and install the UDDI Registry database to use the supplied Cloudscape database.

Before you begin

See "Choice of database product to be used as the persistence store" to decide which database product you should use as your persistence store before proceeding further with this task.

This task is part of a parent task: Installing the UDDI Registry into a deployment manager cell. You should complete this task at the appropriate step in the parent task.

Why and when to perform this task

This task configures Cloudscape on the host where you want to run the UDDI Registry. Cloudscape is supplied with WebSphere Application Server.

In this task you will invoke a script called setupuddi.jacl, specifying the target node and application server into which the UDDI Registry is to be deployed. If the target application server is running when you invoke setupuddi.jacl, the script stops the server and restarts the server after it has completed its operations.

Steps for this 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 installation 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; for example for Windows, this might be C:/Progra~1/WebSphere/DeploymentManager for Windows, or, for Unix platforms it might be /opt/WebSphere/DeploymentManager .
    • servername is the name of the target server on which you wish to deploy the UDDI Registry, such as server1. 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/ - an example of a discoveryURLprefix value might be http://mynode.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; for example for Windows, this might be C:/Progra~1/WebSphere/AppServer/bin/UDDI20 and for Unix platforms: /opt/WebSphere/AppServer/bin/UDDI20 for example on z/OS platforms this might be /WebSphere/V5R1M0/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)

    For example on Windows:

    wsadmin -f setupuddi.jacl "C:/Progra~1/WebSphere/DeploymentManager/" server1 myriad "http://myriad.headoffice.xyz.com:9080/uddisoap/" "C:/Progra~1/WebSphere/Appserver/bin/UDDI20"

    or, on Unix platforms:

    . /wsadmin.sh -f setupuddi.jacl "/opt/WebSphere/DeploymentManager/" server1 myriad "http://myriad.headoffice.xyz.com:9080/uddisoap/" "/opt/WebSphere/Appserver/bin/UDDI20"
    installs the UDDI Registry application into the server server1 running on node myriad, and sets it up to access the Cloudscape UDDI20 database located in the bin subdirectory of the application server.

    The setupuddi.jacl script:

    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 UDDI Registry application is already installed and, if so, stop it and uninstall it.
    3. Updates 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.
    4. Places a number of files that are needed by the UDDI Registry into the WebSphere configuration repository, and updates the ws.ext.dirs list to reference these files.
    5. Installs the UDDI Registry.

    This script deploys the UDDI Registry into the configuration under the deployment manager, and then does a Synchronization to install it into the specified server.

    Note: The setup script, setupuddi.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 application server using the setup script, and then cluster that application server.

What to do next

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

Related reference
Installing the UDDI Registry into a deployment manager cell



Searchable topic ID:   twsu_install_cloudscape_dmc
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/twsu_install_cloudscape_dmc.html

Library | Support | Terms of Use | Feedback