Web Dispatcher on XI Server

Did any one work on the XI server which has WebDispatcher
reg

Naveen,
Check out this presentation on SDN...this is really good one..I have got most of the technical information from this presentation..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/58baa388-0701-0010-2eb6-d7bd4a29ab68
I have some more document will mail you.
Nilesh

Similar Messages

Monitoring Web Dispatcher, SAP Content Server, apache with SM 7.1

Hello,
Did anyone of you come across monitoring possibilities of SAP WD, Content Server or an apache via SM 7.1 SP04? I want to integrate monitoring of these components to technical monitoring in new SM, but didn't find much about it so far.
Thank you very much for help.

Caro Mauro,
I'm more or less in the same situation right now.
Taking into account that you ask for help on this subject last 2004 Oct. I suppose that you have probably solved the problem.
Please can you help me with the solution implemented.
Find below my current work e-mail adress
[email protected]
Thanks in advance,
Best regards, Xavier Grau.

CRM_UI Reporting - HTTPS Terminating at Web Dispatcher or SSL all the way

Hi,
We need to set up access to crm_ui reports (leads and marketing mainly) in CRM 7.0 for vendors coming from the internet. The CRM server is in the internal network. In order for this to work I plan to setup the web-dispatcher in the application dmz. The initial login is going to be via the web dmz layer (using sun's iplanet server), which then routes the crm URL to the web dispatcher in the App dmz and then from the web dispatcher to CRM server.
One requirement from our security team is to set up the flow as HTTPS.
On going through SAP help I get the impression that it can be set up two ways, one, configuring web dispatcher to pass the SSL connection to backend, & two - configuring the web dispatcher to terminate SSL.
Seems the former is quite straight forward (from SAP online help we have to set the icm/server_port_<xx>> = PROT=ROUTER) but does it also require that we setup the crm_ui_frame service as SSL and activate the HTTPS service in ICM?
Or is it better to go via the second option (HTTPS termination) without changing the backend setup? SAP Online help lists steps to do the HTTPS termination but I have not come across any detailed documentation for the first method.
Any thoughts, suggestions will be helpful for either scenario.
Thanks,
Rommel Bhan

Thanks Martin the document helped.
Now the web dispatcher seems to talk to the HTTPS port on the backend.
However there is one issue I see in the dev_webdisp and was wondering if you have an insight.
Based on webdispatcher parameters, its taling to ms_https_port 8533 of backend
[Thr 773] Mon Feb 15 15:03:35 2010
[Thr 773] *** ERROR during SecudeSSL_SessionStart() from SSL_connect()==SSL_ERROR_SSL
[Thr 773] SecudeSSL_SessionStart: SSL_connect() failed --
[Thr 773]   secude_error 9 (0x00000009) = "the verification of the server's certificate chain failed"
[Thr 773] >> -
Begin of Secude-SSL Errorstack -
>>
[Thr 773] ERROR in ssl3_get_server_certificate: (9/0x0009) the verification of the server's certificate chain failed
[Thr 773] ERROR in af_verify_Certificates: (27/0x001b) Chain of certificates is incomplete : "CN=sapcms02.reinternal.com, OU=I0020210975, OU=SAP Web AS, O=SAP Trust Community, C=DE"
[Thr 773] ERROR in get_path: (27/0x001b) Found root certificate of <CN=sapcms02.reinternal.com, OU=I0020210975, OU=SAP Web AS, O=SAP Trust Community, C=DE> which does not fit the given PKRoot
[Thr 773] ERROR in verify_with_PKs: (27/0x001b) Found root certificate of <CN=sapcms02.reinternal.com, OU=I0020210975, OU=SAP Web AS, O=SAP Trust Community, C=DE> which does not fit the given PKRoot
[Thr 773] << -
End of Secude-SSL Errorstack -
[Thr 773]   SSL_get_state() returned 0x00002131 "SSLv3 read server certificate B"
[Thr 773]   SSL NI-sock: local=10.104.146.81:62579 peer=10.104.146.81:8533
[Thr 773] <<- ERROR: SapSSLSessionStart(sssl_hdl=110acb850)==SSSLERR_SSL_CONNECT
[Thr 773] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-57): SSSLERR_SSL_CONNECT [icxxconn_mt.c 1911]
[Thr 773] *** ERROR => IcmConnClientRqCreate() failed (rc=-14) [icrxx_mt.c   5976]
[Thr 773] *** ERROR => Could not connect to SAP Message Server at sapcms02. URL=/msgserver/text/logon?version=1.2 [icrxx_mt.c   3289]
[Thr 773] *** ERROR => rc=-1, HTTP response code: 0 [icrxx_mt.c   3290]
[Thr 773] *** ERROR => see also SAP note 552286 [icrxx_mt.c   3291]
My backend is setup with SSL and web dispatcher is set to the following. Also since the backend and sapweb dispatcher are on the same host, using the same sidadm, the SSL stuff is on one location. I generated the SAPSSLS.pse in the backend using STRUST
Accessibility of Message Servers
rdisp/mshost = sapcms02
ms/http_port = 8100
ms/https_port = 8533
wdisp/server_info_protocol = https
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=ROUTER,PORT=60000
icm/server_port_1 = PROT=HTTPS,PORT=0
icm/server_port_2 = PROT=HTTP,PORT=8080 <-- web dispatcher admin port
#SSL parameters similar to one in backend
ssf/ssfapi_lib = /usr/sap/CMS/SYS/exe/run/libsapcrypto.o
sec/libsapsecu = /usr/sap/CMS/SYS/exe/run/libsapcrypto.o
ssf/name = SAPSECULIB
ssl/ssl_lib = /usr/sap/CMS/SYS/exe/run/libsapcrypto.o
ssl/server_pse=/usr/sap/CMS/DVEBMGS00/sec/SAPSSLS.pse
ssl/client_pse=/usr/sap/CMS/DVEBMGS00/sec/SAPSSLC.pse

