Upgrade Products
This topic must be used with Upgrading Software AG Products. To see which products support upgrade through Command Central, see the Software AG Command Central Feature Support Matrix.
If you need to upgrade multiple similar environments, you can set up composite templates that automate the upgrade (see the template instructions in this help). You will still need to manually perform manual tasks in Upgrading Software AG Products if you cannot script them.
If you are going to install the new products on different machines than the old products, Command Central automatically creates a ZIP file of each old installation directory. The ZIP file includes all files except .log files. If you want to decrease the size of the ZIP file, Upgrading Software AG Products lists the commands that will include only the required files for each product in the ZIP file. You can reconfigure endpoints such as host names and ports by adding commands after the migration section of the template.
If you need to upgrade only one environment, you can use Command Central for many upgrade tasks. Use the instructions in Upgrading Software AG Products, but substitute the tasks below for corresponding tasks in that guide.
Note: You do not have to upgrade Platform Manager.
1. Use Command Central to install the new products and then to install the latest fixes on those products.
Note: If Command Central managed the old product installation, the installation wizard offers an option that can auto-select the same set of products for the new installation.
2. If Command Central managed the old products, you can perform the tasks below to prepare the old environment instead of performing corresponding tasks in the upgrade guide.
a. Use Command Central (9.7 or later products) or Software AG Update Manager (9.6 or earlier products; use the instructions in Using the Software AG Update Manager) to install the latest fixes on the old products that are specifically listed in the upgrade guide.
b. If you are upgrading Integration Server from 9.8 or later, you can pause the Integration Server instance in Command Central to suspend triggers and drain message queues.
c. Use Command Central to shut down the old product instances.
3. Use the Command Central sagcc exec administration command to migrate database components.
Command Central calls the Database Component Configurator to migrate the database components. For information on which Database Component Configurator to use, see the help on creating database components; the guidelines are the same for migrating database components. The command syntax for migrating database components is as follows:
sagcc exec administration product DCC_node_alias DatabaseComponentConfigurator
database migrate [parm1=value1 ] [parm2=value2 ]...
The parameters are the parameters you use when running the Database Component Configurator in command line mode, as documented in the Installing Software AG Products. In the examples below, the database components are on a SQL Server RDBMS at jdbc:wm:sqlserver://DBserver:1433;databaseName=TESTDB, and the database user is webmuser with password webmpass.
To upgrade
Integration Server database components from 9.9 to the latest release:
sagcc exec administration product local DatabaseComponentConfigurator
database migrate db.type=sqlserver product=IS version=latest
db.username=webmuser db.password=webmpass db.name=TESTDB
db.url=“jdbc:wm:sqlserver://DBserver:1433;databaseName=TESTDB”
To upgrade the
My webMethods Server database component to the latest release:
sagcc exec administration product local DatabaseComponentConfigurator
database migrate db.type=sqlserver component=MWS version=latest
db.username=webmuser db.password=webmpass db.name=TESTDB
db.url=“jdbc:wm:sqlserver://DBserver:1433;databaseName=TESTDB”
To check the progress of the migration, click Jobs at the top right of the Command Central web user interface.
4. The upgrade guide provides product-specific migration chapters that describe pre-migration tasks to perform. Perform the tasks in those chapters for all products whose data you are going to migrate.
5. Most products offer migration utilities that migrate their data, configurations, and assets. Products that are hosted by another product are migrated when you migrate the host product (for example, Trading Networks Server is migrated when you migrate Integration Server). The upgrade guide explains the actions that each product migration utility takes by default.
For some products, however, you might want to specify different actions. In this case, run the product's migration utility, specify custom settings, and then export the settings. The utility saves the settings in a file named migrate.dat in the directory listed in the upgrade guide. Copy the file to any directory on the machines that host the new product installations to which you want to migrate data.
For detailed information and instructions on all of these topics, see Upgrading Software AG Products.
6. Use the Command Central command sagcc exec administration to migrate product data, configurations, and assets. You migrate each product on a separate command. The command syntax is as follows:
sagcc exec administration product product_node_alias
product_ID migration migrate
{srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file}
[instanceName name [,name ,name ...]]
[importFile=full_path_to_ migrate.dat]
[-cloneDbURL URL -cloneDbUser user -cloneDbPassword password]
To find the product_ID, run the command sagcc list inventory products node_alias.
If you want to migrate all instances, do not specify the instanceName option.
To check the progress of the migration, click Jobs at the top right of the Command Central web user interface.
7. The upgrade guide provides product-specific migration chapters that describe post- migration tasks to perform. Perform these tasks for all products whose data you migrated.
8. Perform the final upgrade tasks in the last chapter in the upgrade guide.