Export Project Area from Server Linux RTC v.1 to Server AIX RTC v.4
3 answers
Hi Adriano.
You can't export only one project area.
What you can do and I assume you want to do is to move the application server to an AIX machine. Dependent on where you have the database server, there are different considerations.. Can you describe your plans with the databases? Which Vendor?
Here the general outline.
You can't export only one project area.
What you can do and I assume you want to do is to move the application server to an AIX machine. Dependent on where you have the database server, there are different considerations.. Can you describe your plans with the databases? Which Vendor?
Here the general outline.
- You install the product files on the new server.
- You need to do a offline backup of everything on the old server. See https://jazz.net/library/article/795.
- You do a repotools export of the databases (if you want to move the a new DB server, change the vendor or the vendor does not support switching the OS with a backup/restore between the platforms).
- You make sure the new server is reachable using the public URI you have chosen for your Application(s).
-
You restore the teamserver.properties and all other supporting configuration files of all applications that move on the new machine.
- You restore all index files etc. on the new machine.
- You deploy custom extensions on the new machine.
- You check all the teamserver.properties files for the index locations etc. and make sure all the values are valid for the new deployment.
-
If you can still use the old DB or backup restore to another server, do that and make sure the connection information in the properties is valid for the DB server.
- If you have new databases on a new server and no backup/restore on that server, you create the databases. And then you run repotools-import for all databases.
-
Deploy the applications on the new server if you use WAS.
- You can bring up the new machine.
No guarantees, I would suggest to try this in a isolated environment.
Hello Ralph,
thanks for replay. What I need is only to move the single Project Area from a RTC v.1 server
into an existing (production server) one.
I can only EXPORT/IMPORT the source code but what I need is a way to have available the
Work Items, History Logs and Change Sets exported into a Sheet Excel or something similar since the Work Items, History Logs and Change Sets are the Apars of the product that is in maintenance.
I want to close the server and move only the last Project Area into the Production server,
not need to export/import the repository as I made when I updated the RTC v.2 into v.3.
Thanks, Adriano
thanks for replay. What I need is only to move the single Project Area from a RTC v.1 server
into an existing (production server) one.
I can only EXPORT/IMPORT the source code but what I need is a way to have available the
Work Items, History Logs and Change Sets exported into a Sheet Excel or something similar since the Work Items, History Logs and Change Sets are the Apars of the product that is in maintenance.
I want to close the server and move only the last Project Area into the Production server,
not need to export/import the repository as I made when I updated the RTC v.2 into v.3.
Thanks, Adriano
Hi Adriano,
there is currently no Project Move capability in RTC that allows to move a project from one server to another. This is high on the list of several users.
A valid model is to archive all other projects and follow my initial answer to migrate to the new server - keeping the Public URI. You have to shut sown the old server. If you are on 4.x and need/want to do a server rename during the process you should get in contact with support.
If the databases are available using the old connection string, or if you can use backup and restore to move to a new DB server, you don't need to do a repotools export/import.
there is currently no Project Move capability in RTC that allows to move a project from one server to another. This is high on the list of several users.
A valid model is to archive all other projects and follow my initial answer to migrate to the new server - keeping the Public URI. You have to shut sown the old server. If you are on 4.x and need/want to do a server rename during the process you should get in contact with support.
If the databases are available using the old connection string, or if you can use backup and restore to move to a new DB server, you don't need to do a repotools export/import.