How to transfert RTC repository data and history
4 answers
Hi Fabien,
this depends on the use case and the source and target environment.
Today you can migrate from Tomcat to WAS and you can certainly also stay with Tomcat but move to a new tomcat install. See: http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/nav/6_3
However, as of today you have to keep the public URI: https://jazz.net/library/article/749. So what you can do today is, setup the other server, restore the data like for a backup/restore operation. See https://jazz.net/library/article/795 for backup/restore considerations. The important points are the configuration files, index files etc. Then make sure that the new server is reachable using the old URI and keep the old server off. You can use a proxy or something else.
this depends on the use case and the source and target environment.
Today you can migrate from Tomcat to WAS and you can certainly also stay with Tomcat but move to a new tomcat install. See: http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/nav/6_3
However, as of today you have to keep the public URI: https://jazz.net/library/article/749. So what you can do today is, setup the other server, restore the data like for a backup/restore operation. See https://jazz.net/library/article/795 for backup/restore considerations. The important points are the configuration files, index files etc. Then make sure that the new server is reachable using the old URI and keep the old server off. You can use a proxy or something else.
Hi Fabien,
project/server move is not supported today. There were various discussions around this. For example: https://jazz.net/forum/questions/36911/is-it-possible-to-move-project-area-between-jazz-servers
There are various requests for this but as far as I know there is no solution yet. Especially if you want to run both servers in the same network it is impossible. You can't do a URI change and the copy of the server would always relay back to the original machine.
The new CLM2012 4.0 version has some capabilities to rename but this scenario is still not supported as far as I know. See: https://jazz.net/library/article/898 https://jazz.net/library/article/818.
The only data that you could share between the two servers would be SCM data using distributed SCM. You can't just copy the project and work item data over. It is not possible to duplicate a server and run both servers. One of the reasons is the server URI can not be changed.
project/server move is not supported today. There were various discussions around this. For example: https://jazz.net/forum/questions/36911/is-it-possible-to-move-project-area-between-jazz-servers
There are various requests for this but as far as I know there is no solution yet. Especially if you want to run both servers in the same network it is impossible. You can't do a URI change and the copy of the server would always relay back to the original machine.
The new CLM2012 4.0 version has some capabilities to rename but this scenario is still not supported as far as I know. See: https://jazz.net/library/article/898 https://jazz.net/library/article/818.
The only data that you could share between the two servers would be SCM data using distributed SCM. You can't just copy the project and work item data over. It is not possible to duplicate a server and run both servers. One of the reasons is the server URI can not be changed.
If you want to move some/all of the data from RTC A to RTC B while keeping both RTC A and RTC B available, then this is not yet supported. It is requested in work item 93151. You can copy the SCM data between repositores via the cross-repository deliver functionality. You can copy a sub-set of the work item data (but not its history) via export/import.