Component Migration

raeovine

We develop our components on one set of servers and after the component passes testing, we want to migrate the component from the test environment to staging and then production. I've noticed that, when comparing versions of the components after migration, that the BaseComponent Version has a path in it which includes the name of my test server.

I am promoting the component to the next stage by manually moving the file to the next teamsite server environment. Obviously, this isn't the best way to do this because I already have path info incorrect. Is there a better way to go?

karel

Interesting question, I'd like to know that one as well.
Should the servername be modified? Are there other changes recommended?


You can use SPAR files to move components around, or OpenDeploy (TS to TS deployment), that is already better than moving them manually.

BUT, this doesn't resolve the problem with the server name.

In the TeamSite SitePublishers Developers guide, you'll find information about SPAR files (apendix J in ts_672sp1_spdev_v03_en.pdf).
They mention an ant script that resets the version number of your components, maybe it also takes care of the path.
If not, its easy to modify the ant script to reset the path as well.