You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/connectors/sap.md
+36Lines changed: 36 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1170,6 +1170,42 @@ You can control this tracing capability at the application level by adding the f
1170
1170
> If you download a log or trace file that your logic app workflow opened
1171
1171
> and is currently in use, your download might result in an empty file.
1172
1172
1173
+
## Enable SAP CCL (Common Crypto Library) logging
1174
+
1175
+
When you have to investigate any problems with crypto library while using PSE authentication, you can set up custom text file-based CCL logging, which SAP or Microsoft support might request from you. By default, this capability is disabled because enabling this trace might negatively affect performance and quickly consume the application host's storage space.
1176
+
1177
+
You can control this logging capability at the application level by adding the following settings:
1178
+
1. In the [Azure portal](https://portal.azure.com), open your Standard logic app resource.
1179
+
1180
+
1. On Standard logic app resource menu, under **Development Tools**, select **Advanced Tools** > **Go**.
1181
+
1182
+
1. On the **Kudu** toolbar, select **Debug Console** > **CMD**.
1183
+
1184
+
1. Browse a location under **C:\home\site\wwwroot** and create a file for example: **CCLPROFILE.txt** with tracing configurations as requested by Microsoft or SAP.
1185
+
Refer [SAP NOTE 2338952](https://me.sap.com/notes/2338952/E) under **Tracing** for more information regarding tracing parameters. An example tracing configuration is given below:
1186
+
```
1187
+
ccl/trace/directory=C:\home\LogFiles\CCLLOGS
1188
+
ccl/trace/level=4
1189
+
ccl/trace/rotatefilesize=10000000
1190
+
ccl/trace/rotatefilenumber=10
1191
+
```
1192
+
1193
+
1. On the logic app menu, under **Settings**, select **Environment variables** to review the application settings.
1194
+
1195
+
1. On the **Environment variables** page, on the **App settings** tab, add the following application settings:
1196
+
1197
+
* **CCL_PROFILE**: The directory where **CCLPROFILE.txt** was created, for example, **C:\home\site\wwwroot\CCLPROFILE.txt**.
1198
+
1199
+
1. Save your changes. This step restarts the application.
1200
+
1201
+
### View the trace
1202
+
1203
+
1. On Standard logic app resource menu, under **Development Tools**, select **Advanced Tools** > **Go**.
1204
+
1205
+
1. On the **Kudu** toolbar, select **Debug Console** > **CMD**.
1206
+
1207
+
1. Browse to the folder for the parameter named **$ccl/trace/directory** from **CCLPROFILE.txt**. Normally the trace files are named **sec-Microsoft.Azure.Work-$processId.trc** and **sec-sapgenpse.exe-$processId.trc**.
1208
+
1173
1209
## Send SAP telemetry for on-premises data gateway to Azure Application Insights
1174
1210
1175
1211
With the August 2021 update for the on-premises data gateway, SAP connector operations can send telemetry data from the SAP NCo client library and traces from the Microsoft SAP Adapter to [Application Insights](../../azure-monitor/app/app-insights-overview.md), which is a capability in Azure Monitor. This telemetry primarily includes the following data:
0 commit comments