Skip to main content
Matrix42 Self-Service Help Center

Migrating the Databases to a New Server

The process of migrating the databases to a new server is supported by the Configuration Wizard.

Shut Down the Application

Before you start the migration process, shut down the application to avoid data loss. To shut down the application, perform the following steps:

  • Stop the following Windows services:
    • Matrix42 Engine Common
    • Matrix42 Engine Common X86
    • Matrix42 Engine Scheduler
    • AppFabric Workflow Management Service
    • AppFabric Event Collection Service
  • Stop Internet Information Services (IIS)

Back Up the Databases

Perform full backup of the following databases:

  • Main Database (by default M42Production)
  • History Database (by default M42Archive)
  • Warehouse Database (by default M42Warehouse)
  • Reference Database <MAIN DB>_REF (by default M42Production_REF)
  • Workflow Instance Store (by default M42InstanceStore)

There are more databases related to Matrix42 Software Asset & Service Management, such as Workflow Monitoring (M42Monitoring), SSAS Cube (M42AnalysisServices), and Staging databases that are used by Data Providers. However, these databases contain no critical data and can be recreated from scratch at any time. 

For more information about the databases that are used, see How to Determine Which Databases are Used by WPM Installation.

Restore the Databases

Restore the following databases on the new environment:

  • Main Database (by default M42Production)
  • History Database (by default M42Archive)
  • Warehouse Database (by default M42Warehouse)
  • Reference Database <MAIN DB>_REF (by default M42Production_REF)
  • Workflow Instance Store (by default M42InstanceStore)

Change the Application Configuration

Reconfigure the Application to Use the New Database Server

To reconfigure the Database Server, perform the following steps:

  1. Run Configuration Wizard.
  2. Click Change Configuration > Change Database Server.
  3. Specify New Configuration for the Database Server.
  4. Click Next to apply the configuration.

You can also reconfigure the Database Server manually. In this case you should adjust all connection strings that are defined in How to Determine Which Databases are Used.

Reconfigure the Service Host

Open the <INSTALL DIR>/bin/sps.config file in any text editor and make sure that the settings are correct:

<Matrix42.ServiceLayer
...
servicesHost="localhost"
discoveryHostName="<FQCN>"
appFabricAdminGroup="<DOMAIN>\AS_Administrators"
...
/>

servicesHost: equal to "localhost"

discoveryHostName: fully qualified computer name or domain name that is used to access the Matrix42 Software Asset & Service Management Console. This name should match the SSL certificate of the IIS website on which WPM is installed.

appFabricAdminGroup: Domain group that is used to access the Workflow Monitoring database and the Instance Store database.

By default, the setup uses fully qualified computer name (FQCN) as discoveryHostName and generates a self-signed SSL certificate with the corresponding CN (common name). If you use custom domain name and SSL certificate, then you should migrate the certificate manually and configure it to be used as discoveryHostName.

Update to a new SQL server version

There are 2 main scenarios when you update your SQL Server to a new version. Either you update to a SQL version that is still supported by your installed product version or you update to a SQL version that is no longer supported by your product version. In the second case, you have to update your product immediately after you updated your SQL server.

  • Update to a supported SQL Server version
    Perform the same steps as described above. If you directly update your SQL server without moving the databases, you don't need to change the application in any way.
  • Update to an unsupported SQL Server version and update the application
    For example, SQL 2008R2 => SQL 2017, 8.1.7 => 9.0.2
    • Migrate the Databases to a new SQL Server
      Perform the same migration steps as described above. Directly after you changed the configuration with the configuration wizard, update the application to the new version that supports the newer SQL server version.
    • Update the SQL server to an unsupported SQL Server version
      Shut down the application, update the SQL server and update the application immediately after the switch to the new SQL server version. If the update asks you to start some services, to proceed simply start them.

The configuration wizard will not check the SQL server version when you switch to the new database server, but you should not use the application with an unsupported SQL server version!

It is recommended to update the compatibility level of your databases to the newest level supported by your SQL server.