Implementation > EBICS > EBICS Server > EBICS Server administration > Processing

EBICS: Processing

Place the cursor over the Processing menu item to display a context menu with the following menu items:

Fetch transactions
Select this item to display the names of the order types and the handler type.
When you create a new order type or edit an existing order type you can select the handler type. Use the Standard option to set whether newly-created customers are assigned this order type automatically.
Some handler types only make sense with certain order types.

View the handler types available for fetch transactions

Handler	Order type	From-to query	Data import
One file per customer	Any	Yes	Yes
One file per user	Any	Yes	Yes
Public key for EBICS customers	HPB	No	No
EBICS bank parameters	HPD	No	No
HTD	HTD	No	No
HKD	HKD	No	No
One file for all customers	Any	No	Yes
Customer protocol	PTK	Yes	No
Payment Status Report (PSR)	PSR	Yes	No
Payment Status Report (PSR) per user	PSR	Yes	No
PSR with exit	PSR	Yes	No
Customer user PSR with exit	PSR	Yes	No
Account statements (MT940)	STA	Yes	Yes
Fetch public key	VPB	No	No
Avise (MT942)	VMK	No	Yes
Axway Generic Fetch Transaction	Any	Yes	Yes
Axway Verbose Fetch Transaction (identical to Axway Generic Fetch Transaction except that it produces more logs and therefore has reduced performance)	Any	Yes	Yes
Axway Database Fetch Handler	Any	Yes	Yes
Axway Verbose Database Fetch Handler (identical to Axway Database Fetch Handler except that it produces more logs and therefore has reduced performance)	Any	Yes	Yes
Customer protocol - PTK (with forwarding and merging)	PTK	Yes	No

In change mode, after you display fetch transaction search results, you can click the edit button of any fetch item to open an editing screen. This screen enables you to modify the following fetch transaction attributes:
- Name: Name of the transaction
- Standard: Select whether or not newly-created customers are assigned this order type automatically
- Handler: Select the handler type for the transaction
From this editing screen, click the Descriptions button to edit existing fetch transaction descriptions or add additional descriptions.
Configuring exits: To configure exits (Axway Generic Fetch Transaction handler file copy exit, PSR with exit handler file copy exit, and the test parameter exit), you must modify properties in the EBICS Server configuration.properties file.
See Modifying the EBICS Server configuration file
Send order type:
Select this item to display the following properties of order types:
- Name of the order type
- Description of the order type
- Response for setting up D files
- Number of required signatures
- Whether or not newly-created customers are assigned this order type automatically
- Handler type
- Post-processing
You can set these properties when you create an order type or when you edit an existing order type. Use the Standard option to set whether newly-created customers are assigned this order type automatically.
Some handler types only make sense with certain order types.

View internal provision table for send order types

Handler	Order type	Post-processing makes sense	Data import
Binary files	Any 8-bit	Yes	No
CCC (pain.001.001.02.con)	CCC	Yes	Yes
CCM (pain.001.001.02)	CCM	Yes	Yes
CCT (pain.001.001.02.grp)	CCT	Yes	Yes
CDC (pain.001.001.02.con)	CDC	Yes	Yes
CDD (pain.001.001.02.con)	CDD	Yes	Yes
CDM (pain.008.001.01)	CDM	Yes	Yes
DTAUS files	IZV, . . .	Yes	Yes
DTAZV files	AZV, . . .	Yes	No
Initialize keys	INI	No	No
Change key	PUB	No	No
Change password	PWA	No	No
Lock user	SPR	No	No
Text file	Any 7-bit	Yes	No
Customer encryption key	VPK	No	No

To view the attributes of any send order type, click Details, or, if you are in editing mode, click Edit to view and modify the attributes. For example, you may want to define the signature mode for this order type.

View attributes

Attribute	Description
Name	Name of the order type (3 characters)
Description	Manually entered description
D-Files	Response in setting up D files. Possible values: deny: D files are rejected process instantly: D-files are processed without any additional check release by distributed signature: Files are forward to the "distributed electronic signature" release manually: Files must be released manually by an administrator
Signature mode	Set the signature mode as specified by the CFONB. Possible values: Normal: EBICS T profile in France. Also for other countries. French – Single signature: EBICS TS profile in France with only one signature allowed. French – Optional co-signature: EBICS TS profile in France with either one or two signatures required. French – Mandatory co-signature: EBICS TS profile in France with two signatures required. Note: If EBICS TS profile is selected, DS allowed must be unchecked.
Signatures	Minimum required number of signatures for authorization. If you enter a zero value, files with an electronic signature must not be submitted.
DS allowed	Activate or deactivate distributed signatures. This box must be unchecked if EBICS TS profile is selected.
Active	You can deactivate an order type by unchecking this option. Inactive order types will not be shown and may not be selected in the customers’ order types tab.
Standard	Select this option if you want newly-created customers to be assigned this order type automatically.
Wait for feedback	Select this option if you to wait for feedback.
Handler	View or select the handler type for this send order type.
Postprocessing	Selection of post-processing for fully authorized orders.

Descriptions
Select this item to view a list of all descriptive text that has been added to send and fetch transactions.
You can edit the following details of a description.

View details

Item	Description
Name	Enter a name
Language	Select a language from the drop-down list of languages
Prefix	Send the message type prefix: send or fetch
Text	Edit the text that describes the transaction

