Web Dispatcher medium / large configuration

When we install web dispatcher, we are given an option for creating configuration for system of size medium / large...
There is a system installed as medium and I am looking it to adjust for large number of users..
Any help on what parameters will I have to change ?
icm/max_conn =
icm/max_sockets =
icm/req_queue_len =
icm/min_threads =
icm/max_threads =
mpi/total_size_MB =
mpi/max_pipes =
Apart from these, is the any other setting (not only parameter) that should be changed.. memory related etc ?

Hi Jay,
Parameter Settings Dependent on System Size
Depending on which system size you have chosen (s, m or l), different parameter values are written to the profile file. The table below contains these different values.
Parameters                  Small (s)           medium         large
icm/max_conn          100                   500                   16384
icm/max_sockets      1024                 1024                16384
icm/req_queue_len    300                   500                 6000
icm/min_threads       5                       10                   100
icm/max_threads      15                      50                       250
mpi/total_size_MB   100                    500                2000
Please change the above setting in parameter value
If u want more information please find below link
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/877df50e3f2722e10000000a42189d/content.htm
Regards,
K.Ramamoorthy

Similar Messages

Cisco Load balancer and Web Dispatcher to the same portal

Hello Experts,
We have implemented intranet portal with Cisco as the load balancer. Now we need to expose this intranet to the outside world as an extranet portal. So the same portal will be accessed from both intranet and from outside. We are thinking of installing a web dispatcher in the DMZ so that outside users can access the Web Dispatcher URL to access the intranet portal. In effect intranet users will use load balancer and extranet users will use Web Dispatcher to access the same portal. Now my question is if we configure Load Balancer and Web Dispatcher to the same portal, will the portal be able to load balance properly? Is this the right approach?
Thank You,
mansooralip1

Dear Andrew,
We need to provide access to our intranet to some outside companies for them to also use some of our portal applications. As per your answer, I understand that I can configure Web Disptacher to talk to the Cisco Load Balancer of our portal. In this case Web Dispatcher will work just as a reverse proxy. But when I discussed this with one of our basis resource, he told me that when we install and configure Web Dispatcher, it always ask for the Message Server URL and Port number, even if I just want to use Web Dispatcher as a Reverse Proxy. If his concerns are valid, I do not think I will be able to configure Web Dispatcher to access the cisco Load Balancer because I cannot put Cisco load banacer URL and port instead of the Message Server URL and Post Number. Can you kindly share your comment on the same?
Now the second part of my question, if Web Dispatcher cannot be configured to talk to Load Balancer(as mentioned by our basis resource), I will have to use two load balancers. One web Dispatcher in DMZ as a Load Balancer *** Reverse Proxy for the external users. Second the internal Cisco Load Balancer for the intranet users. So the same portal will be accessed by two load balancers. My question here is, in this set up, can the portal work efficieintly here by distributing equal loads two both the server instances?
Thank You,
mansooralip1

Web Dispatcher as the Full reverse proxy

Hi all,
Has anyone configured SAP Web Dispatcher(WD) as the full reverse proxy for THE portal? We need to open our portal on to the internet and we thinking to put WD inside the DMZ and have it forward the requests to the portal server. Which is explained well in a blog on SDN. According to that Blog, WD works ONLY as a redirecting server (or may be a load balancer). When it redirects a request to an internal server, the ip(or domain name) of the server is shown in the address bar. Ex: http://extrenal.com is being redirected to http://internal:50000/irj/index.html thus exposing the internal name or IP.
I thought Reverse proxy when works, it hides the internal ips and and forwards the requests. So my question here is How to configure WD so it won't show the internal Portal IP(or domain name).
Any ideas?
I know it could be done using IIS, Apache or Squid.
Best,
N.

Hi again,
Yes, most probably, you will have to configure specially the corporate reverse proxy.
That is what is explained in the WIKI and the help.sap.com documentation. Did you read it ? If not, do it, it's a must !
This is not very simple because SAP web applications, generate a lot of dynamic URLs and must "know" that reverse proxies are used.
Understand that it is a project and not not just a 5 minutes configuration...
For example when using Apache as a reverse proxy, you need at least to set :
ProxyPreserveHost on and ProxyPassReverse
You need to decide if you want to rewrite URLS.
You need to manage URL mangling if you use BSP applications in the SAP backend.
In short, you need to know what is the corporate reverse proxy and you need to do a specific SAP configuration both on the corporate reverse proxy and the SAP web dispatcher.
This configuration depends from your specific needs.
Regards,
Olivier

