101 - 120 of 1373 results
UpdatedSeptember 26, 2019 12:16 pm
Publication: EBICS Gateway 3.3.0 Administrator Guide
When you call up the EBICS Gateway administration URL in a web browser, it opens a login dialog screen. Enter your user name and password. This information is securely transferred to the EBICS Gateway.
EBICS Gateway runs on an application server.
If you provide external data to the customers, you must store the data in specified directories so that EBICS Gateway can access it. The import rules define what happens with these files.
Select Processing > Fetch Transactions to display the names of the order types and the handler type.
The following sections explain how to use EBICS Gateway and describe the UI menu items.
An Account object represents an account that can be managed in EBICS Gateway.
A Bank object represents a bank or component service of a bank (for example, a department, branch, agency, or filial).
The Customer object represents a customer who performs transactions with a Bank.
The Files menu item enables you to search for records of transfers that are in progress or have been completed by a customer. A record for every correctly-started transfer appears on this screen.
The Protocols menu item enables you view server log entries that are generated for every action in EBICS Gateway. You can search and filter log entry displays using the following input criteria:
Select Processing > Periodical tasks to configure regularly executed tasks. You can execute cleanup or archiving of old customer orders and delete provisional data and log entries.
Select Processing > Post processing to view a list of all configured post-processing chains.
Select Processing > Send Transactions to display the following properties of order types:Name of the order typeDescription of the order typeResponse for setting up D filesNumber of required signaturesWhether or not newly-created customers are assigned this order type automaticallyHandler typePost-processing
The standalone embedded EBICS Gateway is an application that runs on WildFly. This section describes how to configure WildFly to run as a Windows service.
This section provides a high-level workflow of the steps required to create an EBICS configuration.
Select the Handler to be used, or accept the default "One file per Customer".
A supplier scans a directory and then prepares any files that are found so that the User can fetch the files or part of the files.
The Change Processes menu item enables you to view all change operations executed by administrative users on EBICS Gateway. You can filter the operations by user. You also have the option of displaying internal system modifications.