Jeff Woehlner writes: When
designing your internal UDDI registry, planning is key. There are a
lot of posts about using UDDI but most all of them show end results too
generic for immediate use. Because it was so difficult to find a good
template design from which to start, I'm writing this.
The UDDI specification is quite generic. The businessEntity element (MS UDDI "Provider") can be configured to represent a user, a development team, a machine name, or something else entirely. To quote the Microsoft UDDI Guide: "The most important aspect of choosing a provider construct is consistency."
After much contemplation and testing, I found that the most logical and useful Provider would be the root domain name of the host test server. (Example: www-test.intra.net)...
The UDDI specification is quite generic. The businessEntity element (MS UDDI "Provider") can be configured to represent a user, a development team, a machine name, or something else entirely. To quote the Microsoft UDDI Guide: "The most important aspect of choosing a provider construct is consistency."
After much contemplation and testing, I found that the most logical and useful Provider would be the root domain name of the host test server. (Example: www-test.intra.net)...
