Install the UDDI Registry into a single appserver

If you intend to run in a single WebSphere Application server, then complete the following task.

When you select the UDDI Registry option, then the installation will place all files that are needed to run a UDDI Registry onto the deployment manager install tree on the machine on which you are installing IBM WebSphere Application Server for Network Deployment.

To be able to run the UDDI Registry in a single appserver instance in your network space copy these files over to the appserver and then deploy the UDDI Registry. One can do this as follows:

 

  1. Stop the appserver on which you plan to run the UDDI Registry; for example, using the command stopServer server_name (stopServer.sh on Unix Platforms)

  2. Copy the uddi.ear file from the installableApps subdirectory of the deployment manager install tree into the installableApps subdirectory of the target appserver's install tree.

  3. Copy the uddi.properties file from the properties subdirectory of the deployment manager install tree into the properties subdirectory of the target appserver's install tree. In a subsequent step, you configure the UDDI Registry using the properties in the uddi.properties file.

  4. Copy both the uddiresourcebundles.jar and the setupuddimessages.jar files from the lib subdirectory of the deployment manager install tree into the lib subdirectory of the target appserver's install tree.

  5. Optionally, if you are going to write or run code that uses the EJB interface to UDDI on another machine, then copy the uddiejbclient.jar file and the EJB javadoc directory tree from the UDDIReg/ejb subdirectory of the deployment manager install tree onto a location of your choice on any machines where you will be creating EJB clients to access the UDDI Registry.

  6. Configure database support for the UDDI Registry database, in which the UDDI Registry will be held. To do this, complete one of the following tasks then return this point:

    Note: If you set up the UDDI Registry application with a JDBC driver and datasource that reference Cloudscape, but set the persister property in uddi.properties to specify DB2, or vice versa, then some unexpected behavior will result, such as a fatal error on deleting an entity. If this happens, check that the above details are not in conflict. This only applies to a UDDI Registry installation on a single appserver.

  7. Ensure that the UDDI Registry is configured appropriately for your installation, as described in the section on Configure the UDDI Registry.

  8. Stop and then restart the appserver. On Unix platforms remember to run the db2profile script before issuing the startServer.sh command. This script is located within the DB2 instance's home directory under SQLLIB and can be invoked, for example, by typing: 

    ". /home/db2inst1/sqllib/db2profile"

 

What to do next

Continue with Configure the UDDI Registry.

Installing and setting up a 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.