*************************************************************** Microsoft SOAP Toolkit 3.0 Readme File *************************************************************** (c) Copyright Microsoft Corporation, 2002.

All rights reserved. This file contains information about this release. You should read this before using the web release. *************************************************************** Contents *************************************************************** 1.0 Introduction 1.1 Features and Fixes included in this release 1.2 Limitations and Guidelines 2.0 Installing the SOAP Toolkit 2.1 System Requirements 2.2 Files Copied 3.0 Questions/Comments *************************************************************** 1.0 Introduction *************************************************************** If you are first time user of SOAP, read the documentation. The conceptual material in the documentation is written to provide quick start to new users. NOTICE: SOAP Toolkit 3.0 will install "side-by-side" with previous versions of the SOAP Toolkit. Your client applications and service virtual directories MUST be updated to use SOAP Toolkit 3.0. For more information see the "Migrating Applications from SOAP Toolkit 2.0 to 3.0" topic in the help file. --------------------------------------------------------------1.1 Features and Fixes included in the 3.0 release --------------------------------------------------------------* You can now send and receive attachments. Attachments are the most efficient way to send data such as pictures, XML documents, large amounts of text, etc. See the "Handling Attachments" topic in the help file for more information. * A "Generic Type Mapper" (GTM) is now provided. The GTM can map data to/from the public properties of a COM object and the XML in a SOAP message. The WSDL Wizard automatically generates WSDL and WSML that describes complex types and registers those types for use with the GTM. See the "Using the Generic Type Mapper" topic in the help file for more information. * A SOAPVDIR.CMD script is installed in the MSSOAP\Binaries folder. This script can be used to create an IIS virtual directory properly configured to use the SOAP Toolkit 3.0 ISAPI listener and to configure an existing virtual directory to use the 3.0 ISAPI listener. * A SOAPVDIR.CMD script is installed in the Toolkit directory.

This script can be used to create an IIS virtual directory properly configured to use the SOAP Toolkit 3.0 ISAPI listener and to configure an existing virtual directory to use the 3.0 ISAPI listener. * WSDL and XML Schema "import" and "include" elements are now supported. * "One way" messages are now supported. These are simply messages for which no response is expected. They are identified in the WSDL by the absence of an "output" message for an operation. * You can pass a server object instance to the SoapServer object from an ASP page using the SoapInvokeEx method. This allows you to initialize the server object with information taken from the Request ASP object, Session or Application collections, etc. * The elementFormDefault and form attributes are now correctly used when generating and parsing document/literal format SOAP messages. * You can now replace the built in type mappers with a custom type mapper. * Source for the SOAP Messaging Object (SMO) framework classes is now installed with the SOAP Toolkit Samples. The SMO Wizard is no longer part of the SOAP Toolkit release. * IXMLDOMNodeList parameters can now contain attribute nodes. The attributes will be added to the parameter element in the SOAP message. * The WSDL Wizard now generates a "client" side WSML file in addition to the "server" side WSML. The "client" WSML contains type mapper information but not the programmer id of the server object. * The WSDL Wizard now allows you to save settings in a configuration file, and restore those settings when you regenerate WSDL for a particular server object. * The following XML schema versions are no longer supported: "http://www.w3.org/1999/XMLSchema" "http://www.w3.org/2000/10/XMLSchema" You must use the W3C recommended version: "http://www.w3.org/2001/XMLSchema". ------------------------------1.2 Limitations and Guidelines ------------------------------* Any previous version of the SOAP Toolkit 3.0 must be uninstalled before installing this version. You can leave SOAP Toolkit 2.0 installed. SOAP Toolkit 3.0 is independent of SOAP Toolkit 2.0. You must update your client applications and service virtual directories to use the SOAP Toolkit 3.0.

* Soap will not work correctly unless the "Enable Buffering" option is set in the App Options tab of the virtual directory property settings. * Custom type mappers must be registered as Apartment threaded. * An SSL connection may hang on close in Windows ME. See the Knowledge base article Q238934 for more information. A QFE for this problem is available at: http://support.microsoft.com/support/kb/articles/Q238/9/34.ASP * Connector properties set on the SoapClient30 object must be set after MSSoapInit or MSSoapInit2 are called but before any other methods are called. * The error "library not registered" has been seen when attempting to execute: Server.CreateObject("MSSOAP.SoapServer30") The cause of this error has been tracked down to the typelib registry key not giving the Everyone group read access. This is most likely the result of a prior installation of Crystal Reports 8.0. See the following knowledge base article for more information: http://support.microsoft.com/support/kb/articles/Q266/6/21.ASP * Samples are shipped as a separate download. Be sure to follow the instructions in the Samples\Default.htm page before using or building the sample applications. * Properties on the server side COM object are not supported by the high level API. Write a "wrapper" object that allows sets properties and calls methods in a single request. * The WSDL Generator will work on Windows NT, Windows 2000 and Windows XP only. * Client Certificates don't work on Windows 98 with the version of Wininet that comes with IE 5.01 but do work with IE 5.5. * Optional parameters are not supported in interfaces mapped to SOAP. Values must be provided for all parameters defined. * Windows NT 4.0 does not support the CHS:gb2312 or AR:iso8859-6 character set encodings. * Whenever possible, use unique SoapAction fields for each operation in your WSDL file. This is critical in document literal WSDL files because the SoapAction is used to determine which operation to call. * The Soap COM components don't work reliably if called from a Multi-Threaded Apartment. * While the Soap Toolkit 3.0 high level interfaces use normal

