PAM for Web Dispatcher 7.20

Hi Gurus,
I could not find the Web Dispatcher in the PAM lists so I post my question here:
Which Windows Server platforms are supported for Web Dispatcher 7.20?
We currently run Web Dispatcher 7.0 on WIN to serve our ERP systems on HP-UX and the whole system landscape will be migrated to WIN Server 2008 R2.
Is it possible to install WebDisp 7.2 in parallel to 7.0 for test purposes with our new WIN system landscape that is already existing?
Many thanks and best regards
Günter

Hi Markus,
the PAM of Web Dispatcher 7.20 (as sub entry of NW 70 as you told me) contains the entry:
WINDOWS SERVER 2008/X64 64BIT
Do you know whether WINDOWS SERVER 2008/X64 64BIT R2 is supported or not?
Thanks once again and best regards
Günter

Similar Messages

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

Which SAPCRYPTO.DLL for Web Dispatcher on WIN 2008 64-bit

Hi all,
I have installed WebDispatcher 7.20 on a Windows 2008 64-bit platform - according to PAM this is a supported platform.
Now I cannot find a suitable Cryptographic Library that does not cause the following error message during startup in dev_webdisp:
*** ERROR => DlLoadLib()==DLENOACCESS - LoadLibrary("c:program filesSAPSAPWebDispsapcrypto.dll")
Error 193 = "c:program filesSAPSAPWebDispsapcrypto.dll is not a valid Win32 application."
When I browse the download catalogue on marketplace there is only one download available for WIN 2008 64-bit and this one seems to be for Itanium:
SAP Cryptographic Library Microsoft Win64 for IA64 (Itanium)
Can anyone please let me know where to find the suitable sapcrypto.dll for usage on WIN 2008 X-64 platform together with WebDispatcher 7.20?
Thanks a lot in advance and best regards
Günter

Hello Günter,
With my Web Dispatcher 7.2 running on Windows 2008 64 bit, I use SAPCRYPTO-Library 5.5.5pl26 target
x64 (AMD64/EM64T/Intel64). It works OK for my use (SSL ).
I have never been able to download any sapcrypto lib even after asking our SAP correspondant to activate the download link for us.
Each time whe had to wait to get a DVDROM by snail mail....
Regards,
Olivier

Rdisp/j2ee_start parameter for web dispatcher

Hi all,
We want our web dispatcher 7.2 to restart automatically, in case of any core dump.
we used this parameter rdisp/j2ee_start=1, but its not helping.
Is there any equivalent parameter for SAP web dispatcher?
Thanks
Senthil

Hi Sunny,
auto_restart option is fast and its zero downtime, as two process runnings parallely (one acts as watchdog)
we used the below command
./sapwebdisp pf=/sapmnt/WPS/profile/WPS_W01_brewer -auto_restart &
to start the webdisp with the auto_restart option, its working.
I edited the startsap script and added the above line inplace of sapcontrol, but now to stop this process using stopsap script is a big deal.
bcos if we start using sapwebdisp command, the only way to stop is to kill the process.
or is there a command to stop the web dispatcher?
Thanks
Senthil

Using existing SSL Certificate for Web Dispatcher

Hi,
We've registered a SSL certificate with wildcard option via GlobalSign. The history of this process is as below:
1. We created a Certificate Request with IIS and send it to GS (GlobalSign).
2. They send us the certificate file Globalsign Primary Secure Server CA and Globalsign Server Sign CA files.
3. Import all ceritifcates into IIS and then exported the certificate into a Cert.pfx file.
4. By using this file, we are able to import the SSL certificate into J2EE WAS 640 of Portal system.
5. Now we want to use same certificate to establish a web dispatcher installation as intermediate server for internet access.
Web Dispatcher documentations says to create a pse and req file with sapgenpse program and then send it to CA (here globalsign) to get a certificate.
But when we asked GS, they told us to use the certificate they send us before. They cannot create a certificate file for the ourput of web dispatcher. It will be billed us if we persist.
So, we have to find a way to use the existing certificate to enable SSL of Web Dispatcher.
Any idea?

