Install and setting up a UDDI Registry
If you wish to use the UDDI User Console using Internet Explorer as your web browser, and using SSL, then use Internet Explorer V5.5 with SP2 and security fix Q321232 (which must be applied in that order), or later.
If you are migrating from the IBM WebSphere UDDI Registry product that was available to run on WebSphere Application Server 4.0, then you need to read the section Migrating from the IBM WebSphere UDDI Registry on WebSphere Application Server 4.0 before installing the new product.
Choice of database product to be used as the persistence store
The UDDI Registry application can use either DB2 or Cloudscape as the persistence store for the registry data.
- If you plan to use the UDDI Registry in production then use DB2 as your persistence store.
- If you plan to use the UDDI Registry for development and testing purposes, then you can choose to use Cloudscape as your persistence store. Please note that Cloudscape is not intended for production purposes.
Steps for this task
As part of the installation of the IBM WebSphere Application Server with Network Deployment option, you are given the option to install the "UDDI Registry", which is shown under Web Services. Having selected the UDDI Registry and installed the various files that make up the application, you have two choices as to the environment in which you run it:
- Install the UDDI Registry application into the deployment manager cell using DB2 or Cloudscape as the database in which the UDDI Registry data will be held, selecting one of the appservers within the cell in which to run the UDDI Registry.
- Install the UDDI Registry application directly into an appserver using DB2 or Cloudscape as the database in which the UDDI Registry data will be 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 will probably choose option 1, and install the UDDI Registry into a deployment manager cell, but you might find that option 2, to install the UDDI Registry into a stand-alone appserver, is useful for development or test purposes.
Note:
- Several WebSphere commands are used during the following procedures, some of which must execute on the DeploymentManager and some of which must execute on the target Application server. The instructions below will distinguish which is appropriate for each command. The WebSphere commands will be found in the bin subdirectory of the appropriate WebSphere install tree. In order to ensure correct operation of these commands, you will need to do one of the following:
- Ensure that the appropriate bin subdirectory is in your path prior to executing the command
- Change directory to the appropriate bin subdirectory
- Fully qualify the path to the commands
- It is recommended that you use the version of java shipped with WebSphere found in the java/bin subdirectory.
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 WebSphere Application Server with Network Deployment option onto a machine running Windows, and had used the default directory, then a location of "installableApps" would mean that the file had been placed into the C:\Progra~1\WebSphere\DeploymentManager\installableApps directory. For Windows platforms, read the "/" directory separator in the location column as a "\" directory separation character.
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 uddicloudscapeuserfunc.jar Contains functions that are used by Cloudscape if the Cloudscape database is used with the UDDI Registry 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, appserver UDDIReg/scripts SetupDB2UDDI.jar The 'UDDI DB2 Setup Wizard', to create and pre-load the UDDI Registry database if DB2 is to be used as the persistence store UDDIReg/scripts UDDI20 (directory) Cloudscape directory containing the UDDI Registry tables and pre-loaded data bin 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
If you intend to run in a Deployment Manager Cell then complete the following task - Installing the UDDI Registry into a deployment manager cell
If you intend to run in a single WebSphere Application server, then complete the following task - Installing the UDDI Registry into a single WebSphere Application Server
What to do next
Continue with Configure the UDDI Registry.
IBM WebSphere UDDI Registry
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.