Content Manager Upgrade Procedure

Update to 5.1.42 6.0.17 6.2.13 first

The following versions are currently still under support and have been approved for direct upgrade to version 10.5:

Release 6.2.13

Release 10.1.8

Release 10.2.5

Release 10.3.4

Release 10.4.7

• Scala maintenance coverage must not have ended
  • Serial Numbers, Scala Maintenance Subscription and Download Updaters
• Update equal to or newer than 6.2.13 if the Content Manager is like 6.2.02
  • 6.2.02----6.2.13 (Open Content Manager) ----10.5 DVD----10.5.16
• Before Updating, renew a license File.
  • System License Status>Get Licenses File Online.

• Before updating, disable playback audit reporting if it is on. (preferable)
  • System>Network Settings>Miscellaneous Settings>Enable Playback Audit reporting>NO

• Check any serious errors in ContentManger.log
• Prepare several backups and test it.
• If the database size is big (more than 50MB), check number of errors in database. Check row counts of errors (Step 2.b)

Upgrade Procedure Overview

Below are the steps to update Content Manager and related third party applications to the latest version:

1. Stop Tomcat and Scala Services
2. Back up Database, Content and Configuration Files
3. Uninstall old PostgreSQL, Tomcat & Java
4. Install new PostgreSQL, Java, Tomcat
5. Restore Database, Content and Configuration Files
6. Update Content Manager

Before you begin, gather the following information:

• Content Manager URL
• Windows Admin login to server running Content Manager
• Content Manager Administrator password
• PostgreSQL database username and password

Download the following third party software known to work with Content Manager 10.2. This is available via the thrid party company’s website or by going to ftp://bonobo.scala.com/10-2-Applications

• Java 7 update 45 for 32 bit systems jre-7u45-windows-i586.exe)
• Java 7 update 45 for 64 bit systems (jre-7u45-windows-x64.exe)
• Tomcat 7.0.39 (apache-tomcat-7.0.39.exe)
• PostgreSQL 9.2.4-1 for 32 bit systems (postgresql-9.2.4-1-windows.exe)
• PostgreSQL 9.2.4-1 for 64 bit systems (postgresql-9.2.4-1-windows-x64.exe)

Stop Tomcat and Scala Services

Stop the following services by going to Start / Control Panel / Administrative Tools / Services

• Apache Tomcat Service
• PostgreSQL Database Service (If using)
• Scala Transmission Server Service
• Scala Playback Audit Parser (If using)

Back up Database, Content and Configuration Files

It’s good practice to back up your database, especially before an upgrade. Follow these directions if you are using PostgreSQL:

1. Run the PostgreSQL pgAdmin tool.
2. Right-click on the PostgreSQL server and choose Connect.
3. Enter the username and password and click OK.
4. Open the Databases item.
5. Right-click on cm database and choose Backup.
6. Select a backup path/filename.
7. Set the Format to Custom. Leave the other options alone.
8. Click OK.
9. Success is indicated by “Process returned exit code 0”.
10. Also check that the backup file is not zero bytes.
11. Click Done.

If you are using a different database such as MySQL or MS SQL, follow the proper steps to make a backup found in Chapter 8.1 if the Release 5 Content Manager User’s Guide.

The content and configuration files should not be affected by the update process, but you should make a copy of them just in case.

The default location for these files is:

C:\Documents and Settings\All Users\ApplicationData\Scala\InfoChannel Content Manager 5

Note: It’s possible the content files were installed using a custom location. You can find this specified in Content Manager under Settings-> Server Settings-> System Paths frame-> Data root.

Uninstall PostgreSQL, Java & Tomcat

Depending on how old the applications are, it may be better to un-install the old version before installing the new one. For instance, PostgreSQL 8.3 should be removed before installing 9.2. The same goes for Tomcat 5.

To uninstall follow the steps below:

