Correlation is breaking between SAP ERP & PI as well as between PI and .NET.
- An originating call in SAP ERP is a custom SAP GUI transaction (Tcode: ZRTP_DISPO) which calls RFC within a custom ABAP code. Does this require manual instrumentation of the custom RFC call according to the docs below? https://docs.appdynamics.com/display/SAP/Instrument+Custom+ABAP+Code
...
1) ABAP to JAVA RFC calls are not supported (dual stack PI system incoming RFC traffic via the java Java part)
2) SAP GUI transactions are reconstructed from logs into BT. In this case, only 1 RFC "hop" is reconstructed and cannot be correlated with downstream agents
i. Custom development can be done to handle custom code as an "online" BT and custom RFC exit call code snippet can be added, but this only works for ABAP-to-ABAP RFC
SAP PI (dual stack)
1) Dual stack PI system is not in supported environments. Support is only declared for single stack (java Java only) PI/PO systems.
2) End-to-end correlation is not technically possible for dual-stack systems for many in-out message type combinations
- The call from SAP PI to .NET is an HTTP call. We can see the exit call in PI and the related BT in .NET. However, no correlation. Do you have any idea what is breaking the correlation?
.NET (WCF)
1) If WCF has its own adapter in PI, then this is not supported
2) We support only outbound message types HTTP, SOAP, and RFC for PI