Web dispatcher re-direct

Hello all,
We need to setup webdispatcher to forward the traffic to two web application servers. We create the webdispatcher service with profile. We don't know how to redirect the traffic to the application servers. We have installed SAP in a Microsoft cluster server.
Any help is greatly appreciated.
N.S

hello Narayanan
just goto the link
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm">http://help.sap.com/saphelp_nw04s/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm</a>
all ur querry will be resolved
<b>Award Reward Points</b>
regards
Shoeb

Similar Messages

Web URL Re-direction thru Web Dispatcher

Has anybody done web url re-direction using Web Dispatcher. I want to redirect URLs. Please advise what configuration I need to carry out.
Thanks.

Hi!
I guess your sapwebdisp is talking to the Message Server of the Portal behind it. So what you have is the following
situation:
User connects to 'http://sapwebdispname:sapwebdispport/irj/portal' and this URL stays like that regardless
of the Portal-Server the user is actually working on.
To achieve what you outlined you will have to make the sapwebdisp answer to port 80 and the desired
hostname. Everything else should be handled in the background.
The configuration item icm/server_port_xx will have to contain the HOST Parameter
Example:
icm/server_port_1 = PROT=HTTP, PORT=80, TIMEOUT=45, EXTBIND=1, HOST=www.company.com
Where EXTBIND=1 is required if your OS does not allow ports to specify that the port should not be bound to all host names (default), but only to the specified host. In this way the host with only one open port can be reached under various URLs.
In parallel you need to make sure that DNS yields the desired results for the name you want to use in the URL.
Regards,
Jörg

WebAS access via Portal: Web Dispatcher required for load balancing ABAP

Hi Folks -
We have EP 6.0 SP18 (Java only, WebAS 6.40, Unix/Solaris). The portal has a CI/SCS and one DI so we have a Web Dispatcher to load balance the portal servers. This works fine (and provides port 80 access).
This portal will provide access to HTTP services from an ABAP WebAS (6.20 with 6.40 kernel, Unix/Solaris). A landscape configuration entry has been added to the portal for this ABAP system. The ABAP system has a CI and multiple app servers, all capable of handling HTTP requests. This will also require port 80 access.
1. Will we need an additional Web Dispatcher to load balance HTTP requests to the 'backend' ABAP WebAS system, or will the portal be smart enough to handle the load balancing itself (perhaps based on the information in the landscape configuration)?
2. If the portal itself handles the HTTP load balancing can you point me to documentation (so I can make sure I have proper configuration)?
3. Are there any changes to this with NW2004s Portal (we plan to upgrade soon)?
Thanks in advance! Jeff

Jeff,
Regarding:
Q1. If you create a system object from the "SAP system with load balancing" template in portal and configure the object to point to your CI (msg server), the LB should be handled.
Q2. Portal load balancing is handled by the message server. If you point a test URL to the port of your message server, you will notice that you are issued a redirect the URL of your dialog instance. The web dispatcher is just a proxy (with some intelligence). When a request is made to the WD, it makes a connection to the MSG server, the list of active instances is queried, a redirect is made to that instanct. If you use WD, that connection can be proxied behind a standard URL. If you connect directly to the MSG Server instead, you will notice your URL change, just as it does on the service marketplace.
WDs are good for providing services, masked (proxied) behind virtual names. If you do not want the customer to see a physical URL of the server, use the WD. There are lots of other solutions that can do this too though such as Apache, ISA, Juniper devices, Cisco LDs. WDs have a very low performance threshold though, especially if you use SSL. WD is a performance bottleneck and should be benchmarked to see if it is right for your application.
Q3. No changes this architecture in 04s.
jwise

Redirection in web dispatcher

