EBICS Client Architecture
Understanding the EBICS Client architecture will help you when using EBICS Client in Sterling B2B Integrator.
- Creating and managing trading partner
- Managing digital certificates
- Creating and managing mailboxes
- Creating users
- Running services and adapters
- Scheduling business processes
The following sections describe the components of EBICS Client architecture.
A subscriber uses EBICS Client to perform bank transactions. The subscriber or user communicates with the EBICS Client application using the HTTP protocol to send and receive messages.
EBICS Client Application
- File format
- User permissions
- Order submission
- Pending tasks
- Bank key validation
Sterling B2B Integrator and EBICS Client Schema
- Native Sterling B2B Integrator data in Sterling B2B Integrator schema tables.
- EBICS Client data in EBICS schema tables.
Sterling B2B Integrator Platform
The Sterling B2B Integrator platform on which the EBICS Client is deployed.
- The EBClientOrderMetadata mailbox is a common mailbox associated to all users. OrderMetadata associated with a payload is posted in the EBClientOrderMetadata mailbox for processing the payload submitted by a technical or non-technical user.
- Download (Inbox)
- The Download mailbox is used for posting downloaded response in case of HEV order type and unpacked data in case of download orders.
- Upload (Outbox)
- The Upload mailbox is used for posting the payloads.
A Sterling B2B Integrator adapter that can trigger the EBClientOrderPreProcess business process is used to submit orders automatically from the back-end.
EBICS Banking Server
The EBICS Banking Server is installed in a bank. EBICS Client communicates with the EBICS Banking Server application using the HTTP or HTTPS protocol to send and receive information about users, trading partners, digital certificates, order data, file formats, and order types. For more information about EBICS Banking Server, see the Sterling B2B Integrator EBICS Banking Server documentation.