UDDI registry administrative (JMX) interface

Use the UDDI registry administrative interface to inspect and manage the runtime configuration of a UDDI application. We can manage the information about a UDDI node and its activation state, update properties and policies, set publish tier limits, register UDDI publishers, and control value set support.

We can read and invoke the operations of the UDDI registry administrative interface using standard Java Management Extensions (JMX) interfaces. For more information about using JMX administrative programs, see the related links.

Each WebSphere Application Server UDDI registry application registers an MBean with an MBean identifier of UddiNode. Client applications can use this MBean to inspect and manage the runtime configuration of a UDDI application. Management activities include managing the activation state of a UDDI node, managing information about a UDDI node, updating properties and policies, setting publish tier limits, registering UDDI publishers, and controlling value set support.

We can read and invoke the UddiNode attributes and operations using standard JMX interfaces. A UddiNodeProxy.java client utility class provides a ready-made application to connect to a UddiNode MBean and perform all the available operations. Example classes are also provided to drive UddiNodeProxy and demonstrate how to use the various UDDI management data types.

When WAS security is enabled, we can invoke the operations of the UddiNode Bean only if we are a user in an administrative role. Operations that make updates require the administrator or operator role. Administrator, operator, configurator and monitor roles can perform get operations.

Use the UDDI registry

Use administrative programs (JMX)