Hi Huseyin,
I also have the same scenario. We also want to use the same certificate from verisign for our webdispatcher.
Do you know how to do. Can you help me.
Thanks and Regards,
Sailesh K

PAM for web application authentication

Hi,
I am new to PAM. Is it possible to set up PAM to authenticate users listed in a database table?
Thanks,

There may be PAM modules for that, or you could even write one.
This forum probably won't have much input on the topic, since it focuses on Sun's directory server.

SAP Web Dispatcher for Portal reverse proxy

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

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

Web Dispatcher Versions

I currently have 2 web dispatchers that are NW 701. All of my systems that we are looking to use web dispatcher(s) with are also NW701. I can't seem to find a PAM entry for web dispatcher. Is their any version requirements around web dispatcher and systems they connect to? I saw a sme article about web dispatcher 7.2 and using it with multiple network aliases to redirect users to multiple hosts. I.e. one webdispatcher could service both ECC and portal hosts. I believe to do the samething in web dispatcher 701 you have to use url prefixes, or run multiple web dispatchers.
Is Web dispatcher a case where it always makes sense to get the newest version when implementing? Or does it need to match the systems you connect to?
Thanks, Pat

Hi Olivier,
I aam trying to upgrade Web Dispatcher from 701 to 7.20 on Windows box. I downloaded the file "sapwebdisp_73-10007272.sar" from the marketplace. When I unpacked this SAR file it created "servicehttp" folder also I found "wdispadmin.SAR" I also unpacked this file then it created a folder called "admin". In the admin I found 4 folders called, icp, public, publicicp and publicincl.
Instead of icmadm.sar now it is only "wdispadmin.SAR".
Now I started the Web Dispatcher but the webadmin UI does not work correctly. Like I cannot put the web dispatcher in the maintenance mode, I cannot see this screen there is an error called
"unhandled exceptions: "
"ICP_StructValue: illegal struct reference: icm_info.uptime"
"ICP_StructValue: illegal struct reference: icm_serv_info.aclfile"
"ICP_StructValue: illegal struct reference: icm_user_info.locked"
"ICP_Value: Illegal type: 7"
I checked for any related notes, I found 1484856. In the note it said
The follwoing ICP files are not delivered in wdispadmin.sar.
- wdisp_add_system.icp
- icpdef.inc
Therefore the ICM/Webdispatcher Admin UI does not work correctly.
When I clicked the download it takes me to the page called "NO DATA AVAILABLE".
Did you have any of this errors? Meanwhile I have opened an ticket with SAP for this.
Please let me know if you have come across this error.
Thanks in Advance
Ramesh.

Web dispatcher upgradation document from netweaver 7.0 to 7.1

hi guys,
           I need web dispatcher upgradation document.i didn't get document in service market place and sdn.So please tell that document site.

Hi Srinivas,
If you are looking for Web Dispatcher patch upgradation..here is the procedure
Download SAP Web Dispatcher latest version based on your OS.
1) This is available on SAP Service Marketplace at http://service.sap.com/patches:
                    Support Packages and Patches
                    -> Entry by Application Group
                    -> Additional Components
                    -> SAP Kernel
                    -> SAP Kernel 32 Bit or SAP Kernel 64 Bit
                    -> SAP Kernel 7.00 nn Bit
                    -> Operating system platform
                    -> "Database independent
                    The package is called sapwebdisp_<.....>.sar
2) Shutdown your SAP system and take the kernel backup.
3) Uncar the file sapwebdisp_<....>.sar and copy the content to the kernel directory
4) Start the SAP system
Check Note 538405 - Composite SAP Note: SAP Web Dispatcher
Please close the thread if this answers your question.
Thanks,
Sridhar

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

Redirection in web dispatcher

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

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

SAP Web Dispatcher does not start as windows service

