nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

difference between iwupdate -s -w

nagendra

Hi,

Can someone elaborate on difference between using -s and -w with iwupdate CLT when used on single file? What cahnges occur in file attributes, properties or file state in both case? Does below example returns same values in all respects?

Usage: iwupdate [-w|-s|-x] [-o] [-r] {src_vpath}+ dst_vpath
-w overwrite all files. Files in dst_area but not in src_area
will be deleted
-s overwrite all versioned files

Ex:
iw-home/bin/iwupdate -s /default/main/JanProducts/STAGING/templatedata/Product/offer/data/offer1 /default/main/FebProducts/WORKAREA/Content/templatedata/Product/offer/data/offer1

iw-home/bin/iwupdate -w /default/main/JanProducts/STAGING/templatedata/Product/offer/data/offer1 /default/main/FebProducts/WORKAREA/Content/templatedata/Product/offer/data/offer1

thanks,
Nagendra

Find more posts tagged with

Comments

kaalraa

When used over single file, the only difference would be seen in case (-s) the destination workarea file has a version of 0+ . In all other means, it should be same.

It could only make differences in case the commands being used at WORKAREA level.

Hi,

Can someone elaborate on difference between using -s and -w with iwupdate CLT when used on single file? What cahnges occur in file attributes, properties or file state in both case? Does below example returns same values in all respects?

Usage: iwupdate [-w|-s|-x] [-o] [-r] {src_vpath}+ dst_vpath
-w overwrite all files. Files in dst_area but not in src_area
will be deleted
-s overwrite all versioned files

Ex:
iw-home/bin/iwupdate -s /default/main/JanProducts/STAGING/templatedata/Product/offer/data/offer1 /default/main/FebProducts/WORKAREA/Content/templatedata/Product/offer/data/offer1

iw-home/bin/iwupdate -w /default/main/JanProducts/STAGING/templatedata/Product/offer/data/offer1 /default/main/FebProducts/WORKAREA/Content/templatedata/Product/offer/data/offer1

thanks,
Nagendra

nagendra

Thanks kalaraa, can you elaborate on the differences it makes in case of WORKAREA / target with 0+ version?

ISCBorisB

Thanks kalaraa, can you elaborate on the differences it makes in case of WORKAREA / target with 0+ version?

In theory, -s Flag allows you to keep new, never submitted Files in the target area and get the rest from Staging or some other
source. In practice though I would recommend to Submit new Files that you intend to keep before running a risk to lose them

kaalraa

Thanks kalaraa, can you elaborate on the differences it makes in case of WORKAREA / target with 0+ version?

In case of WORKAREA, -w plays a vital role as it also deletes those files on target which does not exists in Source. As per your example, the files which are not on STAGING, but exists on WORKAREA would be deleted.

-s would work as same, as it would not overwrite files which are not versioned (0+).