Enterprise UDDI Services in Windows 2003 has many attractive benefits. Here is a shortlist of some of those advantages:
- It’s free and is available with every edition of Windows Server including standard!
- Compatible with the UDDI v. 2 specification that’s governed by OASIS.
- Built in support for storing data in SQL Server.
- Convenient .NET-based SDK that simplifies working with the UDDI by alleviating the client programmer from having to use SOAP or Web services.
- Ability to publish the location of the UDDI registry in Active Directory, so that clients can find it automatically without having to rely upon configuration.
- Management is done through a Microsoft Management Console (MMC) snap-in that provides a common appearance and user experience that IT administrators are used to.
- Web-based UI for managing, viewing, and searching the UDDI registry.
- Integrated Windows authentication that can use Active Directory accounts or local server accounts.
- Authentication is support via tokens as defined in the UDDI v. 2 specification. Tokens are mapped to Windows accounts that can be managed centrally by IT (in the case of Active Directory) or local server accounts can be used.
- Authorization and permissions are based on roles/groups (local or central).
- Built-in logging that is written to the Windows event log.
- Pre-made GUI tool that can be used to define and export custom taxonomies which can be imported into a registry to aid in the discovery process (available in Windows 2003 Server Resource Kit).
- Included wizard for registering WSDL documents in UDDI registry (helpful in pushing a services description to a development registry prior to deployment).
- Resource Kit includes command-line tools for importing and exporting server configuration settings.
- Provides extensions to the UDDI standard that allow for the creation of hierarchical taxonomies.
Given all this, what are the drawbacks? What are the benefits of other products from alternate vendors? What's changing in Windows Server 2008? Are there any plans to upgrade the service to v. 3 of the UDDI specification?
All of these are important questions when deciding whether or not to standardize on Microsoft's offering. Though I don't have the answers to these questions, hopefully, the above list will help you in your decision making process. If you have the answers to the questions, or any thoughts, please leave a comment.