Sorce and target directories are different

Hi,

I have certain files in a particular directory structure in TeamSite. I want to manipulate this structure and deploy the files in a new directory stucture in the web server. I was able to create a filelist using a new directory structure in WF URL task Java class . But when i pass this filelist to my OD config file , the directory structure gets created in the webserver, but the file is not copied.

i realized that OD was not able to find the file as i am passing the filelist , which is a path , not available in TeamSite. How do i get the file in OD and copy it in the new directory structure.

I have attached the od.xml file and $FILELIST^ is the path i am passing from my Java Class. This is the new directory structure with the filename.

Kindly advice,

Mav

Find more posts tagged with

Comments

Adam Stoller

First - please read this posting and consider it before making any additional posts.

I have certain files in a particular directory structure in TeamSite. I want to manipulate this structure and deploy the files in a new directory stucture in the web server. I was able to create a filelist using a new directory structure in WF URL task Java class . But when i pass this filelist to my OD config file , the directory structure gets created in the webserver, but the file is not copied.

i realized that OD was not able to find the file as i am passing the filelist , which is a path , not available in TeamSite. How do i get the file in OD and copy it in the new directory structure.

In lieu of providing us the actual information, you could at least provide us with some sort of example of what you are trying to do with sample paths on both source side and target side.

All I can see from what you posted is that your source area is "/default/target" (suspicious path) and the target area is "D:\images\" - we cannot see anything about the entries in the file list.

Migrateduser

Hey ,

Ok.. my bad then!

So here we go :

Suppose i have a path as below :

a/b/c/d.jpg in TeamSite

I want to deploy it to a new path in the webserver :

say b/c/a/e/d.jpg.

we can give the source :

<\sourceFilesystem area="/default/sample/workarea/pathtofilelist filelist="$FILELIST^">

but can we define the new target path (b/c/a/e/) in the "targetFilesystem" tag ?. i.e. if i create the targetpath and pass on the variable ,say target , which will look something like below :

<\targetFilesystem area="D:\images\$target ^"/>

Will this work ?

Adam Stoller

(paraphrased)

Source File:
a/b/c/d.jpg
in TeamSite
Target File:
b/c/a/e/d.jpg
Source specification:
<sourceFilesystem area="/default/sample/workarea/pathtofile[color=red]list[/color]" filelist="$FILELIST^">
Proposed Target specification:
<targetFilesystem area="D:\images\$target"/>

Questions:

Anything else (like using a target-side DNR script to copy / move the files into the desired target structure) is just asking for trouble.

Migrateduser

Hey ghoti,

Thanks for your response.

Hope you can get me here .

Ok, for each set of files in the filelist i can have a diiferent source and target . Normally through OpenDeploy we replicate the source at the target. But my situation is unique here.
I have to manipulate the path of the source files so that we have diiferent target paths.

say for eg,

say for first source file : a/b/c/d.jpg , the target should be b/a/e/c/d.jpg.

say for second source file : x/y/z.jpg , the target should be y/x/e/z.jpg.

how can i achieve it using a single filelist ?

Regards,

Mav

Migrateduser

In short ,

I want to have a new folder structure in webserver which will be different from TeamSite . i.e. i want to "append" a new directory name in the folder path.

Adam Stoller

In short ,

I want to have a new folder structure in webserver which will be different from TeamSite . i.e. i want to "append" a new directory name in the folder path.

In short - you're not going to be able to easily do this - and trying to is a mistake - restructure the source tree to match the target tree and then everything will be much simpler.

You could create a deployment configuration file with multiple definitions, each of which has explicit filters for both source and target side to only deploy what you want where you want it and not to generate deletions for anything else (or make sure doDeletes is disabled) - but the maintenance of such a configuration file would be a nightmare.

So - you can go that route or do the right thing - which is fix the source directory structure to match the target directory structure (or a combination of fixing both source and target directory structures to meet at a consensus)

Migrateduser

Well I am getting these assets, resizing them and putting them in appropriate folders in TeamSite according to their sizes. The restriction is that when I import them into TeamSite , I can create the size name folder only at the beginning.

However , in the webserver, i need to add the size name folder in the middle of the path.

I am able to achieve this when i deploy the files from a single directory, i.e. pass the source and target to the deployment configuration file.

Is there a way where i can pass the source and target to the deployment configuration file for each file in the filelist? If that can we done, I will be able to achieve this requirement.

Adam Stoller

Well I am getting these assets, resizing them and putting them in appropriate folders in TeamSite according to their sizes. The restriction is that when I import them into TeamSite , I can create the size name folder only at the beginning.

However , in the webserver, i need to add the size name folder in the middle of the path.

Again - you seem to have a problem providing decent examples of what you're talking about - assuming that we already know the environment and the constraints. It really helps to provide real use-case information.

