Publishing Web Services
| Windows 2003 Server includes UDDI services as an optional component that can be added using Add/Remove Windows Components from the Add or Remove Programs Control Panel (Figure 9.8). UDDI services require SQL Server to store the information regarding the various Web services registered. The UDDI services installation program will prompt you either to select a existing SQL Server or, if required, will install Microsoft SQL Server Desktop Edition (MSDE) Engine. Figure 9.8. Installing Windows 2003 UDDI services. Microsoft also provides a UDDI SDK (http://msdn.microsoft.com/uddi) for programmatic access to UDDI interfaces. Separate UDDI SDKs are available both for .NET and COM programming environments. After the Web service has been developed, it can be published to a UDDI registry. As noted previously, the registry can be either your own internal server or an external registry such as the Microsoft UDDI registry (test or production version). Where you publish your Web service depends on the scope of the Web service and whether it is internally deployed or is available for external consumers. In this scenario, you use an internal Web services UDDI registry. Web services can also be registered by using the Web-based registration application that is part of the UDDI services implementation (Figure 9.9). Figure 9.9. Registering Web services on Windows 2003 UDDI services. After the Web services are registered on a UDDI Registry (whether it is internal or external), the Visual Studio .NET Add Web Reference tool allows the developer to search and bind to Web services from the registry within the Visual Studio .NET environment. In addition, using a simple update command, existing Web service bindings can be updated to match the current implementation. Use http://localhost/uddipublic/addwebreference as the URL within the Add Web Reference tool to connect to local UDDI registry services (Figure 9.10). Figure 9.10. Querying Web services registered in UDDI registries using Visual Studio .NET 2003. |
