You can manage the UDDI nodes in this cell. Each UDDI node represents an individual UDDI registry application. A UDDI node is displayed in this list only if its underlying UDDI application is started. The status of the UDDI node can indicate 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
.Specifies the identifier for the UDDI node.
To manage an individual UDDI node, click on the UDDI _node_id to display the UDDI node settings 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 description of the UDDI node.
Specifies the server in which the UDDI registry application is deployed and running.
For a
cluster configuration, which includes several servers that all run
the UDDI registry application, a location is listed for each of the
active servers in the cluster.
For a
cluster configuration, which includes several servers that all run
the UDDI registry application, a single location is listed; this location
might represent any of the active servers.
Specifies the status of the UDDI node.
If the status of a node is Initialization pending, you must initialize the node before you can activate it. If you attempt to initialize the node and it remains in a pending state, an error occurred during migration or initialization.
To activate UDDI nodes that are deactivated, select them using the corresponding check boxes and click Activate. Similarly, to deactivate UDDI nodes, select them and click Deactivate.