Setting up the UDDI Registry to use DB2 within a deployment manager cell

Use this task to create and load the UDDI Registry database using DB2, and to setup and install the UDDI Registry application within a deployment manager cell.

Before you begin

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

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.

If you plan to use DB2 for the database in which the UDDI Registry will be held, ensure that the correct prerequisite fix packs have been applied, as listed at WebSphere Application Server detailed system requirements , otherwise the startup of the UDDI DB2 setup wizard will fail.

This task uses the UDDI DB2 Setup Wizard to configure DB2 on the system where you want to run the UDDI Registry. Before starting this task, ensure that DB2 is installed and running on that system.

Before starting this task, ensure that you have created an appropriate DB2 userid and password. This same userid and password must be used throughout the following steps where the DB2 userid and password is requested.

Why and when to perform this task

The following steps should be carried out on the system on which the target application server is located (referred to as the 'target system').

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 UDDIReg directory tree from the deployment manager to the target application server where DB2 will run.
  2. On Windows, and if using DB2 Version 7, ensure that since installing DB2 you have run the usejdbc2.bat command file.
    For more information about this, see "Application Building Guide" in the DB2 documentation.
  3. Create and load the UDDI Registry database, called UDDI20.

    Note: If you are migrating from an earlier version of the UDDI Registry, and your UDDI20 DB2 database already exists, skip this step unless you want to replace the existing database with a new UDDI20 DB2 database. If you do choose to replace an existing database, all of your existing UDDI data will be lost. Important: if you do choose to replace the existing UDDI20 database, there must not be any applications or users accessing the database at the time that you run the UDDI DB2 setup wizard.

    [Version 5.0.1 and later]Note: It is recommended you use the SetupDB2UDDI.jar command from IBM WebSphere Application Server Version 5.0.1 or later. This is essential for non-English users.

    [Version 5.0.1 and later]Note: If you have a copy of the file SetupDB2UDDI.jar in your application server directory, then the application of the base and Network Deployment PTFs will not update SetupDB2UDDI.jar in your application server directory. You must apply the PTF for Network Deployment to your DeploymentManager file structure to update the SetupDB2UDDI.jar located there (in the /UDDIReg/scripts subdirectory), and then manually copy this jar file to any application server you may wish to run it on.

    If you are planning to use a remote DB2 system on another host machine, copy the SetupDB2UDDI.jar file to the remote system and run it on that system to create and load the UDDI Registry database following the instructions within this step and continue with the next step (which states "If using a remote DB2 system on another host machine..") on the local host.

    The UDDI DB2 Setup Wizard used in this task will prompt you to provide the DB2 userid and password under which the UDDI Registry database will be created and subsequently accessed.

    On Windows this should be a userid and password with administrative privileges. On Unix platforms, you should supply the userid and password of the DB2 instance in which you wish the database to be created.

    To create the database you use the UDDI DB2 setup wizard, which is supplied as a jar file called SetupDB2UDDI.jar in the UDDIReg/scripts subdirectory, by following these steps:

    1. Change directory to the directory containing the file SetupDB2UDDI.jar (that is, either the UDDIReg/scripts directory in which it is supplied, or a directory on the target system into which you have copied it).
    2. To run the wizard, first ensure that you have access from your command line to the JVM supplied with WebSphere:
      • On Windows, in a command window, a user with administrative privileges should type the following command:
        <AppServer-install-dir>\bin\setupcmdline.bat

        For example,

        C:\Program Files\WebSphere\AppServer\bin\setupcmdline.bat

      • On Unix platforms, at a command line type one of the following commands:
        • If you are using bash, then as the root user run
           . <AppServer-install-dir>/bin/setupCmdLine.sh
        • If you are using csh, then as the root user run
          source . <AppServer-install-dir>/bin/setupCmdLine.sh
    3. Temporarily set your path by typing:
      • On Windows:
        set path=%WAS_PATH%;%path%
      • On Unix or Linux platforms:
        export PATH=$WAS_PATH:$PATH
    4. In the same command window, start the UDDI DB2 setup wizard by entering one of the following commands:
      • To start a graphical user interface, type
        java -jar SetupDB2UDDI.jar
      • To start a text mode interface, type:
        java -jar SetupDB2UDDI.jar -console

        Note: The above commands will fail unless your DB2 installation has the correct fix packs applied as listed on the prerequisite page found at http://www-3.ibm.com/software/webservers/appserv/doc/latest/prereq.html

    5. Follow the prompts to work through the wizard panels or command prompts.
    6. If necessary, check the log files for the wizard. A log file called UDDIloadDB.log is written to the directory from which the wizard is run (but note that on Windows platforms, if you have decided not to overwrite an existing UDDI20 database, then this fact is not logged, and the log file is not be created).
  4. If using a remote DB2 system on another host machine, refer to "Use of a remote DB2 database" and then return to this point and continue with the following instructions.
  5. Create a JBDC driver and datasource to provide access to the UDDI20 DB2 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. This script must be run on the deployment manager node.

    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 this script for DB2 is:
    wsadmin -f setupuddi.jacl
                 deploymgrpath 
                 servername
                 nodename 
                 discoveryURLprefix 
                 dbname 
                 db2userid
                 db2password
                 db2ziplocation
                 > 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 and, for Unix platforms it might be /opt/WebSphere/DeploymentManager/.
    • servername is the name of the target application server on which you wish to deploy the UDDI Registry, such as server1. The server name is case sensitive.
    • nodename is the name of the WebSphere node on which the target application server runs. Typically, this is the same as the machine name. The node name 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://mynode.mylocation.mycompany.com:9080/uddisoap/
    • dbname is the name of the UDDI Registry database under DB2. For this parameter, you should specify UDDI20.

      Note: If a remote DB2 system is being used the dbname stated here must be the alias created when access to the remote database was set up on the local system

    • db2userid and db2password are a valid DB2 userid and password with administrative privileges
    • db2ziplocation is the path to the db2java zip file on your system, specified using forward slashes regardless of platform; for example for Windows, this might be C:/Progra~1/SQLLIB/java/db2java.zip or, for Unix platforms it might be /home/db2inst1/sqllib/java12/db2java.zip.
    • > 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 the command is:

    wsadmin -f setupuddi.jacl "C:/Progra~1/WebSphere/DeploymentManager/" server1 myriad 
    "http://myriad.headoffice.xyz.com:9080/uddisoap/" UDDI20 db2admin secretpwd 
    "C:/Progra~1/SQLLIB/java/db2java.zip" > setupuddi.log

    This command should be entered all on a single line. It was split here for formatting purposes.

    On Unix platforms the command is:

    wsadmin.sh -f setupuddi.jacl "/opt/WebSphere/DeploymentManager/" server1 myriad 
    "http://myriad.headoffice.xyz.com:9080/uddisoap/" UDDI20 db2admin secretpwd 
    "/home/db2inst1/sqllib/java12/db2java.zip" > setupuddi.log

    This command should be entered all on a single line. It was split here for formatting purposes.

    This installs the UDDI Registry application into the server server1 running on node myriad, and set it up to access the DB2 UDDI20 database using the userid 'db2admin' and password 'secretpwd'.

    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 replaces 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 file to configure the discoveryURLprefix value that you have specified, and to set the persister property as 'DB2', and places 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 update the ws.ext.dirs list to reference these files.
    5. Installs the UDDI Registry.

    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 tasks
Installing the UDDI Registry into a deployment manager cell



Searchable topic ID:   twsu_install_fordb2dmc
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_fordb2dmc.html

Library | Support | Terms of Use | Feedback