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

Need to migrate DCRs from teamsite5.5.2 to teamsite 6.7.1

johnmukkad123

Hi friends we are working on the migration of contents from older version of teamsite Teamsite5.5.2 to newer version Teamsite6.7.1 .

Please provide some suggession about how to migrate existing DCRs from old production teamsite to new teamsite. If we copy those DCRs its not opening in edit mode in new teamsite.

Please provide some suggession about copying of those DCRs to new teamsite?

Find more posts tagged with

Comments

kalai

How you are migrating the DCR content from 5.5.2 to new Teamsite server 6.7.1?. If you are manually copying the content from old server to new server then you need to set the extended attributes to each DCR. Also make sure that you have copied the inline/callout related files to new server(if any).

ISCBorisB

Hi friends we are working on the migration of contents from older version of teamsite Teamsite5.5.2 to newer version Teamsite6.7.1 .

Please provide some suggession about how to migrate existing DCRs from old production teamsite to new teamsite. If we copy those DCRs its not opening in edit mode in new teamsite.

Please provide some suggession about copying of those DCRs to new teamsite?

The easiest way to do that is perhaps simply copy DCRs as plain Files and then set appropriate
TeamSite/Templatedata/DCR/Type Metadata to corresponding Category/Type.

Alternatively, you can use OD to deploy DCRs to the new location with "applyExtAttrs=yes" setting
thus keeping all Extended Attributes, Metadata including. Before trying that make sure that your
Source side (Base) OD Version supports this feature, you may have an old OD that does not.

test_crosstab.rptdesign

Adam Stoller

Another alternative, though somewhat intensive, is to actually use iwmigrate to copy the files (with their EAs) along with their historical versions from a copy of the 5.5.2 backing store into the new 6.7.1 backing store.

This would create the branches and (with the -w flag) workareas in the new store and transfer the complete history of the files. This assumes (a) that your 5.5.2 backing store is "healthy" and (b) that you cut an edition on each branch in the 5.5.2 store to use as an end-point for the historical migration.

If you don't care about maintaining all the history, then doing something like what has previously been suggested should work just fine - just remember to create the branches and workareas first (since those cannot be done through a simple copy or deployment process (unless you code it with a custom DNR script)

nipper

Of course an easy way is to write a Perl script that will apply the EAs after the fact if you have copied them over already. Something I do quite often.



#!/bin/sh
eval 'exec `/usr/bin/iwgethome`/iw-perl/bin/iwperl -x -S $0 ${1+"$@}';
#!iwperl -w
use TeamSite::Config;
use File::Find;
(my $iwhome=TeamSite::Config::iwgethome()) =~ tr|\\|/|;
(my $iwmnt=TeamSite::Config::iwgetmount()) =~ tr|\\|/|;
$start=$iwmnt."/default/main/llumc/lomalindahealth.org/Medical_Center/WORKAREA/web/templatedata";
my @list;
find(\&wanted, $start);
foreach $DCR (@list) {
 next if ($DCR =~ m|\.cfg$|i);
 next if ($DCR =~ m|\.tpl$|i);
 next if (-d $DCR );
 $command = "$iwhome/bin/iwextattr -g TeamSite/Templating/DCR/Type \"$DCR\"";
 chomp (my $result= `$command 2>&1`);
 if ($result =~ m|not found|i) {
  ($EA = $DCR) =~ s|.*templatedata/(.*?)/(.*?)/data/.*|$1/$2|i;
  $command = "$iwhome/bin/iwextattr -s TeamSite/Templating/DCR/Type=$EA \"$DCR\"";
  `$command 2>&1`;
 }
}
sub wanted {-f && push(@list, $File::Find::name);}