General (General Data)
(1) The version number of the profile. A new version is created every time you click on button Save & backup & close. This also creates a backup that can be imported on page Backup/Limits.
(2) The validity period of the profile. Only valid and active profiles can receive data. See also section Profile Suspensions.
(3) See section Time-controlled Replacement of a Profile.
(4) Sets the priority of the jobs of this profile. See page Thread Queues. Note: Changes cannot be saved if (8) is set.
(5) The logging of a profile job can take place in a separate Log Pool. See page Log Pool Aliases.
(6) The encoding of the data to be read in.
(7) If this checkbox is set, the crashed jobs of this job cannot be restarted.
(8) Depending on the Input Agent, it is possible that several jobs get processed in parallel for a profile. By setting this checkbox this can be prevented. The jobs are then processed sequentially in the order of their generation. Attention: For the Input Agents HTTP(S) and Message (with option synchronous), the external client waits for a response and therefore a delay of the job, which is necessary to force a strict sequence, would lead to instability, disturbances or timeouts. For that reason, the set checkbox will be ineffective for those cases.
(9) If this checkbox is set, the Comm Log service checks whether a received file has already been processed by checking the ID. If there is no ID, the filename is checked instead. AS2, Mail and X.400 know a message ID, (S)FTP(S) only file names, OFTP has a self-generated ID based on partner ID, file name, date and file counter. This option is only effective if a partner channel is used and the option Use Comm Log is active there.
(10) If this checkbox is set, certain information is stored in system variables. See VAR_MAILSUBJECT, VAR_SENDER, VAR_SYS_MAIL_RECIPIENTS and VAR_TIMESTAMP.
(11) Indicates whether the data is delivered in an archive. In this case, the files are extracted from the archive and passed as individual files to the profile. Each of the files extracted from the archive is processed in a separate job. The processing is done sequentially (with the order from the archive) in the same thread. All jobs receive the name of the archive file in the system variable VAR_SYS_ARCHIVE_NAME (see also VAR_ORIGINATOR_JOBNR, VAR_SYS_ARCHENTRY_PATH and VAR_SYS_LAST_IN_ARCHIVE). In Input Agent HTTP(S), archives containing several files can only be processed if option Send response by fixed value is active.
Attention: The input file must have a file extension (e.g. .zip or .pdf). The specific extension does not matter, there only has to be one, otherwise, the file is not recognised as packed and therefore not unpacked.