COM calls to expose objects through Soap, this DOES NOT mean that the Soap Toolkit is a general replacement for DCOM. Many DCOM features like lifetime-management, passing objects by reference and some COM datatypes don't map to the current Soap specification so these things aren't supported by the Soap Toolkit 3.0. * While the Soap Toolkit 3.0 MAY allow you to expose existing COM objects through SOAP, this is not true in all cases. Expect that wrapper objects and possibly custom mappers will be required to expose some existing objects. * The SOAP Toolkit 3.0 ISAPI listener IS NOT registered as the handler for WSDL files. YOU MUST MANUALLY REGISTER THIS HANDLER for every virtual directory used for a SOAP Toolkit 3.0 service. You can do this using the SOAPVDIR.CMD script or by performing following steps: 1) Right mouse click on virtual directory node in IIS manager 2) Go to properties 3) On the "Virtual Directory" tab, click the Configuration button 4) On the "Applications" tab, in the "Application Mappings" list select any existing mapping for the ".wsdl" extension and click "Remove" 5) Click "Add" 6) In the "Executable" edit box, enter: "c:\progra~1\common~1\mssoap\Binaries\SOAPIS30.dll" 7) In the "Extension" edit box, enter: ".wsdl" 8) Select the "Limit to" option and enter "GET, POST, HEAD" 9) Click "OK" to close the add dialog. 10) Click "OK" to close the application configuration dialog. 11) Click "OK" to close the properties dialog. * It is strongly recommend that a patch for CRYPT32.DLL be applied on Windows NT 4.0 platforms. The patch fixes a hang encountered when shutting down a process that has connected to a secure server using SSL. Please refer to the following URL for more information: http://support.microsoft.com/support/kb/articles/Q238/9/34.ASP * Out and in/out IAttachment parameters do not work with VBScript. * When running a SOAP Toolkit server in an AppCenter environment, you may want to change the AppCenter's "Affinity" configuration parameter to "None" instead of the default which uses the client IP address. This is necessary when using multiple SoapClient30 Objects on a single machine all sending messages to a single cluster (for example, when a "front end" ASP script sends requests to a backend service). * Uninstalling the 2.0 SOAP Toolkit removes all IIS mappings for the .wsdl extension, including mappings to the 3.0 ISAPI listener. If you uninstall the 2.0 SOAP Toolkit after installing the 3.0 SOAP Toolkit and configuring virtual directories to use the 3.0 SOAP Toolkit, you will have to reconfigure those virtual directories. * The ConnectTimeout HttpConnector30 property does not work on

Windows 98 and Windows ME. The effective connect timeout is always 23 seconds. See Knowledge Base article Q176420 for more information. * The ByteArrayAttachment30 object does not work with VBScript or Jscript. The scripting languages do not support arrays of any data type except variant. * In ASP applications, do not send requests to other ASP pages located in the same virtual directory. Doing so can lead to very poor performance and may possibly hang IIS under heavy load. This behavior is due to the fact that there are a finite number of worker threads (in the inetinfo.exe or dllhost.exe process) available to execute ASP pages. Instead, the target ASP page should be located in a different virtual directory and set to run in the "High (Isolated)" Application Protection configuration. * Each use of the WSDL <import> element or the schema <import> or <include> elements to import or include a document in a virtual directory configured to use the SOAP Toolkit's ISAPI listener uses one of the ISAPI listeners worker threads. If such imports or includes are nested, there may not be enough threads available and the IIS process (inetinfo.exe or dllhost.exe) may hang. This issue will be fixed for the final release of version 3.0 of the SOAP Toolkit. * On NT4 sever a service cannot send an attachments 4MB or larger in size. * The DimeComposer30.Initialize method parameters, par_tempFolder and par_maxSize are ignored. * WSDLGen does not support function and method names with DBCS characters or DLL files that have DBCS characters in their file or path names. * The DIME specifications referenced by the documentation are out of date. To locate the DIME specifications implemented by the SOAP Toolkit, goto http://msdn.microsoft.com/ and search for DIME. *************************************************************** 2.0 Installing the SOAP Toolkit 3.0 *************************************************************** You must have Windows Installer 2.0 installed in order to install the SOAP Toolkit 3.0. Download and install Windows installer from the location listed below for your platform: * Windows XP - Windows Installer 2.0 is already installed * Windows NT, Windows 2000: http://www.microsoft.com/downloads/release.asp?releaseid=32832 * Windows ME/9x: http://www.microsoft.com/downloads/release.asp?ReleaseID=32831 Double click on the soapsdk.msi file, or type "start soapsdk.msi"

at a command prompt to install the SOAP Toolkit. ----------------------2.1 System Requirements ----------------------The SOAP client and server objects are supported on the following platforms: * The SOAP client objects will run on Windows 98, Windows ME, Windows NT 4.0 Service Pack 6, Windows 2000 Service Pack 1. * The SOAP server objects will run on Windows XP, Windows 2000 or Windows NT 4.0 Service Pack 6. This release requires Internet Explorer 5.0 or 5.5. The SOAP Toolkit 2.0 installation will install MSXML 4.0. ----------------------2.2 Files Copied ----------------------The SOAP Toolkit installer package (MSI file) installs all the necessary files on your machine. The files needed to run SOAP toolkit service and client applications are copied to the folder C:\Program Files\Common Files\MSSoap and the files needed to develop SOAP toolkit applications are copied to the folder C:\Program Files\MSSoap. *************************************************************** 3.0 Questions and Comments *************************************************************** Please post questions and comments to the microsoft.public.xml.soapsdk newsgroup.