Figure 1.1: Search Results For *.Dll In The C:\WINNT Directory.
Figure 1.2: Shows The Helloworld Dll Added To The “References” Of The Project.
Figure 1.3: Sayhello Executable Displaying The Output Of The Displayhello Method Defined In The Library Example.
Figure 1.4: Remote Objects Can Be Shared By Several Applications In A Business Setting. In This Case, The Remote Object Server Contains Objects For Applications Running On Workstations, Mainframes, Laptops, And Other Servers.
Figure 1.5: How Web Services May Bring Data From A Legacy COBOL Banking System To A .NET- (Or Java-) Based Web Site.
Chapter 2: Brief Introduction to XML
Figure 2.1: Using Internet Explorer to report well-formedness errors in XML documents.
Chapter 3: SOAP
Figure 3.1: This image demonstrates a simple SOAP transaction.
Figure 3.2: How a SOAP message can be routed by a SOAP intermediary.
Figure 3.3: How two SOAP nodes converse over a stock quote.
Figure 3.4: How a CORBA or COM+ connection can handle the same conversation over one connection.
Chapter 4: WSDL
Figure 4.1: How a client asks for a WSDL file and uses it to create an interface to the methods from the Web Service.
Figure 4.2: Illustrates the structure of the WSDL document along with any child elements of each major section.
Chapter 5: UDDI
Figure 5.1: Microsoft’s UDDI home page.
Figure 5.2: The search page at http://uddi.microsoft.com.
Figure 5.3: The results of the search for stock quote Web Services.
Figure 5.4: Web Services available from “Cdyne.”
Figure 5.5: Further details of the stock quote Web Service.
Figure 5.6: The UDDI XML entry for “Cdyne.”
Figure 5.7: The replication of UDDI information amongst the support Web Sites.
Figure 5.8: Illustrates how you can use a UDDI site to find the Web Services you need and then use the UDDI site to promote the resulting services.
Figure 5.9: The results for searching for Sun Microsystems on http://uddi.microsoft.com.
Chapter 6: .NET Web Services with C#
Figure 6.1: The “Add/Remove Programs” dialogue for Windows 2000. Notice the “Add/Remove Windows Components” on the lefthand side.
Figure 6.2: The dialogue to select which Windows components to install.
Figure 6.3: A demonstration of how to create a C# Web Service project in Visual Studio.NET.
Figure 6.4: Design mode for creating Web Services in Visual Studio.
Figure 6.5: The information made available to the browser from Microsoft’s .NET Web Services implementation.
Figure 6.6: How the Web Service displays its WSDL information.
Figure 6.7: Output in Internet Explorer for testing the GetTestQuote method.
Figure 6.8: How Internet Explorer displays the description information. Also notice that the warning from Microsoft that you need to change the namespace is no longer present.
Figure 6.9: The “New Project” dialogue box for creating a Windows application.
Figure 6.10: The design of the Windows program.
Figure 6.11: The “Add Web Reference” dialogue of Visual Studio.NET.
Figure 6.12: The Web reference to local host in the “Solution Explorer” window.
Figure 6.13: The Visual C# client executing and receiving a value back from the Web Service.
Figure 6.14: The appropriate selections for creating an ASP.NET Web Application based on C#.
Figure 6.15: The output of the previous ASP.NET code in Internet Explorer.
Figure 6.16: The ASP.NET Web Services consumer with some minor cosmetic changes.
Figure 6.17: The disco file shown in Internet Explorer.
Figure 6.18: Searching for a Web Service using the “Add Web Reference” dialogue in Visual Studio.NET.
Figure 6.19: The results of searching for “Stock Quote” in the “Add Web Reference” dialogue.
Figure 6.20: The WSDL file for one of the stock quote Web Services found in the “Add Web Reference” dialogue box.
Chapter 7: Web Services with Apache SOAP
Figure 7.1: The appropriate response to a browser after installing the Apache SOAP library.
Figure 7.2: How the SOAP “Admin” tool appears in Internet Explorer.
Figure 7.3: The SOAP RPC router in Internet Explorer.
Figure 7.4: The results of running testit.cmd in the Stock Quote sample directory of Apache SOAP.
Figure 7.5: How the SOAP Admin tool lists the SimpleStockQuote Web Service.
Figure 7.6: Screen capture of the TCPTunnelGui displaying a request and response for the SimpleStockQuote example.
Figure 7.7: How the WebSvcGui example appears under Windows 2000.
Figure 7.8: The output of the first example servlet in Internet Explorer.
Figure 7.9: The output of the servlet form example after entering “C” in the text box.
Figure 7.10: The first JSP example displaying the value from the Web Service.
Figure 7.11: The output of the JSP/Bean example.
Chapter 8: Web Services with Apache Axis
Figure 8.1: The Apache Axis home page shown in Internet Explorer.
Figure 8.2: The results of the Apache Axis diagnostics.
Figure 8.3: How Apache Axis lists installed Web Services.
Figure 8.4: The results of running the testit.cmd file in the Apache Group’s stock example.
Figure 8.5: The response to the browser when pointed to the SimpleStockExample Web Service.
Figure 8.6: All the deployed Web Services available at http://localhost:8080/axis/AxisServlet.
Figure 8.7: The WSDL for the SimpleStockExample from Apache Axis.
Figure 8.8: The TCP Monitor as it appears when it first loads.
Figure 8.9: The “Port 8080” display window of TCP Monitor.
Figure 8.10: The TCP Monitor window showing the results of SOAP requests and responses.
Figure 8.11: The WSDL output for the SimpleStockExample Web Service.
Chapter 9: Java and .NET Web Service Integration
Figure 9.1: Examples in this book execute under different Web Servers but still reside on the same machine and OS.
Figure 9.2: Web Services for C# and the Apache group residing on different machines where UNIX is the most likely platform for Apache products.
Figure 9.3: The MSNETID Web Service output to Internet Explorer.
Figure 9.4: The WSDL created by the Java2WSDL tool for the Apache SOAP example Web Service.
Figure 9.5: The WSDL output of the Axis example Web Service.
Figure 9.6: Notice the output window of the WebServiceStudio for the results of calling the Axis Web Service.
Figure 9.7: The “Request and Response” to the Axis Web Service in WebServiceStudio.
Figure 9.8: The client and proxy code shown in WebServiceStudio.
Figure 9.9: “Solution Explorer” in Visual Studio.NET displaying the renamed Web References.
Figure 9.10: The CallXPlatform program calling a .NET Web Service.
Figure 9.11: The CallXPlatform program calling an Apache SOAP Web Service.
Figure 9.12: The CallXPlatform program calling an Apache Axis Web Service.
Figure 9.13: The output of GetAllTypes Java program that connects with all three of the Web Services.
Figure 9.14: Using Web Services to bridge the gap between heterogeneous systems.
Chapter 10: Web Service Security
Figure 10.1: A firewall and proxy server working together to protect and monitor the network inside a corporation.
Figure 10.2: Using a subnet to control access to a Web Services implementation.
Figure 10.3: The security tab in Internet Information Server.
Figure 10.4: The “Authentication Methods” dialogue box.
Figure 10.5: The Windows authentication dialogue box.
Figure 10.6: The “Security” tab with “Basic Authentication” chosen.
Figure 10.7: Selecting a domain name for users that utilize Basic Authentication to access the Web Services.
Figure 10.8: The “Basic Authentication” dialogue box in Internet Explorer.
Figure 10.9: Visual Studio.NET asks for your username and password to access the WSDL of a secured Web Service.
Figure 10.10: The “Management Console” on Windows 2000 Pro when it first loads.
Figure 10.11: The "Add/Remove Snap In" window.
Figure 10.12: The window in the management console where you select certificates to manage.
Figure 10.13: The console window with certificates selected for the current user.
Figure 10.14: The console window shows the installed certificates for the author’s machine.
Figure 10.15: A .NET Web Services implementation proxying requests to a Java Web Services implementation behind the firewall.
Figure 10.16: IIS and Apache Web servers sitting in the DMZ proxying requests to one another depending on the consumer who makes the request.
Chapter 11: Practical Application of Web Services
Figure 11.1: The JSP consumer with the drop-down list.
Figure 11.2: The ASP.NET client form.
Figure 11.3: Using WebServicesStudio to test one of the Money Exchange methods.
Chapter 12: Using Web Services as a Middle Tier
Figure 12.1: A middle tier utilizing Web Services can act as a clearinghouse to various data sources.
Figure 12.2: Creating a C# class library in Visual Studio.NET.
Figure 12.3: The “Build” settings for the XML parsing code.
Figure 12.4: Proxy requests to another Web Service doubles the amount of traffic being generated.
Figure 12.5: Putting the unit of work within a single method reduces the amount of traffic.
Figure 12.6: Login.aspx in Internet Explorer.
Figure 12.7: Default.aspx in Internet Explorer.
Chapter 13: Creating Your Own Web Services Implementation
Figure 13.1: Making the HTTP request is the first step in creating a Web Service implementation.
Figure 13.2: The HTTP request to the server must include the appropriate XML from the SOAP standard.
Figure 13.3: Reading the response is the next part of designing your Web Services software.
Figure 13.4: How implementing Web Services software as a server implementation opens access to other platforms.
Figure 13.5: The HTML form that communicates with the MoneyExchangeAxis Web Service.
Figure 13.6: The HTML form that communicates with the.NET Web Service.
Appendix D: Visual Basic.NET
Figure D.1: The “New Project” dialogue in Visual Studio.NET with selections made for Visual Basic.NET.
Appendix F: Microsoft’s UDDI .NET SDK
Figure F.1: Adding a reference to a project within Visual Studio.NET.
Figure F.2: How the GUI for the UDDI SDK example in this appendix may appear.