Install the New Products

Follow the instructions in Using Software AG Installer, Installing Software AG Products, and in this section to install your new product.

Make sure the target machine has enough space for custom packages you will migrate. Custom packages include packages that were created by users in Software AG Designer and, for Integration Server, business process packages that were generated by users from Software AG Designer.

On the Integration Server or Microservices Runtime installer panel or in response to a prompt, point the database connection at the ISInternal database component you want to use with the new installation.

On the ActiveTransfer Server installer panel or in response to a prompt, point the database connection at the ActiveTransfer database component you want to use with the new ActiveTransfer Server.

On the Trading Networks installer panel or in response to a prompt, point the database connection at the TradingNetworks database component you want to use with the new Trading Networks.

Note:
When you install new products on the same machine as old products, the installer often allows you to assign ports used by old products to new products as well, even if the old products are running. Assigning the same ports means you will not need to edit port values in assets and clients when you begin using the new release.

Install the latest updates on your new product from the Software AG Installer. Product fix names typically follow the convention product [subcomponent] release Fix number [platform]. In addition, install the applicable fixes below.

For some products, fixes relating to migration are separate from the product fixes. Install the latest of these migration fixes on all new products. For migration fixes, the subcomponent part of the product fix name might be MIG, or UPG, for example.

Install the latest migration framework fix. Fix names for the migration framework follow the convention MIG_release_MigrationFramework_Fixnumber and are listed under Common Library.

Install fixes on database migration scripts. Database migration script fix names follow the convention product Database release Fix number.

Upgrade from 9.9, 9.10, 9.12, or 10.1: If you installed a fix on the Software AG-provided JDK for the new release, and if you made changes (for example, security changes) to the JVM files in the Software AG_directory/jvm/jvm.bck directory in the old release , make the same changes to the JVM files in the Software AG_directory/jvm/jvm directory in the new release.

If you installed your new product on a Windows system, and you installed it as a Windows service, the default startup mode for the service is Automatic. To prevent the new product from starting accidentally before this procedure instructs you to start it, set the service to Manual. If you installed on a UNIX system, and you have scripts that automatically start daemons, disable the scripts for the same reason.

Important:
Do not start any new product at this point. Do not start any new product before the instructions in this guide explicitly tell you to do so, or your database components could become corrupted.