Migrating a Galaxy to Later Versions of System Platform

SUMMARY

Migrating a System Platform galaxy from an older version to a newer version can be accomplished using two methods. The first method involves creating a backup of the existing Galaxy and restoring it onto a new computer. The second method method is performing an in-place migration on the same computer.  Please make sure to reference the ReadMe documentation associated with the version you plan on upgrading to in order to ensure all requirements are met before performing the upgrade.

APPLIES TO

• Application Server
• InTouch for System Platform

PROCEDURE

Section 1- Backing Up the Galaxy Using a .CAB File

1. In the Operations Control Management Console (previously called the System Management Console), expand the Galaxy Database Manager. Select the Galaxy you want to backup.

2. Select Action > Backup. Alternatively, you can right click on the Galaxy name and choose the option to Backup.

3. A warning message will pop up.  Confirm there are no write operations being made to the database, then click Yes to continue.

4. Type in a name for the backup (.cab) file and click Save.

5. Once the backup process is complete, click Close.

Section 2 – Migrating a Galaxy to a Newer Version

Option 1 – Migrating to a new computer

1. On the new computer, copy the previously created backup (.cab) file to: C:\Program Files (x86)\ArchestrA\Framework\Bin\BackupGalaxies.

2. Start the System Platform IDE.
3. On the Galaxy connection page, select to create a  New Galaxy, then select your backup file from the list of available Galaxy Types (2023 software version shown).

4. Name the new galaxy and click Create.

5. Once the galaxy creation process is complete, click Close.
6. Connect to the Galaxy. You will be prompted be migrate now. Click Yes to begin.

7. Once the migration process is complete, click Close.
8. If your galaxy includes a managed InTouch application, double click on the derived InTouchViewApp template to open it in WindowMaker. You will be prompted to migrate the InTouch application. Click Yes.

9. Optionally follow the steps to create a backup of the application before migrating.

10. The application will be migrated to the new version and opened in WindowMaker.

Option 2 – Migrating a Galaxy In-Place

1. Download (or copy) the install media for the new version of System Platform onto the Galaxy Repository (GR node) for the galaxy you wish to migrate.  Once the installation media is downloaded ensure the file is Unblocked, then run the setup.

2. You will be notified with a list of installed products to be upgraded. Press OK.

3. Confirm the Operating System of the computer is compatible with the new version of System Platform. To verify this, reference the “System Requirements and Guidelines” section of the Installation Read Me. Click Next.

4. You will not be able to modify the products to be upgraded, so on the next window, just click Next.

5. If you have not already created a backup of your galaxy, you can exit the upgrade process at this point and follow the steps in Section 1 (above) to create a backup.  Otherwise, click Next.

6. Click Upgrade to begin the upgrade process.

7. Once the installation is complete, press Configure.

8. Use the Configurator to configure each install component, using the Install guide as reference for how to configure each setting. After configuring, you must reboot the computer for the changes to take effect. Click Restart Now to begin the reboot.
9. If the GR Node does not include the IDE, repeat steps 1-8 for at least one of the IDE nodes.

10. Open the IDE and connect to the galaxy.  You will be prompted to migrate the Galaxy database and objects to the installed version. Click Yes.

11. Once the migration process is complete, click Close.
12. If your galaxy includes a managed InTouch application, double click on the derived InTouchViewApp template to open it in WindowMaker. You will be prompted to migrate the InTouch application. Click Yes.

13. Optionally follow the steps to create a backup of the application before migrating.

14. The application will be migrated to the new version and opened in WindowMaker.

15. Once the galaxy has been migrated, you can continue to upgrade and re-deploy your remaining development and/or runtime nodes.