Web Dispatcher configured but not working

Hi,
We wish to configure SAP Web Dispatcher as a reverse proxy. For this we've installed using sapinst SAP Web Dispatcher Version 7.00.11, multithreaded, ASCII, 64 BIT Patch Level 140 which was manally updated to SAP Web Dispatcher Version 7.10.1, multithreaded, ASCII, 64 BIT Patch Level 152.
The SAP Web Dispatcher server is in DMZ whereas the Enterprise Portal servers are in the intranet.
The updated SAP Web Dispatcher is available in /sapmnt/<SID>/exe and not in a seperate directory (/usr/sap/<SID>/sapwebdisp) as per SAP note 908097. The SAP Web Dispatcher has been installed on a standalone machine with instance number 00.
I've configured the Sap Web dispatcher with the -bootstrap option. The -checkconfig option completes with 0 warning 0 errors.
The TCP ports between SAP Web Dispatcher and Enterprise Portal servers are opened in the firewall. Also, required ports 22 & 8100 are opened from my computer to the SAP Web Dispatcher Server.
Yet when I try to connect to the administrator interface with the URL http://<Web_Disp_IP>:8100/sap/wdisp/admin/default.html, I receive the following text on the browser:
Network Error (tcp_error)
A communication error occurred: "Operation timed out"
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
Similar message is received even if the SAP Web Dispatcher is installed in a seperate directory.
Has anyone come across a similar issue?
Thanks.
Regards.
SAP Web Dispatcher Profile generated by bootstrap
Profile generated by sapwebdisp bootstrap
unique instance number
SAPSYSTEM = 00
add default directory settings
DIR_EXECUTABLE = .
DIR_INSTANCE = .
Accessibility of Message Servers
rdisp/mshost = <EP_CI_IP_address>
ms/http_port = 8104
SAP Web Dispatcher Parameter
wdisp/auto_refresh = 25
wdisp/max_servers = 100
wdisp/shm_attach_mode = 6
configuration for default scenario (medium size)
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
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 500
wdisp/HTTPS/max_pooled_con = 500
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=8100
icm/server_port_1 =
SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt,PORT=8100
WebDisp:wdpadm 16> sapwebdisp pf=sapwebdisp.pfl -checkconfig
Checking SAP Web Dispatcher Configuration
=========================================
maximum number of sockets supported on this host: 8192
Server info will be retrieved from host: <EP_CI_IP_address>:8104 with protocol: http
Checking connection to message server...OK
Retrieving server info from message server...OK
Message Server instance list:
------++--
+
instance name
hostname
HTTP port
HTTPS port
------++--
+
J2EE37031000
sappqxx03
50300
50301
J2EE53924900
sappqxx05
50500
50501
------++--
+
Checking ABAP servers with URL "/sap/public/icman/ping":
no server group "!DIAG" defined
Checking J2EE servers with URL "/index.html":
Checking J2EE server sappqxx03:50300...OK
Checking J2EE server sappqxx05:50500...OK
Web Dispatcher configuration for J2EE only system: No server group !DIAG defined
On double stack systems, configure Web Dispatcher to accessMessage Server of SAP Web AS ABAP
Check ended with 0 errors, 0 warnings

