HTTP GET services for UDDI registry data structures

 

The UDDI registry offers an HTTP GET service for access to the XML representations of the businessEntity, businessService, bindingTemplate, and tModel UDDI data structures. The URL at which these structure are accessible uses the entity key as a URL parameter. The XML element that is returned is a businessDetail, serviceDetail, bindingDetail or tModelDetail element, according to the type of entity key supplied. XML for both UDDI V2 and V3 can be retrieved, each at different URLs. The formats of the URLs to send the HTTP GET requests to are:

For UDDI V2:

http://<server>:<port>/uddisoap/get?<entityKey type>=<v2 entityKey>

For UDDI V3:

http://<server>:<port>/uddiv3soap/get?<entityKey type>=<v3 entityKey>

For example, if <server> = myserver.com and <port>=9080, you can access the uddi-org:types tModel at the following URLs:

UDDI V2:

http://myserver.com:9080/uddisoap/get?tModelKey=uuid:c1acf26d-9672-4404-9d70-39b756e62ab4

UDDI V3:

http://myserver.com:9080/uddiv3soap/get?tModelKey=uddi:uddi.org:categorization:types

A number of UDDI property and policy settings relate to the HTTP GET services:

• V3 HTTP GET for UDDI entities

  • Node supports HTTP GET

  • URL prefix for V3 GET servlet

  • Node generates discovery URLs

• V2 HTTP GET for discovery URLs

  • Prefix for generated discovery URLs

  • Node generates discovery URLs

For details, refer to UDDI node miscellaneous policy settings and UDDI node settings.

---

 

Related tasks

UDDI registry client programming

 

Reference topic