cancel
Showing results for 
Search instead for 
Did you mean: 

BW w/webdisp processing terminated

Former Member
0 Kudos

hello forum,

We've implemented the SAP WebDispatcher to terminate SSL and load balance sessions between BW WebAS (ABAP) for BW webreporting.

Before, when connecting directly to the WebAS, webreports were displayed correctly. However, when using the URL via de WebDispatcher the query is displayed initially, but once you enter values the processing is terminated.

This behaviour only occurs when connecting to the WebDispatcher, if you bypass the WebDispatcher and connect to the WebAS directly the report is displayed correctly. However we want to use the WebDispatcher for port translation (default port 443 instead of the WebAS HTTP port, it's not possible in this situation to change the WebAS HTTP port to 443) and SSL termination (also to offload the WebAS).

Any ideas??

Thanks, Walter

Accepted Solutions (0)

Answers (1)

Answers (1)

athavanraja
Active Contributor
0 Kudos

we have been using webdispatcher for BW web reports and it has been working fine. however i cant help you much as i am not a basis person. the following online help should help to you identify the issue.

http://help.sap.com/saphelp_erp2004/helpdata/en/f5/51c7d170bc4a98b1b5a0339213af57/frameset.htm

Regards

Raja

Former Member
0 Kudos

Hello Durairaj,

I have already reviewed that information, also I have maintained the HTTPURLLOC table according to: http://help.sap.com/saphelp_nw04s/helpdata/en/59/31ae42e0fac911e10000000a1550b0/frameset.htm

MANDT SORTKEY PROTOCOL APPLICATN FORDOMAIN HOST PORT

<client> 010 HTTP * <webas1> <internalport>

<client> 011 HTTP * <webas2> <internalport>

<client> 020 HTTPS * <webdisp> <external port>

<webdisp> is the address before the webdispatcher that redirects to <webas1> or <webas2>, which are both BW WebAS servers.

Any ideas?

Walter