WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Displaying the UDDI registry user interface

Why and when to perform this task

Use this task to perform actions on UDDI information through the UDDI user console. The exact behavior of the user console depends on several configurable factors, such as: The following table summarizes the behavior of the UDDI registry user console.
Table 1.
WebSphere Application Server 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 WebSphere Application Server 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; you 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 administrative 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 administrative console or the JMX management interface (this applies to new requests only).
The variables in the table have the following values:

Steps for this task

  1. Start the UDDI application, if it is not already running.
  2. Open a browser window and ensure that cookies are enabled.
  3. 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

Result

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

What to do next

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



Related concepts
Access control for UDDI registry interfaces

Related tasks
Configuring the UDDI registry to use WebSphere Application Server security
Finding an entity using the UDDI registry user interface
Editing or deleting an entity using the UDDI registry user interface
Publishing an entity using the UDDI registry user interface

Related information
Using the UDDI registry user interface

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsu_display_uc.html

© Copyright IBM Corporation 2003, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)