Skip to content

Commit b966e24

Browse files
author
Siddharth
authored
Added CPIC logging for SAP
1 parent c4495b1 commit b966e24

File tree

1 file changed

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

1 file changed

+16
-1
lines changed

articles/logic-apps/connectors/sap.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1096,6 +1096,7 @@ You can control this tracing capability at the application level by adding the f
10961096
* **SAP_RFC_TRACE_DIRECTORY**: The directory where to store the NCo trace files, for example, **C:\home\LogFiles\NCo**.
10971097

10981098
* **SAP_RFC_TRACE_LEVEL**: The NCo trace level with **Level4** as the suggested value for typical verbose logging. SAP or Microsoft support might request that you set a [different trace level](#trace-levels).
1099+
* **SAP_CPIC_TRACE_LEVEL**: The CPIC Trace level with **Verbose** as the suggested value for typical verbose logging. SAP or Microsoft support might request that you set a [different trace level](#trace-levels).
10991100

11001101
For more information about adding application settings, see [Edit host and app settings for Standard logic app workflows](../edit-app-settings-host-settings.md#manage-app-settings).
11011102

@@ -1105,6 +1106,8 @@ You can control this tracing capability at the application level by adding the f
11051106

11061107
### Trace levels available
11071108

1109+
#### NCo Trace Levels
1110+
11081111
| Value | Description |
11091112
|-------|-------------|
11101113
| Level1 | The level for tracing remote function calls. |
@@ -1123,6 +1126,15 @@ You can control this tracing capability at the application level by adding the f
11231126
| SessionProvider | Traces all methods of the currently used implementation of **ISessionProvider**. |
11241127
| SetValue | Writes information to the trace files regarding values set for parameters of functions, or fields of structures or tables. |
11251128

1129+
#### CPIC Trace Levels
1130+
1131+
|Value|Description|
1132+
|---|---|
1133+
|Off|No logging|
1134+
|Basic|Basic logging|
1135+
|Verbose|Verbose logging|
1136+
|VerboseWithData|Verbose logging with all server response dump|
1137+
11261138
### View the trace
11271139

11281140
1. On Standard logic app resource menu, under **Development Tools**, select **Advanced Tools** > **Go**.
@@ -1133,7 +1145,10 @@ You can control this tracing capability at the application level by adding the f
11331145

11341146
A new folder named **NCo**, or whatever folder name that you used, appears for the application setting value, **C:\home\LogFiles\NCo**, that you set earlier.
11351147

1136-
After you open the **$SAP_RFC_TRACE_DIRECTORY** folder, you'll find a file named **dev_nco_rfc.log**, one or multiple files named **dev_nco_rfcNNNN.log**, and one or multiple files named **dev_nco_rfcNNNN.trc** where **NNNN** is a thread identifier.
1148+
After you open the **$SAP_RFC_TRACE_DIRECTORY** folder, you'll find:
1149+
1150+
1. _NCo Trace Logs_: A file named **dev_nco_rfc.log**, one or multiple files named **nco_rfc_NNNN.log**, and one or multiple files named **nco_rfc_NNNN.trc** files where **NNNN** is a thread identifier.
1151+
1. _CPIC Trace Logs_: One or multiple files named **nco_cpic_NNNN.trc** files where **NNNN** is thread identifier.
11371152

11381153
1. To view the content in a log or trace file, select the **Edit** button next to a file.
11391154

0 commit comments

Comments
 (0)