Content Manager 11.00

A more recent release of this software is available. Please refer here to access documentation for other releases.

Skip to end of metadata
Go to start of metadata

Warning

Icon

Release 11.00 of Content Manager included major refactoring of the core engines, including Playback Audit Module's migration to MongoDB. As a result, we strongly recommend that you adhere to the best practice of backing up your system when upgrading to 11.00. Information on how to do that can be found under Creating Backups.

For instructions on how to move your Playback Audit data to Release 11.00 or newer, please see Migrating Playback Audit Data from a 10.x Release.

Update Eligibility

Software updates are provided under the Scala Maintenance program. If your Scala Maintenance is current, then you can access all current updates for products you own.

If your Scala Maintenance coverage has ended, you will not have access to any software updates.

For further information related to licenses, software maintenance and software updates you should contact your Scala sales representative.  If your Scala Maintenance date has lapsed, you can renew your Scala Maintenance Subscription by contacting your Scala Certified Partner. 

Obtaining Current Updates of Scala Software

You can download the latest updates for Scala by visiting http://www.scala.com/updates. You will need your product serial number(s) in order to download any updates.

Most updates are cumulative which means that they include all the changes to the software prior to the version being downloaded. If you have kept your software up to date, then you can apply the newest update without having to apply any in-between updates you may have skipped.  Each update comes with a simple and quick installer. In addition, the Player update comes in a form that can be sent by Content Manager to remotely update players.

Supported Upgrade Path

The Scala product team does its best to test and verify all upgrade paths between the oldest currently supported version and the released version being documented here.  Our tests cover upgrading from the latest release of a noted version to the current version.  As your system configuration may be uniquely customized, this guidance is our advice based on our testing. We hope it provides the most efficient path from your version to this release.

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

  • Release 10.3.4
  • Release 10.4.8
  • Release 10.5.5

Staying on a currently supported version is key to ensuring that your upgrade path is supported as well.  If your currently used version is out of support, then we advise you look at the upgrade path for the prior version to this one and work backwards until you find a suitable upgrade path for your needs.

Apply Scala Updates in the Correct Order

Caution:

Icon
Updating your Content Manager with new versions is dependent on your having an active Scala Maintenance plan and a corresponding License. Updating your license file with your software update is important.

To ensure proper operation, always update in this sequence:

Warning:

Icon

Before updating Scala Enterprise Content Manager, make a backup of your database. This will make it easier for you should you need to rollback the update at any point. Check that the backup file is not 0KB in size. If you are using a virtual environment, such as VMWare to run your Content Manager, an image checkpoint or backup, can do the same function as a backup of your database.  

  1. Update Scala Enterprise Content Manager along with any other server software components, i.e.:
    • Scala Broadcast Server
    • IAdea Bridge Server
  2. Next, Scala recommends that you update one or more Scala Players in your lab-environment or test-environment, and verify satisfactory operation.
  3. Then, update your Scala Players. They do not have to all be updated at once.
  4. Once all the Scala Players are updated, update Scala Designer.

Thus, the "version rule" can be said to be:

Content Manager newer or equal to Players
Players newer or equal to Designer

Scala version numbers are of the form:

  • Release major
  • Release major.minor
  • Release major.minor.hotfix

In general, the hotfix number can be disregarded when applying the "version rule," unless Scala specifies differently for a given hotfix.

Remote Update of Scala Players

Scala Player Remote Updater

You can use Scala Enterprise Content Manager to send software updates to your Scala Players:

  1. Download the desired version of Scala Player Remote Software Updater from http://www.scala.com/updates.
  2. In Content Manager, under Network, click Maintenance Jobs.
  3. Click New to create a new maintenance job.
  4. If your network also has IAdea media appliances, you will need to select Scala Player maintenance job and click Next. Otherwise proceed to the next step.
  5. On the Tasks tab, select the Install software update task, click "Select" to upload Release_version_player_remote_update.zip file. (Do not unzip the file first) or select your Player remote update zip file from the list that will appear. You will also need fill in the "run as" and "password" fields with the proper credentials.
  6. Click on the Scheduling tab and select a suitable schedule (or 'ASAP').
  7. Click on the Players tab and select the players you want to update.
  8. Save the job.
  9. Synchronize those players to apply the update. 

Android Player Remote Updater

You can use Scala Enterprise Content Manager to send software updates to your Scala Android Players.  

  1. Download the desired version of Scala Player Remote Software Updater from http://www.scala.com/updates.
  2. In Content Manager, under Network, click Maintenance Jobs.
  3. Click New to create a new maintenance job.
  4. Under select Player type and choose Android.
  5. On the Tasks tab, select the Install APK update task, click "Select" to upload Release_version_player_remote_update.zip file. (Do not unzip the file first) or select your Player remote update zip file from the list that will appear.
  6. Click on the Scheduling tab and select a suitable schedule (or 'ASAP').
  7. Click on the Players tab and select the players you want to update.
  8. Save the job.
  9. Synchronize those players to apply the update.

Python Remote Updater for Scala Players

From time to time Scala updates the Python distribution (the current version of Python is 2.7.9.) In addition to an installer that is suitable when you have physical access to the PC, Scala provides a Python Remote Updater for Scala Players. You can also download this from http://www.scala.com/updates and remotely deploy this to Scala Players in the same way as the Scala Player Remote Updater, as discussed above.

Keeping Other Software Up to Date

Note:

Icon

