SEEBURGER Connectors:
Information and Resources

Each SEEBURGER Connector

• Covers a specific integration need, or the integration of a specific system or service interface (e.g. Azure File Storage, Salesforce, SAP, etc.)
• Can support one or more functions of one interface
• Is based on generic BIS adapters and standard solutions (BIS EAI/API solutions)
• Includes added value ranging from expert documentation on how to address integration challenge with standard BIS functionality, to a ready-to-run SEEBURGER Connector artefact
• Includes all necessary license modules (limited to the specific scenario) and information (including expert documentation) to address an integration scenario

SEEBURGER BIS Adapters and SEEBURGER Connectors: What is the difference?

SEEBURGER Adapter
An adapter is a generic SEEBURGER BIS module which can be used for multiple connectivity purposes.
Examples: REST adapter, OFTP2 adapter, EDIFACT adapter, SAP tRFC adapter, WebServices adapter.

SEEBURGER Connector
A connector is a SEEBURGER BIS component which is specific to an integration or technology. It may make use of serval adapters, and is used for a defined connectivity purpose. Connectors often come with content (configuration data, mappings etc.) wich serve to minimize implementation efforts.
Examples: BIS Microsoft Dynamics AX connextor, Google Cloud Storage connector, Microsoft Azure File Storage connector, SAP Ariba connector.

In alignment with the process for SEEBURGER BIS and its modules, new connectors are delivered with service packs installation media. Alternatively, they can be delivered as deployable artefacts by the SEEBURGER Professionals Services Organization.

Note that if you chosse full service in the SEEBURGER Cloud, we manage your connections with industry-leading Service Level Availability (SLA) commitments.