on 2009 Feb 16 9:15 PM
Web dispatcher redirecting problem
Dear Experts,
I have implemented a scenario which comprised of customizing that is developed in Portal EP7. What customizing does is getting report from backend system (ERP 6.0)
According to the needs for reaching the portal from internet I configured the SAP Web Dispatcher in the environment as you may see its contents below.
The problem is when I run the customizing in portal system then it requires connecting to backend system (ECC 6.0) to get the data (report). But from this point on web browser comes to a blank page, could not view the data that is from backend system via portal. Because in the time when it tries to retrieve data in backend system, on the left bottom of the explorer the indicator shows internet address that system uses connecting to the backend system as local network address of the backend system which is not known in internet therefore I get blank page.
The question is how to configure the web dispatcher in a way that both portal and backend systems could be reachable from internet?
Contents of profile file of Web Dispatcher as;
SAPSYSTEMNAME = WDP
SAPGLOBALHOST = portald
SAPSYSTEM = 02
INSTANCE_NAME = W02
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_CT_RUN)
#----
Accesssability of Message Server
#----
rdisp/mshost = portald
ms/http_port = 8101
#----
Configuration for medium scenario
#----
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 500
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
#----
SAP Web Dispatcher Ports
#----
#icm/server_port_0 = PROT=HTTP,PORT=81$$
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=60000
icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/index.html
icm/HTTP/redirect_0 = PORT=50000
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 500
wdisp/HTTPS/max_pooled_con = 500
#----
Configuration for medium scenario
#----
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 500
icm/min_threads = 10
icm/max_threads = 50
mpi/total_size_MB = 80
Regards,
Ali Taner
Request clarification before answering.
Hi,
To resovle this you must have registered FQDN for your backend system as well. When you call the report from Portal using internet it should call that FQDN of your backend system then DNS will resolve this & you will get the expected page. This way only you can resolve this issue.
Thanks,
Sachin Sable
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ali,
we got the same problem you encontered on March....did you resolve this issue?
If Yes, how did you find the correct implementation?
Kind regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.