Settings


(1) Priority: Sets the priority of the jobs of this profile. Note: Changes cannot be saved if (5) is set.

(2) Log Pool: The logging of a profile job can take place in a separate Log Pool. See page "Log Pool Aliases".

(3) Encoding: The encoding of the data to be read in. Note: The default value for new profiles can be set in the configuration file ./etc/admin/datawizard/defaults.properties with the entry "profile.<client ID>.encoding=<encoding>". For example, "profile.-1.encoding=UTF-8" for the default client and the encoding "UTF-8".

(4) No auto start of defecrive jobs on restart: If this checkbox is set, the crashed jobs of this job cannot be restarted.

(5) Profile may only run in one instance (strict serial processing): 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" 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.

(6) No processing of files already treated: 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.

(7) Keep input information: If this checkbox is set, certain information is stored in system variables (VAR_MAILSUBJECT, VAR_SENDER, VAR_SYS_MAIL_RECIPIENTS and VAR_TIMESTAMP).

(8) Data comes in compressed: 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", 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.

(9) Valid from/till: The validity period of the profile. Only valid and active profiles can receive data.

(10) Replaces profile: It may be necessary for a particular profile to be automatically replaced by another profile or a new version of the same profile at a predetermined time. We want the new profile to assume the name and the ID of the old profile and thus also inherit the backup data of the old profile. Proceed as follows.

  • Create the new profile.

  • Set the beginning of the validity of the new profile to the predetermined time.

  • Set the name of the old profile that is to be replaced in input field "Replaces profile" of the new profile. Save and activate the new profile. The user you are using has to have administrator rights.

If the following situation occurs, the old profile is replaced by the new one.

  • The validity period of the new profile has started.

  • Both profiles are active and not suspended.

With the replacement, the new profile gets the name and ID of the old one. It thereby takes the place of the old profile. The replaced, old profile becomes inactive and gets the name "DEPRECATED<timestamp>_<old name>" and the previous ID of the new profile. The input field "Replaces profile" in the new profile will now be empty. The following line will be added to the description field and the change history field of the new profile. You will also find this entry on page "General Messages" of the Control Center.

Switched from <old name> to <new name> by System at <timestamp>.

In the following error cases, there will be no replacement.

  • If input field "Replaces profile" refers to itself (the same profile that contains the input field).

  • If the profile to be replaced does not exist (anymore).