UDDI and the understanding of UDDI under the WebLogic

1.weblogic and UDDI
The WebLogic Server includes a UDDI directory called the UDDI directory browser. You can access the UDDI directory browser using the following URLs:
http://localhost:7001/uddiexplorer/index.jsp
WebLogic Server configures a private registry to which Web Service can be published. To publish a Web Service, follow these steps:
(1) In the browser, go to http://localhost:7001/uddiexplorer/index.jsp
(2) Select "Publish Private Registry".
(3) Log in to the UDDI directory browser. The default user name and password are weblogic.
To publish a service, you must fill out the service information:
In the Proj/dept field, provide the name of the project name or the department that can provide the service.
In the "Service Name" field, provide the name of the service.
In the WSDL field, type the URL of the Web Service. This URL brings the user who finds the Web service to the overview page of the test view of the Web service, from which the user can obtain the WSDL file. For example, the URL for the HelloWorld sample Web Service is:
Http://hostname:port/samples/HelloWorld.jws
In the "Service Description" field, enter a description of the service.
(4) Click "Add Service".
On the next page, click Publish.
WebLogic provides the development of the UDDI Client API in Webservices.jar and Weblogic.jar files, which can be used to develop UDDI, which has two instances of reference.
2. Understanding of UDDI:
1). Using a series of keys is created by the user in the related service. When a business entity, Tomdel, and so on, randomly generates a unique ID, this ID cannot be set or changed by itself.
2). Access to UDDI API is actually a Uudi document standard specification, a tree-climbing method from the top to the bottom of a rendition, when using the API access can be based on this rule to achieve UDDI access. This tree climb. Similar to the idea of an XML accessor, it is applicable to various versions of UDDI.
3). The UDDI API is a complete implementation of the UDDI specification, and in enterprise development, the functionality used is limited, and only a few core access programs can be written as needed. Because the specification of UDDI is defined in a large number of things that are unrelated to enterprise technology applications, especially system application development (commercial stuff), you can focus on what you need.