Implementation > EBICS > EBICS Server > EBICS Server administration > Post processing steps

Post-processing steps

Bulk processing

The Bulk processing step blocks the post-processing of all orders of a certain order type until a specified time is reached. Then all orders that have been blocked are concatenated into a collective file and transferred to the subsequent processing steps. If the order collector is not the first processing step of a chain, the preceding steps must not have made any changes to the data. For each processing step, only one order collector may be defined.

Bulk processing has a single attribute that takes a value:

Start Time(s): Specifies at what time (HH:MM) blocked orders are processed. To enter multiple start times, separate the different start times with commas.

Execute script

The Execute script step executes a system command. It transfers the input data to the command if required. The definition of the command and optional environment variables can contain the following types of placeholder:

$(ORDER_TYPE) Order type
$(CHR value) Character with the specified decimal value
$(DATE format) Current time in the Format Java format
$(FILE) Absolute path to the data file, if a data transfer by file is requested
$(HOSTID) Host ID of the bank. This placeholder is not available if one of the preceding processing steps was bulk processing
$(CUSTOMER) Customer ID. This placeholder is not available if one of the preceding processing steps was bulk processing
$(ORDER_NUMBER) Order number. This placeholder is not available if one of the preceding processing steps was bulk processing
$(ORDER_PK) Database key of the order. This placeholder is not available if one of the preceding processing steps was bulk processing
$(FILE_TYPE) D if the order file was sent without a signature, 0 if the order file was signed electronically and X if one of the preceding processing steps was bulk processing
$(RESTART_POSTPROCESSING) TRUE if the post-processing is manually restarted, otherwise FALSE

If the script ends with a return value that does not equal zero, an error is logged and the processing chain is terminated.

You can specify the following properties of execute script:

Command: The command to be executed including optional parameters. Substitutions are made as described above.
Environment Variables: Define additional environment variables for the command in the form VAR= value. The values can contain substitutions of the above-described form.
Data Transfer: Specifies the form in which the script expects the data. Possible values are:
- Not required: Data is not transferred to the script but sent to the next processing step without any changes
- File transfer (read only): A temporary file is generated. The name of this file can be transferred to the script using placeholder $(FILE). It is not assumed that the script modifies the file.
- File transfer (modifying): A temporary file is generated. The name of this file can be transferred to the script using placeholder $(FILE). After completing the script, the file, changed or not, is transferred to the next processing step.
- Standard input (without output): The input data is forwarded unchanged to the standard input of the script and on to the next processing step.
- Standard input and output: The input data is transferred to the standard input of the script. The standard output of the script is forwarded to the next processing step.
Working Directory: Specifies a working directory for the script
Data Directory: Specifies a directory for temporary files
Line Break: Converts line breaks to a defined format. You can set whether line breaks are made in Windows or UNIX format and whether a missing line break is appended to the end of the file.
File Export: Writes the input data into a file. The file name may contain the placeholders for script execution.
File Export options:
- Output File: File name, optionally with placeholders
- Create Directories: Defines whether required directories are created automatically
- Overwrite: Defines whether already existing files may be overwritten. If not, an error is logged and the processing chain is terminated.
Signature Export: Ignores the input data and writes the signature data to the following plug-in.
Signature Export options:
- Format: This test is sent to the following plug-in for each signature including substitutions. In addition to the substitutions mentioned for script execution, the following placeholders are available:
  - $(RAW) Content of the signature file (512 bytes)
  - $(USER) BCS participant ID
- Technical Signatures Only: Determines whether or not transport signatures are to be exported as well