Installer 10.11 | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products On Premises | Upgrade Using Command Central | Upgrade Products Using Software Stacks (10.1 and Later)
 
Upgrade Products Using 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.
For more information, go to https://tech.forums.softwareag.com/t/announcing-one-click-upgrades-for-webmethods/242399 on the Software AG TECHcommunity website. You can find videos on upgrading using stacks on Youtube; search on "Software AG Command Central" to find videos from which to choose.
1. Complete the tasks in Prepare for Upgrade and the Prepare the Old Installation sections in the product-specific chapters 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. 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.
For instructions on installing fixes, see Software AG Command Central Help.
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, 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, the table below explains the next action to take.
If your Windows release...
Take this action...
Has out-of-the-box SSH support
Use the default SSH server on the Windows machine
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. For instructions, see Software AG Command Central Help.
8. Upgrade the stack as described below./
a. Click Stacks at the top of the GUI.
b. On the stack to upgrade, click, click Upgrade stack, click the type of upgrade to perform, and provide the requested values.
c. Click Dry run at the bottom of the configuration page. Command Central generates a composite template for each runtime component in the stack.
d. You might want or need to edit the generated templates for reasons such as the following:
*To reflect changes, deprecations, and removals specified in the product readmes.
*Command Central indicates that a product in a template does not exist in the repositories for the new release, so you need to remove the product entry from the template or specify the replacement product.
*Upgrade from 10.1 or 10.3: The stack contains a database layer, which means you need to copy the database product IDs from the database scripts section to the products section.
To edit the generated templates:
a. Click Templates at the top of the GUI. You will see a list of templates named migration_generated_stack_name.
b. Download a template and edit with a text editing tool.
c. Click to import the template.
d. Repeat the steps above for other templates as necessary.
e. Click Stacks again, click, click Upgrade stack again, and choose to use existing templates.
e. When the generated templates are ready, you can perform the upgrade by clicking Upgrade stack at the bottom of the configuration page, or you can use the templates in automated upgrades.
9. Complete the product upgrades as explained in the product-specific chapters in this guide.