Upgrade considerations for multi-galaxy communication

Important: In multi-galaxy environments, add a System Management Server to only one GR node, and configure the other nodes to point to it. See Configuring the System Management Server for additional information.

Setting up a multiple galaxy environment requires a unique name for each galaxy in the environment. This may require you to rename one or more galaxies if you plan to include galaxies with the same name in your multi-galaxy communication environment. We recommend performing all necessary renaming prior to upgrading System Platform. This will prepare your galaxies for use in a multi-galaxy environment without disrupting the upgrade workflow.

Important: It is very important that you follow the galaxy name change procedure provided in the following steps and in the Application Server User Guide. You must create a new galaxy with a new, unique name, from a backup .cab file rather than creating a galaxy and performing a restore of the backup .cab file.

For more information about creating and backing up galaxies, see "Getting Started with the IDE" and "Managing Galaxies" in the Application Server User Guide.

To rename a galaxy for use in a multi-galaxy environment

1. Select a galaxy with a duplicate name, undeploy it and back it up to create a .cab file.

2. Use the .cab file as a "template" by placing it in C:\Program Files (x86)\ArchestrA\Framework\Bin\BackupGalaxies.

3. Create a new galaxy with a new name, based on the backup .cab file. The name must be unique, not in use anywhere else in the multi-galaxy environment.

4. Repeat the preceding steps for each galaxy to be renamed with a unique name.

5. Redeploy each newly created galaxy.

6. Delete the original galaxy from the GR node.

7. Upgrade to Application Server 2023 R2.

Your galaxy can now be configured for use in a multi-galaxy environment.