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

filelist deployment

Ottawa_IWOV

Hi All-

I have been trying to figure this out for a while, but need some assistance.

I am on OpenDeploy 6.0, trying to do file list deployments. I am acutally replication iw-home from a workarea. So when a file is edited, I need it OD'ed to the server and where it belongs in iw-home.

First off, I am just tyring to get a sample working. So I created a file in /tmp called /tmp/list.lst that contains /data/iw-home/tmp/temp.log

I want to test that this file will move to /data/iw-home/tmp on the server, but to no avail.

Here is what my deployment looks like:

<definition name="LocalConfig">
<source>
<fileSystem >
<filelist area="$flistarea^" filePath="$fpath^" >
<pathSpecification>
<path name="data/iw-home/tmp" />
</pathSpecification>
</filelist>
</fileSystem>
</source>

<target useReplicationFarm="MYFARMNAME">
<targetFilesystem area="/data/iw-home/tmp"/>
<comparisonRules dateDifferent="yes"/>
<permissionRules file="0644" directory="0755"/>
</target>
</definition>

I am passing to parameters flistarea, and fpath that contain the path to the WA and the path to the filelist. I am using the path specification to match only the filename (I picked this up on a prior post).

Nothing seems to work on this.

Any ideas???

Thanks,

Lucas Cochrane
lucas.cochrane@baucanada.com

Find more posts tagged with

Comments

Adam Stoller

Is this a loopback deployment? (i.e. From/to the same machine) - if so - you're specifying the exact same path for both source and target so it's not clear that anything should really happen.

If not - have you ensured that /data or /data/iw-home or /data/iw-home/tmp is an allowed directory for the sender on the receiver? (and you restarted the receiver after making that change to the config file?)

It might also help if you post the logfile(s) associated with the deployment - since "Nothing seems to work on this" is not really very descriptive.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Dwayne

Caveat: I think that the below is right - but I'm not 100% certain

It looks like you're specifying the full path to the filename in your file list. If I understand your setup correctly, what you're telling OD to do is to deploy the file named $flistarea/data/iw-home/tmp/data/iw-home/tmp/temp.log to /data/iw-home/tmp/data/iw-home/tmp/temp.log, when you meant to deploy $flistarea/data/iw-home/tmp/temp.log to /data/iw-home/tmp/temp.log

I would set path="." instead of path="data/iw-home/tmp" and see what happens.

--

Current project: TS 5.5.2/6.1 W2K

Adam Stoller

You are correct (I missed that part - good catch) - the entries in the filelist must be relative to the [filelist area]/[path name] value

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Dwayne

Yup. One of the worst mistakes I ever made at a client site was to assume that the area was the deployment "Base" and that the path just selected a subcompnent of that base for deployment. What actually happens is that the deployment base is the concatination of the area + path.

Based on my mistaken understanding of that mechanism, I tried to use the "path" attribute to delete a component of a production web site. Unfortunately, because of my misunderstanding, I actually wiped out the entire production site. Not a good thing, to say the least. I redeployed immediately, of course, but there were some files that weren't in TeamSite. So we had to restore from backup.

Fortunately, these people happen to be the nicest clients in the world, so I managed to escape without serious injury. But I was panicing for a while.

--

Current project: TS 5.5.2/6.1 W2K

Ottawa_IWOV

Thanks for your quick repsponses. I will look into these immediately!

Lucas Cochrane
lucas.cochrane@baucanada.com

Ottawa_IWOV

This still doesn't seem to work. My filelist contains the path to one file:

data/iw-home/tmp/temp.log

I then past the filelist area as:

/default/main/CONFIG/Workarea/Common

so the full path would be

/default/main/CONFIG/Workarea/Common/data/iw-home/tmp/temp.log

And all I want is temp.log deployed to /data/iw-home/tmp, but it is not working, and I am not receiving any errors either. And, yes, /data/iw-home/tmp is an allowed directory in odbase.xml

It's driving me absolutely insane!!

Thanks,

Lucas Cochrane
lucas.cochrane@baucanada.com

Adam Stoller

What do you have for <path name="...."/> <<== here

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Ottawa_IWOV

nothing currently

Lucas Cochrane
lucas.cochrane@baucanada.com

Adam Stoller

Nothing? or "." ?

Perhaps you can post your *current* deployment config?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Ottawa_IWOV

Here is my current deployment config:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
- <deploymentConfiguration>
<logRules maxBytes="32Mb" level="verbose" />
<localNode host="****" />
- <replicationFarmSet>
- <replicationFarm name="MYFARMNAME">
<nodeRef useNode="MyLocalHost" />
</replicationFarm>
</replicationFarmSet>
- <definition name="LocalConfig">
- <source>
- <fileSystem>
- <filelist area="$flistarea^" filePath="$fpath^">
- <pathSpecification>
<path name="." />
</pathSpecification>
</filelist>
</fileSystem>
</source>
- <target useReplicationFarm="MYFARMNAME">
<targetFilesystem area="/data/iw-home/tmp" />
<comparisonRules dateDifferent="yes" />
<permissionRules file="0644" directory="0755" />
</target>
</definition>
- <deployment transactional="no">
<execDeploymentTask useDefinition="LocalConfig" />
</deployment>
</deploymentConfiguration>

Lucas Cochrane
lucas.cochrane@baucanada.com

Adam Stoller

Okay - so path name = "." - good.
Now - you're saying that $flistarea = "/default/main/CONFIG/Workarea/Common"
and the file list contains a line of "data/iw-home/tmp/temp.log"

You might want to start that path in the filelist with either '/' or perhaps better './'

If I read the config correctly though, you will probably get a result on the target side of:
/data/iw-home/tmp/data/iw-home/tmp/temp.log

You will probably either want to change the target area to '/' and make that an allowedDirectory
*or*
Change things so that you have
<path name="./data/iw-home/tmp"/>
and your filelist would contain an entry of:
"./temp.log"

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com