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

Issue with Extended Attributes

foogoo

OpenDeploy from TS to TS is not working:
It is deploying correctly without setting the file ea attributes.
When I set the value for applyExtAttrs to 'yes', I got the "Failure" error message. I followed the OpenDeploy doc and the steps I did is as follows:
1. Used [highlight] <iwStore> [/highlight] tag for my source directory
2. Added this tag to my target [highlight]
<targetTeamsite area="X:\default\main\CPO\WORKAREA\production\templatedata" applyExtAttrs="yes" />[/highlight]
3. Added this line in deploy.cfg
[highlight] teamsite.version: 6.7.1[/highlight]
Pretty much this is what I followed to work this out. I don't know why I am still getting this error. My question is how is this working fine without setting ea's when I set [highlight] applyExtAttrs="no"[/highlight]

ERROR MESSAGE:
src.ts_to_ts.Filelist_DCR.wcm-cpc-dev.to.wcm-cpc-dev.log

LIB: 2008-11-18 11:35:13 Options: deploy applyExtAttrs ignore_acls do_manifest_for_dnr verbose_level=5
LIB: 2008-11-18 11:35:13 ERROR:[highlight] Failed FindServerByName with TeamSite[/highlight]
LIB: 2008-11-18 11:35:13 Receiver-ERROR: ERROR: prepare-failed.
LIB: 2008-11-18 11:35:13 ERROR: Failed to deploy local_directory[.] of area[X:\default\main\CPO\CM0\WORKAREA\merge\templatedata] for filelist[D:\iw-home\httpd\iw-bin\CPO\common\dynamic\FileList_119875_dcr.txt]
LIB: 2008-11-18 11:35:13 ERROR: Failed 1 of 1 filelists

TeamSite (Windows)

OpenDeploy(6.0.2.1.0 Build 52162 Interwoven 20050921)
TeamSite: 6.7.1 Build 68759 Interwoven 20071029

This is my config file:
[php]
#####################################################################################################

filePath="D:\iw-home\httpd\iw-bin\CPO\common\dynamic\FileList_119875_dcr.txt" name="Filelist_DCR">

#####################################################################################################
#####################################################################################################

\iw-home\OpenDeployNG\etc\odnodes.xml

#####################################################################################################
#####################################################################################################

\iw-home\OpenDeployNG\etc\odbase.xml

bindPort="20014" />

bufferSize="8000" />

dbUrl="jdbc:HypersonicSQL Smiley Very Happy

:\iw-home\OpenDeployNG\db\schedDB"
dbUser="sa"
dbPassword="" />

infoStreamFormat="manifest" />

cfgPath="D:\iw-home\OpenDeployNG\etc\eventReportingConfig.xml" />

directory="E:\Interwoven\Logs\OpenDeploy602"
level="verbose"/>

#####################################################################################################
#####################################################################################################
[/php]

Find more posts tagged with

Comments

kshitiz

You can specify applyExtAttrs="yes" only when you are having TeamSite comparision deployments. Refer OpenDeployment Configuration Guide's Deploying TeamSite Extended Attributes with TeamSite Files section. TeamSite comparison deployments are those deployments when you compare two teamsite areas in source i.e. under you are using element.

Adam Stoller

You can specify applyExtAttrs="yes" only when you are having TeamSite comparision deployments. Refer OpenDeployment Configuration Guide's Deploying TeamSite Extended Attributes with TeamSite Files section. TeamSite comparison deployments are those deployments when you compare two teamsite areas in source i.e. under <iwStore> you are using <areaDiff> element.

In what section of what manual did you find the above?

From my reading of the manual - it looks like if your Receiver is on Windows - you need to specify the absolute path for the target area which, based on the previously posted code would be:

...
        <target> 
            <targetTeamsite  area="Y:/default/main/CPO/WORKAREA/production/templatedata" applyExtAttrs="yes" />
            ...
        </target>
        ...

You might even have to reverse the '/'s to '\'s, though that's less clear

However, there is also a caveat which requires that you not be using a

transientDirectory

setting in the

listenerProperties

of the element in the server configuration file on the Receiver - which at this point we have no information about whether this was or was not done in this scenario.

I'd suggest putting the Y: into the target area path first, if that doesn't work, then try switching the path separators ('/' -> '\')

kshitiz

In what section of what manual did you find the above?

Quoting from the OpenDeploy Deployment Guide for 6.2:

[font=Verdana][size=2]You can include TeamSite extended attributes (EAs) in a TeamSite comparison deployment to a target TeamSite area.

[/size][/font]

[font=Verdana][size=2]

[/size][/font]

[font=Verdana][size=2]As per my understanding 'TeamSite comparison deployment' is kind of deployment where you are comparing two teamsite areas using and deploying the difference. Am I wrong somewhere in the interpretation?

[/size][/font]

landing.zip

Adam Stoller

Quoting from the OpenDeploy Deployment Guide for 6.2:

[font=Verdana][size=2]You can include TeamSite extended attributes (EAs) in a TeamSite comparison deployment to a target TeamSite area.
[/size][/font]
[font=Verdana][size=2]
[/size][/font]
[font=Verdana][size=2]As per my understanding 'TeamSite comparison deployment' is kind of deployment where you are comparing two teamsite areas using and deploying the difference. Am I wrong somewhere in the interpretation?
[/size][/font]

I'm not positive (as I haven't dealt with deploying EAs since that feature became available) - but I think it's more a matter of how the docs were written than a limitation of the product. My guess is that the information about deploying EAs was added to the section about TeamSite Comparison deployments without regard to whether it worked in any of the other deployment contexts.

