WAS v8.5 > Reference > Sets

UDDI node page

We 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 dmgr console page, click UDDI > UDDI Nodes.


UDDI Node ID

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

Description of the UDDI node.


UDDI Application Location

Server in which the UDDI registry application is deployed and running.


Status

Status of the UDDI node.

The UDDI node can have one of the following statuses:

If the status of a node is Initialization pending, you must initialize the node before we can activate it. If we 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.

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


Subtopics


Related


Back up and restore the UDDI registry database


Reference:

UDDI registry administrative (JMX) interface


Related information:

Administrative console buttons
Administrative console page features


+

Search Tips   |   Advanced Search