Server Rename question
From the rename article:
https://jazz.net/library/article/1081
If you are using a Derby database in your pilot to production use case, do you understand the need to migrate the existing data repositories to a production database server?
All production CLM systems are expected to use production quality databases that handle the scalability, robustness, and maintainability required in a production environment. This implies that the pilot Derby database must be migrated to an enterprise database during the server rename to the new production CLM system. You will need to perform the “repotools –export” and “repotools –import” operations to migrate your data to the production database server as part of the CLM server rename procedure. See the topic "Changing the database vendor" in the Information Center for details.
Wait, can I do a server rename using derby on a test server? Or do I have to be using something like DB2?
|
Accepted answer
Hi Sterling
Yes; You can do a server rename using a derby database on a test server.
It is not a mandate to use enterprise level DB for server rename on the test server.
Sterling Ferguson-II selected this answer as the correct answer
Comments
Sterling Ferguson-II
commented May 02 '14, 10:25 a.m.
Thanks Sumant!
Geoffrey Clemm
commented May 03 '14, 12:48 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, all that this article was saying was that if you were trialing RTC using a Derby database, and then decided that you wanted to initialize your production system with the data from that trial, then you could rename the server (from the test server to the production server), but should also switch to an Enterprise database (as part of the move from trial to production).
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.