Extended attributes are missing after deployment

Hi ,
We are using file list deployment for deploying a folder(datatype) from one content store to another.(I am deploying from iwadmin store to xyz store).My aim is to deploy a datacaputre.cfg across the branches. If I deploy the datatype folder of IWADMIN store,the dcrs in data folder of the xyz store are getting effected because of this, Extended attributes are missing and the dcrs are behaving like a static files.
I tried with adding applyExtAttrs="yes, No chnage from that
if change targetFilesystem to targetTeamsite, the following error is coming in the logs
Error : CONFIG_FILE.
Details: applyExtAttr is specified for sourceFileSystem

I have attached my od config file.

Any help will be appreciated . Thanks in advance.

- Harshitha

Find more posts tagged with

Comments

Adam Stoller

On the source side in the iwStore elemenet - you need to specify recordExtAttr="yes"
On the target side in the targetTeamsite (not targetFilesystem) element - you need to specify applyExtAttrs="yes"

Try that and see if it works correctly

Harshitha

I have made the changes as you said, it is giving the same error in the logs

ENG: Start perform internal conversion for:

\Interwoven\OpenDeployNG\conf\xyz\www_filelist_deployment.xml
ENG: ***ERROR - Failed converting config file

\Interwoven\OpenDeployNG\conf\xyz\www_filelist_deployment.xml.
Error : CONFIG_FILE.
Details: applyExtAttr is specified for sourceFileSystem

I have attached the config file

Adam Stoller

I have made the changes as you said, it is giving the same error in the logs

ENG: Start perform internal conversion for: \Interwoven\OpenDeployNG\conf\xyz\www_filelist_deployment.xml
ENG: ***ERROR - Failed converting config file \Interwoven\OpenDeployNG\conf\xyz\www_filelist_deployment.xml.
Error : CONFIG_FILE.
Details: applyExtAttr is specified for sourceFileSystem

I have attached the config file

There's something wrong here - because the error message above does not jive with the configuration file you posted before.

Make sure you're actually trying to use what you posted - and/or post what you're using.

Harshitha

thank you very much for your help, there were other definitions in my config file which are causing this error, I removed all other definitions and tried it again, It is working fine now Smiley Happy

... I am attaching the working code...

Adam Stoller

Glad I could help - though if you had looked more closely at the error message you probably could have figured it out yourself pretty easily; sometimes you just have to "take a step back" in order to "move forward".

Migrateduser

Hi,

I have a similar requirement and followed the above steps and now i can see the EAs are retained for the DCRs.

Here is the problem iam running into, after deployment the attributes 'Modified By', 'Version', 'Owner' and 'Group' also gets changed for all the existing DCRs. I don't want this to be changed and wanted to retain the previous values as is. How do i configure this in my deployment configuration file?

I went through OD manuals but couldn't find any break through.

Any pointers?

Note: TS version 7.1, windows 2008.

Adam Stoller

Here is the problem iam running into, after deployment the attributes 'Modified By', 'Version', 'Owner' and 'Group' also gets changed for all the existing DCRs. I don't want this to be changed and wanted to retain the previous values as is. How do i configure this in my deployment configuration file?

I don't believe what you are asking for makes sense.
First of all - you're talking about file attributes not extended attributes.
Secondly:

be able to record and then somehow utilize the owner/group information to "fix" that aspect - but that would all be custom code.