Setting up a default UDDI node

You can create a UDDI node with predetermined property values. This UDDI node is suitable for initial evaluation of the UDDI registry and for development and test purposes.

About this task

When you set up a default UDDI node, the mandatory node properties, such as node ID, are set automatically and you cannot change them. You can create a default UDDI node with an embedded Apache Derby database but a different data source, or with a database other than Apache Derby.

If you want to set up a UDDI node with your own properties, including the mandatory node properties, you must set up a customized node. See Setting up a customized UDDI node.

If you deploy the UDDI registry application into a cluster, and you want to use an Apache Derby database, you must use the network version of the Apache Derby database. Embedded Apache Derby 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:
    Note: 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 data source 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. Optional: 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, which is located in the root directory of the DB2 user ID (for example, /home/db2inst1/sqllib/db2profile). Alternatively, you can run the db2profile script manually, but you 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 you restart the UDDI application or the application server, the UDDI node always reactivates, 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 your 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

Because you chose to use a default UDDI node, the node is initialized when the UDDI application is started for the first time. Follow the instructions in Using the UDDI registry installation verification test (IVT) to verify that you have successfully set up the UDDI node.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=twsu_default_install2
File name: twsu_default_install2.html