Solution : https://service.sap.com/sap/support/notes/834184 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the implementation of SAP Web Dispatcher within an MSCS (Microsoft Cluster Service) environment as a generic service to avoid a single point of failure. It entails creating a specific cluster group, configuring directories and files on a shared disk, and setting up SAP Web Dispatcher service parameters appropriately. Steps include the setup of system instances, port configurations, and administrative paths. The process requires installing the SAP Web Dispatcher manually using specific SAR files and configuring both the service and dependencies within the MSCS. Proper registration of the service across both nodes ensures system robustness and failover capabilities.
Key words :
/ -> sap documentation -> sap netweaver -> sap web application server -> client server technology -> architecture, #--- instance specific parameterssapsystemname = jeeinstance_name = wd05sapsystem = 06sapglobalhost = <virtual network, >#--- sap web dispatcher-specific parametersicm/server_port_0 = prot=http, icm/http/admin_0 = prefix=/sap/wdisp/admin, sap web application server -> sap web dispatcher 3, = sap web dispatcherresource type = generic servicegroup = mysapwebdispatcher, proctimeout=600rdisp/mshost = <hostname>ms/http_port = 8103, hklm\system\currentcontrolset\services\eventlog\application, sap<sid>_<system number>, additional sap web dispatcher parameters
Related Notes :
| 1397178 | MII not able to read from local host |
| 951910 | NW2004s High Availability Usage Type PI |
| 908097 | SAP Web Dispatcher: Released releases and applying patches |