Step 5: Checking the EBICS Server directory structure (JBoss)

Deployment: JBoss EBICS Server

On JBoss, you do not have to perform any actions to deploy the application. The JBoss Server automatically deploys the application when you start the Server.

Directory structure

During installation, the installer creates the following sub-directories in the <EBICS Server installation directory>.

By default, the <EBICS Server installation directory> is:
<your home directory>/Axway/EbicsServer.

Directory Description
data

Various data used by PassPort, Sentinel and the Supplier
data/conf/passport Setting files for PassPort (*CSD*) – to be imported in PassPort
data/conf/sentinel Tracked Object definition for the configuration of Sentinel (*.xml) – to be imported in Sentinel (using Composer)
data/sentinel

Sentinel working directory – overflow.dat file
data/supplier
  • in: files to be handled by the Supplier service
  • failed: files that could not be handled by the Supplier service
  • success: files that have been handled by the Supplier service
database

Depending on the installed database (Oracle, MySQL):

  • scripts: Scripts used for the creation of the database tables
  • logs: Logs generated during installation if the option Generate and launch scripts was chosen during installation (session.log, create_tables.log, ...)
Encryptor

Tool for encrypting/decrypting passwords in base 64 or AES
Injector

Tool used for configuring EBICS Server (Bank, Customer, User, Account, ...)
Supplier

Tool used for the supply of files to be collected by Bank clients (using Fetch requests)
purge

Purge tool for the EBICS Server environment
Install

Gateway configuration files to use the post-processing mode:

  • The samples subdirectory contains back-office sample launch scripts for FTP.
  • The server subdirectory contains Gateway and Transfer CFT settings (objects).

These MFT files enable you to trigger the link between Gateway and EBICS Server in both directions (Fetch/Send).
Send

Post-processing Gateway and Messaging scripts:

  • The files subdirectory contains backup for files before Send
  • The scripts subdirectory contains script used between EBICS Client and Gateway for Fetch transfers
  • The tmp subdirectory contains execution logs
FetchImport Deprecated
JBossServer

JBoss Server – main directories:

  • Bin: Start directory
  • DataDir: Working directory for Send
  • DataStore: Working directory for Fetch
JBossServer/server/bankrechner

Root directory of the EBICS Server application deployed on JBoss
JBossServer/server/bankrechner/conf

Configuration files, including:

  • wrapper.conf file. This file contains configuration data for JAVA VM parameters, dataDir, dataStore. Refer to the table below for details.
  • configuration.properties file – to manage connections with other Axway products for tracking (Sentinel, Gateway) and storing certificates (PassPort).

See Modifying the EBICS Server configuration file .
JBossServer/server/bankrechner/deploy

This directory contains:

  • Web application server: bankrechner.ear (installed by the Axway Installer)
  • Configuration file for database configuration: bankrechner-ds.xml (parameters defined in the installer)
  • Other configuration files (for Web, EJB3, ...)
synInstall

For the management of EBICS Server by the Axway Installer (Update, ….)

config file

The <EBICS Server installation directory> also contains the config file. This file is used for configuring Send scripts between EBICS Client and Gateway for Fetch transfers.

wrapper.conf file

The wrapper.conf file located in <EBICS Server installation directory>/JBossServer/server/bankrechner/conf contains three variables. The installer assigns the values during installation.

Variable Value Description
bankrechner.dataDir <EBICS Server installation directory>/JBossServer/dataDir Path of the directory that contains the persistent data of the EBICS Server
dataStorePath <EBICS Server installation directory>/JBossServer/dataStore Path of the repository
configurationPath <EBICS Server installation directory>/ JBossServer/server/bankrechner/conf/configuration.properties Path of the configuration.properties file
de.businesslogics.bankrechner.bank.ebicsKeyMode SELF_SIGNED_CERTIFICATE or PLAIN_KEY or PKCS12_IMPORT Default security format to be used for banks
de.businesslogics.bankrechner.bank.ebicsKeyLength length in bits (min. 1024) Default key length to be used for key generation (default value of the key length box in bank creation screen). With certificates, any value under 2048 is rounded up to 2048

Related topics

Installing EBICS Server on JBoss: general implementation procedure