Dear Experts,
I have ABAP backend system and I need to open it to internet. Doing so, I have implemented web dispatcher that is running in DMZ. Up to this point everything went on as desired, but one thing.
When I call the URL http://teidom.com:60000 then it redirects to the target host with the local address http://<localhost>.teidom.local:8000/sap/bc/gui/sap/its/webgui. Hereby this is not possible to call the page from internet. This is working only in local network, not in internet. In order to call and view the page from internet, the address has to be intact with no address redirection.
Just to get you closer to understand the situation, here below I wrote down the parameters which I defined for Web Dispatcher (sapwebdisp.pfl).
SAPGLOBALHOST = WebServerRack
SAPSYSTEM = 02
INSTANCE_NAME = W02
DIR_CT_RUN = C:\WebDisp\NTI3867
DIR_EXECUTABLE = C:\WebDisp\NTI3867
Accesssability of Message Server
rdisp/mshost = backsvr.teidom.local
ms/http_port = 8100
Configuration for medium scenario
icm/max_conn = 500
icm/max_sockets = 1024
icm/req_queue_len = 5003
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$$
icm/server_port_0 = PROT=HTTP,PORT=60001
icm/HTTP/redirect_0= PREFIX=/, PORT=8000, PROT=HTTP, TO=/sap/bc/gui/sap/its/webgui, HOST=backsvr.teidom.local
Kind Regards,
Taner Guler

Hi Matt,
It is very kind of you commenting on the subject.
I just want to be sure of the problem that I am facing. My problem is when I call the URL http://teidom.com:60000 from the internet; it is supposed to view the page (information) from ABAP system. But it couldn't.
Web dispatcher is running on the host named 'webdispsvr'
In the firewall I set port 60000 open from internet to web dispatcher server
And in the other firewall (at the back) I set port 8000 open to R3 ABAP system which supplies information to internet.
After setting up the web dispatcher profile according to (thanks Olivier) instructions from help.sap.com
At next stage I started to test
First I tested it in local by URL http://webdispsvr:60000 it works and web browser views the ABAP login windows. From this point of the subject one thing that took my attention was, after pushing enter button for URL http://webdispsvr:60000 then it directly turns to address URL http://<localhost>.teidom.local:8000/sap/bc/gui/sap/its/webgui -- <localhost> is a host of where R3 ABAP system runs on (the address redirects to local address which is not wanted situation in the internet as long as it redirects to local URL address)
Second test was in the internet
Behaviour of the system is same nothing changed
When I call URL http://teidom.com:60000, as it happens in local test, it redirects the URL to http://<localhost>.teidom.local:8000/sap/bc/gui/sap/its/webgui for this reason page could not be viewed when it is called from the internet.
I hope above information is clear enough to get you understand how bad situation I am in.
Isnt there a way out of this struggle?
Thanks all of you for your great contribution to the situation.
Regards,
Taner

Portal 7.3 & Web Dynpro iView, both accessed from Internet via Web Dispatch

Hi guru,
I'd like to know the best (or the correct) way to configure the FQDN and required DNS setting to allow user access ABAP Web Dynpro iview from internet.
My setup here is very typical:
One EP 7.3 in intranet, having "ep.internal.mycomp.com" as FQDN (given during installation)
One SAP ECC in intranet, having "erp.internal.mycomp.com" as SAPLOCALHOSTFULL parameter
One Web Dispatcher in DMZ, having "service.mycomp.com", and listen to 80 port (later added 8000 port for AS ABAP).
   User access my portal by using http://service.mycomp.com/irj, no problem.
