Use this page to manage the UDDI nodes in this cell. Each UDDI node represents an individual UDDI registry application. A UDDI node will only appear in this list if its underlying UDDI application is started. The status of the UDDI node indicates whether the node is activated (available to accept API requests), deactivated (not allowing user requests), or not initialized. UDDI nodes that are not initialized require some properties to be set before they can be initialized and activated.
To view this administrative console page, click UDDI > UDDI Nodes.
Each UDDI node is represented by a UDDI Node ID, Description, UDDI Application Location and Status. To manage an individual UDDI node, click on its UDDI Node ID link. This takes you to the Configuration page where you can manage its general properties, initialize it if the status is set to Initialization Pending, and access pages for managing policies, UDDI publishers, tiers and value sets.
Specifies the identifier for the UDDI node.
Specifies the description of the UDDI node.
Specifies the server in which the UDDI registry application is deployed and running.
For a cluster configuration, which will
include several servers all running the UDDI registry application, you will
see a location listed for each of the active servers in the cluster.
For a cluster configuration, which will include
several servers all running the UDDI registry application, you will see a
single location listed; this location could represent any of the active servers.
Specifies the status of the UDDI node.
The Status of the UDDI node can be Initialization Pending, Activated or Deactivated. To activate UDDI nodes that are Deactivated, select them by checking the corresponding check boxes in the Select column and click the Activate button. Similarly to deactivate UDDI nodes, select them and click the Deactivate button.
Related information
Managing the UDDI registry
Administrative console buttons
Administrative console page features
Overview of the UDDI registry Administrative Interface
Backing up and restoring the UDDI registry database