OD & File Time Stamp

iwTech

We are deploying non-dcr files from TS using WF’s to stag & prd web server

using OD . The time stamp is different for all three (TS/ Stg/Prd) .

Right now , we don’t want to use WF’s to deploy non-dcr files.

We configured the OD Conf files and using OD UI to deploy files .

When I deployed test files, some of the file time stamps are over written
at the staging web server ?

(I mean the files in TS , but using OD UI to deploy
files to stag & prd

web server )

the files are the same/ no change in files

Any idea “why this happened?”

Please explain “How the OD time stamp works ? “

What’s the best approach to use the time stamps ?

Thanks

-Vin

Find more posts tagged with

Comments

ISCBorisB

Hi

We are deploying non-dcr files from TS using WF’s to stag & prd web server

using OD . The time stamp is different for all three (TS/ Stg/Prd) .

Right now , we don’t want to use WF’s to deploy non-dcr files.

We configured the OD Conf files and using OD UI to deploy files .

When I deployed test files, some of the file time stamps are over written
at the staging web server ?
(I mean the files in TS , but using OD UI to deploy
files to stag & prd
web server )
the files are the same/ no change in files

Any idea “why this happened?”

Please explain “How the OD time stamp works ? “

What’s the best approach to use the time stamps ?

Thanks

-Vin

OD Transfer Rules allow you to specify applySourceFileTime="[yes|no]" attribute, default is "yes".

applySourceFileTime="yes" is normally used when you plan directory comparison deployments.
applySourceFileTime="no" pretty much means "Apply Target System Time" and may (perhaps) be useful for Target
Applications that take some actions on freshly Deployed assets, etc...

yogesh_agrawal

the best approach is to use applySourceFileTime attribute of OD transfer rules element. it works as follows-
Applying the source file time (applySourceFileTime="yes") to deployed files
ensures that the timestamps of files on the target host match their counterparts on the source host. An advantage of this is that directory comparison deployments will only deploy files that have changed on the source, since the time stamps would no longer match those of the corresponding files on the target.
Applying the target system time (applySourceFileTime="no") is useful for
situations where an application on the target system takes an action based on an updated time stamp. For example, a nightly process that looks for new files would only have to search for files with a time stamp within the past 24 hours, or an application server will know to refresh itself based on the updated timestamp on deployed files.

ISCBorisB

the best approach is to use applySourceFileTime attribute of OD transfer rules element. it works as follows-
Applying the source file time (applySourceFileTime="yes") to deployed files
ensures that the timestamps of files on the target host match their counterparts on the source host. An advantage of this is that directory comparison deployments will only deploy files that have changed on the source, since the time stamps would no longer match those of the corresponding files on the target.
Applying the target system time (applySourceFileTime="no") is useful for
situations where an application on the target system takes an action based on an updated time stamp. For example, a nightly process that looks for new files would only have to search for files with a time stamp within the past 24 hours, or an application server will know to refresh itself based on the updated timestamp on deployed files.

By the copy/paste from OD Manual one week later, have you added anything of substance to what already has been said?