cancel
Showing results for 
Search instead for 
Did you mean: 

Patching Web Dispatcher?

Former Member
0 Kudos

Hi,

Web dispatcher download/installation (importing?) info at

http://help.sap.com/saphelp_nw2004s/helpdata/en/7c/6bf41aca84425196bd358df965fe3e/frameset.htm

is misleading, it lists SAPWEBDISP_<PL>.SAR as the latest Web dispatcher version, and mentions that DW_<PL>.SAR naming was used for older versions.

On the https://service.sap.com/patches sapwebdisp_0-20000961.SAR (patch level = 73) is older than dw_88-20000961.SAR (patch level = 87, not 88).

In order to patch older version of Web Dispatcher do I need to uninstall older version, and if so does uninstalling means deleting Web dispatcher directory?

Thanks!

Rob

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member185954
Active Contributor
0 Kudos

Hi,

I do not think there is any miscommunication here, what they mean is that in the older model of patch delivery, the sap web dispatcher was bundled in your DW car file , however now it is shipped seperately as sapweb*.sar.

Regards,

Siddhesh

Former Member
0 Kudos

Hi Siddhesh,

I would like to use the latest patched version of Web dispatcher.

If what you are saying is correct, I then need to download sapwebdisp_0-20000961.SAR file from http://service.sap.com/patches site?

What I'm confused about is why the file dw_88-20000961.SAR has newer timestamp and higher patch level.

If dw naming convention was part of older patch delivery, wouldn’t sapwebdisp_0-20000961.SAR be the newer file with the latest patch?

I'm obviously missing something here, thank you for taking time to try to clarify this.

Rob

former_member185954
Active Contributor
0 Kudos

Hi Robert,

Take a note at other patches alongwith the dw.sar file, you will see that they are not all at same patch levels.

the normal way of patching kernel is :

we apply

sapexedb

sapexe

rest of the patches...

this way we ensure that we are on the latest patches on all fronts... it is normal to have the sap kernel (disp+work) and other sap executables to be at different patch levels.. take the case of R3trans and TP they both would be following a different release strategy.

so it might be that SAP has now decided to seperate the sapwebdispatcher.. just like tp and r3trans !

if you are concerned that dw might contain a latest version of sapweb dispatcher..extract the contents of dw to a seperate directory using

sapcar -xvf dw.car -R <DIRECTORY OF YOUR CHOICE>

and then do the same with sapwebdispatcher.sar file...

view the contents of both directories and see which one has the latest version and use the latest one.

I doubt that dw will contain a more latest version of sapwebdispatcher.. in fact i doubt that dw.sar would contain any version of sapwebdispatcher.. if it does.... pls update this thread so that even i get to share your knowledge maybe we would raise this to SAP

hope this helps,

Regards,

Siddhesh

Former Member
0 Kudos

Hi Siddhesh,

If you read my first post "sapwebdisp_0-20000961.SAR (patch level = 73) is older than dw_88-20000961.SAR (patch level = 87, not 88).". I got patch levels by extracting each sar files and checking the version.

I'll go with patch level 87 and hope for the best.

I'll also assume uninstalling Web Dispatcher means running UninstSAP.exe that is under Web Dispatcher installation root.

Rob

former_member185954
Active Contributor
0 Kudos

Hi,

I am wondering whether sapweb dispatcher executable was present in the dw.SAR file ?

Regards,

Siddhesh

Former Member
0 Kudos

Yes it was,

Here is the version output from DW_88-20000961.SAR package:

W:\>D:\SAPInstall\WebDispatcher\sapwebdisp.exe -v

SAP Web Dispatcher Version 7.00.9, multithreaded, ASCII, 32 BIT

kernel information

-


system name =

kernel release = 700

database library =

compiled on = NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10

compile time = Dec 11 2006 20:33:13

update level = 0

patch number = 87

source id = 0.088

supported environment

-


operating system

Windows NT 5.0

Windows NT 5.1

Windows NT 5.2

patch comments

-


( 0) ( 0.001) Provide option to preserve Unicode chars in HTML Escape (note 832220)

( 1) ( 0.004) CST patch collection 15 2005 (note 834501)

( 2) ( 0.007) CST patch collection 21 2005 (note 845887)

( 3) ( 0.011) CST patch collection 24 2005 (note 851195)

( 4) ( 0.011) VM Patch Collection 2 (note 853183)

( 5) ( 0.014) CST Patch Collection 28 2005 (note 860319)

( 6) ( 0.014) CST Patch Collection 28 2005 (note 860319)

( 7) ( 0.018) CST Patch Collection 31 2005 (note 867690)

( 😎 ( 0.020) Optimization of VMC session storage (note 871988)

( 9) ( 0.021) Enhanced SAP encoding methods (note 866020)

( 10) ( 0.023) CST Patch Collection 36 2005 (note 874665)

( 11) ( 0.023) CST Patch Collection 37 2005 (note 877058)

( 12) ( 0.023) VMC Patch Collection 6 (note 865932)

( 13) ( 0.026) CST Patch Collection 39 2005 (note 884266)

( 14) ( 0.030) CST Patch Collection 41 2005 (note 888245)

( 15) ( 0.033) CST Patch Collection 45 2005 (note 895230)

( 16) ( 0.034) ICM Patch Collection (V) (note 851852)

( 17) ( 0.036) CST Patch Collection 49 2005 (note 904777)

( 18) ( 0.041) CST Patch Collection 1 2006 (note 913187)

( 19) ( 0.046) CST Patch Collection 06 2006 (note 921223)

( 20) ( 0.047) CST: Missing content length in content server upload (note 925327)

( 21) ( 0.047) CST Patch Collection 06 2006 (note 921223)

( 22) ( 0.047) Corrections within the SAP content of filter (note 925602)

( 23) ( 0.049) CST Patch Collection 09 2006 (note 928898)

( 24) ( 0.053) CST Patch Collection 14 2006 (note 937223)

( 25) ( 0.057) CST Patch Collection 17 2006 (note 944284)

( 26) ( 0.060) CST Patch Collection 22 2006 (note 950845)

( 27) ( 0.063) ICM could not handle more than 100 workprocesses (note 956048)

( 28) ( 0.065) CST Patch Collection 26 2006 (note 957514)

( 29) ( 0.069) CST Patch Collection 29 2006 (note 962917)

( 30) ( 0.073) CST Patch Collection 33 2006 (note 970657)

( 31) ( 0.076) CST Patch Collection 36 2006 (note 975552)

( 32) ( 0.079) CST Patch Collection 39 2006 (note 981959)

( 33) ( 0.083) CST Patch Collection 42 2006 (note 991211)

( 34) ( 0.084) Fix potential deadlock in CL_HTTP_CLIENT->LISTEN (note 851852)

( 35) ( 0.087) CST Patch Collection 47 2006 (note 999284)

former_member185954
Active Contributor
0 Kudos

Hi,

That is strange, if I were you , I would post a message to SAP if i am doing this on production system to minimize the risk.

Regards,

Siddhesh

Former Member
0 Kudos

Thanks for the suggestion, I'll let them know.

Rob

former_member185954
Active Contributor
0 Kudos

Hi Robert,

I recently patched a kernel , i have used the DW.SAR for sapwebdispatcher instead of the seperate file.

It works well.

Regards,

Siddhesh