Updating from CM 10.05.16 to 11.02 with a Content Manager 11.02 DVD (PostgreSQL)

This is an example how to update from 10.05.16 to 11.02 with a 11.02 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
- Serial Numbers, Scala Maintenance Subscription and Download Updaters
Update equal to or newer than 10.05.16 if the Content Manager is like 10.05.05
- 10.05.05----10.05.16 (Open Content Manager) ----11.02 DVD----11.02.06
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)

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

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

CMSystemInfo

postgreSQL version

OS: Windows XXXXX (amd64)
Java: 1.7.0_55 (Oracle Corporation)
Scala Enterprise Content Manager: Release 10.5.16
Web Server: Apache Tomcat/7.0.53
PostgreSQL 9.2.4

Check CM11.02 system requirements
1. https://docs.scala.com/display/CM1102/Verifying+Technical+Specifications
2. https://docs.scala.com/display/CM1102/Third+Party+Requirements
3. Java 8 runtime from Oracle, version 1.8.0.73 or better.
4. Apache Tomcat 7 web server, version 7.0.70 or better.
5. PostgreSQL database, version 9.3.5 or better
Confirm current settings
1. Database schema (Case sensitive) and username
  - System>Database Configuration

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)
- System> Server Settings>Client Connection

Administrator password

Database connection password.
- Open pgAdmin

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

CM1102 updating tips.
1. https://docs.scala.com/display/CM1102/Updating+Your+Network
2. The following versions have been approved for direct upgrade to version 11.02:
  - Release 10.5.14 (or higher, as that version was a private build.)
  - Release 11.00.09
  - Release 11.01.04
Backup your current database by following the instructions found on the Creating Backups
1. Data files Defualt:C:\Program Data\Scala\InfoChannel Content Manager 5\Data
2. Configuration Files （Conf, License, SavedValues, License.xml）
3. Database
  - In the Windows Services Manager, stop the Apache Tomcat service and Scala Transmission Server services

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_CMVerion100516 Do not use period (.)

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

If exit code is 1, retry it.

Uninstall any older Versions of PostgreSQL
1. Open Control Panel>Programs>Programs and Features>Right Click on postgreSQL 9.X<Uninstall

Click on ”Yes”. Restart your server.

After reboot, wait until the system stabilizes

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

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 Scala Transmission Server Services
  - Open pgAdmin>Connect to your database server using the same Username and Password you entered when you installed Content Manager. Step 8b
2. Select Databases under postgreSQL 9.3, 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 backup databases.

Start Apache Tomcat And Scala Transmission Server Services
- You might need to restart the server if Apache Tomcat service is not starting.
- Wait until the system stabilizes

Login to Content Manager.

Below might show if you changed the database connection password. Type in Administrator Password>Submit.

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 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 need to re-check 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.

Adobe Flash (Scala Enterprise only supports Flash through version 10.3.x)
- If you do not use Adobe Flash contents, click No
Install Java>Yes

Install Apache

Accept the agreement.

Use Existing installation settings.

Open services. 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
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.
Make sure Automatic Java Updates is unticked .

Click the Update tab to access the settings. To disable Java Update,
1. deselect the Check for Updates Automatically check box. Click on Apply.