EBICS Banking Server: Specific Recommendations

Edit online

After you tune your Sterling B2B Integrator installation, you can tune the EBICS Banking Server.

The EBICS Banking Server is installed on an instance of Sterling B2B Integrator, and shares many of the resources with the latter.

You should, therefore, tune your Sterling B2B Integrator installation first, and then perform the EBICS Banking Server-specific tuning. Be aware that the changes you make to the EBICS Banking Server can also affect the performance of Sterling B2B Integrator.

The following table describes some of the key parameters that must be configured to optimize the EBICS Banking Server's performance:

Recommendation Comments

Allocation of additional threads to the HTTP Server Adapter
You can allocate additional threads to the HTTP Server adapter when the rate of concurrent requests to the EBICS Banking Server is moderately high. Complete the following steps to allocate additional threads to the HTTP Server adapter:
  1. Modify the numOfmaxThread parameter in the http.properties.in file by setting numOfmaxThread to four times the number of processor cores on the system the HTTP Server Adapter is running on. For more information about calculating the settings to tune the performance of your system, refer to the topic View and Restore Performance Configuration Settings.
  2. Run the setupfiles.sh (setupfiles.cmd for Windows) script to apply the changes.

Reduction of the disk I/O amount
In order to reduce the amount of disk I/O on the system, change the persistence of the following EBICS business processes to Error Only:
  • handleEBICSRequest
  • EBICSOrderAuthorisationProcessing
  • EBICSOrderProcessing

Storage size

 The database space required to store the files processed by the EBICS Banking Server is approximately 2.5 times the size of the transacted files. For more information about managing databases in Sterling B2B Integrator, refer to Database management for Sterling B2B Integrator.

Purge documents

The document lifespan in an EBICS transaction is set to ten years. As a result, the business processes associated with the documents remain in the live system databases, and may occupy a large memory and slow down the performance of the system.

The Index Business Process service scans the live systems, and flags the records that have reached their purge eligibility date and time. To reset the document lifespan, schedule the Index Business Process to run every ten minutes. The Index Business Process resets the lifespan after you delete the messages from the mailbox.

For more information about implementing and configuring the Index Business Process service and scheduled purge, refer to Index Business Process Service and Purge Service documentation respectively in the online documentation library.