/
[WINDOWS 2.0] Maximum message size for webservices

[WINDOWS 2.0] Maximum message size for webservices

To enable the biggest possible message size for webservices (e.g. to transfer large/multiple attachments), maintain the following Http Binding settings in the Message Broker configuration file:

 

<basicHttpBinding>

        <binding name="E4Cbinding" maxBufferPoolSize="2147483647"

          maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">

          <security mode="TransportCredentialOnly">

            <transport clientCredentialType="Basic" realm="E4C Message Broker Component" />

          </security>

          <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647"

            maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647" />

        </binding>

      </basicHttpBinding>

 

Please don’t change the security settings: 

<security mode="TransportCredentialOnly">

<transport clientCredentialType="Basic" realm="E4C Message Broker Component" />

</security>

SAP doesn’t recommend sending messages bigger than 20 MB.

          

 

Related content

[WINDOWS 2.0] Application config file
[WINDOWS 2.0] Application config file
More like this
[WINDOWS 2.0] URL namespace reservation
[WINDOWS 2.0] URL namespace reservation
Read with this
Attachment size configuration
Attachment size configuration
More like this
Message Broker Configuration file mapping - XML file to YAML file
Message Broker Configuration file mapping - XML file to YAML file
Read with this
General attachment configuration
General attachment configuration
More like this
FSM Message Broker installation
FSM Message Broker installation
Read with this

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.