Set up a customized UDDI node

We can set up a UDDI node with our own properties, including the mandatory node properties. This type of UDDI node is suitable for production purposes.

We can set up a customized UDDI node with property values chosen. After the node is initialized, we cannot change the mandatory node properties, for example, the node ID.

If we deploy the UDDI registry application into a cluster, and we want to use an Apache Derby database, use the network version of the Apache Derby database. Embedded Apache Derby is not supported for cluster configurations.

Tasks

1. Review the information in Databases and 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. Do not use the default node options where specified.
   • Create a DB2 distributed database for the UDDI registry
   • (iSeries) Create a DB2 for i database for the UDDI registry
   • Create a DB2 for z/OS database for the UDDI registry
   • Create an Apache Derby database for the UDDI registry
   • Create a Microsoft SQL Server database for the UDDI registry
   • Create an Oracle database for the UDDI registry

   If we 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 data source for the UDDI registry application to use to access the database, as described in Create a data source for the UDDI registry.
3. Deploy the UDDI registry application, as described in Deploy the UDDI registry application.
4. (UNIX) For a DB2 database, stop the server if it is running. Edit the user profile for the DB2 user that starts the node agent or server. Modify the user profile to run the db2profile script, located in the root directory of the DB2 user ID (for example, /home/db2inst1/sqllib/db2profile). Alternatively, we can run the db2profile script manually, but we must do this every time that you restart the node agent or server. Enter the following command (there is a single space character after the period in this command):

   . /home/db2inst1/sqllib/db2profile
   

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

   If we restart the UDDI application or the application server, the UDDI node always reactivates, even if the node was previously deactivated.

What to do next

Because we 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.

Subtopics

• Create a DB2 distributed database for the UDDI registry
  Complete this task to use DB2 on the Windows, Linux, or UNIX operating systems as the database store for our UDDI registry data.
• (iSeries) Create a DB2 for i database for the UDDI registry
  Complete this task to use DB2 for i as the database store for our UDDI registry data.
• Create a DB2 for z/OS database for the UDDI registry
  Complete this task to use DB2 for z/OS as the database store for our UDDI registry data.
• Create an Apache Derby database for the UDDI registry
  Complete this task to use an Apache Derby database as the database store for our UDDI registry. Use an embedded or network Apache Derby database, and the database store can be local or remote.
• Create a Microsoft SQL Server database for the UDDI registry
  Complete this task to use Microsoft SQL Server 2005, 2008 or 2008 R2 as the database store for our UDDI registry data.
• Create an Oracle database for the UDDI registry
  Complete this task to use Oracle as the database store for our UDDI registry data.
• Create a data source for the UDDI registry
  Create a data source so that the UDDI registry can use it to access the UDDI database.
• Deploy the UDDI registry application
  We deploy a UDDI registry application as part of setting up a UDDI node. Use a supplied script, the administrative console, or wsadmin scripting commands.
• Initializing the UDDI registry node
  Use this topic to initialize a UDDI registry node after setup or migration.

Related:

Databases and production use of the UDDI registry

Set up a default UDDI node

UDDI node settings