Updating from CM 11.03.06 to 11.04 with a Content Manager 11.04 DVD (PostgreSQL)

This is an example how to update from CM 11.03.06 to 11.04 with 11.04 Content Manager DVD installer(Database: PostgreSQL). This is when Java, Tomcat and PostgreSQL need to be upgraded.

The DVD installer contains third-party components. It might be easier to upgrade Content Manager with the DVD installer because it does not need to download them each time. Support will provide you a download link if you request it.

Note

Scala maintenance coverage must not have ended
Update Content Manager to 11.03.06 or higher 11.03.0X
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

You need to uninstall MongoDB as well. (Backup MongoDB before uninstalling)

Check any serious errors in ContentManger.log
Prepare several backups and test it.
Release 11.03 and above, Windows XP Player is not supported.

Download the DVD installer.
1. Unzip Release_11_04_00_ContentManagerDVD.zip file.
2. Right click on Release_11_04_00_ContentManagerDVD.zip>Extract All

Check current versions in ContentManager.log
1. Default C:\ProgramData\Scala\InfoChannel Content Manager 5\Logs

CMSystemInfo

OS: XXXXXX (amd64)
Java: 1.8.0_73 (Oracle Corporation)
Scala Enterprise Content Manager: Release 11.03.06(2017.04.18, R11_3:f0d058a)
Web Server: Apache Tomcat/7.0.70
Database info (PostgreSQL): PostgreSQL 9.3.5, compiled by Visual C++ build 1600, 64-bit

Check CM11.04 System Requirements
1. https://docs.scala.com/display/CM1104/Verifying+Technical+Specifications
2. https://docs.scala.com/display/CM1104/Third+Party+Requirements
3. Java 8 Update 131 or better.
4. Apache Tomcat 7 web server, version 7.0.77 or better.
5. PostgreSQL database, version 9.5.7 or better.
Confirm current settings
1. Database schema (Case sensitive) and username

Scala does not support the modification of its database schema (which by default is cm). Doing this will lead to negative consequences when patching the database

Connection URL (Virtual folder/port/Connection host address)

Administrator password

Database connection password.

In case you ticked Store password before, the password would be stored in %APPDATA%\PostgreSQL\pgpass.conf. Default: C:\Users\XXXXX\AppData\Roaming\postgresql
Open pgpass.conf to confirm the password

CM1104 updating tips.
1. https://docs.scala.com/display/CM1104/Updating+Your+Network
2. The following versions have been approved for direct upgrade to version 11.04:
3. Release 11.02.06
4. Release 11.03.06
Backup your current database by following the instructions found on the Creating Backups
1. Data Files C:\Program Data\Scala\InfoChannel Content Manager 5\Data
2. Configuration Files （Conf, License, SavedValues, License.xml）
3. Database
4. Backup your database

Open pgAdmin>Right click on the schema>Backup>Save and rename it to an appropriate location. Ex. C:\Users\XXX\Desktop\YYYYMMDD.backup >Format:Tar>Backup

.

Set the Format to tar in the backup dialog. Filename example YYYYMMDD_CMVerion100502 Do not use period (.)

Confirm exit code 0 and the backup file is not 0KB in size nor too large.

If exit code is 1, retry it. It still shows 1, copy the error. Send the error and database backup to support. Cancel updating Content Manager.

Uninstall any older versions of PostgreSQL
1. Open Control Panel>Programs>Programs and Features>Right Click on postgreSQL 9.3<Uninstall

Click on "Yes" to restart the server.

After reboot, wait until the system stabilizes

Install PostgreSQL 9.5.7
1. Open the unzipped file>3rdParty>PostgreSQL 9.5.7

Set database connection password. (prefer same as step 4.d)

Change appropriate settings.
Uncheck Launch Stack Builder at exit.>finish

Restore from the database by following the instructions found in the Restore from Backups page.
1. Stop Apache Tomcat and Transmission Server Services
2. Open pgAdmin>Connect to your database server using the same Username and Password you entered when you installed Content Manager. Step 8b
3. Select Databases under postgreSQL 9.5, and then right click on it> New Database. Type the database schema name (Step 4.a)you want to restore. Make sure the encoding is set to UTF-8 (Definition tab). Click OK.

You can now restore the tables and data. Select the database, right click, and choose Restore.

In the resulting dialog box, choose the database backup file that was created. If you backed up the database using specific options, you must change the restore options accordingly. Otherwise the defaults are okay.

If exit code is 1, retry it（Delete Schema＞Create Schema>Restore) and try other backupdatabases.

Start Apache Tomcat and Scala Transmission Server services

Login To Content Manager.

You may be prompted to reconnect to the database. Select Test to test the connection..Password was set Step 8.b

Save>Select Next to complete the operation

Uninstall the version of Tomcat
1. If you are asked whether you want to remove all the files in the Apache Tomcat directory, select No.
2. Control Panel>Program>Right click on Apache Tomcat>Uninstall

Select No. below

Accidentally if you click Yes, generally it does not affect much. However if you previously changed "Initial memory pool" and "Maximum memory pool", you might need to re-check it after setting up Content Manager.

Run the installer
1. Basically, you click “Yes” and “Next” during the installation unless you want to change settings.
2. Double click on setup_contentmanger.exe.

Install Java>Yes

Install Apache

Accept the agreement.

Use Existing installation settings.

Open Windows Services Manager. Click refresh button. Confirm that Apache Tomcat, Scala Transmission server and PostgreSQL services are started.

Wait until the system stabilizes

Type the administrator password>Submit

Check all the players and filters are showing up

Troubleshooting
1. Content Manager Does not Show Correct Database Value Force Indexing on Next Start
  - Player version shows "Unknown"
  - Playlist filters do not work as expected
  - Only one player is visible on CM after upgrade
  - Plan generation performance is not good.
  - After upgrading a player, filtered view does change after the Player delivers its nightly log files. (Generally next day) Fix Version/s:11.05
Edit a backup batch file.
Update players.
1. Install a Player Updater via CM 11.00.06
  1. After updating ContentManager, Scala recommends that you update one or more Scala Players in your lab-environment or test-environment, and verify satisfactory operation.