Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products On Premises | Upgrade Using Command Central | Upgrade Products in a Single Environment
 
Upgrade Products in a Single Environment
Read all chapters in this guide to understand all information and tasks beyond Command Central, such as cluster upgrade guidelines, preparing the old installation, and manual tasks that need to be performed after data migration.
Follow the instructions in Software AG Command Central Help to install your new products and fixes, install fixes on your old products, shut down the old products, and create ZIP files of the old installations to use as sources for cross-host migration.
The preparation steps for the old Integration Server or Microservices Runtime include suspending and draining triggers. You can perform this task from Command Central.
Use the Command Central command sagcc exec administration to migrate database components. The command syntax is shown below. The parameters are the parameters you use when running the Database Component Configurator and are documented in Installing Software AG Products. To check the progress of the migration in Command Central, click Jobs on the Command Central web user interface.
sagcc exec administration product DCC_node_alias DatabaseComponentConfigurator
database migrate [parm1=value1 ] [parm2=value2 ]...
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 components from 9.9 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”
Use the commands below to migrate the product configurations, data, and assets.
Product
Migration Command
Application Platform
sagcc exec administration product target_node_alias
PLSCore migration migrate
{srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file}
Digital Event Services
sagcc exec administration product target_node_alias
DEVRuntime migration migrate
{srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file}
Integration Server or Microservices Runtime and Hosted Wm Packages Command
If you want to run a custom migration, first run the migration utility manually, and then specify the resulting migrate.dat file on the importFile parameter. If you are upgrade on the same machine and you want to migrate all instances, do not specify the instanceName parameter. If you are upgrade Integration Server on a new machine, migrate one instance at a time to avoid causing concurrency issues with your database.
sagcc exec administration product target_node_alias
integrationServer migration migrate
{srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file}
[importFile=full_path_to_migrate.dat]
[instanceName=name [newInstanceName=name]]
[cloneDbURL=URL cloneDbUser=user cloneDbPassword=password]
My webMethods Server
If you want to run a custom migration, first run the migration utility manually, and then specify the resulting migrate.dat file on the importFile parameter. If you want to migrate all instances, do not specify the instanceName parameter.
sagcc exec administration product target_node_alias
MwsProgramFiles migration migrate
{srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file}
[importFile=full_path_to_migrate.dat]
[instanceName=name[,name...]]
[newNodeName=instance_name:new_node_name[,instance_name:new_node_name...]]
[cloneDbURL=URL cloneDbUser=user cloneDbPassword=password]
Note:
If you migrate the instances, and then have to re-run the migration later for some reason, Command Central handles the re-migration differently than the migration utility. If migrated instances in the new installation have the same name as old instances, the utility deletes the migrated instances and then re-migrates the old instances. Command Central, conversely, skips the migrated instances and only re-migrates old instances that do not yet exist in the new installation.
Universal Messaging
If you want to run a custom migration, first run the migration utility manually, and then specify the resulting migrate.dat file on the importFile parameter. If you want to migrate all instances, do not specify the instanceName parameter.
sagcc exec administration product case_sensitive_target_node_alias
NUMRealmServer migration migrate
{srcDir|srcFile}=full_path_to_{old_Software AG_directory|ZIP file}
[importFile=full_path_to_migrate.dat]
[instanceName=name[,name...]]