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; } } }

OD - Using file list on reverse target

Jenni

Hi,

Advance thanks.

We are doing reverse deployment. We have the file list text file on reverse source. The OD is using this file and deploying the files to the reverse target.
I would like to use a script(in before tag) to make a backup of the files to be copied. Can I able to use the file list(which resides in reverse source) in my perl script?

Thanks
Jenni

[html]

........

......

<script cmd="D:\\iw-home\\iw-perl\\bin\\iwperl

\\iw-home\\httpd\\iw-bin\\plc\\copyFiles.ipl" where="D:\\temp" as="ts-admin" async="no" />

[/html]

Find more posts tagged with

Comments

Adam Stoller

Hi,

Advance thanks.

We are doing reverse deployment. We have the file list text file on reverse source. The OD is using this file and deploying the files to the reverse target.
I would like to use a script(in before tag) to make a backup of the files to be copied. Can I able to use the file list(which resides in reverse source) in my perl script?

Thanks
Jenni

If the filelist is on the reverse-source server (receiver) it isn't accessible on your reverse-target (base) server in order to make backups of the files there.

If the filelist is static (never changing from one run to the other) than you could have a copy of the list on your base server and run a DNR (or pre-deployment) script on your base server to rename/copy/backup those files before retrieving new ones.

Jenni

Hi Ghoti,

The file list is being used by the teamsite system and writing the manifest file. Is there any way to pass that information as a parameter or something else to use in the perl script?

The list is not static, it will keep on changing based on the developer changes of the requested files.

Thanks
Jenni

nipper

The filelist is on the sender and not on the receiver. You could deploy that as well, but I think you may want to, instead, have a DNR on the sender that lists the last deployment in a filelist. This is very situation specific, are you always only interested in reverse deploying the last deployment or the last 2 or 3 ?

If it is only the last then the DNR is a good option

Jenni

Hi Nipper,

we are confused with the reply. We are talking about the script which is running before taking the actual deployment. Can we able to access that file by any means? The TeamSite system is using that file and writing the manifest file at the end.

Thanks
Jenni

nipper

Hi Nipper,

we are confused with the reply. We are talking about the script which is running before taking the actual deployment. Can we able to access that file by any means? The TeamSite system is using that file and writing the manifest file at the end.

Thanks
Jenni

I think we are confused as well. What I am suggesting is that on the outbound (not reverse) deployment, you have a DNR run which dumps the files deployed into a filelist format file. Then when you reverse deployment, it takes the last set of files deployed and pushes them.

Adam Stoller

Hi Ghoti,

The file list is being used by the teamsite system and writing the manifest file. Is there any way to pass that information as a parameter or something else to use in the perl script?

The list is not static, it will keep on changing based on the developer changes of the requested files.

Thanks
Jenni

Here's what I think is the scenario:

Your answers to the above will make it much more likely that you will get a reasonable answer.

Jenni

Hi Fish,

I am really pleased with the your question/options format. Thanks a lot for taking time to write such a big reply. Here are the answers for your questions.

Thanks!
Jenni

Here's what I think is the scenario:
-The filelist for the deployment must exist on the receiver side at the time the reverse deployment is executed - The file list is on source side, we would like to use that if available automatically. The TeamSite system is using that and generating the manifest, so we are assuming there might be a way to use that.

Question: How are you initiating the deployment? - manually from command line

Question: How are you creating the filelist? - manually - Whenever we need the deployment we will create the new file.

Question: Where is the filelist actually being created? - on the reverse-source (receiver side)

nipper

One more question, how is the filelist created (populated) ?

Is it some arbitrary list of files that you or someone else decides to reverse deploy ?

Is it a consistent set of files ?

Is it a list one can easily calculate (i.e. all files in ./here that were updated since yesterday) ?

Is it the list of files that was most recently deployed to the server ? (that was my though a few posts back)

Jenni

One more question, how is the filelist created (populated) ?
Mannually

Is it some arbitrary list of files that you or someone else decides to reverse deploy ?
We are trying to move files from dev. to prod using reverse deply. The new files are nothing but the new changes to the files, the developer has made.

Is it a consistent set of files ?
No

Is it a list one can easily calculate (i.e. all files in ./here that were updated since yesterday) ?
No. It is random.

Is it the list of files that was most recently deployed to the server ? (that was my though a few posts back)
No. It might differ depending on the files, that the developer worked on.

Thanks!
Jenni

Adam Stoller

We are trying to move files from dev. to prod using reverse deply. The new files are nothing but the new changes to the files, the developer has made.

When you say from dev to prod - are these both TS servers and thus both OD Base Servers?

If so - you cannot do a reverse deployment between two Base Servers. You can only do a reverse deployment between a Base Server and Receiver (and you cannot have both a Base Server and a Receiver installed on the same host)

Please clarify your "dev to prod" statement.

Adam Stoller

...Here's what I think is the scenario:
-The filelist for the deployment must exist on the receiver side at the time the reverse deployment is executed - The file list is on source side, we would like to use that if available automatically. The TeamSite system is using that and generating the manifest, so we are assuming there might be a way to use that.

Question: How are you initiating the deployment? - manually from command line

Question: How are you creating the filelist? - manually - Whenever we need the deployment we will create the new file.

Question: Where is the filelist actually being created? - on the reverse-source (receiver side)

You start off by saying that the filelist is on the source side and that TeamSite is using that, then you say the filelist is on the reverse-source (receiver side) - which is it?

If your talking about Base Server to Base Server deployments (see my other response) you can only do a forward deployment in that scenario - depending on where you initiate the creation of the file list and where you are trying to push / pull content to / from - you could conjure up a number of possible implementations (like a deployment on one side that pushes a file list to the other side and then via a DNR initiates a new deployment from that side to push the contents of that filelist back to the original initiating server)

The more clearly you can define / explain the situation, the more clearly we can respond.