We are

the right


SKYVVA is often used in addition to the existing middleware to supplement the missing functionalities such as monitoring, alerting and error handling. In this way, SKYVVA ideally coexists with the existing infrastructure in the case of a Salesforce integration without having to expand the middleware.

SKYVVA Middleware Connector
SKYVVA Orchestration Middleware Connect


Middleware Connect

The middleware on the market follows the generic approach of integrating a variety of systems and applications with each other. The special properties of the applications do not play a role here, as this approach only focuses on the pure technical connection. The subtleties and peculiarities of the applications to be integrated, such as Salesforce, are often ignored and lead to a non-performant and sometimes faulty connection of the systems. SKYVVA’s approach is different: it considers Salesforce as a special application, knows its characteristics and peculiarities, and above all takes into account the well-known Salesforce “Governor Limit” and counteracts it with adequate means.


Use Cases

All middleware integrations use the standard Salesforce API (soap, rest). API's are generally excellent for fast and timely request & response scenarios. With our Connect solution we avoid an inherent architectural danger of so called "tight coupling" which can lead to a high resource consumption at the requesting client. If the load of the request is too high and unintentional using this type of tight coupling, it could lead to server overload (Salesforce) and eventually to a standstill of the client application.

Middleware Connect Beispiele

Extension native adapter


Extension of the middleware via native adapters, e.g. in the case of SAP-PI/PO or SAP-CPI. If the middleware has an Adapter Connectivity Kit, in which a third-party adapter can be developed, SKYVVA represents the so-called native adapter. This means that the integration runs with the native technologies of the two platforms and is therefore the most efficient.

SKYVVA API Middleware Connect

Using the SKYVVA API


Use of the SKYVVA specific API via the Middleware API Gateway or Connect. Middleware does not always offer the possibility of developing to a third-party adapter. In this case, the additional functions offered by SKYVVA can be accessed via API. A so-called API Gateway or Connect is available with every middleware.

Hybrid Mapping Middleware Connect

Hybrid Mapping


Hybrid Mapping means to carry out the data transformation where it makes the most sense. For example, it makes no sense to assign a salesperson to a sales territory in the middleware mapping if the information is not available there. The information as to which sales employees are responsible for which territories is stored in Salesforce and therefore the transformation is in Salesforce, i.e. in this case SKYVVA is the only correct implementation.


Fields of application

Our connector extends the easy integration, which is based only on the synchronous Salesforce Standard API. This type of integration only supports CRUD operations and is therefore not sufficient and of low quality for an enterprise-class integration. Wherever it is technically possible and the middleware provides an ADK (Adapter Development Kit) for the development of native adapters, SKYVVA offers its own adapters such as for SAP-PI/PO, SAP-CPI, MuleSoft. For a middleware which does not provide an ADK, the functional expansion is realised via the optimised SKYVVA API.

Blog Anwendungsbereich Middleware Connect

SAP-PI/PO Connect

Native Connector on the SAP PI/PO platform for high-performance integration that goes beyond the simple CRUD API approach

Read more

MuleSoft Connect

Native Connector on the Mule Engine for more functionalities such as the BULK API with error handling via the SKYVVA Monitor on the Salesforce side.

Read more

Webmethods Connect

Extension of the integration with value-added functionalities such as monitoring, alerting, reprocessing via the SKYVVA native API.

Contact us