Red Hat Training

A Red Hat training course is available for JBoss Enterprise SOA Platform

Chapter 14. Administering Your Service Registry with the jUDDI Web Console

14.1. Service Registry

A service registry is a central database that stores information about services, notably their end-point references. The default service registry for the JBoss Enterprise SOA Platform is jUDDI (Java Universal Description, Discovery and Integration). Most service registries are designed to adhere to the Universal Description, Discovery and Integration (UDDI) specifications.
From a business analyst’s perspective, the registry is similar to an Internet search engine, albeit one designed to find web services instead of web pages. From a developer's perspective, the registry is used to discover and publish services that match various criteria.
In many ways, the Registry Service can be considered to be the "heart" of the JBoss Enterprise SOA Platform. Services can "self-publish" their end-point references to the Registry when they are activated and then remove them when they are taken out of service. Consumers can consult the registry in order to determine which end-point reference is needed for the current service task.

14.2. How the Registry Works

  1. The JBoss Enterprise Service Bus funnels all interaction with the Registry through the registry interface.
  2. It then calls a JAXR implementation of this interface.
  3. The JAXR API needs to utilize a JAXR implementation. (By default, this is Apache Scout.)
  4. Apache Scout, in turn, calls the Registry.

14.3. jUDDI Console

The jUDDI Console is a web-based graphical interface that you must use in order to configure the jUDDI Registry. It is accessible at http://localhost:8080/uddi-console/.

14.4. Grant Access to the jUDDI Console

Prerequisites

  • A user with the name "root" who has been assigned the security roles of "user" and "admin".
You must log in as a jUDDI Publisher named root to give anyone administration rights. Once a user has these administration rights, they can grant them to other users.

Procedure 14.1. Task

  1. Open a web browser session and go to the jUDDI Console at http://localhost:8080/uddi-console/. Log in as root.
  2. Click "Publisher".
  3. From the Publisher ID list, click on the username.
  4. Select the "Is Admin" checkbox.
Result

The user you selected now has administrative rights.

14.5. jUDDI M-Beans

You can query jUDDI M.-Beans in the JMX console. Doing so allows you to observe Service Registry operations. These are the M.-Beans available:
  • org.apache.juddi.api.impl.UDDIServiceCounter
  • org.apache.juddi.api.impl.UDDICustodyTransferCounter
  • org.apache.juddi.api.impl.UDDIInquiryCounter
  • org.apache.juddi.api.impl.UDDIPublicationCounter
  • org.apache.juddi.api.impl.UDDISecurityCounter
  • org.apache.juddi.api.impl.UDDISubscriptionCounter
Each UDDI operation under the API supplies the following functionality for each method:
  • successful queries
  • failed queries
  • total queries
  • processing time
  • an aggregate count of total/successful/failed per API
Only one operation is available: resetCounts.