Need to publish files to two different physical path in IIS server

manu1905

Hi All,

I am using TS/OD 732 version both are installed in same sever.

Now I want to publish files from TS to two different physical path/folders in same IIS server, Its like some files from TS I want to publish to one folder and some to other in same IIS server. for this wat I did was to use filelist deployment to mention the pre-configured set of files in filelist1.txt and filelist2.txt file.

I am sending the config file, please suggest if this is ok as in filelist we have limitation is every time if we add something in TS we need to update filelist.

should I go for some other deployment type like remotediff etc, if I go for remotediff then how can I achieve above case.

content delivery method using is fan-out.

waiting for inputs.

Thanks,

Find more posts tagged with

Comments

Adam Stoller

Since it appears, from the configuration file you posted, that the same types (extension) of files are being posted to both locations, the way you are doing this sounds reasonable.

The alternative is to do to two distinct deployments - one with the first filelist, and then one with the second filelist.

The first way (the way you're planning) is static, and thus fine if it is always going to be like that.

The second (alternative) way allows for some dynamic aspects - though you would need to be passing in the target area as a parameter too - such that you could handle 1, 2, or N different source/target pairings.

There are other alternatives that could come into play depending on whether all the files from one (or N) source paths go to one target path and all the files from a different (or M) source path go to the other target path. In such instances you could use a single filelist with two distinct pathSpecification elements where each excludes the files from the other's source path.

Rick Poulin

manu1905 wrote:
I am sending the config file, please suggest if this is ok as in filelist we have limitation is every time if we add something in TS we need to update filelist.

If you're using filelist deployments, then your publishing process (workflow) should be generating that filelist based on what's attached to the job. There's no sense maintaining a separate filelist manually. If you want to always deploy a whole structure, then yes, use remoteDiff instead (optionally with some filters).

manu1905

Hi,

In my previous attachment I had used filelist where I created two filelist filelist1.txt, filelist2.txt to send the set of files to different location in same server.

Now I am sending the config file where I m using remotediff deployment type, I have 2 mail folders 1. testPublic with subfolders inside to publish in one location and 2.testSecure with subfolders inside it to publish on other locations in the same server.

I will follow wat u al said, but want if you can have a look on this as well.

Thanks

manu1905

Hi All,

waiting for the input in this.

thanks