I am able to achieve this when i deploy the files from a single directory, i.e. pass the source and target to the deployment configuration file.

Is there a way where i can pass the source and target to the deployment configuration file for each file in the filelist? If that can we done, I will be able to achieve this requirement.

If the source/target path changes are something that can be programmatically determined, write your own deployment-preprocessing-program (Perl or Java) to process the list of files into source/target pairs and then perform N deployments passing in the explicit source and target directories with the files listed relative to whatever the common denominator is (which sounds like it could be ".")

You're not going to be able to do this with a single deployment configuration file that processes the entire file list at once - at least, as I've already said, not in any reasonable manner that won't turn out to be a nightmare to test and maintain. Break the problem down into manageable components.

Migrateduser

Hey,

Thanks Ghoti.

Let me break this down to as much as I can !!

I can programmatically create the sourcepath , targetpath and also the filelist in a deployment preprocessing program (written in Java). But when we pass this on to the deployment task ( which has the deployment configuration file) , i can only pass ONE sourcepath and ONE targetpath as of now . But I need a sourcepath and targetpath for each file in the filelist. You have talked about N deployments. How can that be done ?

So I need the w/f cycle to go back and forth from the Generate source/target program task to the deployment task till every file in the filelist is processed. Can this be done in OD ?

Adam Stoller

I can programmatically create the sourcepath , targetpath and also the filelist in a deployment preprocessing program (written in Java). But when we pass this on to the deployment task ( which has the deployment configuration file) , i can only pass ONE sourcepath and ONE targetpath as of now . But I need a sourcepath and targetpath for each file in the filelist. You have talked about N deployments. How can that be done ?

By not using an OOTB deployment class and creating your own that does the pre-processing and invokes the deployment, passing all the parameters you need - or (and probably better) creating your own class that does the pre-processing and invokes the deployment in a loop, passing a single source / target pairing along with a file list that contains only the relevant files.

If you search the forums, you should be able to find information about creating your own custom deployment class - or, if you're not using Non-OS Users on Unix, you can write the whole thing in Perl; Either way it's pretty simple:

Migrateduser

Well i looked into the OOTB DeployURLExternalTask class. It extends another class called StartDeployHelper. In the StartDeployHelper class , a variable called "fDeployName" is used as the deployment configuration filename . This is passed onto a perform the deployment. So i believe that an individual source filepath cannot be dynamically modified to another path in the target.

Again my req,

a source filepath : a/b/c/d.jpg

a target filepath : b/a/c/d.jpg.

In the above the starting folder "a" needs to be inserted in between the path in the targetpath. (As shown above)

Basically it is modifying tthe source file path to deploy it at the target for each file.

Has this been done ?

Adam Stoller

Well i looked into the OOTB DeployURLExternalTask class. It extends another class called StartDeployHelper. In the StartDeployHelper class , a variable called "fDeployName" is used as the deployment configuration filename . This is passed onto a perform the deployment. So i believe that an individual source filepath cannot be dynamically modified to another path in the target.

I think you're digging too deep - you should be able to do what you need by extending the DeployURLExternalTask class. See Invoking OD through CSSDK? and Overriding transition comment for DeployTask? for some code snippets and other information. You need to control the deployment process through either (recommended) multiple file lists and multiple invocations of the deployment or (not recommended) a single file list with a difficult-to-maintain single deployment configuration file.

Again my req,
a source filepath : a/b/c/d.jpg
a target filepath : b/a/c/d.jpg.

In the above the starting folder "a" needs to be inserted in between the path in the targetpath. (As shown above)

Basically it is modifying tthe source file path to deploy it at the target for each file.

In the above example (which differs from your previous examples - the source path would be a/b and the target path would be b/a and the file list would contain c/d.jpg

Has this been done ?

Unclear, but the point is that it can be done - if you're willing to invest the time and effort into coding for it.

Migrateduser

Hi,

Today,I have a root folder "a". I have a list of files in different folder stuctures ,

say

a/d/e/f.jpg
a/x/y/z.jpg
a/p/q/r.jpg

I want the target to be :

d/e/a/f.jpg
x/y/a/z.jpg
p/q/a/r.jpg

This is my requirement . Re-structuring the source path for EACH file in the filelist.

Adam Stoller

You've provided piece-meal information all the way along.
I've provided you all the information you need to develop a solution.
I suggest you start working on the code, or hire someone who is capable to do so.

Migrateduser

Hey ,

Thanks for your response Ghoti.

This is such a particular use case that things had to get complicated.

When I called up support, they told me it can go as an Feature Enhancement request..

SO......

Anyways thanks for all your painstaking replies.( even the hiring part.. LOL)

Anyways , for the rest , my previous post has the exact requirement. If anyone has even come close to doing something like that .. do give me a shout

Mav