1. Stop the following services by going to Start / Control Panel / Administrative Tools / Services
• Apache Tomcat Service
• PostgreSQL Database Service (If using)
• Scala Transmission Server Service
• Scala Playback Audit Parser (If using)
1. Make sure all Scala 5 applications are closed on the Content Manager server.
2. In Control Panel Add & Remove Programs or Programs and Features delete the following in order:
   1. Apache Tomcat 7.0
   2. Java 6 (delete all if more than one)
   3. PostgreSQL 8.x or 9.x
3. Delete the following Folders in C:\Program Files if they exist.
   1. Apache Software foundation
   2. Java
   3. PostgreSQL
4. In Start / Run key-in regedit and hit Enter to launch the Registry. Delete the following Registries:
   1. HKEY_CURRENT_USER\Software
      1. Apache Software Foundation
      2. JavaSoft
      3. pgAdmin III
   2. HKEY_LOCAL_MACHINE\Software
      1. Apache Software Foundation
      2. JavaSoft
      3. PostgreSQL
      4. PostgreSQL Global Development Group
   3. HKEY_LOCAL_MACHINE\Software\Wow6432Node (64 bit systems only)
      1. Apache Software Foundation
      2. JavaSoft

Update PostgreSQL, Java & Tomcat

Go to the folowing Scala FTP site to download the appropriate versions of PostgreSQL, Java, and Tomcat: ftp://bonobo.scala.com/10-2-Applications

Install in this order:

1. PostgreSQL: At the end do not select option to launch Stack Builder.
2. Java: If you are running a 64 bit operating system, install 64 bit Java. You may also install the 32 bit version if other applications require it.
3. Tomcat: Make sure the installer successfully finds the Java runtime.

Restore Database, Content and Configuration Files

Follow these steps if you are using PostgreSQL:

1. First stop the Apache Tomcat and Scala Transmission Server services. Start / Control Panel / Administrative Tools / Services / Apache Tomcat, and Scala Transmission Server. Right-click and select Stop.
2. Select Start / All Programs / PostgreSQl 9.2 / PGAdmin III
3. Log into the database by right clicking on "PostgreSQL Database Server 9.2 (localhost:5432)" and type the PostgreSQL Superuser Password if prompted.
4. Expand the the database by right clicking on "PostgreSQL Database Server 9.2 (localhost:5432)" category by left clicking on the small square enclosing a plus sign.
5. Expand the "Databases" category.
6. Right-click on the "cm" schema and select "Restore".
7. Format should be Custom or TAR. Browse to file path and the backup file. Select 'Restore'.
8. Wait a few minutes for the Restore to finish. You should see 'Process returned exit code O'. Select 'Done'.
9. Restore is complete. Close PGAdmin III.

If the content and configuration files were removed in the process, now is the time to restore them.

Update Content Manager

Go to http://www.scala.com/updates to obtain the download for the correct Content Manager update.

Run the Content Manager installer and follow the steps.

Check that everything is working. Then make a backup.

Sending Remote Update to Players

1. Go to Content Manager / Network / Maintenance Jobs
2. Select the Upload Files, navigate to, and download the remote update ZIP file from www.scala.com/updates. You must key in your Content Manager serial number.
3. Example: Release_10_2_2_player_remote_update.zip
4. Select 'New' to create a new maintenance job, select the type Player, and enter a name for the job. Example type: Scala Player Update. You can choose to select Players by their names or if created by group name.
5. Select 'Next' and add the Players you wish to update.
6. Select 'Tasks' and 'Add' Give the update task a name, select the task command 'Install software update’.
7. Click on the 'Select' button, and then the Upload button. Select 'Add' and navigate to the Remote Update ZIP file you downloaded. You will now see it listed in the Maintenance job. Place a check mark, and click on 'Select'. Click on 'Add'.
8. Select the Scheduling tab. Click on 'Add'. Schedule the type when you want it to update. ASAP is best. If selecting a time make sure you account for the time the synchronized Plan needs to be delivered. Click on 'Add'.
9. Save the Maintenance Job.
10. Synchronize the Players.