Migrating data JAZZ test to prod
One of our project groups wants to start using JAZZ right away. I'm not complete in my prod server setup, having only a low powered test server running 4.0.1.
I know in the past releases there was no easy way to "rename" the URI without a lot of back end work but I seem to recall some enhancements to this.
Is it possible/feasible (aka. easy to do) to start up a project on our JAZZ test server and then migrate its data to our prod server? Note that we do not have any reverse proxy in place at this time. We plan on using RTC, DNG and RQM.
2 answers
Norman,
With the release of CLM 4.x , there is now built in functionality to rename your Public URI
When you have a moment, take a look at the following two articles; they will give you a good overview of the functionality and impact
https://jazz.net/library/article/818
https://jazz.net/library/article/1120
Ara
Comments
I'd recommend setting the public URI of the new project to what you want to use in your production environment. Use the DNS or etc/hosts on local machines to route the CLM URL to the test server's IP address.
For example (in etc/hosts):
For example (in etc/hosts):
my.clmserver.com 123.456.789
When you want to move the installation to a production machine, you keep the public URI and change the DNS (or etc/hosts).
It's cleaner to keep the public URI rather than changing it if you can. The Server Rename feature is not without its baggage. It doesn't actually change the URI of the data stored in the project. It creates a hash table that maps each call from the new public URI to the old public URI, and uses the old URI to actually access data.
The result is that Server Rename prevents you from re-use the old public URI. And you take performance hit for each call, though it's a very small one that you probably won't even notice. But there's no reason to add cycles to your URI calls if you don't need to.
Comments