Install and Set up a UDDI Registry

If you wish to use the UDDI User Console and use Internet Explorer as your web browser, and use SSL, then use Internet Explorer V5.5 with SP2 and the Microsoft security fix Q321232 (which must be applied in that order).

The UDDI Registry application uses DB2 as the persistence store for the registry data.

The UDDI Registry application files are installed on your iSeries with the IBM WAS with Network Deployment option. When deploying (installing) the UDDI Registry application to an application server, you have two environment choices:

  1. Install the UDDI Registry application into the deployment manager cell using DB2 as the database in which the UDDI Registry data is held, selecting one of the application servers within the cell in which to run the UDDI Registry.

  2. Install the UDDI Registry application directly into an application server using DB2 as the database in which the UDDI Registry data is held. Please note that, if you choose this option, then the application server on which you run the UDDI Registry must not be added into a deployment manager cell, as this would cause the file synchronization within the cell to remove the application.

In most cases you chose option 1, and install the UDDI Registry into a deployment manager cell, but you may find that option 2, to install the UDDI Registry into a stand-alone application server, is useful for development or test purposes.

The following table lists the UDDI Registry files, and the locations into which they are placed by the install. The Location column shows the subdirectory under the WebSphere DeploymentManager install directory. For example, if you had installed IBM WAS with the Network Deployment option onto an iSeries server, then a location of installableApps would mean that the file had been placed into the /QIBM/ProdData/WebAS5/ND/installableApps directory.

Files Purpose Location
uddi.ear The UDDI Registry application itself, which is packaged and runs as an Enterprise Application installableApps
uddi.properties Provides configuration properties for the UDDI Registry application properties
uddiresourcebundles.jar Contains system messages for the UDDI Registry application lib
setupuddi.jacl Admin script to create a JDBC driver and datasource for the UDDI Registry, and to install the UDDI Registry application in a DeploymentManager Cell UDDIReg/scripts
setupuddimessages.jar Contains setup and install messages for the UDDI Registry application lib
removeuddi.jacl Admin script to undo the effects of setupuddi.jacl UDDIReg/scripts
appserverremoveuddi.jacl Admin script to undo the effects of appserversetupuddi.jacl UDDIReg/scripts
appserversetupuddi.jacl Admin script to create a JDBC driver and datasource for the UDDI Registry, and to install the UDDI Registry application in a single, stand-alone, application server UDDIReg/scripts
SetupDB2UDDI.jar The JAR file contains Java classes needed to create and pre-load the UDDI Registry database for iSeries DB2 to be used as the persistence store UDDIReg/scripts
uddiejbclient.jar Class library for use when writing an EJB client to access the UDDI Registry UDDIReg/ejb
Various javadoc files JAVADOC to describe the EJB interface to the UDDI Registry UDDIReg/ejb/javadoc
UDDITaxonomyTools.jar Provides tools for supporting custom taxonomies with the UDDI Registry UDDIReg/scripts
CustomTaxonomy.properties Provides configuration properties to be used the the UDDITaxonomyTools UDDIReg/scripts

To install UDDI Registry, perform these steps:

  1. Start Qshell by entering the STRQSH command on your OS/400 command line.

  2. In Qshell enter this command: 
    /QIBM/ProdData/WebAS5/ND/UDDIReg/scripts/installuddiregistry -envopt your_option 
-instance your_instance -server your_server -node your_node 
[-collection your_collection] [-userid your_userid -pwd your_password]
    where

    • the -envopt parameter can have the value ND to install to a deployment manager cell or Base to install to a stand-alone application server.

      Note: If you chose Base, the UDDI Registry must not be added into a deployment manager cell, or the file synchronization within the cell removes the application.

    • the -instance parameter is used to specify your WAS instance.

    • the -server parameter is used to specify the server name.

    • the -node parameter is used to specify the node name.

    • the -collection parameter is used to specify the database collection name for the UDDI registry database. The default value is UDDI20 (database is *LOCAL/UDDI20).

    • the -userid and -pwd parameters are used to specify the userid and password of the user profile that owns the database collection. If not specified, the default values are uddiuser and uddipwd, respectively.

This script should restart your application server. After the application server restarts, you can access the UDDI Registry at this URL: 

http://host:port/uddigui
where host is the name of the iSeries server on which you are running, and port is the internal or external http port. For more options on the installuddiregistry script use the -help option.