Hi,
We wish to configure SAP Web Dispatcher (WDP) as a reverse proxy. For this we've installed using sapinst SAP Web Dispatcher Version 7.00.11, multithreaded, ASCII, 64 BIT Patch Level 140 which was manally updated to Version 7.10.1, multithreaded, ASCII, 64 BIT Patch Level 152.
The SAP WDP server is in DMZ whereas the Enterprise Portal servers are in the intranet.
The updated SAP WDP is available in /sapmnt/<SID>/exe and not in a seperate directory (/usr/sap/<SID>/sapwebdisp) as per SAP note 908097. The SAP WDP has been installed on a standalone machine with instance number 00.
I've configured the Sap WDP with the -bootstrap option. The -checkconfig option completes with 0 warning 0 errors.
The TCP ports between SAP WDP and Enterprise Portal 7.0 SP14 servers are opened in the firewall confirmed as per note 552286. Also, required ports 22 & 8100 are opened from my computer to the SAP WDP Server.
Yet when I try to connect to the administrator interface with the URL http://<Web_Disp_IP>:8100/sap/wdisp/admin/default.html, I receive the following text on the browser:
Network Error (tcp_error)
A communication error occurred: "Operation timed out"
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
Similar message is received even if the SAP WDP is installed in a seperate directory.
Has anyone come across a similar issue?
Thanks.
Regards.
SAP Web Dispatcher Profile generated by bootstrap
SAPSYSTEM = 00
DIR_EXECUTABLE = .
DIR_INSTANCE = .
rdisp/mshost = <EP_CI_IP_address>
ms/http_port = 8104
wdisp/auto_refresh = 25
wdisp/max_servers = 100
wdisp/shm_attach_mode = 6
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
wdisp/HTTP/max_pooled_con = 500
wdisp/HTTPS/max_pooled_con = 500
icm/server_port_0 = PROT=HTTP,PORT=8100
icm/server_port_1 =
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt,PORT=8100
Brief output of checkconfig
Maximum number of sockets supported on this host 8192
Server info will be retrieved from host EPHostIPAddres 8104 protocol http
Checking J2EE server sappqxx03:50300...OK
Checking J2EE server sappqxx05:50500...OK
Web Dispatcher configuration for J2EE only system: No server group DIAG defined
Check ended with 0 errors, 0 warnings

SAP Web dispatcher not forwarding incoming HTTP portal sessions.

