Set up a customized UDDI node

 

You set up a UDDI node with your own property values so that it is suitable for production configurations.

 

Overview

Use this task to set up a UDDI node with property values that you choose. You cannot change the mandatory node properties, such as node ID, after the initialization of the node. Such a node is suitable for production purposes.

If you deploy 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. Review the information in Database considerations for production use of the UDDI registry to decide which database system to use, then create a database schema to hold the UDDI registry by completing one of the following tasks, ensuring that you do NOT 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.

 

What to do next

Because you chose a user-customized UDDI node, set the properties for the UDDI node using UDDI administration, and initialize the node, before it is ready to accept UDDI requests. See Initializing the UDDI registry node for details.

---

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

Initializing the UDDI registry node

 

Related tasks

Setting up a default UDDI node
Setting up and deploying a new UDDI registry

 

Related information

UDDI node settings