Redirect web dispatcher to java nwa

Hello all,
Can you suggest me: how can I redirect from web dispatcher link host:port/ to  java link host:port/nwa
I used:
icm/HTTP/redirect_0 = PREFIX=/, TO=host:port/nwa
icm/HTTP/admin_0 = PREFIX=/,DOCROOT=$(DIR_DATA)$(DIR_SEP)icmandir,AUTHFILE=$(icm/authfile),PORT=8100
Thx
Chris

Hi Chris,
Did you check this link?
Examples
Parameter Value
Description
icm/HTTP/redirect_0 = PREFIX=/, TO=/bc/bsp/demo/default.html
Access attempts on "/" are redirected to "/bc/bsp/demo/default.html".
icm/HTTP/redirect_0 = PREFIX=/, FROM=/mime/*,HOST=mimeserver, PORT=8080
Only requests with specific URL patterns are redirected to HTTPS
icm/HTTP/redirect_0 = PREFIX=/sap/bc/bex, FROMPROT=http, PROT=https, HOST=px155.sap.com
Only requests with a specific URL are redirected to HTTPS
icm/HTTP/redirect_0 = PREFIX=/, FROM=/sap*, FROMPROT=http, PROT=https, HOST=px155.sap.com
Only specific HTTP requests are redirected to HTTPS
icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, PROT=https, HOST=px155.sap.com
All HTTP requests are redirected to HTTPS
icm/HTTP/redirect_0 = PREFIX=/, FROM=/mime/*,FOR=crm.sap.com*,HOST=crmserver, PORT=80
Requests with the URL prefix /mime/ and the HTTP header field HOST that matches the pattern crm.sap.com:* are redirected to the server crmserver:80.
icm/HTTP/redirect_<xx> - SAP Web Dispatcher - SAP Library
THanks and Regards,
Vimal

Similar Messages

  • Getting connection error after installing Web Dispatcher for JAVA engine

    Hi SAP Guru's,
    I have installed Web Dispatcher instance on solution manager server machine for Production JAVA portal. I am getting below error when I am trying to access Production JAVA portal.
    500 Dispatching Error
    Error: -26
    Version: 7000
    Component: HTTP_ROUTE
    Date/Time: Sat Feb 05 16:18:12 2011 
    Module: http_route.c
    Line: 3139
    Server: ERPSOL_WDP_04
    Error Tag:
    Detail: no valid destination server available for '!ALL' rc=13
    Where as I have define all suitavle parameters in Web Dispatcher instance profile
    SAPSYSTEMNAME = WDP
    SAPGLOBALHOST = ERPSOL
    SAPSYSTEM = 04
    INSTANCE_NAME = W04
    DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
    DIR_EXECUTABLE = $(DIR_CT_RUN)
    Accesssability of Message Server
    rdisp/mshost = sapepjlg.pdilnoida.com
    ms/http_port = 8102
    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=8105
    Please help on this as I have to deliver this before go live.
    Regards,
    Bijay

    Hi Bijay,
    Please check if services /public/icman, /public/icm_info are active & accessible in SICF(in case of Dual stack system) tx.
    Regards,
    Neeraj

  • 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.

  • Need help in web dispatcher settings for redirect

    Hello All!
    I need to redirect users from one URL (http://webdispatch:port1/abc/efg) to another (http://host2:port2/abc/efg) but URL in browser must stay unchanged (http://webdispatch:port1/abc/efg) after redirect. As I think server should get requested URL from browser, internally redirect to URL #2 and send response of URL #2 to browser.
    I've set up Web Dispatcher for redirecting by using parameter icm/HTTP/redirect_0, but now URL in browser is changing with http://host2:port2/abc/efg
    icm/HTTP/redirect_0 = PREFIX=/,FOR=webdispatch:,FROM=/sap/bc/webdynpro/sap/zwd_rep,HOST=host2,PORT=port2
    How I can do it?
    Helpful answers will be appreciated
    Regards, Lev

    Thanks for your replies.
    I've tried to comment wdisp/permission_table parameter but it had no effect. And it seems that I've made a mistake: I forgot to comment icm/HTTP/redirect_0 while tested work of icr file.
    I have:
    web dispatcher at webdisp_host:1090
    host with ABAP+Java instance at inst_host
    icm/HTTP/redirect_0 commented
    use icr file:
    >Version 1.0
    >SYS
    >J2EE crmdev.oao.sng 8010 DIA=2
    At inst_host I has two apps:
    /b2b_sng/ ( inst_host:50000/b2b_sng/ )
    and /sap/bc/* ( inst_host:8010/sap/bc/webdynpro/* )
    webdisp_host:1090/b2b_sng/ works fine.
    webdisp_host:1090/sap/bc/webdynpro/* don't work:
    500 Dispatching Error
    Error:     -26
    Version:     7000
    Component:     HTTP_ROUTE
    Date/Time:     Mon Dec 01 17:41:24 2008
    Module:     http_route.c
    Line:     3121
    Server:     crmdev_WDC_30
    Error Tag:     
    Detail:     no valid destination server available for '!ALL' rc=13
    Slava,
    > 8010 is probably an HTTP message server port.
    I think no since inst_host:8010/sap/bc/webdynpro/* working fine.
    Parameters
    > rdisp/mshost = crmdev.oao.sng
    > ms/http_port = 8010
    has been already added into profile, but http_port = 8101 instead 8010

  • 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.
    Isn’t there a way out of this struggle?
    Thanks all of you for your great contribution to the situation.
    Regards,
    Taner

  • Web dispatcher URL redirect

    Hi ,
    We have web dispatcher which is used for accessing portal and fiori using public url as below .
    https://fiori.xyzcorp.com
    https://portal.xyzcorp.com
    But when they're trying to access via internet portal url goes to https://portal.xyzcorp.com/startPage by default it should route to irj/portal
    Same for Fiori also I'm using the  ICM redirect parameter still can't access
    icm/HTTP/redirect_0 = PREFIX=/, FOR=portal.xyzcorp.com:*, TO=/irj/portal,
    icm/HTTP/redirect_1 = PREFIX=/, FOR=Fiori.xyzcorp.com:*, TO=/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=800&sap-language=EN,
    Could you please share you thoughts?

    Hi Krishna,
    Please go through below doc
    SAP webdispatcher and URL redirect?
    icm/HTTP/redirect_&lt;xx&gt; (SAP Library - SAP Web Dispatcher)
    BR
    Atul

  • Web Dispatcher and SSL on ABAP+Java

    Hello,
    Have installed SAP web dispatcher on WAS 6.40 ABAP+Java system. Communicating with Portal SP16 system.
    The HTTP works fine. Have not been able to get SSL working with web dispatcher.
    For troubleshooting activated ITS on this system and HTTPS works fine with ITS webgui.
    Have followed the "how to" SSL for web dispatcher guide.
    Also should mention that we have generated certificate requests and PSE's but our organization has not yet chosen a certificate authority to sign the cerficates. For other scenarios (log onto Portal, XI, etc) the only difference is the certifcate warning dialog, otherwise works fine.  Would this cause a problem for Web Dispatcher?
    Trying the SSL end to end scenario receive
    WARNING: Could not start service 0 for protocol HTTPS on host "max-sap" on all adapters
    Is there anything
    unique for the ABAP+Java configuration?
    Thanks,
    Alan

    I solved this problem by setting the following profile parameter on my webdispatcher profile.
    wdisp/ssl_ignore_host_mismatch = true
    Doesn't fix the underlying problem but got me going until I can figure it out.

  • Web Dispatcher configuration (ABAP+Java vs. ABAP+Portal)

    We are using an internal Web Dispatcher to allow the connections from different networks.
    This Webdispatcher entry we add to WAS configuration within Portal system object
    By defintion of ABAP+Java double stack we do not have any problems and the test
    http://webpispatcher:port/sap/bc/ping is successful.
    When we have a ABAP system + Portal (Java) we only can test the connection
    http://webpispatcher:port/
    When we execute the test
    http://webpispatcher:port/sap/bc/ping we get an error, because the url goes to Java stack.
    We also detected that on Web Dispatcher configuration for ABAP+Java we have ABAP and J2EE server groups and  application servers.
    For ABAP+Portal we have only J2EE groups on Web Dispatcher configuration.
    Question:
    Which SAP parameter (e.g. ms/server_port_0, icm/HTTP/j2ee_0) or Web Dispatcher parameter (ms/http_port) is responsible for generation of ABAP groups (e.g. PUBLIC) within Web Dispatcher?

    Which SAP parameter (e.g. ms/server_port_0, icm/HTTP/j2ee_0) or Web Dispatcher parameter (ms/http_port) is responsible for generation of ABAP groups (e.g. PUBLIC) within Web Dispatcher?
    In ABAP the logon group is handled by the ICF. In SICF you specify within the actual services(properties) which logon group that service should use for load balancing. As far as I remember though there is an exception if you are using an "end-to-end" ssl configuration where you can specify the destination logon group using wdisp/HTTPS/dest_logon_group parameter.
    rdisp/mshost is the parameter on your web dispatcher that points to your message server to get a list of available logon groups.
    Nelis

  • URL redirect to ECC through web dispatcher

    Hi,
         I need to forward the  link
    http:// 85.89.237.93/zincontact?sap-client=200?opid=$(operatorid)?cli=$(cli)?qid=$(queueid)?dato=$(startcalldate)?  viderefort=$(forwarded)
    to
    http:// vindevde1:8020//zincontact?sap-client=200?opid=$(operatorid)?cli=$(cli)?qid=$(queueid)?dato=$(startcalldate)?viderefort=$(forwarded)
    where vindevde1 is ECC box.
    Here operatorid , queueid , startcalldate  will change in runtime.
    I set the parameter icm/HTTP/redirect_0 as given below.
    icm/HTTP/redirect_0 = PREFIX=/zincontact?sap-client=200?opid=$(operatorid)?cli=$(cli)?qid=$(queueid)?dato=$(startcalldate)?viderefort=$(forwarded) ,
    TO=/zincontact?sap-client=200?opid=$(operatorid)?cli=$(cli)?qid=$(queueid)?dato=$(startcalldate)?
    viderefort=$(forwarded),HOST=vindevde1,PROT=HTTP,PORT=8020
    Please help me on this.
    Sandip

    Hi again,
    >Now is it possible to access the service through url http://85.89.237.93 from internet or I have to use http://vinweb01:8101/ as >in web dispatcher server ?
    Sorry but you are really difficult to understand.
    If you want to access your ECC system from the internet through the web dispatcher, the web dispacher should be in a DMZ and have 2 IP address : 1 published on the internet and one to access the internal network.
    Usually you would configure the web disptcher to listen on the standard ports 80 for HTTP and 443 for HTTPS.
    If vinweb01 is the name of your web disptcher as published on internet DNS, you would access to ECC with the URL
    http://vinweb01.
    All of this is explained in detail in help.sap.com. You should really read the documentation...
    Regards,
    Olivier

  • 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

  • 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

  • Web Dispatcher not doing the load balancing on the portal

    Hi Experts
    I am having a production issue where the SAP web dispatcher is not doing the load balancing on the portal.
    We have ESS/MSS portal with 1 Message server and 2 Application servers. The Web dispatcher is installed on the message server itself. Here is my Web disp profile file
    Profile generated by sapwebdisp bootstrap
    unique instance number
    SAPSYSTEM = 16
    add default directory settings
    DIR_EXECUTABLE = .
    DIR_EXECUTABLE = F:\usr\sap\<SID>\sapwebdisp
    DIR_INSTANCE = .
    Accessibility of Message Servers
    rdisp/mshost = <hostname>.com
    ms/http_port = 8111
    #Log and Trace
    rdisp/TRACE = 2
    SAP Web Dispatcher Parameter
    wdisp/auto_refresh = 120
    wdisp/max_servers = 100
    wdisp/shm_attach_mode = 6
    configuration as per SAP note 538405
    icm/max_conn      = 7000
    icm/max_sockets   = 14000
    icm/req_queue_len = 6000
    icm/min_threads   = 100
    icm/max_threads   = 300
    mpi/total_size_MB = 500
    mpi/max_pipes       = 14000
    wdisp/HTTPS/max_pooled_con = 7000
    SAP Web Dispatcher Ports
    icm/server_port_0 = PROT=HTTP,PORT=8888
    SSL
    icm/server_port_1 = PROT=ROUTER,PORT=443, TIMEOUT=60
    SAP Web Dispatcher Web Administration
    icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin,AUTHFILE=icmauth.txt
    wdisp/enable_j2ee_groups = TRUE
    wdisp/HTTPS/sticky_mask = 255.255.255.255
    In my Web dispatcher Admin page, I see all the three application servers, however the requests are going to only 1 App server. We are using ENd to End SSL configuration for the web dispatcher.
    We also have a reverse proxy in the landscape and reverse proxy is forwarding all the requests to the Web dispatcher. In Web disp Admin page>Dispatching Module>SSL End to END dispatching, I see only ONE table entry in the dispatching table and it is our Reverse Proxy.
    As all the requests are coming from only one source (Reverse proxy), it seems to me that the sap web dispatcher  is forwarding those to the same Application server every time.
    Can anyone please advise ?
    I also tried to configure logon group in NWA, the web dispatcher is detecting the logon group and all the app servers in the logon group. It still not doing the load balancing.
    I would greatly appreciate any help.
    Thanks
    Viny

    Vincent, can you please elaborate more ?  Is the web dispatcher not able to recognize stateful and stateless application requests ?
    I saw that the procedure for configuring SSL Termination on Web dispatcher is long and complicated and looks like SAP web dispatcher needs to have SSL certificate of its own. As we have no ABAP servers and only Java servers, I can not even create the PSEs using STRUST (as described in SAP help -http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/99c388d7c46bb9e10000000a42189d/frameset.htm
    We already have SSL certificates for Java App servers.
    I suppose there should be a way for web dispatcher to identify the incoming requests and forward to appropriate application servers.
    Any help is much appreciated.
    Thanks
    Viny

  • 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

  • Error in Web Dispatcher

    Hello,
    SAP web dispatcher is down.
    Log dev_sapwebdisp:
    Thr 11068] Mon Jun 08 11:56:35 2009
    [Thr 11068] *** ERROR => no valid destination server available for '!J2EE' rc=13 [http_route.c 3126]
    [Thr 11068] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3146]
    [Thr 11068] *** WARNING => original destination was '!J2EE' [http_route.c 3149]
    [Thr 11068] *** ERROR => no valid destination server available for '!ALL' rc=14 [http_route.c 3126]
    [Thr 11068] *** WARNING => redirect failed request to foreign destination '!ALL' [http_route.c 3146]
    [Thr 11068] *** WARNING => original destination was '!ALL'
    Thanks.

    I am very happy to know it, thank you !
    That's is funny, you got a wicked sense of humor!
    Is there a question in your message ?
    I am sorry, is this twitter, where you just blog your updates? No! this a forum where you come if you have problems. Sometimes, you are over burdened with problems and you forget to mention "Please help" or any other obligatory line, requesting a solution. But any considerate person with even half a brain should understand that.
    It's a very commonplace mistake and you exactly know that I have a problem and I am seeking help here.
    Instead of trying to act over-smart and arrogant, you could have easily ignored the post and moved on.
    If you want answers, you should learn how to post questions on a forum...
    You may be an administrator/moderator here, Sir, but you lack the very basic skills of humility and understanding.

  • SAP Web Dispatcher Configuration in a FPN

    Hi all,
    We are using SAP Web Dispatcher 720 (latest patch 85).
    We are having a FPN network. One consumer portal, with  more than 5 producer portal (ECC JAVA, BW JAVA..etc) and more than 5 different backends (ECC, BW, SRM..etc)
    We are using SSL termination at the web dispatcher.
    We have configured all our consumer, producer, backends in  our web dispatcher instance,  to use the domain name with different ports.
    Eg :
    https://domainname.com - refers to our consumer portal
    https://domainname.com:7110 - refers to our producer portal 1
    https://domainname.com:7111 - refers to our producer portal 2
    https://domainname.com:6100 - refers to our ABAP backend system 1
    https://domainname.com:6111 - refers to our ABAP backend system 2 ..etc..,
    by configuring so, we are facing lots of page not found issue intermittenly, as SAPlb cookies are passed incorrectly, since all refers to the same domain name (it ignores the different ports).
    Can someone helps us to narrate how to configure web dispatcher which suites our  FPN network. We can't go for different URLs for each system, as it requires more than 16 URLs and 16 web dispatcher instances.
    Can someone share their experience
    Thanks & Regards
    Senthil

    Hello Ravi,
    Try to include directory 'admin' within directory
    'sapwebdisp'.
    You can let sapwebdisp create a sapwebdisp.pfl on your
    behalf with option '-bootstrap'.
    You will see the password for user 'icmadm'.
    and this line
    "icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin"
    Then you use URL
    'http://sapwedisphost:<xxxx>/sap/wdisp/admin/default.html'
    See this documentation in
    'http://help.sap.com/saphelp_nw04/helpdata/en/b4/9aa8862e714e6db8e74e48e5d3283b/frameset.htm'
    (specially topic "Monitoring ..."
    Kind Regards,
    Toni

Maybe you are looking for