Load Balancer and Web Dispatcher "keepalive page"

I would like our monitoring and load balancer to be able to perform http status check against SAP web dispatchers.
Is there a built in "keepalive" page that can be queried within Web Dispatcher, or will a URL rule be needed?

Dear Andrew,
We need to provide access to our intranet to some outside companies for them to also use some of our portal applications. As per your answer, I understand that I can configure Web Disptacher to talk to the Cisco Load Balancer of our portal. In this case Web Dispatcher will work just as a reverse proxy. But when I discussed this with one of our basis resource, he told me that when we install and configure Web Dispatcher, it always ask for the Message Server URL and Port number, even if I just want to use Web Dispatcher as a Reverse Proxy. If his concerns are valid, I do not think I will be able to configure Web Dispatcher to access the cisco Load Balancer because I cannot put Cisco load banacer URL and port instead of the Message Server URL and Post Number. Can you kindly share your comment on the same?
Now the second part of my question, if Web Dispatcher cannot be configured to talk to Load Balancer(as mentioned by our basis resource), I will have to use two load balancers. One web Dispatcher in DMZ as a Load Balancer *** Reverse Proxy for the external users. Second the internal Cisco Load Balancer for the intranet users. So the same portal will be accessed by two load balancers. My question here is, in this set up, can the portal work efficieintly here by distributing equal loads two both the server instances?
Thank You,
mansooralip1

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

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.

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

Invalid configuration for catalog/Web dispatcher (Fiori Smart Business Cockpit)

Hi all,
For our smart business cockpits, we have following issue in our administration (launchpad):
Invalid configuration for catalog/Web dispatcher
Title
SAP: KPI Catalog for SAP Smart Business
ID
X-SAP-REMOTE:SAP_KPIFRW_TC_R
Remote ID
HANA_CATALOG
System alias
HANA
Base URL
/sap/hba/apps/kpi/s/odata/hana_chip_catalog.xsodata/
Type
REMOTE
When I check our console client, the only error that we see is following message:
2014-08-04 14:33:16 Base URL '/sap/hba/apps/kpi/s/odata/hana_chip_catalog.xsodata' already registered - sap.ui2.srvc.Factory
Does someone already saw this issue before? I noticed that we only have those issues on REMOTE CATALOGS.
Thx!
Regards,
Hans
Tags edited by: Michael Appleby

