[Version 5.0.1 and later]Setting up the UDDI Registry to use DB2 in a single application server

Use this task to create and load the UDDI Registry database using DB2, and to setup and install the UDDI Registry application to use the database.

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 and setting up a UDDI Registry. 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 is held, ensure that the correct prerequisite fix packs have been applied as listed at Target can be accessed only when this topic is linked to the World Wide Web   http://www-3.ibm.com/software/webservers/appserv/doc/latest/prereq.html 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.

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 below as the 'target system').

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, if you are 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, you should 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, then 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 prompts you to provide the DB2 userid and password under which the UDDI Registry database is created and subsequently accessed. 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.

    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, you need to first ensure that you have access from your command line to the JVM supplied with WebSphere. This is done as follows:
      • 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:\Progra~1\WebSphere\AppServer\bin\setupcmdline.bat

      • On Unix platforms, enter one of the following commands as the root user:
        • If you are using bash:
          . <AppServer-install-dir>/bin/setupCmdLine.sh
        • If you are using csh:
          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 issuing one of the following commands:the following command:
      • To start a graphical user interface, enter:
        java -jar SetupDB2UDDI.jar
      • To start a text mode interface, enter:
        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 into 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, this fact is not logged, and the log file is not 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 next step.
  5. Ensure that the persister property in the uddi.properties file is set to persister=DB2.
  6. On Unix, run the db2profile script to set up the environment for the DB2 instance that the UDDI Registry is using:
    . /home/db2inst1/sqllib/db2profile
  7. Start the application server on which the UDDI Registry is to run. For example:

    On Windows:

    startserver server1

    On Unix platforms:

    . /startServer.sh server1              

  8. Copy the appserversetupuddi.jacl script from the UDDIReg/scripts subdirectory of the deployment manager install tree to the WebSphere Application Server bin subdirectory (for example, on Windows, C:\Progra~1\WebSphere\AppServer\bin).
  9. Change directory to the WebSphere Application Server bin subdirectory.
  10. Create a JDBC driver and datasource to provide access to the UDDI20 database, and install the UDDI Registry application.
    To do this, first read all the information in this step before performing any actions. Then run the wsadmin tool with the script appserversetupuddi.jacl as input, on the target application server, using the following command syntax. (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 bin subdirectory.)
    wsadmin -f appserversetupuddi.jacl
                 uddi-ear-location
                 servername
                 nodename
                 WebSphere-lib-subdirectory
                 dbname 
                 db2userid 
                 db2pwd
                 db2ziplocation
                 > 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 application server on which the UDDI registry is to run; for example: server1. Note that the name of the server is case sensitive.
    • nodename is the name of the WebSphere node on which the application server, servername, is running. Typically, this will be the same as the machine name. Note that the name of the node is case sensitive. Typically this is the machine name.
    • 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
      • On Unix: /opt/WebSphere/AppServer/lib
    • dbname is the name of the UDDI Registry database under DB2. You should specify UDDI20 for this parameter

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

    • db2userid and db2pwd are a valid DB2 userid and password with administrative privileges, as specified in an earlier step.
    • db2ziplocation is the path under which you have installed DB2, 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 /opt/SQLLIB/java//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)

    The appserversetupuddi.jacl 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, stops 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 application server using the setup script, and then clustering that application server.

What to do next

Return to the next step in the parent task Installing and Setting up a UDDI Registry.

Related tasks
Installing and setting up a UDDI Registry



Searchable topic ID:   twsu_install_fordb2
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_fordb2.html

Library | Support | Terms of Use | Feedback