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.

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.

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

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

    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. 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.
    2. 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_nameparameters 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. 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.sh -f setupuddi.jacl
                 deploymgrpath 
                 servername
                 nodename 
                 discoveryURLprefix 
                 dbname 
                 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, on z/OS platofrms this might be /WebSphere/V5R1M0/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 the database name you specified when you ran the UDDI DB2 setup wizard.

      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

    • db2ziplocation is the path to the db2java zip file on your system, specified using forward slashes regardless of platform.
    • > 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 z/OS the command is:

    wsadmin.sh -user wsadmin -password wsadmin -f 
    /WebSphere/V5R1M0/AppServer/UDDIReg/scripts/appserversetupuddi.jacl
     /WebSphere/V5R1M0/AppServer/installableApps/uddi.ear server1 SY1
     /WebSphere/V5R1M0/AppServer/lib UDDI20 db2admin secretpwd
     "/db2-install-dir/classes/db2j2classes.zip" > setupuddi.log

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

    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 application into the server server1 running on node myriad, and set it up to access the DB2 database..

    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 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_fordb2dmc.html

Library | Support | Terms of Use | Feedback