[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".

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.

To install the UDDI Registry onto the z/OS platform, access Unix System Services (USS), using for example telnet or Open Edition MVS, then issue the Unix commands described in this task.

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. Create and load the UDDI Registry database.

    [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.

    If you are planning to use a remote DB2 system on another z/OShost 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.

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

    1. Ensure you are using the JVM supplied with WebSphere Application Server Version 5.1
    2. Gather the following information about your DB2 z/OS configuration from your DB2 administrator:
      1. The location of the DB2 system where you want to persist the UDDI directory.
      2. The name of the DB2 database that will be used for the UDDI directory. If a database does not already exist, the UDDI DB2 setup wizard will create one for you.
      3. The name of the DB2 tablespace that will be used for the UDDI directory. If a tablespace does not already exist, the UDDI DB2 setup wizard will create one for you.
      4. The name of the DB2 storage group that will hold the UDDI directory.
      5. The Coded Character Set id to use for the database.
      6. The name of the volume on which the DB2 database should be created.
      7. The name of the alias of the VSAM catalog for DB2 datasets.
    3. Run the UDDI DB2 setup wizard

      The UDDI DB2 setup wizard supports two modes of operation:

      1. Create and load

        To initiate this mode of operation, issue the following command from an MVS command line prompt:

        /install_root/UDDIReg/bin/SetupDB2UDDI.sh DB2_location_name 
              DB2_database_name DB2_tablespace_name create 
              ccsid DB2_storage_group_name volume_name
              VSAM_catalog_name

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

        This mode of operation requires you to specify all of the parameters on the shell script. This enables the DB2 database and tablespace to be created. The newly created database will be primed for use by the UDDI Registry.

        Note: If you use the create and load mode of operation, you must run the wizard using a USERID that has the authority to create or update DB2 databases, storage groups, ect. Also, that USERID will be used as the SQLID of the resulting DB2 tables.

      2. Load

        To initiate this mode of operation, issue the following command from an OMVS command line prompt:

        /install_root/UDDIReg/bin/SetupDB2UDDI.sh DB2_location_name 
              DB2_database_name DB2_tablespace_name skip
              

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

        This mode of operation does not require you to specify the DB2_storage_group_name volume_name and VSAM_catalog_name parameters on the shell script. This mode uses the existing DB2 database and tablespace and only primes that database for use by the UDDI Registry.

      The output from the UDDI DB2 wizard will be placed in a file called setupDB2UDDI.tracelog. Errors that occur will be written to the user's telnet session.

  2. Ensure that the persister property in the uddi.properties file is set to persister=DB2.
  3. Start the application server on which the UDDI Registry is to run. For example:

    Note: This command must be entered on a single line. It is split here for display purposes.

  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. Create a JDBC driver and datasource to provide access to the 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.sh -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.

      /webSphere/V5R1M0/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. For example:
      • WebSphere/V5R1M0/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.
    • > 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 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/twsu_install_fordb2.html

Library | Support | Terms of Use | Feedback