But problem raised during access WD4A iview, here are my problem and questions:
[Problem]
At the beginning, we found that the WD4A iView can only be accessed in intranet, not from internet. Eventhough we register "service.mycomp.com" in public DNS. After some http level analysis, I was shock that the WD4A iview is provided directly by AS ABAP which running this WD4A, EP does not play a "relay" role. (Don't believe the URL bar in your IE, use Tamper Data or HTTP live to check the HTTP requests, you will get it). Since we DO NOT have "erp.internal.mycomp.com" in public DNS, so the iview cannot be displayed. But I DON'T want direct access to my ERP box.
I don't know a way to get rid of the "erp.mycomp.com" request generated by EP. So I tried to overcome the problem by leveraging the same Web Dispatcher used by EP. And I did make the WDisp -> ERP WD4A work using WDisp's FQDN (ie. service.mycomp.com:8000, also keep original service.mycomp.com:80 to EP), but the iview in EP does not use this FQDN. It use the SAPLOCALHOSTFULL parameter configured in backend ERP. WDisp does not do any URL replacement for me.
[Question 1]
Is there any way to hide WD4A iview in EP (server to server communication only)?
[Question 2]
If I can only have "service.mycomp.com" entry in my public DNS, should I change the SAPLOCALHOSTFULL in ERP to "service.mycomp.com"? I doubt that it may cause a "loop" situation between WDisp and ERP ?
[Question 3]
Is it possible to access WD4A on ERP by two different FQDNs (one for public via WDisp, the other for internal access w/o WDisp) ? I know there is only one SAPLOCALHOSTFULL configuration.
Anyone have done such integration ? please share your configuraiton. Thanks

Hay Wei-Shang Ku,
Many thanks to your prompt reply of this very old post I tried to ask!
for the /sap/* redirect, think it required to use icm/HTTP/redirect_<xx> parametet in WDISP profile. And i did applied below too to make default WDISP URL go to /irj (Portal login page).
icm/HTTP/redirect_0 = PREFIX=/,TO=/irj
so for "all request to /sap/* will go to ERP":
icm/HTTP/redirect_0 = PREFIX=/sap/*,TO=/??? (how do you set the TO value here?)
May i have your WDISP profile setting for reference? Did you make use of parameter wdisp/system_0?
And here is my overall setting:
we only have "service.mycomp.com" entry in public DNS.
1. "service.mycomp.com" is WDISP URL mapped to 1 public IP (we used default http 80 port)
2. we want user can access JPortal & also backend ERP via WebDynpro iView in JPortal via
   service.mycomp.com (only port only)
3. ERP system profile:
    SAPLOCALHOSTFULL = <ERPHOSTNAME>.mycomp.com (not in public DNS)
    icm/server_port_0 = PROT=HTTP,PORT=80$$,TIMEOUT=3600,PROCTIMEOUT=3600
4. Portal:
    ABAP WebDynpro iView setting -
   System = XXX (where XXX is alias of system iView)
System iView setting -
    Logical System Name = ERPCLNTXXX
    ITS host = <ERPHOSTNAME>.mycomp.com:8000
Thanks again your information, have headache of this issue for long times....
Gary

Deactivate Portal server node from Web dispatcher, but still keep online

We want to deactivate a Portal server node from the Web dispatcher. We also need to connect directly to the specific node.
We configured the Server Node using Config Tool --> Server_ID####### --> Debug --> Debuggable --> Restricted Load Balancing. The node is not available to the Web dispatcher, However we are unable to explicitly connect to that node. We get the error message in the browser:
503 Service Unavailable
SAP WebAS engine is starting...
If this state does not change within a few minutes,
please contact your system administrator.
Check the recommendations in SAP Notes: 943498, 764417
Message: Dispatcher running but no server connected!
I have also read through the Web dispatcher online Help. They mention creating groups but they all seem to pertain to ABAP groups using SMLG. Our Web dispatcher is used in a strictly J2EE environment.
There must be a Profile setting or some config to restrict specified nodes... Let me know if you have found out?
Thank You,
Jon Sells

Hi PR,
Yes I understand that the Web Dispatchers Job ends at that point. That's why I want to stop the requests at the Web dispatcher by not allowing those nodes to be available.
Here is the situation. We have 3 Windows Servers with 10 Server Nodes spread accros them.
Host A - 2 Server Nodes, Central instance (Message Server) and SQL Server DB.
Host B - 4 Server Nodes.
Host C - 4 Server Nodes.
The Going Live Analysis suggested we move the DB off of the CI. We cannot do that at this time. What we can do is shut down the 2 nodes on Host A. Instead of shutting them down, we would rather remove them from the WD group. that way, our users never connect to the 2 nodes on the CI but Basis can still use them for Administration and those 2 nodes on the CI are never used for production purposes. Those nodes will just be used for monitoring and maintenance or even emergency purposes.
Right now our process to remove the 2 nodes from the Web dispatcher is to connect to the Admin page for Web Dispatcher --> Monitor Server Groups --> Right Click on the Host and select Deactivate. We have to do this whenever the Message Server is retarted. The million dollar question: How can that be set via a startup parameter?
Thanks
Jon Sells
Here is an example of how you can connect to a specific node:
https://<Host_name>.domain.local/b2b/b2b/init.do;sapj2ee_irj=7501753

Web dispatcher redirects to Message Server

Hello SDN members.
Iu2019m using web dispatcher in front of a ABAP+JAVA installation. When Iu2019m tracing (HTTP) requests from the portal that are aimed to the ABAP WAS (usually requests to the webgui service) I can see the following:
1. the request are first directed to port 8100 (message server)
2. and then redirected to port 8000 (its)
Is this normal? Iu2019m aware that the Web Dispatcher uses the message server for information regarding load balancing, but is this redirect necessary? If not, how can I avoid it? From what i have seen in the SAP documentation, Web Dispatcher sends the requests to the ICM directly. Maybe I am missing something here.
Thank you very much for your time.
giorgos.

Hello Allaine,
Thanks for your answer. It really clarifies the process. However I would like to elaborate a bit on a gray (for me) spot:
SAP suggests that you should use Web Dispatcher as an HTTP Load Balancer (especially when a portal is used) and not the Message Server. Since that is what we are trying to do, I expected not to see any u201Cactionu201D on the Message Server port (8100 - even though the Web Dispatcher uses the Message Server for information regarding available servers, I thought that this would happen in the background). My expectations are based on the Web Dispatcher documentation where it is stated that:
Unlike [HTTP Load Balancing Using the SAP Message Server|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/c5935087b62d66e10000000a42189c/content.htm], redirects are not executed when the SAP Web dispatcher is used. This avoids the associated disadvantages (several IP addresses must be known, book marking is not possible, authentication after changing the application server).
So, what you meant in your post is that when the message server is accessed the HTTP balancing has already taken place? Or not?
Also as stated in Note [857596|https://service.sap.com/sap/support/notes/857596] HTTP 301 is sent by the Message Server when Load Balancing takes place. Thatu2019s why I said I want to avoid the redirection . I would like to comply with SAP directive to use the Web Dispatcher for HTTP Load Balancing and not the Message Server.
any suggestion is valuable!
Giorgos.

Web Dispatcher - Page Cannot Be Displayed

We have a Web Dispatcher in a DMZ (DMZ2) that is used for external (Internet) access to our E-Sourcing application. The E-Sourcing application is in another DMZ (DMZ1).
When external (sell-side) users enter the url in their browser to connect through the Web Dispatcher over the Internet, the initial E-Sourcing screen is displayed very briefly in the browser and then the message 'Page cannot be displayed' comes up on the screen. If the browser screen is refreshed, the login screen is then displayed and the user is able to log in with no issues.
This occurs only when trying to access the E-Sourcing application through the Web Dispatcher. It does not make any difference if the Web Dispatcher hostname is used in the url (internal access through Web Dispatcher) or if the url created specifically for the Web Dispatcher is used (external (Internet) access through the Web Dispatcher). The result is the same.
If either http://WebDisp_Hostname (internal) or http://www.myESOapp.here.com (external Internet) is entered in the browser, both display the front-end ESO screen briefly and then display the 'Page cannot be displayed' message. Refreshing the browser screen then displays the login screen and users can log in OK.
Can anyone point me in the right direction to solve this? I have reviewed the Web Dispatcher trace file and the E-Sourcing log file and can find no errors or anything that would indicate what might be going on. It appears to be a Web Dispatcher issue. Any help would be appreciated.
WL

Hi Wayne,
When external (sell-side) users enter the url in their browser to connect through the Web Dispatcher over the Internet, the initial E-Sourcing screen is displayed very briefly in the browser and then the message 'Page cannot be displayed' comes up on the screen. If the browser screen is refreshed, the login screen is then displayed and the user is able to log in with no issues.
When first time you call URL , do you the page of Esourcing or you directly get the error page.
It better , install HTTP watch software on you dekstop and then activate the HTTP watch and start browsing the page and generate the problem which you are facing .
Once it is done share the result of HTTP Watch in the forum , depend upon that we can come to some solution.
Thanks
Anil

Web Dispatcher Performance Problem

Hi,
We are using the Web Dispatcher with the Enterprise Portal 6.0
installed on Solaris 9 with Oracle 10g.
When we are trying to access the Portal via the web dispatcher we are
seeing that the loading of the initial page is long time as compared to
when we are using the direct portal link to access the same.
The difference in accessing the iniital page using the web dispatcher
url is nearly 3 times as compared to accessing the same by the direct
portal url.
We have installed 2 application servers with 4 java server nodes in one
application server and 2 java server nodes in one application server.
Please find the web dispatcher profile parameters enclosed herewith
<b>Parameters set in web dispatcher profile</b>
sp1adm> pg SP1_SCS85_sapwebdisp
SUN Cluster | SAP Web Dispatcher
SAPSYSTEMNAME = SP1
SAPSYSTEM = 95
DIR_INSTANCE = /usr/sap/SP1/SYS/sapwebdisp
SECUDIR = /usr/sap/SP1/SYS/sapwebdisp/sec
rdisp/mshost = sapsp1ms-db
ms/http_port = 8185
wdisp/auto_refresh = 60
wdisp/max_servers = 100
wdisp/permission_table = /usr/sap/SP1/SYS/sapwebdisp/sapwebdisp.tab
wdisp/HTTP/context_timeout = 3600
wdisp/HTTP/jsessionid_tab_support = 1
is/HTTP/show_detailed_errors = FALSE
icm/host_name_full = sapsp1ms.in.telstra.com.au
icm/server_port_0 = PROT=HTTP,PORT=80,HOST=sapsp1ms.in.telstra.com.au,EXTBIND=1
icm/server_port_1 = PROT=HTTP,PORT=50100,HOST=sapsp1ms.in.telstra.com.au
icm/server_port_2 = PROT=HTTPS,PORT=443,HOST=sapsp1ms.in.telstra.com.au,EXTBIND=1
icm/HTTP/server_cache_0 = PREFIX=/, CACHEDIR=/usr/sap/SP1/SYS/sapwebdisp/data/cache0
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin, DOCROOT=/usr/sap/SP1/SYS/sapwebdisp/admin, AUTHFILE=/usr/sap/SP1/SYS/sapwebdisp/icmauth.txt
icm/HTTP/file_access_0 = PREFIX=/sap/public/icman, DOCROOT=/usr/sap/SP1/SYS/sapwebdisp/public/icman
SAP Web Dispatcher Web Administration
icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/index.html
icm/HTTPS/verify_client = 1
ssl/ssl_lib = /usr/sap/SP1/SYS/exe/run/libsapcrypto.so
ssl/server_pse = /usr/sap/SP1/SYS/sapwebdisp/sec/SAPSSLS.pse
ssl/client_pse = /usr/sap/SP1/SYS/sapwebdisp/sec/SAPSSLC.pse
wdisp/ssl_encrypt = 0
wdisp/ssl_auth = 2
wdisp/ssl_host = sapsp1ms.in.telstra.com.au
icm/keep_alive_timeout = 1800
icm/conn_timeout = 180000
SUPPORTING LARGE USER BASE PARAMETERS
icm/max_conn = 8192
icm/max_sockets = 16384
wdisp/HTTP/max_pooled_con = 8192
wdisp/HTTPS/max_pooled_con = 8192
icm/req_queue_len = 6000
icm/min_threads = 100
icm/max_threads = 200
mpi/total_size_MB = 500
mpi/buffer_size = 65536
mpi/max_pipes = 21000
Please check and let us know as to how do we improve the performance of
the same.
Thanks & Regards,
Srinivas Reddy

Jochen,
Thanks for the reply. Here is the "graphical" flow;
IE==>HW-LB==> 3 (Apache==>Reverse Proxy-->WebDisp) --> 2 (WAS 6.40 SP11 PL3)
(Legend ==> HTTPS --> HTTP)
At the risk of redundancy, there are 3 Linux SLES8 servers running Apache2 with Reverse Proxy, and the Web Dispatcher 6.40 PL90. Each of these servers are/should be distributing load to 2 WAS 6.40 SP11 PL3 Java-only servers running Windows 2003.
My assumption is that reverse proxy is sending HTTP to the dispatcher then on to WAS or at least pass thru. Should I setup a HTTPS terminate at the dispatcher?
Here's the sapwebdisp.pfl;
Profile generated by sapwebdisp bootstrap
unique instance number
SAPSYSTEM = 01
Accesssability of Message Servers
rdisp/mshost = msgserver.reinternal.com
ms/http_port = 8101
SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 8000
wdisp/HTTPS/max_pooled_con = 8000
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=8080
SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin, PORT=8080
icm/max_conn = 8192
icm/max_sockets = 16384
icm/min_threads = 100
icm/max_threads = 250
icm/req_queue_len = 6000
icm/conn_timeout = 90000
icm/keep_alive_timeout = 90
mpi/total_size_MB = 350
mpi/max_pipes = 13500
mpi/buffer_size = 32768
Any advice or suggested course of action would be appreciated.
Thanks,
Dan

Web Dispatcher and SNC WAS

If I connect my Web Dispatcher to a WAS that is not running SNC it connects okay but if I point it to a WAS that is running SNC I get SNC related arrors in the file dev_webdisp.log:
[Thr 6968] *** ERROR => invalid service descriptor token 'p:GB\SAPServiceQAS' [ictxxroute_r 2681]
[Thr 6968] *** ERROR => syntax error in text description near line 4 [ictxxroute_r 3135]
[Thr 6968] *** ERROR => IcrUpdateServerPoolFromDescrString() failed 6 [icrxx.c      1762]
If I call the /sap/public/ping service on the WAS directly from Internet Explorer on my PC it connects okay, but if I call the same service from my PC via the Web Dispatcher it failes with the above message in the log file and the below HTTP message:
500 Dispatching Error
Dispatching Error
Error: -26
Version: 6040
Component: HTTP_ROUTE
Date/Time: Tue Feb 07 12:47:50 2006
Module: http_route.c
Line: 2352
Server: UKLONSAP011_QE7_10
Detail: no valid destination server available for '!ALL' rc=13
I cannot find any information relating to the Web Dispatcher and SNC on help.sap.com or OSS.
Do I have to install the SNC library onto the Web Dispatcher server? If so, how do I then reference it?
Any ideas?
Thanks.
Paul

Hi Paul,
SNC library is not required for Web Dispatcher.
The problem seems to be the data the message server provides with the URL http://<msg_host>:<msg_http_port>/msgserver/text/logon?version=1.2
If SNC is activated you will have an entry for RFCS in the data like:
RFCS     bin.wdf.sap.corp     4853     p/secude:CN=BIN, O=SAP-AG, C=DE
The error " invalid service descriptor token 'p:GB\SAPServiceQAS' " indicates that the parser could not parse the response from the message server. Then the server list is empty and you get the "dispatching error".
Maybe the backslash lets the parser struggle. Please check that you have an up to date version running (6.40 kernel patch level > 90). If that is the case, then this problem should be handled by OSS message.
Kind regards,
   Oliver

SAP Web Dispatcher for Portal reverse proxy

Hi Experts,
I am on EP6.0 SP20 and trying to use SAP web dispatcher as reverse proxy.
I followed the below web log to configure the web dispatcher.
[How to...Configure SAP Webdispatcher as a reverse proxy|How to...Configure SAP Webdispatcher as a reverse proxy]
I still have some problems logging into the Portal through the web dispatcher.
Web Dispatcher is in the DMZ not behind the firewall. We opened the port 80 only for Web dispatcher server.
We are getting an error in the browser,
http://<host of portal>.<domain name>:50000/irj/portal can not be recognized.
I have no clue to how to get rid of this error. any help will be greatly appreciated.
Regards,

Hi,
I do not know the exact ESS WebDynpro you are using but it may be possible that these WebDynpros use absolute URLs which of course do not point to the hostname and port of the Web Dispatcher.
There are several ways to circumvent this:
Please check http://help.sap.com/saphelp_nw04s/helpdata/en/62/5f374ff72c40478fcba2bb4fa79ddf/frameset.htm and add the parameters wdisp/add_client_protocol_header and (more important for you: wdisp/handle_webdisp_ap_header) to the WebDynpro configuration.
(A nice explenation why we have to use this can be found here: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bsp/using+proxies&)
another way would be to tell the J2EE engine directly that it is behind a WebDispatcher, by setting the ProxyMappings (http://help.sap.com/saphelp_nw70/helpdata/en/b8/437d46d4451e4c9ab756e272a1581d/frameset.htm)
Regards,
Holger.

Web dispatcher can't connect msserver

hi, experts,
Our web dispatcher B is in DMZ1, which faces internet directly, and I wanna its msserver is A which is in Core, which only in protection zone.
Now, DMZ1 has allowed Core with port 8111, but when start web dispatcher, it says error in dev_webdisp, following is details:
[Thr 1] Mon Sep 19 11:35:06 2011
[Thr 1] Profile configuration error detected, use temporary corrected setup
[Thr 1] Shared Pool 10: ipc/shm_psize_10 = 19880000 (too small)
[Thr 1] Shared Pool 10: (smaller than min requirement 150848560)
[Thr 1] started security log to file dev_icm_sec
[Thr 1] SAP Web Dispatcher running on: dga114
[Thr 1] MtxInit: 30001 0 2
[Thr 1] IcmInit: listening to admin port: 65000
[Thr 1] WLM Tag 'CWI/ICM' successfully set for this process
[Thr 1] IcrCoreInitSessionTable: Session table initialized
[Thr 515] *** WARNING => HttpPlugInInit: Parameter icm/HTTPS/trust_client_with_issuer or icm/HTTPS/trust_client_with_subject not set
=> do not trust any intermediary
X.509 cert data will be removed from header [http_plgrt_m 730]
[Thr 515] HttpExtractArchive: files from archive /usr/sap/CWI/SYS/exe/run/wdispadmin.SAR in directory /usr/sap/CWI/W05/data/icmanroo
t are up to date
[Thr 515] HttpSubHandlerAdd: Added handler HttpAdminHandler(slot=0, flags=4101) for /sap/admin:0
[Thr 515] CsiInit(): Initializing the Content Scan Interface
[Thr 515]            IBM RS/6000 with AIX (mt,unicode,SAP_CHAR/size_t/void* = 16/64/64)
[Thr 515] CsiInit(): CSA_LIB = "/usr/sap/CWI/SYS/exe/run/libsapcsa.o"
[Thr 515] HttpSubHandlerAdd: Added handler HttpAuthHandler(slot=1, flags=12293) for /:0
[Thr 515] HttpSubHandlerAdd: Added handler HttpWebDispHandler(slot=2, flags=28677) for /:0
[Thr 515] Started service 8005 for protocol HTTP on host "dga114"(on all adapters) (processing timeout=60, keep_alive_timeout=30)
[Thr 1] IcmCreateWorkerThreads: created worker thread 0
[Thr 1] IcmCreateWorkerThreads: created worker thread 1
[Thr 1] IcmCreateWorkerThreads: created worker thread 2
[Thr 1] IcmCreateWorkerThreads: created worker thread 3
[Thr 1] IcmCreateWorkerThreads: created worker thread 4
[Thr 1] IcmCreateWorkerThreads: created worker thread 5
[Thr 1] IcmCreateWorkerThreads: created worker thread 6
[Thr 1] IcmCreateWorkerThreads: created worker thread 7
[Thr 1] IcmCreateWorkerThreads: created worker thread 8
[Thr 1] IcmCreateWorkerThreads: created worker thread 9
[Thr 3343] IcmWatchDogThread: watchdog started
[Thr 773] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 4 / sock 12
    (SI_ECONN_REFUSE/79; I4; ST; 10.180.225.107:8111) [nixxi.cpp    2845]
[Thr 773] *** ERROR => Connection request from (-1/65535/0) to host: dga107, service: 8111 failed (NIECONN_REFUSED) [icxx
conn_mt.c 2759]
[Thr 773] *** ERROR => IcmConnClientRqCreate() failed (rc=-8) [icrxx_mt.c   5284]
[Thr 773] *** ERROR => Could not connect to SAP Message Server at dga107. URL=/msgserver/text/logon?version=1.2 [icrxx_mt.c   2634]
[Thr 773] *** ERROR => rc=-1, HTTP response code: 0 [icrxx_mt.c   2635]
[Thr 773] *** ERROR => see also OSS note 552286 [icrxx_mt.c   2636]
Do you have any suggestion to solve such problem?
and in DMZ1, may I telnet Core 8111?
Thanks a lot!
BestRegards,
Lily

hi,Srihari,
We check the connection what you mentioned.DMZ1 is OK for Core and Port 8111.We open 8111 in Core as telnet port too. I try to use such command:
dga114:cwiadm 9> sapwebdisp -bootstrap
SAP Web Dispatcher Bootstrap
============================
This bootstrap will perform the following steps:
1. create profile file "sapwebdisp.pfl"for SAP Web Dispatcher (if not already existing)
2. create user for web based administration in file "icmauth.txt"(if not already exisiting)
3. start SAP Web Dispatcher with the created profile
After the bootstrap you can use the web based administration
Generating Profile "sapwebdisp.pfl"
Hostname of Message Server (rdisp/mshost): dga107
HTTP Port of Message Server (ms/http_port): 8111
Checking connection to message server...
ERROR: Illegal data received (no HTTP?) -
please check that 8111 is really the HTTP port of the Message Server
and I think the parameter doesn't matter about this problem, does it?
Thanks for your reply.
Best Regards,
Lily

URL Load Balancing through Web Dispatcher

Dears,
We are facing heavy load on our portal server.
We are planning to installed one J2ee Dialog instance for it.
Please suggest how can we configure Url Load Balancing through Web Dispatcher.
Regards,
Shivam

HI Shivam,
While installing webdispatcher you provide Hostname and http message server port of j2ee of CI .
So , webdispatcher communicate directly with message server, where message server check which application server is free and hence forward the request to that specify application server of j2ee instance.
Pls find the below link for configuring webdispatcher
http://help.sap.com/saphelp_nw04/helpdata/en/42/5cfd3b0e59774ee10000000a114084/content.htm
Thanks
Anil

Call EP and ERP through web dispatcher

Hi,
I have configure multiple system on Web dispatcher EP and ERP.
My issue is our company do not want to publish EP and ERP over the internet but by the web dispatcher uses as a reverse proxy i want to publish the web dispatcher only now my EP called successfully over the internet but WDA application is not working cause it's redirects the directly to ERP so error occur's page not found.is there any way-out to call internally the ERP system.
Regards:
Akash Ahuja

Hi Akash,
As per my understanding from your message. If your EP system called successfully through internet , then your ERP system also should visible via internet. kindly check with your Network team that the ERP system there must be firewall settings to open. For internal call out you can use "redirect menthod" for portal using instead ofhttp://<host>:<port>/irj use http://<host>:<port>/redirect. To change the authentication for another application use:http://<host>:<port>/redirect?url=/customapp.
Need more information about your issue.
Thanks,
Brindavan

Exception accessing portal over web dispatcher

Hello experts,
We are facing issue while accessing portal over web dispatcher on IE (7 & 8).
We get following exception when we try to load any WebDynpro IView (both standard and custom)
com.sap.tc.webdynpro.services.sal.deployment.core.ClassLoaderException: Classloader of 'sap.com/pb' is null, even though application is started.
We are able to execute the application in following ways though
1. Accessing the portal directly bypassing webdispatcher
2. Using Mozilla Firefox browser to access the webdispatcher URL.
Please guide what is missing from the configuration perspective to make it work on IE.
Appreciate the responses.
Thanks
Ashutosh

Yes
ERROR => shmget(15162,744864600,480) (22: Invalid argument) [shmux_mt.c 1501]
[Thr 2199027274608] *** ERROR => ShmCreate( ATTACH 62, 744864600) failed 1 [mpixx_mt.c 1061]
[Thr 2199027274608] *** ERROR => IcmBufInit: MpiInit failed (rc=1) [icxxbuf_mt.c 189]
[Thr 2199027274608] *** ERROR => IcmInit: IcmBufInit failed (rc=1) [icxxrout_mt. 2024]
We have 4 GB of SWAP memory and 4GB of the main memory available.
Ashutosh

Web dispatcher re-direct

Similar Messages

Maybe you are looking for