Migration from 2.0 M1 to 2.0 Beta1
Hi, can I migrate my RTC 2.0 M1 installation to RTC Beta1?
I've used the zip to install 2.0 M1. Using tomcat and derby (Express C edition). The download page tells us: "We recommend that you install any pre-release build as an additional instance, in a separate directory, and that you do not "Update" your existing installation to the pre-release build using the IBM Installation Manager." Does this mean there is no way to migrate? |
3 answers
Hi, can I migrate my RTC 2.0 M1 installation to RTC Beta1? Hello, Give the steps below a try: 1. Download and extract 2.0Beta1 installation code 2. Run launchpad.exe under the rtc sub-folder, under the folder where the installation code is extracted to 3. Pick "Launch IBM Installation Manager to update existing product components" option from the Instllation menu 4. Pick "Udate" from the Installation Mananger menu 5. select the current RTC 2.0Mx package group to find updates for. 6. Installation Manager will automatically detect version 2.0 beta1, select it from the list, click next to complete the install. Hope this helps Susan |
Ok, but the server is not listed in the "existing
product components" because I used the zip and I just extracted the files for the server. Is there a way to pass it in as a parameter? Hi, can I migrate my RTC 2.0 M1 installation to RTC Beta1? Hello, Give the steps below a try: 1. Download and extract 2.0Beta1 installation code 2. Run launchpad.exe under the rtc sub-folder, under the folder where the installation code is extracted to 3. Pick "Launch IBM Installation Manager to update existing product components" option from the Instllation menu 4. Pick "Udate" from the Installation Mananger menu 5. select the current RTC 2.0Mx package group to find updates for. 6. Installation Manager will automatically detect version 2.0 beta1, select it from the list, click next to complete the install. Hope this helps Susan |
Hi, can I migrate my RTC 2.0 M1 installation to RTC Beta1? To answer your specific question, the fact that we recommend installing into a different directory has nothing to do with the migration of the repository. We usually recommend so that people don't replace a GA release such as 1.0.1 or 1.0.1.1 with an early build such as 2.0 M1 or 2.0 Beta 2. If you are already on M1 then you may just want to go ahead and replace/update it with a later early build. However all of this is separate from the repository migration. You can migrate from M1 to Beta 1. If you haven't done this already, now that M3 is out you're probably best off moving to that or waiting for Beta 2 which will be posted in the next couple of weeks. |
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.