Migrate the Commander application and database to new servers

This guide explains how to move the Commander application, the Commander database, or both to new servers. Before beginning, ensure that you have snapshots of your application server and backups of your database to avoid data loss should an issue occur during migration.

Scenario 1: Migrate Commander and PostgreSQL database

On the Commander application server, copy the following directories to a temporary location. Include any scripts called by Commander workflows that are stored on the filesystem:
- ..\Commander\tomcat\reports
- ..\Commander\tomcat\public
- ..\Commander\tomcat\wfplugins
In Commander, go to Help > About to note the installed version number.
Confirm that you have the same version of the installer. Obtain it from the Flexera Communiuty website or request legacy installers from Support.
On the original server, back up the PostgreSQL database.
Install the same version of Commander on the destination server.
After installation, stop the Commander Windows services.
On the destination server, restore the PostgreSQL database backup.
Overwrite the directories copied earlier to their original locations on the new server. Include any scripts.
Restart the Commander Windows services.

When the services initialize and data is confirmed, decommission the original server.

Scenario 2: Migrate Commander application (Microsoft SQL database remains)

On the current application server, copy the following directories to a temporary location. Include any workflow scripts:
- ..\Commander\tomcat\reports
- ..\Commander\tomcat\public
- ..\Commander\tomcat\wfplugins
In Commander, go to Help > About to note the installed version number.
Confirm that you have the same installer version as the application.
Install Commander on the destination server, using a new empty Microsoft SQL database during installation.
After installation, overwrite the directories from the temporary location to the destination server.
Shut down the legacy Commander server and set its services to manual.
On the new server, open Commander Control Panel from the Start menu.
Switch to the DB Management tab, update the connection details to the original Microsoft SQL database, and click Test Connection.
When prompted, confirm the service restart.

When the service initializes and you confirm access to data, decommission the original server.

Scenario 3: Migrate the Microsoft SQL database (Commander application remains)

In Commander, go to Help > About to note the installed version number.
On the application server, open Commander Control Panel, go to Service Control, and click Stop Service.
Back up the Microsoft SQL database on the original SQL server.
Restore the database backup on the destination Microsoft SQL server.
In Commander Control Panel, switch to DB Management and update the connection details to point to the new SQL location.
Test the connection and confirm the service restart.

Once confirmed, you can decommission the original database server.