The following settings only apply to the event-driven Input Agents of type "AS2", "FTP" and "SSH", and to time-driven Input Agents "File" and "FTP".
Note that no job is created at all when the maximum size of a file (specified in the configuration file) is exceeded. The data is simply rejected and lost.
Profiles can also check the maximum size of an input file. However, this occurs after a job has already been created, and if the maximum size of a file is exceeded, this job fails with an error. However, a backup of the input file has already been created and the job can be restarted in the Control Center (the check will then be ignored). This allows the user to individually decide on a case-by-case basis how to deal with oversized input files.
Maximum size for messages and files
If this maximum value is defined, all received files whose size exceeds the maximum value are discarded. No job is created and these files are also not stored in the Unresolved area. This setting prevents the system from being overloaded with data from outside (e.g. denial-of-service attacks).
Following the parameter maxMessageSize in configuration file ./etc/startup.xml, which defines the maximum size of Messages and input files in kilobytes. If the maximum size is set to 0, no check will be performed.
Maximum size for messages and files on the DMZ Server
Parameter maxSize in configuration file ./etc/startup.xml (of the DMZ server) can be used to already limit the file size (in kilobytes) on the DMZ server. If the maximum size is set to 0, no check will be performed.
Input files that exceed the specified size are not transferred from the DMZ server to the inner Integration Server. This is primarily a security measure against the system getting flooded with unwanted data.