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

Similar Messages

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

SSL Re-encryption with Portal and Web Dispatcher: certificate expired

Hello,
I am trying to set up HTTPS connection to the Portal through SAP Web Dispatcher. We are using SSL Re-encryption. I think I got everything set up correctly. When trying to access through a Web browser the web dispatcher trace file shows error message 'certificate expired'. Looking at the Portal (Visual admin - Keystore) I am pretty sure it is the service-ssl with localhost. It is expired. Two questions:
- is it correct that it uses localhost or am I missing anything?
- How would I recreate the certificate? (I am sure it is somewhere in the Online documentation, but haven't found it yet). Can I do this while the Portal is productive without breaking the normal access (http) to the Portal. This is our Production portal.
Thanks,
Ingrid

Hi,
Go thru the contents of SAP Note,
685306 -Enabling SSL and renewing the J2EE certificate
And also the help contents in,
http://help.sap.com/saphelp_nw04/helpdata/en/65/6a563cef658a06e10000000a11405a/content.htm
These might of some help to you !
Regards
Srinivasan T

Could not connect to backend system through portal via Web Dispatcher

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

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

Search fails when accessing portal over HTTPS

Dears,
We want to use the Ajax framework page within our company.
We activated the standard deliverey and during our first tests we see that the search functionality does not work correctly.
Scenario:
1) we access our portal on https://portal.company.com/irj/portal
2) When we type in our search query and click [Go] we get a pop-up but the URL called is:
http://portal.company.com/irj/portalapps/com.sap.portal.navigation.helperservice/html/child.html
Findings:
- When we access our portal over HTTP the search is working fine with the ajax frameworkpage.
- when we use the 'old' defaultframeworkpage search is working fine when connecting through HTTPS
- to enable HTTPS we pass through a proxy server, HTTPS is not managed by the JAVA WAS
Anybody faced similar problem and was able to solve this?
Many thanks,
Geert

Hi,
I would say that it hast to do with the URL Generation configuration of KM, but as it works for the old iview then this is strange behaviour. So I think it is a bug... this seems a call of an absolute url instead of a relative url.
I would advise you to report is as a bug via a SAP OSS message...
Cheers,
Benjamin

Error when configuring Web Dispatcher for SSL with Enterprise Portal

We are in the process of configuring the Web Dispatcher using SSL to connect to our Enterprise Portal (the Web Dispatcher will be in the DMZ). We have followed all of the help.sap.com guides and now have SSL listening on the EP side (port 8103). We are now receiving this strange certificate error when we start the Web Dispatcher:
[Thr 5332] Tue Mar 20 00:36:23 2007
[Thr 5332]   MatchTargetName("<FULLY QUALIFIED HOSTNAME>", "CN=XXX, OU=XXX, O=XXXX, C=XX") FAILS
[Thr 5332]   SSL socket: local=<IPADDRESS>:4742 peer=<IPADDRESS>:8103
[Thr 5332] <<- ERROR: SapSSLSessionStart(sssl_hdl=009D7670)==SSSLERR_SERVER_CERT_MISMATCH
[Thr 5332] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-30): SSSLERR_SERVER_CERT_MISMATCH [icxxconn.c 2005]
[Thr 5332] *** ERROR => IcmConnClientRqCreate() failed (rc=-14) [icrxx.c      4919]
[Thr 5332] *** ERROR => Could not connect to SAP Message Server at <FULLY QUALIFIED HOST NAME>. URL=/msgserver/text/logon?version=1.2 [icrxx.c      2301]
[Thr 5332] *** ERROR => rc=-1, HTTP response code: 0 [icrxx.c      2302]
[Thr 5332] *** ERROR => see also OSS note 552286 [icrxx.c      2303]
We have gone through the trouble shooting note 552286 as listed in the error above. Any assistance is appreciated.

Hello, did you receive any resolution for this problem? We are receiving a similar error and I am unsure of how to resolve.

Reverse Proxy in web dispatcher

Any statistic on which product is better / qualifies better to be used as a reverse proxy.. (& wherein generic (forward) proxy services can be disabled)
Web Dispatcher
Apache
Microsoft IIS
Any other product ?
Thanks,

Thanks !!!
> URL filtering: the Web Dispatcher 7.2 supports more than one SAP backend, but you should take a look into the confguration page at SAP Help to find out if it matches your future scenario.
I am looking for WD based on 7.3 for both the roles (Reverse proxy and load balancing). But I'll check if there is anything for me to be concerned about...
> looking at your scenario, you'll have at least 1 reverse proxy in your DMZ and the Web Dispatcher will be an additional reverse proxy (for internal and/or external access).
>
> The Web Dispatcher will be connected to the message server of the portal, so when a server/node goes down, the web dispatcher will be notified. That's a vantage over another reverse proxy.
Yes, we have one server reserved for reverse proxy software and another for load balancing (WD).. These two roles need to be on separate servers as per logistics requirement... So, is this what you are talking about..
User <> WD as reverse proxy on server1 <> WD for load balancing server2 <--> EP Message Server.

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

Exposing Portal over Internet

Hi,
We have implemented SAP modules like SRM, BI and HR in our landscape and Portal is the single point for accessing all the available functionalities. Now, we want to access the portal from Internet WITHOUT MAKING OTHER SYSTEMS accessible because of security reasons. With this, I am not able to access SRM applications because it tries to connect to Web AS of SRM system as configured in System Object of Portal.
Please let me know the way or method used in accessing Portal over Internet.
Thanks,
Iftekhar

