SAP WebDispatcher start method

[Former Member]

Hi,

Would like to know to start the SAP WebDispatcher is it have 2 method?

1) startsap

2) sapwebdisp pf=<profile>

Problem now is, earlier I'm using startsap and stopsap to start WD instance. It working fine, but then I run sapwebdisp command. I kill the sapwebdisp process, but now I can't use startsap. Whenever I run the command it will like normal start the instance and said it started. But when I check, it is not started.

Now I'm using sapwebdisp to start the instance. But I need to use the startsap method.

Would like to know is it because there are 2 method of starting the instance, and is because I use command sapwebdisp therefore it switch the starting mode?

Or any reason in behind and how can I fix it.

Thanks.

[rsnit]

Hi,

did you try to check your current config of the webdispatcher?

sapwebdisp pf=D:\profile\tbw_wdt_kurvtbw0.pfl -checkconfig

Also you should be able to stop and start webdispatcher over the sapmmc or over 5xx13 port in SAPMC.

Also you can do further investigation with increasing the tracelevel for the webdispatcher

sapwebdisp pf=E:\usr\sap\WPB\SYS\profile\START_W01_br-bw7ps -f dev_webdisp -t 3

Best regards

Robert

[feng_shi]

Hi,

Please try to use startsap command to start the webdispatcher again and attach the following trace log:

1, the updated log files which under home directory of sidadm user

2, the updated log files which under work directory of webdispatcher

thanks and best regards,

Shi

[Former Member]

Hi Feng Shi,

Here is the log as requested.

SAP-R/3-Startup Program Rel 745 V2.0 (2008/11/15)
-------------------------------------------------
Starting at 2016/03/22 20:41:24
Startup Profile: "/usr/sap/WP2/SYS/profile/WP2_W00_celwd-prd2"
Setup Environment Variables
---------------------------
(10158264) SETENV DIR_LIBRARY=/usr/sap/WP2/SYS/exe/uc/rs6000_64
(10158264) SETENV LD_LIBRARY_PATH=/usr/sap/WP2/SYS/exe/uc/rs6000_64:
(10158264) SETENV SHLIB_PATH=/usr/sap/WP2/SYS/exe/uc/rs6000_64:
(10158264) SETENV LIBPATH=/usr/sap/WP2/SYS/exe/uc/rs6000_64:/usr/sap/WP2/SYS/exe/uc/rs6000_64:/usr/sap/WP2/SYS/exe/run:/usr/sap/WP2/SYS/exe/nuc/rs6000_64
(10158264) SETENV PATH=/usr/sap/WP2/SYS/exe/uc/rs6000_64:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home/wp2adm/bin:/usr/bin/X11:/sbin:.:/usr/sap/WP2/SYS/exe/nuc/rs6000_64:/usr/
sap/WP2/SYS/exe/run:/home/wp2adm
(10158264) SETENV SECUDIR=/usr/sap/WP2/W00/sec
Execute Pre-Startup Commands
----------------------------
(8192112) Local: rm -f wd.sapWP2_W00
(8192114) Local: ln -s -f /usr/sap/WP2/SYS/exe/uc/rs6000_64/sapwebdisp wd.sapWP2_W00
Starting Programs
-----------------
(8192118) Starting: local wd.sapWP2_W00 pf=/usr/sap/WP2/SYS/profile/WP2_W00_celwd-prd2
(10158264) Waiting for Child Processes to terminate.
(8192118) New Child Process created.
(8192118) Starting local Command:
 Command:  wd.sapWP2_W00
           pf=/usr/sap/WP2/SYS/profile/WP2_W00_celwd-prd2
(10158264) **** 2016/03/22 20:41:25 Child 8192118 terminated with Status 252 . ****
(8192118) **** 2016/03/22 20:41:25 No RestartProgram command for program 0  ****
(10158264) **** No more Child Processes to wait for.
(10158264) Parent Shutdown at 2016/03/22 20:41:25
Execute Post-Shutdown Commands
------------------------------
(10158264) Exiting with Return-Code 3. (No more child processes)

[isaias_freitas]

Hello Adrian,

The log you shared shows that the Web Dispatcher is crashing right after it is started.

Please simulate the issue again and then collect and share:

• the updated "startsap.log" file;
• the "dev_webdisp.new" trace file. If this file does not exist, please share the "dev_webdisp" trace instead;
• the "stderr0" file;
• the "stdout0" file.

All mentioned files would be located at the "/usr/sap/WP2/W00/work" folder.

You can "zip" all files and attach the "zip" file to this thread, instead of pasting their content in your reply .

Regards,

Isaías

[raquel_gomez]

Hi,

See also:

Starting the SAP Web Dispatcher - SAP Web Dispatcher - SAP Library

Regards,
Raquel

[Former Member]

Generally, the startsap command will kick off the sapwebdisp command, and therefore be the one to use.  I think when you started sapwebdisp manually, it may have boogered (technical term) the startsap command.  Fret not.

You can try a couple of things:

1. Kill the sapwebdisp manually, then simply try the startsap <SID> command and see if it will work.

2. Restart the sapinit service (on newer installs) after doing above and retry. 

Hopefully one of those will fix your issue. 

Thanks,

MM

[Former Member]

Hi Mathew,

OK. Will try that but only can perform that on weekend.
Thanks.