Scala has minimum requirements for some of the software components discussed in this section, which can be found on the Verifying Technical Requirements page. Please be aware that the version of these components may change from one release to another, so it is important to check the minimum requirements for every release before upgrading your Scala Enterprise Content Manager.

Windows Update

It is generally a good idea to keep at least reasonably current with Windows Update. That said, from time to time a Microsoft update has introduced undesirable side effects. Your organization may have Windows Update practices and policies to help.

A great many Microsoft security fixes protect PCs when users visit malicious web sites or open malicious documents. As such, a lot of those fixes are not particularly relevant to a properly-hardened Player PC, which does have users driving web browsers or opening arbitrary documents. A more selective approach to updating may be suitable for remotely administered hardened Player PCs. 

Scala Enterprise requires Windows 7 Professional or newer. 

To see our list of certified Scala PC Players, please click here

Apache Tomcat

Note:

Icon

If you are updating your Tomcat to version 7.0.70, please re-install your Content Manager or it will not work with special characters.


From time to time, the Apache Software Foundation may release updates to Tomcat, to address security issues and/or other issues. The Apache Tomcat security team maintains a 
web page of security vulnerabilities and the revision in which they are addressed.

If you need to update your Tomcat installation:

  1. Back up your Content Manager database, as a precaution. Check that the backup file is not 0KB in size.  For detailed instructions on how to back up your database, go to Creating Backups
    Normally, you will not need to restore from this backup.
  2. Uninstall the version of Tomcat you already have installed. If you are asked whether you want to remove all the files in the Apache Tomcat directory, select No.
  3. Download and install the desired version of Apache Tomcat. This site will lead you to the correct download location.
  4. Apply the latest Content Manager updater (even it it had previously been applied.) This is needed in order to regenerate the web application settings for Tomcat, which contain the deployment parameters for Content Manager. It also will ensure that the Apache Tomcat Windows service is set to auto-start. 

Note:

Icon

Starting with Release 11, HTTPS from a proxy server, such as Apache HTTPD or NGINX can now be used without the need to configure SSL within Content Manager or Tomcat. More information can be found on Managing HTTP Connectors in Tomcat.

PostgreSQL

Most Content Manager installations use PostgreSQL as the database. 

To check your PostgreSQL version, check your Windows Start menu, under Programs. You will have an entry reflects your version of PostgreSQL.

Starting and Stopping Services

To update your PostgreSQL installation you will have to start and stop certain Windows services as indicated below, using the Windows Services Manager. To access the Services Manager, either:

  • right-click on My Computer and select Manage, then in the left pane select Services and Applications > Services
  • in your Control Panel, select Administrative Tools > Services

From here, you can start and stop services by finding the right service in the list, right-clicking, and selecting Start or Stop.

Upgrading to PostgreSQL to the current version

  1. In the Windows Services Manager, stop the Apache Tomcat service.
  2. Back up your current database by following the instructions found on the Creating Backups pageCheck that the backup file is not 0KB in size.
  3. Follow this link to download the new version of PostgreSQL.
  4. Uninstall any older versions of PostgreSQL.
  5. Run the installer you downloaded to install the new version of PostgreSQL. Toward the end of the install, uncheck Launch Stack Builder at exit.
  6. Restore from the database backup you made above, by following the instructions found in the Restore from Backups page. 
  7. Start the Apache Tomcat service.
  8. Login to Content Manager. You may be prompted to reconnect to the database. Select Test to test the connection. Select Next to complete the operation.

Java

From time to time, Oracle may release updates of Java, to address security issues and/or other issues.

On most systems, Java is configured to automatically update, so no further action should be needed.

If you need to update Java, follow the appropriate link from the list below, then download and apply the appropriate installer:

Java 8

Caution:

Icon

When updating to a newer version of Java 8, certain Tomcat parameters need to be adjusted in order for Tomcat to continue to work. You should re-run the Content Manager installer to make sure this has occurred, but in rare cases, such as upgrading Content Manager after a hardware upgrade, these may have to be manually set. In addition, if you have manually set these values in the past, the Installer may overwrite your values as it tries to optimize your system for the Java install. Please take care to record your Tomcat settings before running the Content Manager installer, in case they need to be recovered later.  

For guidance on what Scala's recommended settings for Tomcat, please see Checking the Tomcat Java Memory Settings in Advanced Configuration Options for Content Manager

Because of this, Scala does not recommended that you allow your Java to update automatically, but instead stay aware of Java updates, and install them manually, then do the above step. 

Remote Firmware Update of IAdea Media Appliances

From time to time IAdea issues firmware updates for its media appliances. You can also download these from http://www.scala.com/updates. For simplicity, IAdea provides a single unified file containing the firmware updates for all devices. Remotely deploying the firmware updates is done in a very similar manner to deploying the Scala Player Remote Updater:

  1. In Content Manager, under Network, click Maintenance Jobs.
  2. Click New to create a new maintenance job.
  3. If your network also has Scala Players, you will need to select IAdea maintenance job and click Next. Otherwise proceed to the next step.
  4. On the Tasks tab, select the Install software update task, click "Select" to upload Release_version_player_remote_update.zip file. (Do not unzip the file first) or select your Player remote update zip file from the list that will appear.
  5. Click on the Scheduling tab and select 'ASAP'.
  6. Click on the Players tab and select the players you want to update.
  7. Save the job.
  8. Synchronize those players to apply the update.
  • No labels