Attachment size configuration
- proaxia
Attachment size configuration is necessary for proper inbound and outbound attachment handling. Allowed attachment (or message in general) size should be adjusted in:
Example recommended values:
Customizing | Recommended value |
|---|---|
FSM company settings (CompanySettings.MaxAttachmentSize) | 20,971,520 Bytes (= 20 MB) |
Message Broker configuration file | Maximum. For Windows 2.0 - see: [WINDOWS 2.0] Maximum message size for webservices, for Windows 3.0/Linux - set value '0' |
Transporter settings (TransporterSettings.TransferDocumentSize) | The new transporter version (Message Broker version 6.5.0 and higher) - 1000, the older version - 20 |
FSM Cloud Connector (/PACG/ECM_CUST_ATTA) | Not lower than what is set in FSM Company setting CompanySettings.MaxAttachmentSize |
FSM company settings
Use the FSM company setting CompanySettings.MaxAttachmentSize to specify the maximum allowed size of attachments added in SAP FSM (e.g. the mobile app). It is recommended that the allowed attachments size don’t exceed 20 MB.
Message Broker configuration file
Windows 2.X
To adjust the allowed message size for webservices (e.g. to transfer large/multiple attachments), maintain the following Http Binding settings in the Message Broker configuration file. The maximum size is recommended:
[WINDOWS 2.0] Maximum message size for webservices
Windows 3.X
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: 3.X - Message Broker 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 filearchived
Transporter settings in FSM company settings
The FSM company settings TransporterSettings.TransferDocumentSize is used to specify the allowed number of messages in one package. The entered value can be bigger in the newer transporter version, because apart from the number of messages, also the overall size is taken into consideration (heavy messages such as attachments are counted as more). For the older transporter version, value ‘20’ is recommended, for the newer (Message Broker version 6.5.0 and higher) - up to ‘1000’.
FSM Cloud Connector, transaction /PACG/ECM_CUST_ATTA, node General Attachment configuration, field MaxAttSize
Use this customizing to not allow sending attachments bigger than the specified size (in bytes) from SAP ECC/S4 to SAP FSM. If no value is entered, the value of 5242880 bytes (5.24 MB) will be used.
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 FSM Cloud Connector versions 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.
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.