Use the UDDI registry user interface

WAS v8.5 > Develop applications > Develop web services - UDDI registry > Develop with the UDDI registry
Use the UDDI registry user interface

The UDDI registry user interface (also referred to as the UDDI registry user console) is a graphical interface used to issue inquiry requests and explore the UDDI registry.
If you require multiple language encoding, the UDDI user console supports only Universal Transformation Format (UTF)-8 encoding. For UTF-8 encoding support, configure the application server that hosts the UDDI registry for UCS transformation format. The UDDI user console does not support UTF-16 encoding.
The UDDI user console provides a graphical user interface to most of the UDDI v3 API. The user console does not support the full API set, but provides a way to issue inquiry requests and to familiarize yourself with general UDDI concepts. Explanatory text on the screens provides help. The following list describes areas that are not supported through the user console, and other known restrictions in the user console.

We cannot specify maximum rows on find queries. We can set the "Single maximum rows" value for the registry using the "Maximum inquiry result set size" general property on the dmgr console.
The identifier feature is not supported in the find business area or the find technical model (tModel) area.
In the add business area, adding discovery URLs, identifiers or digital signatures is not supported.
In the add technical model (tModel) area, adding identifiers or digital signatures is not supported.

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

Whether WebSphere Application Server security is enabled.
How the UDDI registry GUI role mappings are set. The UDDI registry supports two security roles for the user console:

GUI_Publish_User
GUI_Inquiry_User.

How the UDDI registry GUI SSL transport guarantee constraints are set. The UDDI registry supports the configuration of SSL settings, including two settings for the user console.
The following table summarizes the behavior of the UDDI registry user console.
Behavior of the UDDI user console. The table lists the URLs used for the different UDDI registry settings, along with a description of the behavior associated with each setting.

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 require WAS authentication. When you access the publish pane, you are dynamically redirected to use HTTPS, and are prompted for a user ID and password. For a successful request, 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; you are prompted to authenticate with a user ID and password. For a successful request, 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 dmgr 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 dmgr 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 9080.
ssl_port is the internal SSL port for the profile, for example 9443.

To display the UDDI registry user console, use the following procedure.
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 through one of the following default URLs.

http://host_name:http_port/uddigui
https://host_name:ssl_port/uddigui
Optional: To change the appearance and operation of the UDDI registry user console, modify the appropriate .css stylesheet files. We can edit style class definitions in the stylesheet files, including font attributes, layout, and colors. The stylesheet files are in the following directory:
profile_root/installedApps/cell_name/
UDDIRegistry.node_name.server_name.ear/v3gui.war/theme
After you change a stylesheet file, refresh the browser window for the changes to take effect.
Results
The user console displays the default frameset, which contains the following items:

The header frame.
The navigation frame, which shows find options.
The details frame.

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

Subtopics

Finding an entity using the UDDI registry user interface
We can use the UDDI registry user interface to find services, businesses, and technical models.
Publishing an entity using the UDDI registry user interface
We can use the UDDI registry user interface to publish businesses and technical models.
Edit or deleting an entity using the UDDI registry user interface
We can use the UDDI registry user interface to edit or delete the businesses and technical models that you own, for example, to add services to businesses.
Create business relationships using the UDDI registry user interface
If your business has an association with another business in the UDDI registry, for example a preferred supplier, we can describe this association in the UDDI registry by creating a business relationship.
Example: Publishing a business, service, and technical model using the UDDI registry user interface
This example describes how to use the UDDI registry user interface to publish a used car business called Modern Cars to the UDDI registry, and how to publish a service and technical model for the business.

Related concepts:

Access control for UDDI registry interfaces

Related

Configure application servers for UCS Transformation Format
Configure the UDDI registry to use WAS security

+
Search Tips | Advanced Search

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 require WAS authentication. When you access the publish pane, you are dynamically redirected to use HTTPS, and are prompted for a user ID and password. For a successful request, 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.
Enabled	https://host_name:ssl_port/uddigui	Requests are secure; you are prompted to authenticate with a user ID and password. For a successful request, 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 dmgr console or the JMX management interface (this applies to new requests only).
Disabled	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 dmgr console or the JMX management interface (this applies to new requests only).