About EBICS integration with Sterling File Gateway

Sterling File Gateway is required in order to route files to or from EBICS Partners/Subscribers. After you install Sterling B2B Integrator with the EBICS module, you must separately install Sterling File Gateway, and perform an additional procedure to set up integration.

Sterling File Gateway is an application for transferring files between partners using different protocols, file naming conventions, and file formats.Sterling File Gateway supports movement of large and high-volume file transfers, with visibility of file movement in a process-oriented and highly-scalable framework that alleviates file transfer challenges, such as protocol and file brokering, automation, and data security.

When handling EBICS transactions, Sterling File Gateway uses templates to describe how each transaction is interpreted to determine how and where it should be delivered and provides visibility into the details of the transfers for auditing and troubleshooting.

Files move between the EBICS server and Sterling File Gateway using shared partners and mailboxes. The shared mailboxes are created when EBICS partners are created. Sterling File Gateway then uses the mailboxes for transferring files to or from EBICS partners.

For inbound scenarios, a partner uses an EBICS client to perform an EBICS order file upload (FUL) to the Sterling B2B Integrator EBICS Server, which unpackages the payload and deposits it into a shared mailbox (generally of the structure /User/Partner/Inbox). Sterling File Gateway is configured to pick up the file from that mailbox, perform any needed processing, and ultimately deliver the file to a consumer mailbox.

In the outbound scenario, a file (or files) is available in an EBICS partner shared mailbox (generally of the structure /User/Partner/Outbox). The partner uses an EBICS client to perform an EBICS order file download (FDL) from the Sterling B2B Integrator EBICS Server, which packages the payload and makes available to the EBICS client.

To ensure appropriate v operation for EBICS inbound and outbound transfer scenarios, routing channel templates and routing channels require specific configurations. Routing channel templates used in EBICS scenarios must include the configuration of provisioning facts and routing channels using those templates must include the specification of values for provisioning facts. Provisioning facts are optional elements in an RCT that provide a controlled way to customize particular routing channels within the context of a particular routing channel template by requiring user input during routing channel creation.

Operators can search for EBICS-specific activity in the Sterling File Gateway application and view an EBICS-centric information display. An individual activity can be selected to retrieve additional detail about the EBICS transaction and related messages.

Alternatively, operators can search for general activity and view a file-centric information display that includes routes and deliveries that resulted from EBICS activity.

Operators can perform basic and advanced searches for activity initiated with the EBICS protocol.

Operators can subscribe for notifications of specified EBICS events. When a subscribed event occurs, the subscriber receives an email notification.