Content Manager 11.00


This release has reached its end of support. We strongly advise that you update to a more current release.

For more information on updating or upgrading, please contact your sales representative.

Skip to end of metadata
Go to start of metadata

Important Note about Software Dongles:


Scala Content Manager and Designer come with a USB key (dongle).

To ensure the correct driver is installed and used, please do not insert the USB key (dongle) until requested by the Installer program.

Installing Scala Enterprise Content Manager is a relatively simply process when followed closely.  The install wizard will allow the user to quickly install the product.

Here’s what will be installed:

  • Content Manager
  • Microsoft Visual C++ 2013 Redistributable
  • Java Runtime (as of Release 11.00, Content Manager now ships with, and requires, Java 8 Update 25)
  • Apache Tomcat Web Server (as of Release 11.00, Content Manager now ships with, and requires, Tomcat 7.0.57)
  • PostgreSQL Database 9.3.5-3 (if selected)

Suggested components you may wish to install:

  • Flash – So Content Manager can render thumbnails of SWF files.

Supported databases other than PostgreSQL:

  • Microsoft SQL Server 2008, 2008 R2, 2012



Before reading the Installation Steps below, it is recommended that you read the Advanced Configuration Options page, as the information contained there may effect your individual installation process.

Installation Steps


Please be aware that users have reported issues during this process when connecting remotely to Content Manager to configure, specifically with selecting a network name that is not localhost.

1. Insert the Disc

Insert the Content Manager disc into your computer. The installer should run automatically.

Another option is to right click on Start and select Explore. Open the drive for the disc. Then run setup.exe by double clicking on the icon. Then choose to install Scala Enterprise Content Manager.

If you have Windows User Account Control On, you will be prompted for permission by your system. Scala recommends that this setting is turned off. This page provides details on how to change the setting.  

2. Welcome


The Welcome dialog box offers the option of opening the Getting Started for 11.00 Guide. Otherwise, click Next to continue.

3. Third Party Components


Here you can choose to download additional components which are recommended but not installed automatically. Click Yes or No to continue.

4. Microsoft Visual C++ 2013 Redistributable



You will see the following note: "Scala Enterprise Content Manager requires Microsoft Visual C++ 2013 Redistributable Component. Would you like to install it now?"

Click Yes to continue.

5. Java Runtime



You will see the following note: Scala Enterprise Content Manager requires Java 8 Update 25, and a suitable version is not installed. Would you like to install Java now?"

If you do not have a supported version of Java Runtime installed on your computer, the installer will do this now. Click Yes to continue.

6. Apache Tomcat Server



You will see the following note: "Scala Enterprise Content Manager requires Apache Tomcat 7 Web Server (Version 7.0.57 or newer). Would you like to install Apache Tomcat 7 now?"

If you do not have a supported version of Apache Tomcat installed on your computer, the installer will do this now. Click Yes to continue. 

7. End User License Agreement

Select the “I accept the agreement button. Click Next to continue.

8. Select Language 

A list of the languages supported by Content Manager will appear. Choose the one you would like to use and click Next to continue.

9. Select Destination Location

The installation path will default to the following folder: C:\Program Files (x86)\Scala\Content Manager. If you want to change that location, click the Browse button to find the folder you want to use. Click Next to continue.

10. Database Installation Options

Choose whether to use the default PostgreSQL database server, or use an existing one. Click Next to continue.


If you chose to use a different database server, skip ahead to Step 13, Web Application Configuration.

11. PostgreSQL Database Password


Choose a password that will be used for both the database Superuser and Windows service accounts.



You will need to enter this password again later in the installation. Make sure to save this password somewhere can retrieve when you need it.

Click Next to continue.

Click OK.

12.  PostgreSQL Data Storage Options

The installer will use the PostgreSQL default location or you can specify a custom folder. Click Next to continue.

13. Web Application Configuration




If you are using a different database server, you will resume here.

Enter the parameters for Content Manager’s web application including the virtual folder and port. Click Next to continue.



Steps 14 relates to changes made for Release 11.00.03 and onward. If you are not using a release before 11.00.03, please proceed to Step 15.

14. Add, Edit or Delete Connector Settings 

Content Manager allows you to add, edit or delete Apache Tomcat connector settings. Click the appropriate button to add, edit or delete the connector. Once finished, click Next.

By clicking the Add button, the box will appear as it does below for (for HTTP):

If you select an HTTPS connector, the box appears, as below, with additional options for recording the Keystore information:

If your HTTP/HTTPS connector has custom attributes, click Add and enter that information in the following box:

To edit a connector, select it from the list and click Edit

If you choose to delete a connector, you will see the following message asking you to confirm the action by clicking Yes

Once you have made the necessary changes, click OK to proceed. 

15. Connection Configuration

Enter the parameters for Content Manager’s web application including the port and connection host address. The web address you entered must be reachable by your players. An HTTPS connector can be used by selecting the check box. Click Next to continue.

16. Tomcat Access Logs

Use the screen to turn the access logs for Tomcat either on or off. They are disabled by default, but can (re)enabled from this screen. Once you have made your selection, click Next to continue.

17. Select Data Location

Select the appropriate Data Location. This is where Content Manager will store media items. Make sure the drive has sufficient space available. If the default location is acceptable, click Next to continue.



The data folder selected cannot be at the root level (e.g. C:\). It must be in one of the subfolders of the root level (e.g. C:\Data).

18. Allow Microsoft Internet Connection Firewall Connections for Content Manager

The Microsoft Internet Connection Firewall must allow Content Manager to access network connections. Leave the box on the screen checked, and click Next to continue.

19.  Allow Network Connections for Apache Tomcat

Click Next to allow network connections for Apache Tomcat. In order for the player(s) to communicate with Content Manager, the box on the screen must be checked.

20. Ready to Install

You are now ready to install. Click Install to continue.

21.  Disable Apache Tomcat Default Page

For security reasons, click Yes to disable the default Apache Tomcat web page.



Content Manager will be installed on your system. The file extraction process can be monitored with the progress bar. This may take several minutes. Additional Third Party installations may take place depending on what you selected earlier. 

22. Insert USB Key

Content Manager comes with a USB dongle that you must insert into a USB slot on your computer in order to operate. Insert it and wait for the device to initialize, then click Next.

23. Setup Will Resume in Browser

Once the install is complete, an information dialog box will note that setup will continue in a browser. Click OK.

24. Finish Installer

Your browser will open, but you can return to the installer and click Finish. If you selected View the Update Notes, you can read them after installation is complete. A browser will launch in a separate window.

25. Welcome to the Setup Wizard

The setup process will be completed in a browser. Click Next to continue.

26. Administrator Password and 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.

On this screen, you will need to choose and enter a password for the Administrator account which must be at least 8 characters in length. As with any password, make sure it is a secure password and save it in a safe location.  Further down, select your database configuration from the Type button. Then enter the host, port and other relevant information. If you choose PostgreSQL, all but the password will be filled in for you. Otherwise you will need the host, username and password for a different database server. You can test the connection by clicking Test. Click Save to continue, once you have successfully tested your connection. 



The language of the database user, which is located external to Content Manager, must be set to English.

27.  Database Creation

Content Manager will establish a connection and create the database schema. Click Next to continue.  Once complete, the system will redirect you to the login page.

28. Login to Content Manager

Enter the Username (Administrator) and Password (previously chosen) then click Sign In.


User names are not case sensitive, but passwords are.

29. Specify a Network Name

Select a name for your network. This name will appear in various places in the Content Manager interface and is helpful if you have more than one Content Manager.


Once you select a network name, you cannot change it.

Click Create. Content Manager is now available to use.

  • No labels