Migrating From an Older Installation
To migrate from an older version of a Model Manager server running as a service on Windows®:
1
Stop the currently running Model Manager server Windows® service. Also make sure that the Windows® service is not set to be started automatically — that is, set the startup type to Disabled.
2
Install COMSOL Model Manager Server 6.2 — see Installing in Windows.
3
Once you have verified that the COMSOL Model Manager Server 6.2 has successfully started, uninstall the old version of the server if desired.
For a systemd service installed on Linux®, make sure to stop and disable the old service before installing the new service.
The Model Manager databases hosted by the old Model Manager server will now be available in the new server.
You are strongly recommended to at least stop any older installations of Model Manager server before installing a newer version to not risk any unwanted cross-talk in the data directories. When stopping an older Model Manager server installed as a Windows® service, make sure that the service is not set to be started automatically. When stopping an older systemd service installed on Linux®, make sure that the service is also disabled.
When a Model Manager server starts for the first time, it tries to locate a Model Manager server Preference Directory belonging to an older installation of the server. If such a preference directory is found, all server settings are migrated to the new installation’s preference directory. This includes, for example, any account settings and database configurations set up for the older server. You can also manually copy the subfolder db in the preference directory of the older installation to that of the newer installation before the latter server has been installed and started (you will need to first manually create the newer installation’s preference directory). This is useful, for example, if the older installation is located on another computer.
The Data Directories for any configured databases are not copied, however. This means that older installations of Model Manager server may potentially read and write in the same data directories as the newer installation unless the older servers are first stopped.