Post-processing
Select this item to view a list of all configured post-processing chains.
Once a customer order has been fully authorized, it can be transferred to a post-processing chain. A chain is always identified by a unique name.
A processing chain consists of one or more processing steps. Every step receives inbound data, processes this data and forwards is to the next processing step, in modified form if necessary. The inbound data of the first processing step corresponds to the original file. In the detail view of a processing chain, the individual processing steps are listed in chronological order. You can change the order of the steps. Steps can be deleted, created anew and possibly configured as well.
For details of possible post-processing steps, see Post-processing steps
Periodical tasks
Select this item to configure regularly executed tasks. You can execute cleanup or archiving of old customer orders and delete provisional data and log entries.
Each existing scheduled task, the interface displays:
- Action: The name of the action
- Last run: The date the action was last executed
- Next run: The next programmed execution date
When you create or edit a periodical task, you complete the following fields:

View fields

Field	Description
Execution mode	Enables you to select the periodicity of the action: Day of week Execution hour Execution minute
Last run	Read only field indicates the last time the task was run.
Action	Specifies which action is to be performed: Clean up orders: Deletes and archives old customer order files. For each order, the original file, the signatures and all log entries are archived. See corresponding section below. After you clear an order the customer can create an order with an identical order type and order number. Clean up deliveries Clean up protocol
Clean up orders
Order older than	Together, these two attributes define how much time must have passed since the last customer action for an order before it can be cleared.
Time unit
Exported zip file	Orders are never just deleted. They must be exported at the same time. Here, you specify the name of a ZIP file into which the order data is to be exported. The file name may include substitutions of the form $(DATE format), whereby format must be a valid Java date format. For example, if C:\archive\CLEANUP-$(DATE yyyy-MMdd).zip is specified as the file name, a ZIP file named CLEANUP-2012-11-13.zip is generated in directory C:\archive on 13 November 2012.
Create directories	Select this option to automatically create directories required for writing.
EBICS transaction older than	Together, these two attributes define how much time must have passed since the last EBICS customer transaction for an order before it can be cleared.
Time unit
Incomplete order older than	Together, these two attributes define how much time must have passed since the last customer action for an order before it can be cleared.
Time unit
Clean up deliveries
Older than	Together, these two attributes define how much time must have passed since the last customer action with the delivery, before it can be cleared.
Time unit
Order type	Order type associated with the delivery.
Clean up protocols
Older than	Together, these two attributes define how much time must have passed since the last customer action using the protocol, before it can be cleared.
Time unit

Directories
If you provide external data to the customers, you must store the data in specified directories so that the EBICS Server can access it. The import rules define what happens with these files.
The Directories menu item enables you to set up and maintain import rules. You can edit existing import rules and create new ones.
When you create or edit a directory, you complete the following fields:

View fields

Field	Description
Directory	Specifies the directory to be searched for files to be imported.
Recurse
Filename pattern	Specifies a regular expression that is to be used to recognize files to be imported. For example, the expression ".*" means that every file in this directory is to be imported.
Order type	Specifies for which order type an imported file is to be provided. This can be an explicitly specified order type ("FTB") or an implicit type in the form of a number i. The order type is the result of the substitution of group number i of the regular expression. For example, "0" sets the order type automatically, if the file name is identical to the order type.
Scan interval (in sec.)	Specifies how often the directory is to be searched for new files. Before a file is imported, it must be found at least twice because it is only processed if it has not changed between two runs. After the successful import, the file is deleted from the directory.
Protocol destination	Indicates the path to the log file.
Send protocol on success	Option enables logs of successful transfers.
On error abort	Optionally, select to abort the directory search in the event of an error.
Last run	Indicates the last time that the directory was searched.
Last error	Description of the last error that occurred.
Supplier	Supply one file per customer The collected file is provided to exactly one customer. In the Customer ID field, enter a fixed customer ID, or a number whose value determines which group from the regular expression contains the customer ID. Enter: Customer ID Host ID
	Supply one file per user of a customer The collected file is provided to exactly one customer. In the Customer ID field, enter a fixed customer ID, or a number whose value determines which group from the regular expression contains the customer ID. Enter: Host ID Customer ID User ID
	One file for all customers Enter: Host ID
	MT940 Splitter The collected file must contain account statements. This file is split according to accounts (field 25). The parts are saved separately for each account. All customers who have STA authorizations for an account receive the corresponding statements during retrieval. Use the following settings: Check numbering: sort the statements by year, statement number and sheet number. Only consecutive statements are made available. Sheets with errors are written to the error file. Unknown accounts: If a statement contains unknown accounts, these can be ignored or provided (possibly with a warning output). If unknown but retrieved accounts are administered subsequently, the statements can be retrieved afterwards. Error file: If errors occur during the parsing of the input file or the check of the numbering, the incorrect data is written to this file.
	MT942 Splitter The collected file must contain transaction notes. This file is split according to accounts (field 25). The parts are saved separately for each account. All customers who have authorizations for the account statements of an account receive the corresponding statements during retrieval. Use the following settings: Append: If data is provided several times a day, is it concatenated, or does every file receive all transaction details of a day? Unknown accounts: If a note contains unknown accounts, they can be ignored or provided (possibly with a warning output). If unknown but retrieved accounts are administered subsequently, the advice notes can be retrieved afterwards. Error file: If errors occur during the parsing of the input file, the incorrect data is written to this file.
	Backend Feedback The collected file contains data for the further processing of a customer order in the back-end system. If this is an error message, the file content is written to the customer log of the customer in the form of ADDITIONAL INFORMATION. Use the following settings: Order-PK: Group from the regular expression of the file name that refers to the database key of the customer order. Generate header: Select this option to generate a header line with reference to the customer order in the additional information. Success pattern: This regular expression is applied to the file content to distinguish whether the feedback is positive or negative. Write in case of success: Select this option to write additional information into the customer log in case of success.
	Execute scripts Command: Enter the command line for executing the script Environment variables: Enter required environment variables for executing the script Mode: Enter the execution mode: No data Read file Modify file Work directory Temp directory