EBICS Configuration

The following sections explain how to configure an EBICS host from scratch using the generic EBICS preconfigured host. Only use this host if Cleo does not have a preconfigured host for the banking partner being connected to. Visit www.cleo.com/products/lexihubs.asp for a list of available preconfigured hosts.

Obtain the following parameters from your bank server:
- URL, of the form https://remote-host:port/resource-path?optional-parameters .
- The server's Host ID.
- EBICS version supported (2.4 or 2.5).
- ES (electronic signature) version supported (A005 or A006).
Provide the following parameters to your bank server:
- Your Partner ID
- Your User ID
Click the Templates tab in the tree pane.
If necessary, expand the Hosts tree in the Templates tab to find the host you want to use.
Right-click the host and select Clone and Activate.
The entire pre-configured host branch (including a mailbox and actions) is copied and activated, the Active tab is selected in the tree pane, and the new active host is selected in the tree. If necessary, you can append the new active host alias with a number to make it unique.
Note: The original pre-configured host remains in the pre-configured tree.
Enter host-level configuration information.
1. Click the new host in the tree pane.
2. Enter host-level configuration information on the tabs in the content pane. See EBICS Host.
3. Click Apply to save your work.
Enter mailbox-level configuration information.
1. Click the mailbox under your host in the tree pane.
2. Enter mailbox-level configuration information on the tabs in the content pane. See EBICS Mailbox.
3. Click Apply to save your work.
Enter action-level configuration information.
1. Click an existing mailbox action to display its configuration tabs. Alternatively, right-click the mailbox and select New Action.
2. Edit action information on the tabs in the content pane. See EBICS Action .
3. Click Apply to save your work.
Click Apply to save your work.

Important: If you leave any of these panels without clicking Apply, your work will not be saved. You can configure the native UI to prompt to you click Apply when changes are made. See Other system options. However, in the web UI, this is not valid. In the web UI, if you make updates to a host and then click a part of the product not related to a host, for example any of the buttons in the banner, the product will not prompt you to click Apply and your updates will not be saved.