As I don't have OD available to me currently, I cannot verify this - but perhaps someone who does have OD available could string together a quick verification deployment to see if, for example, a filelist deployment could be performed with transfer of EAs - assuming all other aspects of the deployment are set correctly for it?

ISCBorisB

I'm not positive (as I haven't dealt with deploying EAs since that feature became available) - but I think it's more a matter of how the docs were written than a limitation of the product. My guess is that the information about deploying EAs was added to the section about TeamSite Comparison deployments without regard to whether it worked in any of the other deployment contexts.

As I don't have OD available to me currently, I cannot verify this - but perhaps someone who does have OD available could string together a quick verification deployment to see if, for example, a filelist deployment could be performed with transfer of EAs - assuming all other aspects of the deployment are set correctly for it?

I have no problem whatever deploying Extended attributes in File List mode.
Target Format for Windows is ...area="Y:/default/main...", eg "With Y, forward slash"

foogoo

[php]
In my odbase.xml, I have
...

...

...

When I change the path,I am getting the same error message.

area="X:\default\main\CPO\WORKAREA\production" applyExtAttrs="no" /> => It is working without setting ea
area="X:\default\main\CPO\WORKAREA\production" applyExtAttrs="yes" /> => Is is not working
area="X:/default/main/CPO/WORKAREA/production" applyExtAttrs="no" /> => it is working without setting ea
area="X:/default/main/CPO/WORKAREA/production" applyExtAttrs="yes" /> => It is not working

area="/default/main/CPO/WORKAREA/production" applyExtAttrs="no" /> => It is working without setting ea
area="/default/main/CPO/WORKAREA/production" applyExtAttrs="yes" /> => Is is not working

area="\default\main\CPO\WORKAREA\production" applyExtAttrs="no" /> => It is working without setting ea
area="\default\main\CPO\WORKAREA\production" applyExtAttrs="yes" /> => It is not working

and my error message is:
LIB: 2008-11-19 09:13:32 ERROR: Failed FindServerByName with TeamSite
LIB: 2008-11-19 09:13:32 Receiver-ERROR: ERROR: prepare-failed.
LIB: 2008-11-19 09:13:32 ERROR: Failed to deploy local_directory[.] of area[X:\default\main\CPO\CM0\WORKAREA\merge] for filelist[D:\iw-home\httpd\iw-bin\CPO\common\dynamic\FileList_119875_dcr.txt]
LIB: 2008-11-19 09:13:32 ERROR: Failed 1 of 1 filelists

[/php]

foogoo

Has anybody tried this with OpenDeploy(6.0.2.1.0 Build 52162 Interwoven 20050921)? I heard from some people, that 6.0.2 won't support ea.
Can somebody make sure it for me..
Thanks

nipper

Has anybody tried this with OpenDeploy(6.0.2.1.0 Build 52162 Interwoven 20050921)? I heard from some people, that 6.0.2 won't support ea.
Can somebody make sure it for me..
Thanks

According to the 6.0.2 manual (OD Admin, page 111):
You can include TeamSite extended attributes (EAs) in a TeamSite comparison deployment
to a target TeamSite area. TeamSite extended attributes are metadata that provide additional
properties information about TeamSite files. You might want to deploy TeamSite EAs along
with the associated files for the following purposes:
o Migrating files from one TeamSite server to another.
o Synchronizing the content between multiple TeamSite servers.
o Syndicating content from one TeamSite server to another for repurposing.
Refer to your TeamSite documentation for more information on TeamSite extended
attributes and their usage.
Deploying EAs with TeamSite files is enabled through the targetTeamsite element’s
applyExtAttrs attribute:
<targetTeamsite area="/default/main/dev/WORKAREA/jdoe"
applyExtAttrs="yes">
If you specify yes for the applyExtAttrs attribute, the EAs associated with the TeamSite
files are included in the deployment. The default value is no. If you specify no (or omit the
attribute), the EAs are not included in the deployment.
Note: You cannot deploy TeamSite EAs to a TeamSite target where an alternate location
for temporary deployed files is specified in the listernerProperties element’s
transientDirectory attribute. Refer to "Specifying Alternate Locations for
Temporary Deployment Files" on page 114 in the OpenDeploy Installation Guide for
more information on this feature.

groupnm.rptdesign