...
In the newer Message Broker version, property MaxRequestBodySize defines the maximum size of http request the web service will accept. If not provided, .NET default is used, which is 30000000 (around 28 MB). If MaxRequestBodySize is set to 0, no limit is applied, this is the recommended setting for attachments. It is customized in the application configuration file: [WINDOWS 3.X] Application config file
Linux 3.X
Similar to the Windows 3.X version of Message Broker, property MaxRequestBodySize defines the maximum size of http request the web service will accept. If not provided, .NET default is used, which is 30000000 (around 28 MB). If MaxRequestBodySize is set to 0, no limit is applied, this is the recommended setting for attachments. It is customized in the application configuration file: [LINUX 3.X] Application config file
...
FSM Cloud Connector, transaction /PACG/ECM_CUST_ATTA, node General Attachment configuration, field MaxAttSize
...
The maximum attachment size allowed in FSM Cloud Connector should never be lower than the maximum attachment size set in FSM company settings. This is crucial for the older FSM Cloud Connector versionversions older than add-on 200 service pack 3, where generic idocs for attachments (sent to FSM after adding an attachment in FSM) are heavier and could be blocked by FSM Cloud Connector - as a result, the attachments could not be confirmed correctly. In the newer FSM Cloud Connector version, generic idocs for attachments are significantly lighter than the attachments themselves, however it is still recommended to align the maximum attachment size set in FSM Cloud Connector with the one allowed in the FSM company settings.