- Installing the Microsoft SOAP Toolkit
- Creating a Virtual Directory
- Using WSML and WSDL
- Writing the WSML File
- Writing the WSDL File
- Testing the SOAP Connection
- Wrapping Up
Creating a Virtual Directory
SOAP clients specify which SOAP service they want to invoke by connecting to a specific URL hosted on a SOAP-compliant server. Although it's possible to commingle SOAP and non-SOAP content in a single virtual directory, this application will isolate all SOAP-related content in a single IIS virtual directory called OrderHandler.
The examples and test scripts for this application assume that IIS is running on the local machine (that is, all URLs begin with http://localhost/). Create an empty subdirectory that will contain the SOAP-related gateway files, and share it using IIS as the OrderHandler subdirectory of the IIS default web site. This directory will contain the Web Services Meta Language (WSML) and Web Services Description Language (WSDL) files that are used by the SOAP ISAPI plug-in to serve SOAP client requests.
After the virtual directory has been set up, it's time to create the WSML and WSDL files that will be used by the SOAP server (and some SOAP clients) to call the OrderHandler object.