Installer 10.7 | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products On Premises | Create an Upgraded Installation Using Command Central and Software Stacks (10.1 and Later)
 
Create an Upgraded Installation Using Command Central and Software Stacks (10.1 and Later)
You can upgrade Command Central software stacks using this procedure, or you can create stacks from existing product installations managed by Command Central and then upgrade them using this procedure.
1. Follow the steps in Critical Factors and Requirements for Successful Upgrade and Prepare the Old Environment for Migration in this guide.
2. Install the new release of Command Central and then open Command Central using instructions in Software AG Command Central Help).
3. If you are upgrading from 10.1 or 10.3, install the fixes below using instructions in Software AG Command Central Help.
*Upgrade from 10.1: Install wmFix.SPM 17 and wMFix.SDRepository 9 on the Platform Manager of each installation you are upgrading. If the stack includes a database layer, install wMFix.DatabaseComponentConfigurator 3 on Database Component Configurator
*Upgrade from 10.3: Install wmFix.SPM 12 on the Platform Manager of each installation you are upgrading. If the stack includes a database layer, install wMFix.DatabaseComponentConfigurator 6 on Database Component Configurator
4. If the installations you want to upgrade currently exist as standalone installations, create stacks from those installations. To do so, you will identify installations to Command Central, and Command Central will create one stack for each set of installations that are the same release, are installed on the same operating system and in a directory of the same name, and whose Platform Manager uses the same port and protocol (HTTP or HTTPS).
Note:
An installation can be part in only one stack. If an installation is already part of an existing, therefore, it will not be added to the new stack.
a. Go to Environments, click the environment that contains the installations from which to create stacks, click at the bottom right of the Environments pane, and then click Auto-create stacks.
b. In the Auto-create stacks dialog box, in the Product releases drop down, click the release of the installations from which to create stacks or click ALL.
By default, Command Central will name the stacks 1, 2, 3, and so on. In the Stack prefix field, specify a prefix for those names that will help you better identify the stacks later.
c. Click OK to create the stacks.
d. If you need a database layer in a stack, add it manually.
e. If you do not want to include a particular layer in a stack, you can delete it.
5. Command Central needs its bootstrapper to install Platform Manager in the new product installation. Follow the instructions in your installation email from Software AG to download the bootstrapper of the new release for your operating system. Store the bootstrapper in the Command Central_directory/profiles/CCE/data/installers directory.
6. If you are going to install the new products on UNIX or Windows operating systems, make sure the target machines have a Secure Shell (SSH) server running and the system is configured for remote access with the user account for your products. For Windows:
*If your Windows release has out-of-the-box SSH support, use the default SSH server on the Windows machine.
*If your Windows release does not support SSH by default, set up OpenSSH on the Windows machine using a third-party tool such as Cygwin. For information about how to install Cygwin, go to https://cygwin.com/install.html or follow the instructions in the Using Cygwin to Configure OpenSSH When Installing Platform Manager on a Remote Windows Machine article located on Software AG TECHcommunity.
7. Create product and fix repositories for the new product release, import product license keys, and register any necessary credentials for the target machines using instructions in Software AG Command Central Help.
8. Click Stacks at the top of the GUI. On the stack to upgrade, click, click Upgrade stack, click the type of upgrade to perform, and provide the requested values. You can now do one of the following:
*Click Dry run at the bottom of the configuration page. Command Central will generate a composite template for each runtime component in the stack and validate the templates (for example, by making sure the products in the templates exist in the repositories for the new release). You can edit the generated templates to reflect changes, deprecations, and removals as described above. You can then perform the upgrade using Upgrade stack, described below, or you can use the templates in automated upgrades.
*Click Upgrade stack at the bottom of the configuration page. Command Central will generate a composite template for each runtime component in the stack, validate the templates, and use the templates to perform the upgrade.
If a product in a template does not exist in the repositories for the new release, the upgrade will fail and you will see a message that says you must edit that template. Click Templates at the top of the GUI; the generated templates will be named migration_generated_stack_name. Download the template and edit it with a text editing tool; for example, if the product no longer exists, you would delete the product entry in the template, or if the product has been replaced, you would change the product entry to the replacement product. When you are done editing, click to import the template. Then click Stacks again, click, click Upgrade stack again, and choose to use existing templates.
9. Follow the steps in Complete Final Upgrade Tasks for All Products in this guide.