Before you begin
If you wish to use the UDDI User Console using Internet Explorer as your Web browser, and using SSL, you must use Internet Explorer V5.5 with SP2 and security fix Q321232 (which must be applied in that order), or later.
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.
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. However, in a z/OS environment, you should use DB2. If you use Cloudscape, you must restrict the WLM policy to the server to allow only one servant process.
Cloudscape Restriction
Cloudscape Network Server Version 5.1 requires a WebSphere Version 5 datasource to utilize the multiple connection features. As IBM WebSphere UDDI Registry uses a WebSphere Version 4 datasource, this precludes other connections to the Cloudscape database when the UDDI Registry application is in the started state.
Why and when to perform this task
You are given the option to install the UDDI Registry as part of the IBM WebSphere Application Server for z/OS ISPF Customization Dialog.
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:
Note:
The following table lists the UDDI Registry files, and the locations into which they are placed by the installation. The Location column shows the subdirectory under the WebSphere DeploymentManager install 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 | Administrative 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 | Administrative script to undo the effects of setupuddi.jacl | UDDIReg/scripts |
appserverremoveuddi.jacl | Administrative script to undo the effects of appserversetupuddi.jacl | UDDIReg/scripts |
appserversetupuddi.jacl | Administrative 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 '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 |
UDDIUtilityTools.jar | Provides support for import/export of UDDI entities | UDDIReg/scripts |
UDDIUtilityTools.properties | Provides configuration properties for the UDDI Utility Tools | UDDIReg/scripts |
What to do next
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