Prerequisite Configuration on Sterling B2B Integrator
Before using the EBICS Client, you must configure Sterling B2B Integrator.
Basic Configuration
To begin, configure the following:
- Check in the public keys shared by the bank to the Certificate Authority (CA) store or create a self-signed certificate with SHA256 hash algorithm.
- Create an identity record for the partner, indicating the partner as the base identity.
- Create a user account.
- Configure an adapter that enables you to send and receive files and invokes the EBClientOrderPreProcess business process. For example, configure a File System Adapter to invoke the EBClientOrderPreProcess business process. EBClientOrderPreProcess business process is used to validate the payload received from a technical user and to extract the folder containing the payload or metadata and post the payload data to appropriate mailboxes.
- Configure the following mail boxes and associate them with each user:
- EBClientOrderMetadata (preconfigured)
- Download (Inbox)
- Upload (Outbox)
- Verify that the EBClientMailboxArrivedMessage business process is associated with the EBClientOrderMetadata Mailbox. The automatic routing rule triggers the business process to perform automated functions, such as notifying an interested party about an incoming message in the mailbox.
- Ensure that the MailboxEvaluateAllAutomaticRulesSubMin Schedule is enabled. The schedule periodically evaluates the routing rule to ensure proper functioning of the routing rule.
File System Space Requirements for FDL Requests
Because the FDL order type uses the file system to store the payload, it is important to plan file system storage accordingly. A large FDL payload requires about 6 times as much file space as the payload size itself. For example, a 5 GB payload requires over 30 GB of file space in Sterling B2B Integrator to process the request.