Use the UDDI registry user interface

Use the UDDI registry user interface

The UDDI registry user interface (also referred to as the UDDI registry user console) is a graphical interface that we can use to explore the UDDI registry.
Set the appserver that hosts the UDDI registry for UTF-8 encoding support. See the topic about configuring appservers for UCS transformation format. The UDDI user console does not support UTF-16 encoding.
The user console provides a GUI to the majority of the UDDI V3 API. The user console is not intended to support the full API set. There is some focus on inquiry operations, because the main purpose of the UDDI user console is to allow us to issue inquiry requests and to familiarize theself with general UDDI concepts.
The following list describes areas for which support through the user console is not provided, and other known restrictions to the user console.

Help is provided in the form of explanatory text on the screens.
We cannot specify maximum rows on find queries. We can set the single maximum rows value for the registry by using the Maximum inquiry result set size general property on the admin console.
The identifier feature is not supported in the find business area or the find technical model (tModel) area.
In the add business area, no support exists for adding Discovery URLs, Identifiers or Digital Signatures.
In the add technical model (tModel) area, no support exists for adding Identifiers or Digital Signatures.

The exact behavior of the user console depends on the following configurable factors:

Whether WebSphere Application WAS security is enabled.
How the UDDI registry GUI role mappings are set. The UDDI registry supports a number of security roles, including two for the user console: GUI_Publish_User and GUI_Inquiry_User.
How the UDDI registry GUI SSL transport guarantee constraints are set. The UDDI registry allows SSL settings to be configured and this includes two settings for the user console.

The following table summarizes the behavior of the UDDI registry user console.

Table 1. Behavior of the UDDI user console

WAS security status URL used to access the UDDI user console Behavior of the UDDI user console
Enabled http://host_name:http_port/uddigui Inquiry requests do not require authentication; they use the HTTP URL and are not secure. Publish requests do require WAS authentication. When you access the publish pane you will be dynamically redirected to use HTTPS, and will be prompted for a user ID and password. For the request to be successful , the authenticated user must be registered as a UDDI publisher.
If the GUI_Inquiry_User role is mapped to all authenticated users, and the transport guarantee in the user data constraint section for that role is set to CONFIDENTIAL, all requests, including inquiry, require authentication and use of HTTPS.
https: //host_name:ssl_port/uddigui Requests are secure; we are prompted to authenticate with a user ID and password. For the request to be successful , the authenticated user must be registered as a UDDI publisher.
Disabled http://host_name:http_port/uddigui No requests, either publish or inquire, are authenticated and the data flow is not secure (non SSL). Even though SSL transport-guarantee settings are defined, they are not enforced if security is disabled. All publish operations are performed using a user ID of UNAUTHENTICATED or a value that can be configured using the admin console or the JMX management interface (this applies to new requests only).
https: //host_name:ssl_port/uddigui No requests, either publish or inquire, are authenticated, but the data flow is secure because the SSL URL and port are used explicitly. All publish operations are performed using a user ID of UNAUTHENTICATED or a value that can be configured using the admin console or the JMX management interface (this applies to new requests only).

The variables in the table have the following values:

host_name is the name of the machine that is running the relevant profile.
http_port is the internal HTTP port for the profile, for example 9082.
ssl_port is the internal SSL port for the profile, for example 9443.

Start the UDDI application, if it is not already running.
Open a browser window and ensure that cookies are enabled.
Access the UDDI registry user console using one of the following default URLs.

http://host_name:http_port/uddigui
https: //host_name:ssl_port/uddigui

We can change the look and feel of the user console by modifying the appropriate .css stylesheet files.
You can edit style class definitions in these files to alter the overall theme of the UDDI registry user console, including font attributes, layout and colors.
The .css files are located in...
$WP_PROFILE/installedApps/mycell/UDDIRegistry.mynode.myserver.ear/v3gui.war/theme

Refresh the browser window after changing a stylesheet file, for the changes to take effect.

Results
The user console displays the default frameset containing the following items:

The header frame.
The navigation frame showing find options.
The details frame.

Next steps
We can now use the UDDI user console to find, edit or publish UDDI information.

Finding an entity using the UDDI registry user interface
Publishing an entity using the UDDI registry user interface
Edit or deleting an entity using the UDDI registry user interface
Create business relationships using the UDDI registry user interface
Example: Publishing a business, service and technical model using the UDDI registry user interface

Related concepts

Access control for UDDI registry interfaces

Related tasks

Set appservers for UCS Transformation Format
Set the UDDI registry to use WAS security
Use the UDDI registry

WAS security status	URL used to access the UDDI user console	Behavior of the UDDI user console
Enabled	http://host_name:http_port/uddigui	Inquiry requests do not require authentication; they use the HTTP URL and are not secure. Publish requests do require WAS authentication. When you access the publish pane you will be dynamically redirected to use HTTPS, and will be prompted for a user ID and password. For the request to be successful , the authenticated user must be registered as a UDDI publisher. If the GUI_Inquiry_User role is mapped to all authenticated users, and the transport guarantee in the user data constraint section for that role is set to CONFIDENTIAL, all requests, including inquiry, require authentication and use of HTTPS.
https: //host_name:ssl_port/uddigui	Requests are secure; we are prompted to authenticate with a user ID and password. For the request to be successful , the authenticated user must be registered as a UDDI publisher.
Disabled	http://host_name:http_port/uddigui	No requests, either publish or inquire, are authenticated and the data flow is not secure (non SSL). Even though SSL transport-guarantee settings are defined, they are not enforced if security is disabled. All publish operations are performed using a user ID of UNAUTHENTICATED or a value that can be configured using the admin console or the JMX management interface (this applies to new requests only).
https: //host_name:ssl_port/uddigui	No requests, either publish or inquire, are authenticated, but the data flow is secure because the SSL URL and port are used explicitly. All publish operations are performed using a user ID of UNAUTHENTICATED or a value that can be configured using the admin console or the JMX management interface (this applies to new requests only).