Skip to content

Commit a8f773b

Browse files
daviburgecfan
andauthored
Update articles/logic-apps/connectors/sap.md
Co-authored-by: Esther Fan <[email protected]>
1 parent a00fff6 commit a8f773b

File tree

1 file changed

+3
-1
lines changed
  • articles/logic-apps/connectors

1 file changed

+3
-1
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,9 @@ SAP upgraded their .NET connector (NCo) to version 3.1, which changed the way th
205205

206206
In Standard workflows, the SAP built-in trigger named **When a message is received** uses the Azure Functions trigger instead, and shows only the actual callbacks from SAP.
207207

208-
* For the SAP built-in connector trigger named **When a message is received**, you have to enable virtual network integration and private ports by following the article at [Enable stateful mode for stateless built-in connectors in Azure Logic Apps](../../connectors/enable-stateful-affinity-built-in-connectors.md). If you don't configure the workflow application per these prerequisites, the action named **Respond to SAP server** may lack the necessary state to properly function. You can also run the workflow in Visual Studio Code to fire the trigger locally. For Visual Studio Code setup requirements and more information, see [Create a Standard logic app workflow in single-tenant Azure Logic Apps using Visual Studio Code](../create-single-tenant-workflows-visual-studio-code.md). You must also set up the following environment variables on the computer where you install Visual Studio Code:
208+
* For the SAP built-in connector trigger named **When a message is received**, you have to enable virtual network integration and private ports by following the steps in [Enable stateful mode for stateless built-in connectors in Azure Logic Apps](/azure/connectors/enable-stateful-affinity-built-in-connectors). Otherwise, without these requirements, the action named **Respond to SAP server** might lack the necessary state to properly work.
209+
210+
To locally fire the trigger, you can run the workflow in Visual Studio Code. For Visual Studio Code setup requirements and more information, see [Create Standard workflows in Azure Logic Apps with Visual Studio Code](/azure/logic-apps/create-standard-workflows-visual-studio-code). You must also set up the following environment variables on the computer where you install Visual Studio Code:
209211

210212
- **WEBSITE_PRIVATE_IP**: Set this environment variable value to **127.0.0.1** as the localhost address.
211213
- **WEBSITE_PRIVATE_PORTS**: Set this environment variable value to two free and usable ports on your local computer, separating the values with a comma (**,**), for example, **8080,8088**.

0 commit comments

Comments
 (0)