If you just want to know how to redirect users to Web Dispatcher and avoid the users' directly in ICM, you can go to the Resolution section.
If a wrong redirect is made in the ICM side, it is possible that Web Dispatcher, in front of ICM, stop connecting to the ICM reporting errors like:
| *** WARNING => Failed to read group info for system <SID> (ABAP,HTTP): Internal ICM error(-1) [icrxx.c 3762]
*** WARNING => Failed to read URL prefix info for system <SID> (ABAP,HTTP): Internal ICM error(-1) [icrxx.c 3762]
With a high trace level we see:
NiICheckPendConnection: connection of hdl 704 to <dest IP>:<port> established
In the browser we see error "503 Service not available" or even a message like "server is redirecting the request for this address in a way that will never complete."
These are examples of wrong redirections made in ICM side that affect the Web Dispatcher behavior.
- SAP NetWeaver Systems
- SAP Web Dispatcher
Webdispatcher HTTP response modification handler rewrite header rewriting Internet Communication Manager , KBA , BC-CST-WDP , Web Dispatcher , BC-CST-IC , Internet Communication Manager , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.