Use SAP_KPIFRW_TC_R role (I think you already did).
(https://<WEBDISPhostname>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?sap-client=xxx&sap-language=EN#/Catalog/X-SAP-REMOTE:SAP_KPIFRW_TC_R)
However, to be able to access this catalog, the HANA user needs the role sap.hba.apps.kpi.s.roles::SAP_SMART_BUSINESS_RUNTIME
If the user has to model KPIs, they need sap.hba.apps.kpi.s.roles::SAP_SMART_BUSINESS_MODELER.
Regards,
Kiran

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

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

SOLMAN_SETUP/ preparation phase 5.1 configure web dispatcher config failed.

Hello
Based on SAP Solution manager 7.1. SPS 11 Fresh install, SOLMAN_SETUP/ preparation phase 5.1 configure web dispatcher config failed.
Error message:
L3 - Failed to reach test WS through System Settings (ICM/HTTPURLLOC):
http://vip.myfqdn.fr:80
L2 - Test WS can be reached through ICM:
http://hostname.myfqdn.fr:8000
SOAP:1.023 SRT: Processing error in Internet Communication Framework: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_FAILED")
Solman is located in a DMZ, http/https are configurated in table
HTTPURLOC and load balancer is used to publish http and https url and port redirection
instead of native url « hostname » + default port (80xx / 443xx)
• In DMZ for url
http://hostname.myfqdn.fr:8000/ManagedSetupWS/Config1?style=document
system answer is OK
• In LAN via Load balancer url return KO message
http://vip.myfqdn.fr:8000/ManagedSetupWS/Config1?style=document
Any help will be appreciate.
Regards
Eric

Hi All,
I have resolved the issue with re-setting the password of SM_INTERN_WS & SM_EXTERN_WS.
from step 1.
with no-dispatcher configuration..
Regrads,
Gagandeep Singh

SAP Web Dispatcher Configuration (SSL, certificates)

Hi all,
We're trying to configure the SAP Web Dispatcher for the use of SSL (terminated) and client authentication using x.509 certificates. All works (almost)fine. However, there's some strange behavior that I can not explain.
The following access point have been specified in the profile:
Description of the Access Points
icm/server_port_0 = PROT=HTTPS, PORT=443, TIMEOUT=15
icm/server_port_2 = PROT=HTTP, PORT=83, TIMEOUT=15
icm/HTTPS/verify_client = 2
Basicly we only need users to access the web dispatcher using SSL. However, when I remove the line: icm/server_port_2 = PROT=HTTP, PORT=83, TIMEOUT=15
The Web Dispatcher returns an error upon accessing it using HTTPS:
Dispatching Error
Error: -26
Version: 6040
Component: HTTP_ROUTE
Date/Time: Tue Mar 14 07:19:38 2006
Module: http_route.c
Line: 2383
Server: sapvm1_DVS_26
Detail: no valid destination server available for '!ALL' rc=13
Any help would be highly appreciated. Thanks!
Frodo

Hi KS,
Maybe you were right afterall I found a nice How to on the servce.sap.com (https://websmp203.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000073632&_SCENARIO=01100035870000000202) and it seems you do have to add the HTTP server_port parameter in case SSL is being terminated (no re-encryption).
icm/server_port_0 = PROT=HTTPS, PORT=443, TIMEOUT=15
icm/server_port_1 = PROT=HTTP, PORT=0, TIMEOUT=15
However, the trick is to set the port to zero (0), that way you can still only access the Web Dispatcher via HTTPS.
All is working now.
Frodo

How to Install & Configure Web Dispatcher

Hi techies,
How to install and configure SAP Webdisptacher in an existing BI System.
What are the parameters need to be set after installation like ports, memory , profile parameters etc., for webdispatcher.
I am new to this concept
Thx in advance.
Haroon Khavi.

Hi,
The webdisp does not need the SID of the system it is connecting to. The only parameter it needs is a "Unique Instance Number for SAP Web Dispatcher (SAPSYSTEM)".
You can check this with the following command:-
sapwebdisp -bootstrap
If you are installing the webdisp on a server that already has a SAP instance then you have to enter a unique number (not the SAP instance number). You can used any value from 0-99.
This parameter is used for shared memory allocation so should not be the same as the SAP instance or any other webdisp installed on the same server. Of course if there is only the webdisp on the server than any value from 0-99 can be used.
Hope this helps
Michael

SAP Web Dispatcher Configuration guide for Windows

Hi,
I am searching for SAP Web Dispatcher Configuration guide for Windows. It is WAS 6.4, SP14 and JAVA. If any one knows this mean please guide.
Thanks.

Hi Mahesh,
check out the help pages here:
http://help.sap.com/saphelp_nw04/helpdata/en/f5/51c7d170bc4a98b1b5a0339213af57/frameset.htm
Regards,
Pascal

SSL Configuration between Web Dispatcher and Portal

Here is the scenario:
INTERNET -
https--> WEB DISPATCHER (decryipts)-https> PORTAL
When a request for portal page is sent to WEB DISPATCHER, it gives the following error in dev_webdisp:
[Thr 1087416640] ERROR in ssl3_get_server_certificate: (9/0x0009) the verification of the server's certificate chain failed
ERROR in af_verify_Certificates: (12851/0x3233) Verification of one certificate of path failed because the CA flag of its basic constraints is set to FALSE
ERROR in check_basicConstraints: (12851/0x3233) Verification of one certificate of path failed because the CA flag of its basic constraints is set to FALSE
I am using SAP's test certificates and there is no documentation for the error as far as I know.
Any ideas ?

Hi Cristiano,
I solved the problem.
This error message is being caused by the mismatch between the issuer (SAP Test) and server pse generation strings (for example O and OU values ).
As the documentation suggests:
"For example, if you use the SAP CA, the naming convention is CN=<host_name>, OU=I<installation_number>-<company_name>, OU=SAP Web AS, O=SAP Trust Community, C=DE."
Thanks for the reply,
Best Wishes
Edited by: Yuksel Guney Hanedan on Aug 6, 2010 4:35 PM

Web Dispatcher medium / large configuration

Similar Messages

Maybe you are looking for