Why the new SAP connector for Logic Apps


When you search for the keyword SAP in the Azure Logic Apps designer action card, you will see three connectors, four actions (and one trigger, not shown here):

Why did we introduce earlier this year this new SAP connector in addition to the earlier SAP Application Server and SAP Message Server connectors?

The new connector consolidate both Application and Message Server (aka Group) types of connection (aka logon in SAP terminology) under one connector such that you don't have to change the Logic App definition to change the connection type between say a dev environnent single machine SAP system with direct connection to Application Server and a production system with multiple servers behind the Message Server for load balancing.

The new connector adds schema generation (as an action) and trigger (SAP to Logic App) as well. This is further the connector we are working on to enable in ISE (Isolated Service Environment, the dedicated offering of Azure Logic Apps).

All the three connectors use the same SAP Adapter library in the On-Premises Data Gateway. The improvements we have been doing for both functionality and performance of sending messages to SAP in this SAP Adapter library, they are been done in a backward compatible way so the two older connectors continue to function for now.

Eventually we will deprecate the two old connectors and only the consolidated new connector will be promoted to general availability.

Comments (4)
  1. Loogman says:

    Is there any ETA on the enablement of the SAP connector in integration service environments (ISE)?

    1. David Burg says:

      To be clear the shared environment connectors including SAP are already reachable from ISE, although then they are not running inside the ISE VPN. You can also use right now the native REST / HTTP actions of Logic Apps with SAP Gateway.
      As to the ETA for support running within ISE – ‘soon’: This is the feature I am working on at the moment. It is non-trivial as what was previously hosted on the On-Premises Data Gateway will be hosted in the connector underlying Web App host; this means a rework of how the 3rd party assemblies (SAP NCo’s) get onto the host in compliance with SAP’s licensing terms; rework of getting the SAP credentials to the SAP adapter; rework of holding RFC server registration active for SAP trigger in sync on all host instances covering HA, scale-out & scale-in, to name a few of the challenges being addressed.

      1. Loogman says:

        Thanks for the confirmation David. I understand the challgens involved with all that’s involved and wasn’t counting on anytime soon, great work!

  2. David Burg says:

    This blog has been moved off the MSDN platform. Find further content and update at https://www.linkedin.com/today/author/daviburg

    Comments are locked as part of the blog migration, so please reach out to your customer support contact for assistance with Microsoft products and services.

Comments are closed.

Skip to main content