Migration of TeamSite and LSCS servers

Shah Khatri

We have TS/LSDS/LSCS 7.3.1 on Windows servers.  We are migrating from a dedicated Data Center to a Cloud, but retaining the same versions of Interwoven's software (and Windows).  We've already migrated TS to a box in the Cloud.  Now we need to migrate LSCS to another box in the Cloud.

 

The problem is that we'd really like not to republish content from the new TS to the new LSCS server (as some content is in flux).  So, how can we migrate the LSCS content store, the IDOL folder and the LSCS Database so they refer to the new TS host name?  I tried updating the TS hostname in the project table in the LSCS DB, but it doesn't seem to be that simple.

 

By the way, I also tried "http://new-lscs-host:1876/lscs/v1/projects///new-ts-host/default/main/our-branch?method=DELETE," but that didn't seem to do anything.  The reason I tried this is that we've already migrated TS and are publishing from the new TS server to the old LSCS server.  So the old LSCS server has ended up with both old-ts-host and new-ts-host projects!  Ai, woe is me.

 

Ideas?

 

Thanks,

 

Sunny

Rick Poulin

First, cloning an LSCS instance is documented in the LSCS tech ref document, in a section called something like "adding an instance to the lscs farm". You can use this to 'move' your repository by cloning it to the new server and then throwing out the old one.

 

The unfortunate part is that you won't be able to change the project names, so any new deployments will go to the different project name, as you've said. You can force your new TS server to use the old project names via entries in lscs-authoring.xml, but that's not ideal. I've had to do a full republish before, for lack of any better options.

 

Lastly, your delete won't work unless you enable HTTP Tunnelling in the lscs-conf.properties. Otherwise, use telnet to connect to the proper port and then issue an HTTP DELETE manually:

DELETE /lscs/v1/projects/project-name

Topic_37091_XML_PGV.rptdesign