Hello,
We are using an EP6 Portal from which Abap Web dynpros are launched. The incoming http sessions were accessing our backend ECC6 SAP system through the sap server message . The http sessions were badly dispatched between the two abap servers. We have been advised by SAP to use the sap web dispatcher instead.
The sap web dispatcher has been correctly installed and configured (on the central abap instance ).
I have carefully read the SAP help section concerning the server selection using the sap web dispatcher :
http://help.sap.com/saphelp_nw04s/helpdata/en/5f/7a343cd46acc68e10000000a114084/frameset.htm
All our settings seem to be OK :
The incoming HTTP requests are forwarded to abap servers only.
*In transaction SICF, all the services under the tree
sap/public/icf_info have been assigned to the same logon group .
The capacity of the two servers included in the logon
group " is the same :
server40 LB=12
server60 LB=12
In the Web interface, capacity equal "1" for the two servers.
wdisp/load_balancing_strategy= weighted_round_robin
In the SAP web interface, the prefered server is ALWAYS the same :
Status of Server Group "LOADIS"
Loadbalancing Information
Number of Servers in this group 2
Last used Server
Preferred next Server server40_SPA_10
But it seems that the sap web dispatcher is not used at ALL.
The Load distribution is still based on the SMLG workload as it was the case, before, with the sap message server. The information displayed in the web interface (preferred server) is wrong.
The Preferred next Server is ALWAYS server40_SPA_10 (shown in the web interface), but, in fact, the http sessions are distributed between the two servers server60_SPA_00 and server40_SPA_10 depending on the server quality diplayed in transaction smlg. It was exactly the same behaviour we had before, only with the sap server message .
Any useful help would be highly appreciated.
Best Regards.

Hi,
firstly, have you checked note 1094342? What variant do you want to use? Do you terminate a SSL connection on web dispatcher and create a new one between web dispatcher and application server? It looks like the web dispatcher can't verify SSL certificate used by application server. Maybe you've already tried this but you can try to turn off SSL between dispatcher and application server. If this setup works then problem is in SSL connection. You can check what host name is used in SSL certificate and what host name is used by dispatcher. You can use parameter wdisp/ssl_certhost which sets host name which will be used for certificate validation.
Cheers

Single point of failure for web dispatcher

Hi
I need advise on how can i resolve single point of failure for web
dispatcher in case the web dispatcher goes down on another system, what
are the alternative which can be used to avoid this.
In our enviroment we have db server with two application server and web
dispatcher is installed on db server and i need to know what can i do when
the web dispatcher on db server crashes and cannot be restarted at all.
We are running oracle 10.2.0.2.0 on AIX 5.3.
Regards,
Codlick

Hi Codlick,
the answer is, you cannot (switch to two web dispatchers).
If you want to use two web dispatchers, they need something in front, like a hardware load balancer. This would actually work, as WD know their sessions and sticky servers for those. But remember you always need a single point for the incoming address (ip).
Your problem really is about switchover groups. Both WD need to run in different switchover groups and need to switch to the same third software. I'm not sure if your switchover software can handle this (I'm not even sure if anyone can do this...), as this means the third WD needs to be in two switchover groups at the same time.
Hope this helps,
Regards,
Benny

SAP Web Dispatcher in Front of EP6 SP2?

For increased network security, is it possible to put a Web Dispatcher in front of an EP6 SP2 J2EE engine?
The Web Dispatcher would be in the DMZ with the J2EE in the next layer of the DMZ.
If so, is is also possible to have a Web Dispatcher then XI server?
If the above are not possible, what is the best solution?
Thanks.

If you are referencing SAP Web Dispatcher, then yes, your scenarios are possible. Usually, the XI server would be located where the SAP Portal apps would be. You can read,
http://help.sap.com/saphelp_nw04/helpdata/en/42/5cfd3b0e59774ee10000000a114084/frameset.htm
If you are refering to just a web dispatcher (ISA, IIS), it typically resides infront of your Apps (i.e. Portal, XI).
Regards,
James

Retrieving ServerHost and ServerPort in Server with Web Dispatcher

