Home › Forums › Luminis Platform / System

Channel Migration

Fri, 2007-08-17 13:55 — vikram

Is there a simple way of migrating all channels from one environment to another? I know in Luminis III, there was this Migration Cloner that migrated the entire platform. I know a similar process exists in IV but was wondering if there is a short, simple way to migrate JUST the channels.

0
No votes yet
‹ Lum IV custom role problem CAS in Parallel Deployment ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Mon, 2007-08-20 10:34 — wjdennen

For targeted content channels....

From the Admin guide:

"Luminis Platform IV provides the ability to migrate targeted content channels from one Luminis Platform system to another. This feature makes it easy for institutions to share targeted content channels between several systems or to create and validate targeted content channels in a test environment before moving them to a production environment."

lp40000cstg.pdf is the file that has more info. Page 4.37.

The script that exports and imports targeted content channels is located under
$CP_ROOT/bin and is called tccmigrator. This script is used to migrate targeted content channels from one Luminis Platform IV or higher system to another.
The migrator script requires the following syntax:

tccmigrator export|import []

Valid options for the script are:
-d = pathname to input/output directory
-h = displays this message

The migration data directory is specified as shown above with the -d option. For exporting, a migration directory is not required as a default time-stamped directory will be created in the current directory. By specifying the -d option, the user is allowed to specify the name of the exported migration data directory. On import, it is required that the migration data directory be specified using the -d option.

The migration data directory contains all the files needed to migrate the Targeted Content Channels to a different system.

Thu, 2008-05-01 23:55 — ToddTrann

Copying channels did work

Inspired by your question, I set about to do exactly as you had said: copy all of our production channels into our test environment. It took two days of messing around, but yes, it did work.

Now, the sad part: I actually didn't write down what I did. Well, I started to, but then I got sent off on so many wild goose chases that I lost track. Why? Because I also copied all of the layout fragments (owners, tabs and channels) so that test was a mirror of production. It isn't for the faint of heart. :)

Anyway, here's what I can recall:

- copy all data from prod db tables UP_CHANNEL and UP_CHANNEL_PARAM and UP_CHANNEL_SUBSCRIBABLE, except for channels that already exist in test db

- update data in test db for the three tables above, changing any URLs and host names from prod to test

- add any CPIP config data (via configman) that was missing from test, remembering to adjust URLs for test systems where appropriate

- copy all files from prod file system /opt/luminisShared/site/content/ into test (this is for the targeted content channels)

- export LDAP data from ou=Channel,ou=Content,ou=mail.your.edu,ou=your.edu (as an LDIF)

- go through LDIF, looking for data that needs to be changed from prod to test

- import LDIF into test LDAP

- and of course, reboot

Well, sorry for the sketchy details, but perhaps this can get you on your way, should you try this at home! To answer your original question: no, there is no "simple" way.

Todd