Command Central Requirements
You can use Command Central to install most products in the new release, and to install fixes on most old and new products. You can also use Command Central to migrate product files and assets for some products from some old releases to the new release. For the list of products that Command Central can install and migrate, and the upgrade paths that Command Central supports for those products, see the Command Central readme.
This section explains how to upgrade Command Central and how to install and upgrade products using Command Central. The section is intended for use with the rest of this guide. You must perform all tasks in this guide for your products, in the order they are written, unless this section indicates otherwise.
For instructions on using Command Central, see Software AG Command Central Help.
1. Upgrade Command Central.
a. Install Command Central using the instructions in Installing Software AG Products.
b. If you installed the new
Command Central on a different machine than the old installation, create a Zip file of the old
Command Central. For instructions, see
Create Zip Files for All Other Products.
c. Use the Command Central bootstrapper to migrate configuration files and assets from the old Command Central to the new Command Central. On the bootstrapper command, specify the -m option and set the option to the Software AG directory that contains the old Command Central installation or the Zip file you made in the previous step. For a list of files and assets that are migrated, see Software AG Command Central Help.
d. Go to the Software AG_directory\profiles\CCE\configuration \com.softwareag.platform.config.propsloader directory in the old and new installations and open the com.softwareag.sso.pid.properties. If a value in the old file is different from the corresponding value in the new file, copy the old value over the new value. In addition, update any absolute file system paths in the new files to point to the new installation. Do not update paths that use tokens (for example, do not update @path\:sag.install.area\common\conf\platform_truststore.jks).
e. 9.0, 9.5, 9.6, or 9.7 upgrade: If you set a custom password for Platform Manager, set the custom password in the new Command Central.
f. Set the LDAP domain property in the new Command Central.
2. Use the new Command Central to set up custom templates that will automate the migration of your products. If you used custom templates to provision your old environment, you will need to make only minor changes to those templates. If you did not use custom templates to provision your old environment, create custom templates in the new Command Central. In the templates, specify the product migration utilities to run, including the Software AG Infrastructure migration utility, and specify the database components to migrate.
3. This guide explains how to install the new products using
Software AG Installer. You can install the new products using
Command Central instead, but you must still read and perform the actions described in
Install the New Products.
4. This guide explains how to install fixes on some old products using Software AG Update Manager. You can install the fixes using Command Central instead.
5. This guide explains how to prepare the old Integration Server for upgrade, including suspending document retrieval and making sure all messages have been sent. When you migrate using Command Central, Command Central automatically quiesces Integration Server to suspend all triggers and drain message queues for you.
6. This guide explains how to shut down the old products manually. If Command Central managed the old products and the new and old installations are Secure Shell (SSH)-accessible, Command Central shuts down the old products automatically.
7. This guide explains how to install fixes on the database migration scripts using Software AG Update Manager. You can install the fixes using Command Central instead.
8. This guide explains how to make Zip files of old installations and copy them to new installations manually when your old and new installations are on different machines. If the new and old installations are SSH-accessible, Command Central automatically creates a Zip file of the entire old Software AG installation directory and copies the Zip file from the old installation to the new installation for you. By default, the Zip file does not include log files and jar files from the old installation.
9. This guide provides product-specific migration chapters that describe pre- and post-migration tasks you must perform and explain how to run the product migration utilities. Even when you migrate your products using Command Central, you must perform the pre-migration tasks first and the post-migration tasks afterwards.