some clarification related to filelist based deployment

manu1905

Hi All,

I have attached the od config file for deployment of the content from interwoven to targetfilesystem area.

in that target location I want the content to get deployed as:

/common/zone1/test1/...

/common/zone1/test2/...

/common/zone2/test1/...

/common/zone2/test2/...

In my interwoven I have to main folders apart from templatedata&colon;

maincontent/test1/....

maincontent/test2/....

seccontent/test1/...

seccontent/test2/....

but i want only the test1/.... and test2/.... should get deployed from maincontent and seccontent to the above path...and not these main folders maincontent and seccontent should get deployed

mean I want :

/common/zone1/test1/...

/common/zone1/test2/...

and not

/common/zone1/maincontent/test1/....

/common/zone1/maincontent/test2/...

similarly for seccontent as well.

/common/zone2/test1/...

/common/zone2/test2/...

and not

/common/zone2/seccontent/test1/....

/common/zone2/seccontent/test2/...

.I have attached the config file as well.....plz confirm if that is ok or

give ur valuable suggestions on it.

thanks,

Find more posts tagged with

Comments

Rick Poulin

OD doesn't do any path remapping, so if you don't want "maincontent" to be part of the runtime structure, you'll have to set your source area to include this folder (instead of stopping at the root) and update your target area accordingly. Given that you have multiple source "areas" now, you'll likely require more than one <deployment> and <execDeployment> nodes.

manu1905

Hi,

can calrify more with the example or on the file which I attached.

thanks

Rick Poulin

Right, sorry, you already have two separate <dpeloyment> nodes. So you'd be changing this part:

    <source>
          <fileSystem>
                <filelist area="$area/maincontent" filePath="$filelist">
                    <pathSpecification>
                        <path name="test1"/>
                    </pathSpecification>
					<pathSpecification>
                        <path name="test2"/>
                    </pathSpecification>
                </filelist>
            </fileSystem>
        </source>

And then you'll have to update the piece that generates your filelist such that the entries start inside maincontent instead of the root of the workarea.

Adam Stoller

Try clarifying for yourself (i.e.: read the manuals) and posting what you come up with - and then we'll critique it for you.

manu1905

Thanks for response rpoulin,

Just one more favor, how to update the filelist such that entries start inside maincontent rather than the root of tthe workarea.

waiting for your positive response.

thanks

Adam Stoller

manu1905 wrote:

Just one more favor, how to update the filelist such that entries start inside maincontent rather than the root of tthe workarea.

waiting for your positive response.

thanks

This is what is known as "custom code" - i.e.: You need to write some code to do that; or hire someone who knows how to do it for you.

manu1905

Thanks ghoti...

if I get some directions for this or the place from where I can refer for this, it will be great help for me...

thanks

Adam Stoller

You have already been given directions. What, exactly, do you not understand?

manu1905

Hi Ghoti,

directions to write the custom code to generate the filelist such that the entries start inside maincontent instead of the root of the workarea.

I need to know how the filepath ="$filelist" gets generated, I do not have idea on this etc.

thanks,

Adam Stoller

If you do not understand the directive that was shown - you need to read the manuals.

If you do not understand how to programmatically create the contents of the filelist to meet your needs, you need to either take some basic code writing training or hire someone who knows what they're doing - this is kind of like "programming 101", however I'll give you a hint:

Navigate a directory structure to obtain a complete list of paths to files and modify the path for each entry so that the first (and/or second) path elements are not included in the final result.

Rick Poulin

I'm guessing you're using the OOTB deployment task, so the filelist is currently generated for you.

As ghoti said, the modification you want to make requires custom coding, which you'll have to write. You can either do this by

a) overriding the Java class that drives the deployment task and setting it via the TaskName variable, or

b) you can create a brand new task in front of it to generate the filelist and then set that as an odSubst_ variable on your deployment task

Option B would be my suggested approach, since you then don't have to rewrite the part that connects to OD.