Hi,
I am using IWDRequest to get server host and port in my Web Dynpro DC.
This is the code which I am using for it.
IWDRequest req = WDProtocolAdapter.getProtocolAdapter().getRequestObject();
String l_str_host = req.getServerName();
int l_int_port = req.getServerPort();
In our NW landscape, some servers have Web Dispatcher for load balancing purpose. Hence in this case, what would I get in l_str_host, l_int_port ?
I need them to prepare KM URL to a specific location.
Thanks and regards,
Amey Mogare

Hi,
I finally managed to achieve it through following :-
IURLGeneratorService ug = (IURLGeneratorService)ResourceFactory.getInstance().getServiceFactory().getService(IServiceTypesConst.URLGENERATOR_SERVICE);
l_str_kmurl = ug.getAbsoluteUri(PathKey.CONTENT_ACCESS_PATH).toExternalForm()

Apache Server Sizing and Web Dispatcher filtering

Hi,
We are planning to expose our intranet portal for internet user. An internet user would access it via browser (https) -> Apache - reverse proxy (outer DMZ) -> Web Dispatcher - Load Balancing (Inner DMZ) -> Portal.
We are looking for end-to-end SSL implementation.
My questions:
1] Do we need to have load balancing at apache server for performing reverse proxy? If yes, how it would be achieved?
2] What is the hardware sizing required for Apache server on Linux box?
3] Does the portal performance is affected by end-to-end SSL implementation?
4] In load balancing using Web Dispatcher, can we forward particular request to a specific application server? Like, filter out the internet requests or forward BI related requests to a specific application server node.
Regards,
Sham

Hi,
1) Depends on your requirement. When you have 1 Apache RP and 1 SAP Web Dispatcher, you won't need load balancing of at the Apache.
2) Depends on the number of concurrent requests you are expecting. More information on that can be found at apache.org
3) Portal performance gets affected when using SSL and the portal is responsible for the SSL (there are product out there that do the SSL handling). How much the SSL will affect your portal depends on the number of users. But generally the impact of SSL isn't really high with recent hardware, the portal will be more occupied with the number of users, navigation, etc than with SSL
4) You can use logon groups to assign a specific user (group) to a dedicated server
br,
Tobias

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 Connection to another host if Message Server not reached

Hi Folks,
Basically, the SAP Web dispatcher gets information which it needs for load distribution from the message server. If the message server is available the web dispatcher connects itself using the parameter rdisp/mshost.
May i know if there is any parameter to enable connection to another host in case of e.g. a hardware failure and the message server is not able to receive any quests anymore from the web dispatcher?
Regards,
Collosis

Hi,
>May i know if there is any parameter to enable connection to another host in case of e.g. a >hardware failure and the message server is not able to receive any quests anymore from the web >dispatcher?
There is no such parameter and it would not make any sense. There is only one Message server to connect to.
If you need High availability you need to suppress the SPOFs.
The Message server is one, the web dispatcher is another one.
For this need, my CI and my web dispatcher are clusterised with MSCS.
Regards,
Olivier

Add aditional SAP web dispatcher on Server

Hi expoerts,
Could you guide me how to add an aditional web dispatcher on AS ABAP + Java?
My AS is a Windows 2003 x64 with SQL Server 2005.
Thanks!

Hope below docs will help you
http://sapbasis-admin.blogspot.com/
/message/7660921#7660921 [original link is broken]
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/99d42fee2b73e7e10000000a42189b/content.htm
Note 538405 - Composite SAP Note: SAP Web Dispatcher
Note 928952 - Web Dispatcher Installation based on NW 7.0(2004s)
regards
nag

Accessing portal server with virtual host via web dispatcher

