Solution : https://service.sap.com/sap/support/notes/888687 (SAP Service marketplace login required)
Summary :
This SAP Note explains the diagnostics methods for logon and communication errors within BEx Web Java environments. It guides through classifying issues into categories, focusing on the RFC and HTTP(S) communication protocols involving SAP Web Application Server Java and ABAP. It details troubleshooting steps, emphasizing the importance of log settings and necessary information to be provided to SAP Support for efficient issue resolution. Areas covered include setting up communications, authentication errors, and classifying errors by analyzing logs to trace the origin of communication disruptions, thereby streamlining support interactions.
Key words :
file /usr/sap/<sid>/jc<sysnr>/j2ee/cluster/server<#>/log/defaulttrace, directory /usr/sap/<sid>/jc<sysnr>/j2ee/cluster/server<#>, %20to%20configure%20sso%20in%20a%20complex%20system%20landscape, /saphelp_erp2005/helpdata/en/6c/7ffb3f6c78ee28e10000000a1550b0/frameset, /saphelp_erp2005/helpdata/en/e3/e86878c8204acc856d8d5da4a54fa4/frameset, java-based bex web applications communicate differently, sap web application server java appears, sap web application server abap communicate, calling sap web application server abap, respective sap web application server abap
Related Notes :
| 1025307 | Composite note for BW 7.00 / BW 7.01 performance: Reporting |
| 989525 | BI 2004s: Checking Java Connections Web Application Designer |
| 951381 | Report Designer cannot embed data provider |
| 948483 | Reporting problems in SAP NetWeaver 2004s BI Usage |
| 934275 | Timeout settings NW 2004s BI PDF |
| 918236 | WD ABAP ALV - creating print version |
| 917950 | SAP NetWeaver 2004s: Setting Up BEx Web |
| 916090 | RFC-error messages in Web Application Designer 2004s |
| 596698 | Session Release Agent - Typical Problems & Troubleshooting |