This guide refers to CMS Fiona 6.0.4 or later. With Sybase or MS SQL databases, this guide refers to CMS Fiona 6.5.0 or later. If your Fiona version is not covered by the version ranges mentioned, or if you wish to switch-over to a different database product in the migration process, please read the section on migrating older versions first.
Before you start migrating, please ensure that the following requirements are met.
The machine on which the new version is to be installed needs to meet the system requirements. Also, from version 6.7.0, a machine-specific license without ID limit is required for migrating in-place.
Make a dump of the CM and TE databases. In the case of unexpected problems, you can revert to the original state using these dumps.
In-place migration is supported for the following database products and versions:
In-place migration is not available for SQLite databases.
Install the current version of CMS Fiona on the machine on which the migration is to be performed.
The current version is required to be installed only, there is no need to configure it. It will be configured by the in-place migration process.
The new installation requires access to the instance directories and the database of the old installation since the migration process copies the configuration from the old to the new installation and migrates the content. This requirement is met if the new Fiona version has been installed on the machine on which the old version is located.
However, if the new CMS Fiona version has been installed on a new server on which no file system access to the old instance directories exists, these directories need to be copied to the new server. Do not copy them into the new installation, copy them to a temporary directory instead.
If the database is also not available, or if you wish to migrate a copy of the database, Falls die Datenbank ebenfalls nicht erreichbar ist oder falls Sie die Migration mit einer Kopie der Datenbank durchführen wollen, you can use the database dumps of the CM and the TE you created at the beginning. After the database server has been set up (if required) and the dumps have been imported, adapt the database configuration in the old instance directories so that the database copies are used. Note that it is neither necessary nor possible to ever start the CMS server from one of the copied old instance directories.
For every existing instance you wish to migrate, create a corresponding instance in the new installation using the original name. To every new instance the port range should be assigned that was assigned to the corresponding old instance. This helps to prevent the configuration of the web applications (which cannot be migrated automatically) and of the the CMS server configuration from becoming inconsistent.
The CMS server configuration is stored in the instance-specific
config/server.xml file. If a different port range has been
assigned to an instance, the server configuration and the configuration of
the GUI web application need to be adjusted manually (with respect to the
port range) after the migration process. The configuration of the GUI is
stored in the instance-specific
webapps/GUI/WEB-INF/basicConfig.properties file.
Please note that only during the migration of the CM (and not of the TE) the configuration of the TE is copied to the new instance and adapted to it. Thus, if the TE was active in the old installation, its configuration is covered by the migration only if it was run from the instance directory.
If you are exporting
the content incrementally, please ensure that prior to the migration all
existing update records have been transferred to the TE. This can be done by
running the SystemPublish job. Unprocessed update records cause
the migration process to be aborted and a corresponding message to be
displayed.
Please ensure that enough hard disk space is available. Take into account that
script, config, and data directories are copied from the old to the new instance.