SOAP Registry Settings (Windows Embedded CE 6.0)
1/6/2010
The registry stores information necessary to configure the system for applications and hardware devices. The registry also contains information that the operating system continually references during operation.
The HKEY_LOCAL_MACHINE\COMM\HTTPD\ScriptMap registry key configures the ISAPI handler, which is different from the Windows SOAP applications for the desktop. The ScriptMap contains name and value pairs that specify the file extensions and the scripts.
The following example shows a name and value pair:
[HKEY_LOCAL_MACHINE\COMM\HTTPD\ScriptMap]
".wsdl"="\\windows\\soapisap.dll"
".wsml"="\\windows\\soapisap.dll"
Note
Windows Embedded CE does not support wildcards in file extension names. You cannot map *.dll to an ISAPI dll.
The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSOAP\SOAPISAP registry key also defines the configuration variables for SOAP messages.
Note
The default registry values vary depending on which Catalog items are included in your OS design. For more information, see Default Registry Settings.
The following table shows the named values.
Value : type | Description |
---|---|
MaxPostSize : REG_DWORD |
Default setting is 100, in kilobytes Maximum size, in kilobytes, of the SOAP message that you can POST to the ISAPI handler.
Security Note:
While this setting helps prevent hackers from tying up your service by posting extremely large messages, you may need to increase the default size if your service accepts large SOAP messages.
|
NumThreads : REG_DWORD |
Default setting is 3. If this value is not present in the registry, the ISAPI handler uses 3. In most cases, the default value provides the best performance. You may try increasing this number if you are getting a lot of messages queued for your service. |
ObjCachedPerThread : REG_DWORD |
Default setting is 5. On the first call, the ISAPI listener loads the WSDL and WSML files, and keeps them cached for performance. Generally, this should be the number of WSDL files you have on your server. |