Set up a default UDDI node

 

Use this task to create a UDDI node with predetermined property values.

 

Overview

You cannot change the mandatory node properties, such as node ID, either during the creation of the node, or afterwards. Such a node is suitable for initial evaluation of the UDDI registry and for development and test purposes. To choose the mandatory node properties yourself, set up a customized node as detailed in Setting up a customized UDDI node.

If you are deploying the UDDI registry application into a cluster, and you want to use Cloudscape for your database, use the network version of Cloudscape. Embedded Cloudscape is not supported for cluster configurations.

 

Procedure

1. Create a database schema to hold the UDDI registry by completing one of the following tasks, ensuring that you use the default node options where specified:

   • Creating a DB2 distributed database for the UDDI registry

   • Creating an Oracle database for the UDDI registry

   • Creating a DB2 for z/OS database for the UDDI registry

   • Creating a Cloudscape database for the UDDI registry

   If you are creating the UDDI node in a cluster, it is assumed that a single database is used for all members of the cluster.

2. Set up a datasource for the UDDI registry application to use to access the database, as described in Creating a data source for the UDDI registry.

3. Deploy the UDDI registry application, as described in Deploying the UDDI registry application.

4. If you are using DB2, stop the server if it is running. Edit the user profile for the DB2 user that will start the node agent or server. Modify the user profile to run the db2profile script, which is located in the root directory of the DB2 userid (for example /home/db2inst1/sqllib/db2profile). Alternatively, you can run the db2profile script manually, but we need to do this every time you restart the node agent or server. Enter the following command:

   . /home/db2inst1/sqllib/db2profile
   

   In the example of the command above, there is a single space character after the period.

5. Click Applications > Enterprise Applications to display the installed applications. Start the UDDI registry application by selecting the check box next to it and clicking Start. Alternatively, if the appserver is not already running, start the appserver. This action automatically starts the UDDI registry application. The UDDI node is now active.

   Restarting the UDDI application, or the appserver, always reactivates the UDDI node, even if the node was previously deactivated.

6. Click UDDI > UDDI Nodes > UDDI_node_id to display the properties page for the UDDI registry node. Set Prefix for generated discoveryURLs to a valid URL for the configuration. This property specifies the URL prefix that is applied to generated discovery URLs that are used by the HTTP GET service for UDDI version 2.

 

What to do next

As you have chosen to use a default UDDI node, the node will be initialized when the UDDI application is started for the first time. Follow the instructions in Use the UDDI registry Installation Verification Program (IVP) to verify that you have successfully set up the UDDI node.

---

Creating a DB2 distributed database for the UDDI registry

Creating a DB2 for z/OS database for the UDDI registry

Creating a Cloudscape database for the UDDI registry

Creating an Oracle database for the UDDI registry

Creating a data source for the UDDI registry

Deploying the UDDI registry application

 

Related tasks

Setting up a customized UDDI node
Use the UDDI registry Installation Verification Program (IVP)
Setting up and deploying a new UDDI registry