Hi,
I have portal installed at http://hostname.com:50000. A web dispatcher is installed in front of it which uses port number 80 and redirects to http://hosname.com:50000.
so when i say http://hostname, my web dispatcher redirects to http://hostname.com:50000/ from where i can access my portal.
now I want to create an alias for my hostname, say when user types http://mydev, it should redirect to http://hostname.company.com thru webdispatcher.
so i created virtual host for my portal server . how to use this in my virtual hosts in my webdispatcher.
I have already gone throug this..
http://help.sap.com/saphelp_erp2005/helpdata/en/fe/cda776f2f64d5287c614b2f715c25f/frameset.htm
would be great if some one can help me in this regard.
Thank you
P.S: I dont want to create a DNS alias with name mydev, then i think virtual host concept doesnt make sense, atleast in java engines..which has different concept in SAP systems.

HI Jacob,
Thank you for the reply.. I am little bit confused.could you please clarify the followint to me.
My requirement is when user types "http://epdev", it should redirect to http://hostname.company.com:50000
1. To do that, according to what you said, I will create a DNS alias epdev to the IP address where my portal is hosted. so when the user types http://epdev, I have set up a parameter in web dispatcher profile to redirect to http://hostname.company.com:50000/.. so my requirement is fulfilled now..I hope this the correct proc for what I intended to achieve. am I right?
2. As said above, I am using web dispatcher only for redirection to a fully qualified name, as portal requires as fully qualified domain name. Is there a possibility other than web dispatcher for redirection.
3. if the above procedure works, I got a question like..what is the use of "virtual hosts".
How is it different from creating for instance, creating as many DNS aliases to IP address.
Although, it was explained at http://help.sap.com/saphelp_erp2005/helpdata/en/0b/fbf5a47928f84e8d0beba8371508e6/frameset.htm
I didnt clearly understand it.
I would really appreciate, if you could clarify these to me.
Thank you

Portal and web dispatcher

Please i need your help, i´am new in this and i´am trying to run the portal on internet with the web dispatcher, i already get the wd work, and i can see the admin page.
I have de wd running on a web server (saphost1) in standalone mode,(when i configured the wd i gave the portal message server port, and the name of the host in which the portal is running), and the portal running in other server (saphost2) in an ABAP+JAVA WebAS,
i want to access the portal through the wd but i don´t know how to do that (redirect the url from saphost1:/irj/portal) , i searched in the docs but i haven´t found something.
Please help me i really need to get this done the sooner as possible
Thanks
Coatl

Hi Martin!!!
Thank you very much, that was just what i was looking for. i have another doubt, i done everything that the SAP Library says, but when i try to display the portal, i get the next error:
500 Dispatching Error
Error: -26
Version: 7000
Component: HTTP_ROUTE
Date/Time: Wed Feb 14 12:46:58 2007
Module: http_route.c
Line: 3122
Server: acsservicios__00
Error Tag:
Detail: no valid destination server available for '!ALL' rc=13
In the sapwebdisp.pfl i have the next values:
Profile generated by sapwebdisp bootstrap
unique instance number
SAPSYSTEM = 6
add default directory settings
DIR_EXECUTABLE = .
DIR_INSTANCE = .
Accessibility of Message Servers
rdisp/mshost = acslobot.advanced.local
ms/http_port = 8106
use static description files for logon groups: group info
wdisp/group_info_location = file:
icrgroups.txt
use static description files for logon groups: url prefixes
wdisp/url_map_location = file:
urlinfo.txt
#maximum number of concurrent connections to one server
wdisp/HTTP/max_pooled_con = 500
wdisp/server_info_location = file:
C:\SAPWebDisp\icrgroups.txt
wdisp/HTTPS/max_pooled_con = 500
SAP Web Dispatcher Ports
icm/server_port_0 = PROT=HTTP,PORT=8006
SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/icm/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt
icm/HTTP/redirect_0 = PREFIX=/, TO=/irj/portal
when i aces to de address: <webdisphost>:8006/...i get the mentioned error, where 8006 is the port where the wd listen, but when i try to aces the url <webdisphost>:8006 it says that the page cant be found
What can be grown with my configuration....please need your help
Coatl

Web Dispatcher on XI Server

Similar Messages

Maybe you are looking for