Hi,
I have successfully installed and configured SAP Web Dispatcher. When I start the web dispatcher from command prompt, it works fine. I created a windows service for web dispatcher using the command
ntscmgr install sapwebdisp -b "c:\program files\sap\sapwebdisp\sapwebdisp.exe"
-p "service pf=sapwebdisp.pfl -cleanup -auto_restart"
The command successfully created sapwebdisp service. The service also starts fine, but web dispatcher does not get started.
Any ideas experts?

Hi,
Ok. Few suggestions.
1. Can you review the SAP note:
552286 Troubleshooting for the SAP Web Dispatcher
2. When you said: "web dispatcher does not get started ", what error you got ? Can you be more details here ?
3. Please check the trace file dev_webdisp" that generated in the work directory. If the log entries is not abvious, increase the trace level to 2 or 3, and reproduce and re-check the trace file.
4. What is the output of the command "sapwebdisp -v"
5. How about sapwebdisp.pfl ? Are those settings correct ?
Hope this helps.
Regards,
Vincent

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

Cluster Web Dispatcher together with CI in MSCS?

I need to provide HA for Web Dispatcher by clustering in MSCS. My plan is to share the MSCS of the CI it is connecting to. The CI (ASCS and SCS) is already installed in cluster with all proper shared resources (disk, global share, services, ip, netname, etc.) My question is whether I should or need to create a separate cluster group for the WD or if it would be easier/better to install in same shared disk as CI? I have been referring to SAP Note 834184 regarding the manual install of the WD in MSCS and have run into an issue because of the global share of the CI. Currently the WD is installed on its own shared disk (with directory structure), and its own netname and IP. When starting it is trying to access the SAPMNT share of it's host, which is successful (as the hostnames and ip are really just virtual resources of the cluster), but the directory path it tries to access on the share is not correct because the share is really for the shared disk of the CI and not that of the WD.
Does anyone have a recommended method of clustering the WD in an existing SAP MSCS cluster? It seems that the Note referenced above was not written with this in mind. However, due to the very low resource needs of the WD, I think it would be fairly common to cluster it with an existing installation or the msg server it is serving. My next thought is to install the WD on the same shared disk and cluster group as the CI and allow it to fail over with the CI so it will access the proper sapmnt file share, but I'm not sure if this is the recommended or best practice for this type of scenario.
Thank you for any input on this and I would be happy to provide any futher details of my configuration.
thanks,
John

John,
First, lets clarify the confusion: CI is not where your ASCS and SCS are installed.
"The system consists of two instances: a Java central instance with SDM, and the Central Services instance"
http://help.sap.com/saphelp_nw04s/helpdata/en/43/1af03eae11e16be10000000a114084/frameset.htm
(A)SCS - "(ABAP) SAP Central Services", consists of Message Server and Enqueue Server, resides in a cluster group of MSCS
CI - "Central Instance" - Dispatcher, Server Processes and SDM. Not part of cluster group, resides on C: drive (your case).
Now to the point:
It is absolutely OK to install your Web Dispatcher on the cluster group of your (A)SCS.
You can use shared drive as a location for the Web Dispatcher and PFL file.
In this case you do not need to do step "6. Register the SAP Events DLL in registry" from note 834184.
During the failover, Web Dispatcher comes up properly on the target node.
Let me know if you need step by step instructions.
I can send you screenshots for the install.
Regards,
Slava

Support pakages and patch sap web dispatcher

Hi,
I have install sap web dispatcher on a sap server on abap stack.
I have download support packages for web dispatcher form sap mark.
Anybody know how can I patch web dispatcher with u201Csapwebdisp_86-20003979.saru201D file..
Thanks for any help.

Hi my friend
Just unzip the SAR file and replace the old files with the latest, like replacing kernel files.
Note 908097 - SAP Web Dispatcher: Released releases and applying patches
Regards,

PAM for Web Dispatcher 7.20

Similar Messages

Maybe you are looking for