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

Importing DCRs

brooke

Has anybody encountered problems when migrating DCRs into a new environment?

We reinstalled TeamSite and replaced all of our files with the backups -- everything migrated well except the DCRs. When we try to view/edit a DCR, it does not treat them as valid files. However, we're able to copy and paste the same DCR XML into a new file, and it works perfectly.

Any ideas? Thanks so much!
Brooke

Find more posts tagged with

Comments

Migrateduser

Check to make sure that the extended attributes attached to the dcr's on the source are also on your new imported files. This is the only way that TeamSite knows that a file is a dcr and should open the dcr editor rather than launchpad.

brooke

That sounds like what's happening here -- do you happen to know how to do this?

Migrateduser

Well the thing you probably want to first look at is here:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=1730

There are some scripts floating around that will extract all of the dcr extended attributes out to a file that can then be used as the input to another script. I am trying to find one of those scripts now, but not having any luck at the moment. If someone else has one, please post.

Jeremy

Hi,

We've just been doing that...here are the files that Interwoven Support sent me...they are for Unix - hope they do the trick!

Jeremy

Migrateduser

Like nacks said, if you import a DCR into a new environment, all the meta-data that associated that DCR is lost. It now becomes a file to be edited through Launchpad. I ran into this when I had to delete my templatedata folder and import the entire folder again (from a backup I made before deleting). The templates in the workarea opened fine, but not if I tried opening a dcr directly (in templatedata folder) it took it through launchpad. I had to reopen all of the pages in the wa, save the dcr again and it reset the meta-data and corrected the problem. This might be a little different problem than what you are explaining but I thought it might shed a little light on the issue.

Migrateduser

This is occuring because when you copy or move DCRs through the filesystem, the metadata isn't moved along with the file. TS no longer knows that the DCR is in fact a DCR which should be opened via templating. The specific CLT to extract and specify extended attributes is iwextattr. You can enter iwextattr without any flags to get te basic syntax of the command. As an example, to list the extended attributes for a DCR, use this syntax:

iwextattr -l Y:\default\main\[branch]\WORKAREA\[workarea]\templatedata\internet\data\test1

You will get something similar to: TeamSite/Templating/DCR/Type=internet\pr

So after the file (DCR) is copied to a new system, you will need to "re-set" the metadata using this command:

iwextattr -s /DCR/Type=internet\pr Y:\default\main\[branch]\WORKAREA\[workarea]\templatedata\internet\pr\data\test1

Case and syntax is very important and if they are not correct, you will get an error. If you have many DCRs you can create a script to run these commands.

faz
Interwoven Technical Support Engineer

Gery

Hi,

I can not access to https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=1730 to get a script that takes all of dcrs in order to launch iwextattr -s attr=valor Y:\dir\...\asset

I'd like someone send to me this script to unix environment (my e-mail address of devnet: gerardo.suarez@ienet.es).
I need only this to close my project.

Thanks for help.

Gery

gzevin

something like this could help:

#!/usr/iw-home/iw-perl/bin/iwperl
my $category=shift;
die "no arguments supplied" unless $category;

my($iwhome) = `iwgethome`; chomp $iwhome;
my($setAttrib) = $iwhome . "\/bin\/iwextattr -s TeamSite/Templating/DCR/Type\=$category";

my $exec_string = "find . -type f -name \\\* -exec $setAttrib \'{}\' \\\;";

`$exec_string`;

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

Migrateduser

The support article is also visible on devnet here:
http://devnet.interwoven.com/site.fcgi/techlib/1730.

If you do not have access to the support site, but are given an article to look at there, you can always try to see if the article is visible on DevNet. the article IDs are shared, since the back-end repository for support and DevNet is the same.

To get the first part of the URL (if you don't remember it), go to the Tech Library tab, and click on "look up article by ID". Then type in the article ID from support. If you get "not found" then DevNet does not have that article.

Regards,

lissa