A typical error situation is when the adapter throws an error but there is not much details about it. You can try communication channel monitoring from RWB or checking the logs via Visual Admin. But if the error is not logged there what else can you do?
In order to see some more entries for each java based adapter you can increase the tracing level. Before the relase of 7.1 version of PI you could do it directly from Visual Admin but how to do it from 7.1 onwards?
open NWA then:
– Problem Management
– – Logs and Traces
– – – Log Configuration
and change the view to Tracing Locations
– – sap
– – – aii
– – – – adapter
– – – – – soap
and change the severity to DEBUG
Click on Copy To Sub-Tree button in order to copy severities to the subnodes
Click on Save configuration button
Now you can run the adapter and check the defaultTrace log – you can do it either from NWA or from transaction AL11 for example (I like this second approach as it’s a little bit more readable for me) – you just need to check the defaultTrace file in this location:
This approach is described in some apdater faq notes but from what I can see on the forum not a lot of us knew about it so that’s why I’m posting this short blog.