Hi Iftekhar,
The ideal scenario should be configuring a reverse proxy which can be place in a DMZ zone. The Reverse proxy will be use to write the rewrite rules.
Also to ensure the security a SSL implementation is highly recommended.This can be through out the landscpe or from the internet cloud to the reverse proxy depends on the requirement.
You can find a tons of material in SDN for configuring reverse proxy and SSL in the landscape.This could be starting point for configuring reverse proxy.
[The Reverse Proxy Series -- Part 1: Introduction]
and for SSL you can follow this [ADS SSL configuration journal I. / ABAP -> JAVA / 640 - 70x]
Regards
Indranil

How to monitor the load on web dispatcher

We have implemented a web dispatcher in our landscape for our portal production servers. We have 3 application servers that are being accessed through the web dispatcher. Sometimes users get the error "Service Temporarily Available" when accessing the portal. How do i check the load on the web dispatcher. Which is the parameter that sets the maximum number of connections?
Regards,
Sridevi

To be able to administrate the SAP Web dispatcher in the Web interface see [Monitoring the SAP Web Dispatcher|http://help.sap.com/saphelp_nw04/helpdata/en/05/ac923fa5e93c17e10000000a114084/frameset.htm]. To do so, call SAPCAR as follows: SAPCAR u2013xvf icmadmin.SAR
You can find the archive file ICMADMIN.SAR like the SAP Web Dispatcher in the kernel package DW.SAR.
More info u can find: http://help.sap.com/saphelp_nw04/helpdata/en/0b/25453cf1fcc85ee10000000a11402f/frameset.htm
Hope this helps

Web Dispatcher Configuration.

Hi,
1)Our srm server is connected to portal and end-users are using portal to connect to it. Srm server has another 2 other application server for load balancing.
As Load balancing is not happening we are getting ITS memory bottle neck issue.
We have installed Webdispatcher for load balancing but I have confusion how will be connectivity Portal --> SAP Web Dispatcher --> SRM.
2) C:\usr\sap>sapwebdisp.exe -checkconfig pf=c:\usr\sap\sapwebdisp.pfl
Checking SAP Web Dispatcher Configuration
=========================================
maximum number of sockets supported on this host: 32768
Server info will be retrieved from host: CIserver:8100 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
------++--
+
APPS602_PRD_01
APPS602
8001
50101
APPS601_PRD_00
APPS601
8000
50001
CIserver_PRD_02
CIserver
8002
8003
------++--
+
Checking ABAP servers with URL "/sap/public/icman/ping":
Checking ABAP server APPS602:8001...OK
Checking ABAP server APPS601:8000...OK
Checking ABAP server CIserver:8002...OK
Checking J2EE servers with URL "/index.html":
Checking J2EE server APPS602:8001...ERROR: unexpected OK code: 404
ERROR: check if application is deployed and active
Checking J2EE server APPS601:8000...ERROR: unexpected OK code: 404
ERROR: check if application is deployed and active
Checking J2EE server CIserver:8002...OK
Retrieving group info from server APPS602:8001...OK
Defined server groups:
+
group name
#entries
+
!J2EE
3
!J2EES
3
!DIAG
3
!DIAGS
1
!ALL
3
LOGON_PRD
3
+
Retrieving url info from server APPS602:8001...OK
Url map info file "/sap/public/icf_info/icr_urlprefix" is OK
Check ended with 2 errors, 0 warnings
Please advise
Regards
Mazher

Hi All,
I have crossed checked in T-code SMLG still load balancing is not happening
some time getting below warnings in SM21
ITS, New user session denied due to memory bottleneck.
ITS, User session terminated
Can you please advise.
Thanks

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

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

Using web dispatcher for portal and BW access

We currently have SAP's Web Dispatcher installed in our DMZ, which links the outside world to our internal enterprise portal installation. This configuration works fine for portal connectivity (see sapwebdisp.pfl below). However, we have BW reports (BW report iViews and URL iViews) which are accessed via the portal.
I do not know what configuration (if any) needs to additionally be set up on the Web Dispatcher host to allow connectivity. Currently, when accessing a BW report via the portal (coming from the Web Dispatcher) the report request is immediately terminated with an error due to a DNS lookup error (as the BW server is on our internal segment).
The Web Dispatcher is aware of both the internal portal server and BW server IP address and hostname and has the appropriate access (port/firewall) to retrieve these reports. Further, the HTTPURLLOC table is maintained (see example below) on the BW server as recommended in SAP Note 750292 (help file = http://help.sap.com/saphelp_nw04s/helpdata/en/59/31ae42e0fac911e10000000a1550b0/frameset.htm)
However, I can't get BW reports to work remotely. Should Is there something else that should be added to the Web Dispatcher's configuration? Is there something that I should be doing on the iView side (ie. not hardcoding hostname / port to the query string?). Please advise. Thanks!
sapwebdisp.pfl
Profile generated by sapwebdisp bootstrap
unique instance number
SAPSYSTEM = 0
Accessibility of Message Servers
rdisp/mshost = epprd1
ms/http_port = 8101
SAP Web Dispatcher Parameter
wdisp/auto_refresh = 120
wdisp/max_servers = 100
wdisp/add_clientprotocol_header = 1
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=80
icm/server_port_1 = PROT=ROUTER,PORT=443
SAP Web Dispatcher Web Administration
icm/HTTP/admin_0 = PREFIX=/sap/wdisp/admin,DOCROOT=./admin
HTTPURLLOC table (BW):
MANDT
SORT_KEY
PROTOCOL
APPLICATN
FOR_DOMAIN
HOST
PORT
100
10
HTTPS
/SAP/BW/BEX
Internal_host.company.COM
8443
100
20
HTTPS
/SAP/BW/BEX
webdispatcher_host.company.COM
443

Hi James -
We're running EP 6.0 SP16 (WebAS 640 NW04) and BW 3.1/3.2 Content (WebAS 620).

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

Exception accessing portal over web dispatcher

Similar Messages

Maybe you are looking for