What steps to migrate to a new Content Manager?

What steps to migrate to a new Content Manager?

1. When installing the new Content Manager you must use the exact same ‘Network’ name you used on the original Content Manager. You can fine the name of the ‘Network’ by navigating to your old Content Manager’s Data folder. There is a sub-folder named after the ‘Network’ name.
2. Backup your old Content Manager server data and configuration files by the instructions found in Chapter 8.1.1 of the Release 5 Content Manager User’s Guide. NOTE: It is important to stop the Apache Tomcat and Scala Transmission Server Services before this backup.
3. Backup your database by the instructions for your type of database (PostgreSQL, MySQL, MS SQL) found in Chapters 8.1 2 thru 8.1.5 of the Release 5 Content Manager User’s Guide. NOTE: It is important to stop the Apache Tomcat and Scala Transmission Server Services before this backup.
4. If upgrading to Windows 7 64 bit or Windows Server 2008 R2 64 bit you need to install Java 6 Update 18 64 bit or higher, and Apache Tomcat 5.5.28. You can order a current installation CD, which contains the needed Java and Apache Tomcat, or you can go on-line for these versions.
5. Restore your old Content Manager server data and configuration files to the new Content Manager server by the instructions found in Chapter 8.2.1 of the Release 5 Content Manager User’s Guide.
6. Restore your old database to the new Content Manager server by the instructions for your type of database (PostgreSQL, MySQL, MS SQL) found in Chapter 8.2.2 thru 8.2.5 of the Release 5 Content Manager User’s Guide.
7. ‘Refresh’ your Designer and Players to the new Content Manager hostname or IP Address.

Regards,

Scala Technical Support