Unable to load files larger than 300 KB when using SOAP

Answer

To fix this problem, you must:

1. Specify MaxClientRequestBuffer for IIS.
2. Increase the file size allocation for SOAPISAP.
3. Increase the file size allocation for the DDMLibrary.wsml
4. Restart the IIS service for the changes to take effect.

1) Specifying MaxClientRequestBuffer
The MaxClientRequestBuffer registry value was added to IIS as a security measure, so that the maximum size of the request line and header fields could be set by the IIS administrator The purpose of this option is to reduce the likelihood of an attack caused by requests containing large amounts of data in the request line or headers.

Increasing file size allocations in IIS 4 and 5
In IIS 4.0, the default maximum size of request line and header fields is 2 MB.
In IIS 5.0, this is reduced to 128 KB.
In IIS 5.0 with Windows® 2000 Service Pack 4 installed, this is reduced to 16 KB.

To change the maximum size of a URL request, complete the following steps to add the MaxClientRequestBuffer registry value:

1. Run the Registry Editor (regedit.exe).
2. Locate the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters
3. Click Edit > Add Value and add the following registry value:
   Value Name: MaxClientRequestBuffer
   Data Type: REG_DWORD
4. In the Data text box, type the number of bytes for the maximum URL request size 16 KB for Windows 2000 and 2003

Decimal: 16384
Hexadecimal: 4000

See Microsoft Knowledge Base article 260694 for more information.

2) Increase the file size allocation of SOAPISAP MaxPostSize - This setting directly affects the maximum size of the file that you can load. While this setting helps keep hackers from tying up your service by posting extremely large messages, you may need to increase the default size (100 KB) if your trying to load large files with SOAP.
To increase the file size allocation for SOAPISAP:

1. Locate the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSOAP\30\SOAPISAP
   REG_DWORD MaxPostSize
2. The MaxPostSize value is in bytes, with a default value of 100 KB:
   Decimal: 102400
   Hexadecimal: 19000
3. Change the value for this registry setting to the largest file size your users will be loading, for example 50 MB:
   Decimal: 52428800
   Hexadecimal: 3200000

3) Increase the file size allocation of the DDMLibrary.wsml (for FP2 or later also edit the DDMLibraryClient.wsml)
The WSML file is located in the \\Program Files\IBM\DB2 Document Manager\soap by default.

1. Modify the file with a Text editor like Notepad.exe
2. Find this section of the WSML file

 <servicemapping name='DDMCache' temporaryAttachmentFolder='%TEMP%' maximumAttachmentSizeMB='50' xmlns:dime='http://schemas.xmlsoap.org/ws/2002/04/dime/wsdl/'&gt;
  <service name='DDMCache'>.

By default the attachment size is 50 MB.
Note this is a whole value for MB (50, 75, 100) not bytes.
3. Set the maximumAttachmentSizeMB to match the SOAPISAP value in section 2 above.

4) Restart the IIS and WWW windows services

1. Go to Start - Programs - Control Panel - Administrative Tools - Services
2. Stop and Start the World Wide Web Publishing Service
3. Stop and Start the IIS Admin Service