content manager 5 getting started guide

8/10/2019 Content Manager 5 Getting Started Guide

http://slidepdf.com/reader/full/content-manager-5-getting-started-guide 1/86

www.scala.com

®

Getting Started GuideContent Manager



Getting Started Guide

for

Content ManagerRelease 6

www.scala.com



Content Manager Getting Started Guide

1

Copyright © 1993 to 2012 Scala Inc. All rights reserved.

Published by Scala Incorporated, Exton, PA

No part of this publication, nor any parts of this package may be copied or

distr buted, transmitted, transcr bed, recorded, photocopied, stored in a

retrieval system, or translated into any human or computer language, in any

form or by any means, electronic, mechanical, magnetic, manual or

otherw ise, or disclosed to third parties w ithout the prior w ritten permission of

Scala Incorporated.

Trademarks

The follow ing are trademarks or registered trademarks of the companies

listed, in the United States and other countries.

Scala, Scala Player and the logo: Scala Incorporated.

Warranties and Disclaimers

The f ollow ing paragraph does not apply to the United Kingdom or any other

country w here such provisions are inconsistent with local law .

Scala Incorporated provides this publication “as is” w ithout any w arranty of

any kind, either express or implied, including, but not limited to, the limited

w arranties of merchantability or f itness f or a particular purpose. Some states

do not allow disclaimer or express or implied w arranties in certain

transactions, therefore this statement may not apply to you.

This publication could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein: these changes w ill

be incorporated in new editions of the publication. Scala may make

improvements and/or changes in the product(s) and/or the program(s) in this

publication at any time.

It is possible that this publication may contain reference to, or information

about, Scala products or services that are not announced in your country.

Such references or information must not be constructed to mean that Scalaintends to announce such Scala products or services in your country.

Requests f or technical information about Scala products should be made to

your Scala Authorized Distr butor, Dealer or your Scala Marketing

Representative.

Scala may have patents or pending patent applications covering subject

matter in this document. The furnishings of this document does not give you

any license to these patents. Send license inquires, in w riting to Scala Inc.,

350 Eagleview Blvd, Suite 350; Exton, PA 19341, USA




2

Table of Contents

Table of Contents............................................................ 2

Preface ............................................................................ 4

In this Guide ................................................................ 4

Other Resources ......................................................... 4

Important Note about Software Dongles .................... 5

Introducing Content Manager ......................................... 6

System Requirements..................................................... 8

Before You Install.......................................................... 10

Installing Content Manager ........................................... 12

Installation Steps ....................................................... 12

Logging On To Content Manager ................................. 36

Activating Content Manager...................................... 37

Navigating Content Manager .................................... 38

Workflow in Content Manager................................... 39

Adding Users................................................................. 40

Create a Workgroup .................................................. 40

Create a User Account .............................................. 41

Adding Players .............................................................. 44

Creating a Channel ....................................................... 48

Uploading Media ........................................................... 51

Creating Playlists .......................................................... 54

Modifying a Playlist ................................................... 57

Scheduling Playlists ...................................................... 58




3

Updating Players........................................................... 60

Assign a Channel ...................................................... 60

Manage Distribution .................................................. 61

Monitoring Status .......................................................... 63

Doing More with Content Manager ............................... 65

Optional Components ................................................... 67

Getting Updates ............................................................ 68

Backup and Restore ..................................................... 69

Troubleshooting ............................................................ 70

Content Manager....................................................... 70

Player ........................................................................ 71

Scala End User License Agreement............................. 73




4

Preface

We know you are anxious to get started and install the

software, however this Getting Started Guide contains

the instructions required for a successful installation.

It is important for users to read through the guide

BEFORE you install the software so you can understand

the options, settings and configurations of the program.

In this Guide

This Getting Started Guide will help you install and learnthe basics about Content Manager, including:

The Scala Workflow

Installing Content Manager

Setting up Users

Adding Players

Creating Channels, Playlists and Schedules

Optional Components

Troubleshooting

Other Resources

In addition to this guide, additional resources are

available:

User Manualsprovide a complete reference for all thefeatures of Content Manager. These are available on

the installation disc as well as online (See Extras).

Release Notes provide addition information about

changes since the manual was published and advanced

subjects including data integration. A shortcut is

installed in the Windows Start Menu or visit

http://www.scala.com/releasenotes.

http://www.scala.com/releasenotes

http://www.scala.com/releasenotes




5

Updates shows which updates are available for the

product(s) you have currently licensed.

Visit http://www.scala.com/updates.

Extras is a resource of information and inspiration, from

documentation to examples and more.

Visit http://www.scala.com/extras.

Support provides help through FAQs and a Discussion

Forum. Visit http://www.scala.com/support.

Services and Training are available to help you get the

most out of your digital signage network. Visithttp://www.scala.com/services.

Important Note about Software Dongles

Scala Content Manager and Designer come with USB

keys (dongles).

To ensure the correct driver is installed and used,

please do not insert the dongle(s) until requested by the

installer program.

http://www.scala.com/updates


http://www.scala.com/extras


http://www.scala.com/support


http://www.scala.com/services

http://www.scala.com/services







6

Introducing Content Manager

Scala Content Manager is a powerful application for

digital signage content distribution, scheduling and

management.

Content Manager is a server-based application that lets

you control from one to hundreds, even thousands of

digital signage displays from a simple browser interface.

Advertising, news, training or virtually any other visual

communication can be easily distributed to Scala

Players via any standard Windows-based network.Content is created using Designer or other industry

standard applications.

In a Scala Enterprise network, Designer is part of a

workflow process, allowing users to create scripts and

templates, manage them in Content Manager and play

them in Player.




7

Creative designers use Designer to create Scripts and

Templates. Media can also be uploaded directly to

Content Manager.

Message editors use Content Manager to create and

edit Messages using Templates.

A schedule manager works in Content Manager to set

up Playlists consisting of media, Scripts and Messages,

and schedules when the Playlists will appear.

A network administrator uses Content Manager to

manage and monitor Players, ensuring content is

playing properly.

In advertising-based networks, sales managers would

use Ad Manager to price and sell ad inventory on the

network.




8

System Requirements

Carefully follow the recommendation for all hardware

requirements to insure the maximum performance of

your Content Manager System.

Required Operating Systems

Windows 7 Professional, Ultimate (32 or 64 bit)

Windows Server 2008 R2

Windows Server 2003 SP2 Enterprise, Web

Edition

Windows XP Professional SP3 Professional




9

Required Hardware




10

Before You Install

Go through this checklist to make sure you are ready to

install and configure Content Manager.

Make sure you have the USB key.

Select a server to install Content Manager. See

the System Requirements for details.

Choose a database type and location. Content

Manager comes with PostgreSQL and will install

it on the same computer as the application

unless you specify otherwise. It does allow otherdatabase types, as well as a separate

PostgreSQL server. If you plan to use an existing

database server, make sure you have the

necessary host name and credentials to access

the database.

You will need to know the Content Manager

server host name and understand how users &players will access the server. Scala uses HTTP

protocol over port 8080. The settings may

depend on where things are located and if proxy

server(s) or NAT firewalls are in place.

During the installation process you will need to:

If you will be installing the PostgreSQL server,

you will be asked for a user name and password

that is used for the PostgreSQL service and

accessing the database. This will be created for

you by the installer.

Select the password for the built-in Administrator

user account.

Choose a name for your network in Content

Manager. This name will appear in Content




11

Manager and is useful for customers that have

more than one Scala network.

Activate content manager. This requires either

an Internet connection or the ability to downloada license file and copy it to the Content Manager

server.

After installation you will need to:

Create user accounts.

Add players.

Set up content to play.




12

Installing Content Manager

Installing Scala 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

Java Runtime

Apache Tomcat Web Server

PostgreSQL Database (if selected)

DirectX

MainConcept MPEG 2,H.264 and MPEG-4 ASP

Decoders

Suggested components you may wish to install:

Flash – So Content Manager can render

thumbnails of SWF files.

Acrobat – To read Scala documentation.

Supported databases other than PostgreSQL:

MySQL 4.1, 5.0

Microsoft SQL Server 2005, 2008, 2008 R2

Installation Steps

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 Content Manager 5.




13

2. Welcome

The Welcome dialog box offers the option of opening

the Getting Started Guide in PDF format. Click Next to

continue.

3. Third Party Components

Here you can choose to install additional components

which are recommended but not installed automatically.

Click Yes or No to continue.




14

4. Java Runtime

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.5. Apache Tomcat Server

Scala Content Manager requires Apache Tomcat web

application server. Click Yes to continue.

The installer will proceed to install the selected

components. Then it will continue with the setup

process.




15

6. End User License Agreement

Select the “I accept the agreement” button. The full

EULA can be read here and is also available at the end

of this document. Click Next to continue.




16

7. Select Language

Choose the appropriate language and click Next.

Note: This only specifies the default language. Each

user can pick their own language in the RegionalSettings of their account options.




17

8. Select Destination Location

The installation path will default to the Program Files

folder. If you want to change that location click the

Browse button and select another location. Click Next

to continue.




18

9. Database Installation Options

Choose whether to use the default PostgreSQL

database server, or use an existing one. Click Next to

continue.

Note: If you chose to use a different database server,

skip ahead to Step 12, Web Application Configuration.




19

10. PostgreSQL Database Password

Choose a password that will be used for both the

database Superuser and Windows service accounts.

Note: You will need to enter this password again later inthe installation. Make sure to save this password

somewhere can retrieve when you need it.

Click Next to continue.

Click OK.




20

11. PostgreSQL Data Storage Options

The installer will use the PostgreSQL default location or

you can specify a custom folder. Click Next to continue.




21

12. Web Application Configuration

Note: If you selected to use a different database server,

you will resume here.

Enter the parameters for Content Manager’s webapplication including the virtual folder, port and

connection host address. Click Next to continue.




22

The web address you entered must be reachable by

your players. Click Yes to continue.




23

13. 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.




24

14. Video Decoders

The installer will install MainConcept’s MPEG-2, H.264

and MPEG-4 ASP decoders. Click Next to continue.




25

15. Allow Network Connections for Content Manager

The Microsoft Internet Connection Firewall must allow

Content Manager to access network connections. Click

Next to continue.




26

16. Allow Network Connections for Apache Tomcat

Click Next to continue to allow network connections for

Apache Tomcat.




27

17. Ready to Install

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

Content Manager will be installed on your system. The

file extraction process can be monitored with theprogress bar. This may take several minutes.

Additional 3rd Party installations may take place

depending on what you selected earlier.




28

18. Disable Apache Tomcat Default Page

Click Yes to disable the default Apache Tomcat web

page.

19. Insert USB Key

Content Manager comes with a USB key that you must

insert into a USB slot on your computer in order to

operate.

Insert the USB key and wait for the device to initialize,

then click Next.




29

20. 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.




30

21. Finish Installer

Your browser will open, but you can return to the

installer and click Finish. If you selected View the

Release Notes, you can read them after installation is

complete.




31

22. Welcome to the Setup Wizard

The setup process will be completed in a browser. Click

Next to continue.

23. Administrator Password

Choose and enter a password for the Administrator

account. As with any password, make sure it is a secure

password and save it in a safe location. Click Next to

continue.




32

24. Database Configuration

Select the type of database configuration from the Type

button. Then enter the host, port and other relevant

information.




33

If you choose PostgreSQL, all but the password should

be filled in for you. Otherwise you will need the host,

user name and password for a different database

server. You can test the connection by clicking Test.Click Next to continue.

25. Database Monitor

The Database Monitor will establish a connection and

create the database schema. Once created, click Next.




34

26. Login to Content Manager

Enter the Username (Administrator) and Password

(previously chosen) then click Login.

Note: User names are not case sensitive, but

passwords are.




35

27. 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 Managers.

Note: Once you select a network name, you cannot

change it.

Click Create. Content Manager is now available to use.




36

Logging On To Content Manager

After completing setup, you will log in to Content

Manager. But at some point you will need to log on

again and probably from a different location.

When working on the server where Content Manager is

installed, you can find a link to Content Manager Start

Menu under Program -> Scala Content Manager 5 ->

Access Scala Content Manager 5.

If you are logging on from another computer, you will

need to open a browser and enter the URL to server,which usually looks like this:

http://servername:8080/ContentManager

Enter the Administrator user name and password (or

your own user name and password) and Click the Login

button.




37

Activating Content Manager

In addition to the USB key, Content Manager must be

activated in order to operate.

If you have not activated Content Manager, a message

will appear indicating that you must activate Content

Manager with a license file. You can install the license

file now or choose to defer installing the file for up to 30

days.

If you select “Get New License File Online”, Content

Manager will retrieve it from the Scala license server.

You can also select “I have It” if you have a copy of your

license file or defer by selecting “Get it Later ”.




38

Navigating Content Manager

The Content Manager home page is divided into six

areas:

1. Title Bar 2. Menu Tabs (Content, Planning, Network,

Reporting, Settings)

3. Main Area

4. Network Summary

5. Network Status

6. Scala Online Extras

1

2

3

4

5

6




39

Workflow in Content Manager

Content Manager incorporates a workflow that allows

users to perform tasks ranging from creating content to

scheduling playlists to managing players.

1. As an Administrator, your first tasks will be to

add User Accounts and Players to the network.

2. Next you will need to create a Channel, which

defines the layout of the screen.

3. Then upload any media files that you want to

play.4. Create Playlists from those media files.

5. Schedule when the Playlists should play on the

Channel.

6. Finally, assign the Channel to Players and

update the Players with the new content.




40

Adding Users

Content Manager has a built-in Administrator user

account, but it is recommended to create separate user

accounts for each person using the system.

Create a Workgroup

If you plan on having multiple groups of users working in

Content Manager, you should have at least one

Workgroup defined.

Open the Settings tab and click on Workgroups.

Workgroups allow content to be made visible to only

certain users. Content created by a user inherits the

user’s Workgroup. But if you don’t have any defined, it is

visible all users.

To create a workgroup:

1. Click New.

2. Enter a name (eg: Main, Default, Corporate).




41

3. Click outside the Name field. This will enable theSave button.

4. Click Save.

Create a User Account

It is recommended that each user have their own

account on the system. Start by creating your own.

1. Under the Settings tab, click on Users.2. Click New.

3. Enter a user name, password, first name, last

name and email address.




42

Note: Email addresses are used for player error

and content approval notifications (see below).

4. Assign the user’s role by highlighting the role

from the list. Roles control access to functionswithin Content Manager.

5. Roles can be customized in the Roles page

under Settings.

The pre-installed roles include:

Administrator – has access to everything.

Graphic Designer – has access to mostly

content related functions.

Message Editor – has access to media and

messages but cannot delete or approve.

Message Manager – has full access to media

and messages.Network Manager – has access to all but

system administrative functions.

Schedule Manager – has full access to content,

messages, playlists and schedules.

Viewer – has limited view-only access.

6. Assign the user to a Workgroup. If you did not

create any workgroups, this will not beselectable.

7. Select any desired Regional Settings from the

drop down and radio buttons.




43

8. Choose any Miscellaneous Settings that are

appropriate for this user:

User account is active – Leave this checked

assuming you want the user to be able to startusing this account.

Approval all content from this user – This

means all media uploaded and messages

created by the user will be automatically

approved. If this user is intended to require

approval from other users, un-check this option.

User can change password – allows the userto change their own password.

User must change password at next logon –

forces the user to choose a password when they

log on the next time.

Receive email alerts – Sends player error

messages via email to this user. Enable for

users who have technical responsibilities for the

network.

Receive approval notification emails – Sends

emails when media or messages require

approval or when their approval status has

changed. Enable for users who have content

approval responsibilities for the network.

9. Click Save.

Useful Tip: Enable the approval and the email options

for higher level users, and disable them for users who

will be contributing content that needs to be approved.

Refer to your Users Guide for more information on how

to use Approvals.




44

Adding Players

Open the Network tab and click Players.

From this location you will be able to add new or delete

players, control properties and channels of players and

manage other aspects of the player list.

The light colored text in the listing area displays how

many player licenses are available.

Note: Players must be configured on the player

computer to be able to communicate with the Content

Manager. This process is described in the Player

Getting Started Guide.

1. Click New.

2. Depending on your Content Manager license,you may see a list of Player Device Types.

Choose the appropriate type and click Next.




45

Your Content Manager will have a set number of

licenses for each type of player available. The

number of remaining licenses appears in the

players list.3. Enter the player name and description.

4. If you have a channel created, you can select it

from the button in the Display Setup group. If

not, you can set the Channel later.

5. Click on the Configuration tab.

6. Select a Distribution Server . The most common

choice is the Main – Point-to-Point server,

which is built into Content Manager.

7. Select a Plan Delivery Method. If you chose

Main – Point-to-Point above, the most common

choice is Content Manager Direct.

8. The default polling interval is 1 minute. Choose a

longer interval on large networks where network




46

traffic may be an issue. Choose a shorter interval

only for demonstration or testing purposes on a

local network.

9. Other options include:

Network Bandwidth Throttling – Allows you to

limit network usage over specified times and

days.

Number of download threads – Allows the

player to download multiple files at a time.

Keep Unused Files – Keeps files on a playerthat are no longer needed by the schedule. If the

item is rescheduled within the time specified, it

will not need to be downloaded again.

Logging level – enables diagnostic logging on

the player to troubleshoot problems. Only use

this if instructed by Scala Support.

10. Click the EX Modules tab.

11. Enable any EX Modules you plan to use with this

player. Note: You will also need to enable and

configure them on the player itself.

12. Click Save.




47

You should now see your player in the list. The right

hand pane in the window will allow you to search and

filter the list by various criteria.




48

Creating a Channel

A channel defines the resolution and layout of the

screen, and contains the schedule for what will play. A

channel may optionally have a dedicated audio track,

separate to any visuals. A channel can be assigned to

one or more players.

Open the Planning tab and click on Channels.

To create a channel:

1. Click New to create a new channel. This will

open the Channel Properties on the right.

2. Enter a name and description for the channel.




49

3. Click on the Audiovisual tab.

Four sections are presented:

Audio Properties: Use a dedicated audio trackVisual Properties: Define the display layout

Preview: Representation of the visual properties

Frame Properties: Advanced frame details

4. Leave the options under Audio Properties

unchecked.

Note: Channels can have Audio-specific options,including:

Play dedicated audio track – Adds a separately

scheduled track for audio-only playlists.

Mute audio from visual media – Mutes thesound of any videos played on the channel so

they don’t interfere with the dedicated audio

track.

5. Under Visual Properties, pick a Frameset. For

example, Fullscreen 1360x768. The screen size

and layout preview will be filled in automatically.




50

6. The Frame Properties area allows you to

customize the channel layout. You can add,

delete or modify frames in the channel. However,

since framesets are shared among channels, it issuggested to create a new frameset rather than

change an existing one.

7. Click Save. Your new channel should now be

listed.




51

Uploading Media

In this section we will outline how to upload content and

manage that content for use.

Open the Content tab and click on Media.

If there are media items in the media library they will

appear here. If this is the first time you are using

Content Manager, you will need to add media files to the

library.

There are several ways media can be brought into

Content Manager:

Scala Scripts and templates are published to

Content Manager using Designer.

Media files (images, video, audio, etc.) can be

manually uploaded into Content Manager.

Media files can also be automatically uploaded

using a Publish Location (see User Guide for

details).

Applications can be written to upload media files

via Content Manager’s Web Services API.




52

In this guide, we will look at manually uploading media

files. Note: The Content Manager disc has a Clipart

folder with images, videos, music, templates and more.

1. Open the Content tab and click on Media.

2. Click on Upload Files.

3. Click Run when the Security Information window

appears.

4. The File Uploader Applet will open in a

separate window.

5. Either drag and drop files into the window, or

click Select File(s) in the toolbar.




53

6. The files will automatically start uploading to

Content Manager.

7. When done, return to the Content Manager

window. You can choose to leave the File

Uploader open for later use, or close it.

You should now see your media in the list. Note: You

may need to re-select the Media menu item to refresh

the list.

The right hand pane in the window will allow you to

search and filter the list by various criteria.




54

Creating Playlists

Playlists are sequences of media items that you can

schedule to play over a period of time. If the playlist is

shorter than the time period, as is often the case, it will

loop over and over until the end of the scheduled period.

Open the Planning tab and click Playlists.

To create a playlist:

1. Click New. You should see the Playlist

Properties tab.

2. Enter a name for the playlist.

3. The Type button has three choices:

Media – only standard media file can be used.

Audio – only audio files can be used.

Data – any file type can be used.

Leave it set to Media.




55

4. If you have Categories defined, you can select

them here. If not, the window will be empty.

5. The Ordering options let you choose how the

playlist will play on the Player.Sequence – the order in which you arrange the

items.

Shuffle – the items will be randomly arranged

like cards in a shuffled deck.

6. If you created a Workgroup, you can choose it

here. Other workgroups can have view-only

access by selecting their names in the View

workgroups list.

7. Click Add Media Item in the tool bar to add the

item(s) to the Playlist.

8. You will see a list of your media files. Select oneor more and click Add Item(s) to complete the

selection.




56

9. The item(s) should appear in your playlist.

10. Click Save to save your playlist.




57

Modifying a Playlist

1. Either double-click or select a playlist then click

Properties to edit it. You can change the

properties of the Playlist itself, or the items within

it.

2. To rearrange the items, simply drag and drop the

thumbnails to the desired sequence.

3. Each item has additional settings that you can

access by selecting the item and clicking

Properties.

4. Here you can modify things such as:

Duration and Transition

Audio Ducking

Play Fullscreen

Start and End Date

Time Range(s)

Player-based Conditions

5. Click OK to close.

6. Click Save when you are done.




58

Scheduling Playlists

In order for a playlist to play on a player, it must be

scheduled on a channel.

Open the Planning tab and click Schedules.

1. Select your desired channel from the Channel

button. If your channel has more than one frame,

select the desired frame from the Track button.

2. The grid below represents the hours of the day

and days of the week. To schedule a playlist,

click in one box and drag to another.




59

For example, to schedule it for every hour of

every day (eg: 24/7), click in the upper left box

and drag to the lower right box.

3. The Timeslot Properties window will appear.Here you can fine tune the time and days you

selected as well as other options.

4. Choose your playlist from the Playlist button.

5. Click OK.

6. Click Save.

Note: Changes or additions to the schedule are

not complete until you click Save.




60

Updating Players

Assign a Channel

Before updating a player, make sure it is assigned achannel.

1. Open the Network tab and click on Players.

2. If the Player’s Channel is <Not assigned>, select

the Player and click Properties.

3. Choose a channel in the Display Setup area.

Note: If the player is configured to display two

channels, change the Number of displays to 2 so you can specify both channels.

4. Click Save when done.




61

Manage Distribution

To see the distribution page, open the Network tab and

click Distribution.

Content Manager periodically checks for changes in

media, playlists, schedules, etc. These changes are

provided to players so they can update accordingly.

Each player receives a unique list of changes (called a

“Plan”) so it can make updates and download media. If a

player has already downloaded a media file and it has

not changed, it will not download it again.

To manage distribution:

1. Select the Main server. The information in this

view shows which players are receiving planupdates, and their progress in downloading any

new or changed media files.

2. The default interval between updates is 10

minutes. If you want to make it check

immediately, click Synchronize Now. Then click

Send Now when prompted.




62

3. As media files are being downloaded, they will

appear in the list below and will be removed from

the list when they have been downloaded by all

the players that require them.




63

Monitoring Status

The Distribution view provides information about player

plan and media file distribution to players.

For each distribution server, you can see:

Sync Status – When plan updates have been

generated and players are in the process of receiving

them.

Received Plans – How many players have receivedupdated plans.

Transfer – The progress of media file distribution.

Remaining – How many media files are being

downloaded by players.

The Players list shows the update status and health of

each player.

For each player, you can see:

Last Heartbeat – how recently the player has reported

its status to Content Manager.




64

Plan – Whether the player has the latest plan or not.

Download Status – Whether the player has

downloaded all the files required by its plan.

The Player Health view shows a list of any problems

reported by your players.

To find out more about a problem, select it and click

Details in the title bar. This will show more information

about the problem, which players it occurred on, and

when.

If you believe the problem is already resolved, click the

Clear button. This removes the problem from the list,

but if it occurs again, It will reappear.

A live stream of player status can also be accessed from

the Network Activity tab.




65

Doing More with Content Manager

Congratulations, you have made your first channel. But

you have just scratched the surface of what can be

done.

For example:

Categories – Helps you organize and search your

media.

Media Metadata – Add data to media for dynamic

playback.

Smart Playlists – Select media for playlists based on

search criteria.

Approvals – Users can submit content for approval by

others.

Multi-frame Channels – Channels can have any

number of independent display areas.

Time Triggers – Schedule playlists for specific times of

the day.

Event Triggers – Interrupt playback with triggers from

external sources.

Non-scheduled Content – Send media files to players

for dynamic playback or future use.Non-PC Players – Scala supports media devices, photo

frames and more.

Player Metadata – Target players by location, type of

environment, etc.

Maintenance Jobs – Perform remote updates, install

files, reboot, etc.




66

Publish Locations – Automatically pull content files

from a remote source.

To learn more about these features as well as receive

support, services and training from Scala, refer to the

Other Resources section in the Preface of this guide.




67

Optional Components

The following are additional software applications sold in

conjunction with Content Manager. Contact your Scala

Sales Representative for more information.

Template Composer Module – Allows users to fill in

templates created in Designer.

Playback Audit Module – Generates reports on media

and player activity.

Broadcast Server – Adds distribution via Multicast-IP

over WAN or Satellite networks.

Bridge Server – Adds the ability to control non PC-

based players.




68

Getting Updates

A newer version of Content Manager may be available.

To find out, visit http://www.scala.com/updates.

There you can enter your Content Manager serial

number and click Submit.

Useful Tip: You can find your Content Manager serial

number by logging in as Administrator and going to

Settings/License Status.







69

Backup and Restore

Backing up your Content manager is highly

recommended. Refer to the Content Manager User

Guide for detailed instructions.




70

Troubleshooting

If your Player is not receiving new plans or is not playing

what it should be playing, below are some settings you

can check.

If the issues appear to be network-wide, start by

checking Content Manger. If they are isolated to one or

more players, check the players first (see steps below).

Content Manager

Check in Content Manager -> Settings -> LicenseStatus to see if the License file has been downloaded

and is current.

Check to see if the Content Manager and Player are

using the current Release. In Content Manager,

navigate to Settings -> Server Settings and select the

System Information tab. In the Player 5 Configuration,

select the Info tab.

On the Content Manager server, go to Start -> Settings

-> Control Panel. Double-click on Administrative

Tools, then Services.

Make sure the following services are running:

Apache Tomcat

PostgreSQL Database Server

Scala Transmission Server

Check the Content Manager and Transmission Server

Service IC.log file for errors. Shortcuts to the log folders

are in the Start Menu.

Try rebooting the Content Manager system.




71

Player

On the Player system, check to see if the Player

Transmission Client is running. This is indicated by an

icon in the Windows task bar.

Note: If the Player was installed with the option to make

the Transmission Client as a service, the icon will not be

there and you will need to check the Windows Services

console.

In the Player 5 Configuration tool, check to see if you

are able to connect to Content Manager, by Selectingthe “Refresh” button. If so, the Player should load the

Network name and no error message will appear.

You can also diagnose the network connection to

Content Manager outside of Player:

Open a web browser and see if you can connect

to: http://servername:8080/ContentManager Open a Command Prompt and try to Ping the

Content Manager server.

In a Command Prompt, try to Telnet to the server

using port 8080.

Check the Player’s IC.log for errors. (The shortcut to the

log folder is in the start menu).

Note: This is one of the most significant locations to

identify issues with your system. The most recent error

is at the bottom of the log file.

Players upload their log files to Content Manager, which

you can access by going to Player Properties and

clicking on the Logs tab. But if you have access to the

player directly, you can see the log immediately, insteadof waiting for it to be uploaded.








72

If you have additional questions, please contact your

Scala Sales and Support Partner or visit us on the web

at www.scala.com.

http://www.scala.com/






73

Scala End User License AgreementThis Softw are License Agreement (“Agreement”) is entered into betw een

Scala, Inc. (w hich, for purposes of this Agreement, shall be deemed to

include any majority ow ned subsidiary of Scala, Inc.) (“Scala”), and thepurchaser, licensee or user (“Licensee”) of Scala Software (as defined

below). The terms of this Agreement also apply to any Scala Software

Updates, and/or Softw are Maintenance (as each term is defined below) for

the Scala software, unless other terms accompany those items. If so, those

terms apply.

READ THIS LICENSE CAREFULLY. BY OPENING THE SCALA

SOFTWARE PRODUCT PACKAGING AND/OR USING THE SCALA

SOFTWARE, LICENSEE AGREES TO BE BOUND BY THE TERMS AND

CONDITIONS OF THIS AGREEMENT.

If Licensee does not agree to the terms of this Agreement prior to opening the

Scala Software packaging or installing the Scala Softw are, Licensee shall

cease using (or ref rain from commencing use of) the Scala Softw are, and

shall, as applicable, uninstall and/or permanently delete the Scala Software,

Documentation (and any copies thereof) f rom the computers or computer

system(s) on w hich the Scala Software has been loaded or stored, and return

the Scala Softw are and Documentation, all media on w hich it is stored, all

product packaging, and proof of payment to the Scala Partner (as defined

below) pursuant to such Scala Partner’s return policy. If Licensee does not

agree to the terms of this Agreement, and has acquired the Scala Softw areas part of a pre-conf igured computer system on w hich the Scala Softw are has

been installed, Licensee must either promptly cease using the Scala

Softw are, uninstall and/or permanently delete the Scala Sof tware and

Documentation (and any copies thereof) from the computer system(s) on

w hich the Scala Softw are has been preloaded, or return the pre-configured

system pursuant to the system vendor’s return policy.

1. DEFINITIONS.

1.1. “Commencement Date” means the ship date of the Scala Softw are

f rom Scala or a Scala Partner to the Licensee.

1.2. “Documentation” means the user guides, tutorials, printed

instructions, reference manuals, and other explanatory materials developed

by Scala that accompany or are stored on or in the Scala Software for use in

connection w ith the Scala Softw are.

1.3. “End User” means, as applicable, Licensee or any person or entity

(including, for the avoidance of doubt, any employee or agent of Licensee)

that uses the Scala Software.




74

1.4. “Object Code” means the form of Scala Softw are wherein computer

programs are assembled or compiled in magnetic or electronic binary form on

sof tware media, w hich are readable and usable by machines, but not

generally readable by humans w ithout reverse-assembly, reverse-compiling,

or reverse-engineering.

1.5. “Software Maintenance” means the provision of Software Updates.

1.6. “Scala Partner” means any Scala Certif ied Partner, reseller or

distr butor of Scala that sold or licensed the Scala Software to Licensee.

1.7. “Scala Softw are” means, as applicable, the Object Code form of

Scala Starter Kit, Scala Designer, Scala Player, Scala Content Manager,

Scala Broadcast Server, Scala Ad Manager, EX Modules, sof tware add-ons

or such other Scala software products or access licenses as may be identified

in a purchase order provided to Scala or a Scala Partner, and shall be

deemed to include the Documentation for such Scala Software, the license

keys, clip art, fonts and multimedia files included in such Scala Software, their

related software options, software extensions, software upgrades and

Softw are Updates, and Third Party Softw are integrated into such identified

products.

1.8. “Software Updates” means bug f ixes, documentation improvements

and feature additions, including all major (i.e., numbered) and minor (i.e.,

point) releases, w hen and if made available by Scala.

1.9. “Third Party Softw are” means sof tware, referred to asredistributable code that is licensed to Scala by third party licensors for

redistribution w ith the Scala Softw are. The redistributable code is the property

of Scala’s licensors, and protected under United States and international

copyright, trade secret or other proprietary rights laws, and international

treaties.

2. GRANT OF LICENSE RIGHTS.

2.1 License. Subject to the terms, restrictions and limitations set forth

herein, Scala hereby grants to Licensee a non-exclusive, non-transferable,

non-sublicensable license to use (and to permit its End Users to use) the

Object Code version of the Scala Softw are, including any Third Party

Softw are included therein or therew ith, along w ith any graphical, textual,

pictorial, audio or visual w orks or materials incorporated into or delivered w ith

the Scala Softw are, including the Documentation.

2.2 Term. This Agreement is eff ective as of the date at w hich Licensee

accepts the license terms as set forth above, and w ill continue unless

terminated as provided in Sections 7.3 or 8.

2.3. Scope of License and Use




75

A. Internal Use. Licensee may use the Scala Softw are and

Documentation only for its ow n internal use and only on one, single-user

computer. Licensee may internally transfer the Scala Software to a different,

single-user computer (a “Transferred Installation”), provided that the Scala

Softw are and any copies thereof are permanently uninstalled and/or deleted

from the computer from w hich the Scala Software is transferred.

B. Limitations. In connection w ith the creation, development or

management of content files, and/or the planning or scheduling of information

using Scala Softw are (including, but not limited to, media creation and/or

management, template message creation, metadata, schedules, layouts,

timetables, playlists, or triggers), Licensee may publish or transmit f iles for

playback (i) to one or more properly licensed individual Scala Players; (ii) to

an audio visual netw ork of screens showing identical content controlled by aproperly licensed individual Scala Player, and (iii) f or preview and approval

purposes over the w eb or other means. Notw ithstanding the above, Licensee

shall not directly or indirectly, use or cause to be used for playback content

f iles, plans, schedules or other information created, developed or managed

w ith Scala Software without also having properly licensed Scala Software for

the playback devices involved.

C. Copies. Licensee may make one (1) copy of the Scala Software

and one (1) copy of the related Documentation for archival or back-up

purposes, only.

D. Third Party Softw are. The license granted hereunder includes the

right of Licensee to use the Third Party Softw are in Object Code form, solely

in connection w ith the authorized operation and use of the Scala Softw are in

conformance with the terms and conditions of this Agreement. For the

avoidance of doubt, Licensee may not decouple, disassemble or otherw ise

separate the Third Party Sof tw are from the Scala Softw are or use the Third

Party Softw are except in connection w ith the use and operation of the Scala

Softw are as permitted hereunder.

E. Restrictions. The Scala Softw are is licensed, not sold. This Agreement only gives you some rights to use the Scala Softw are. Scala

reserves all other rights. Unless and solely to the extent otherw ise permitted

under applicable law , you may use the Scala Softw are only as expressly

permitted in this Agreement. Except as expressly permitted under applicable

law, or as otherw ise agreed to in w riting by Scala, Licensee shall not, and

shall not permit any End User to: (i) w ork around any technical limitations in

the Scala Softw are; (ii) publish the Scala Software for others to copy; (iii)

make more copies of the Scala Softw are than authorized under this

Agreement ; (iv) sell, lease, rent, redistribute, assign, sublicense, or transfer

the Scala Softw are and/or Third Party Softw are; (v) reproduce, decompile,reverse engineer or disassemble the Scala Softw are and/or Third Party




76

Softw are; (vi) offer the use of the Scala Softw are to third parties as an

application service provider, service bureau or remote-hosted service; or (vii)

deliver, export, transfer or otherwise distribute the Scala Softw are acquired

hereunder to, or use the Scala Software acquired hereunder in, a country

other than the country in w hich the Scala Software was purchased (including,

for the avoidance of doubt, in connection w ith a Transferred Installation).

3. LICENSE AND OTHER FEES. Licensee agrees to be bound by

and pay the license fee(s) set forth in the Scala Softw are price list in effect as

of the date of purchase. License fees for Scala Software and maintenance

fees for Software Maintenance may be updated and changed at any time.

3.1 Softw are Maintenance Coverage. Where Software Maintenance is

offered upon separate purchase terms from the Scala Sof tware, the Scala

Softw are products are sold w ith an initial period of Softw are Maintenance

coverage included in the price of the product. Such Initial Maintenance Term

is def ined as follow s: With the exception of Player and EX Module Products,

the initial maintenance term of software supplied under this Agreement

commences upon delivery of the product and remains in force for one year.

The initial maintenance term for Player and Player EX Module Products w ill

commence upon delivery of the product and shall remain in force until the

anniversary of the Content Manager renew al date that such sof tware

products are associated with, regardless of the purchase date of the Player or

Player EX Module Products. The initial maintenance term for other EX

Module Products w ill commence upon delivery of the product and shall

remain in force until the anniversary of the renewal date of the product that

such sof tware products are associated with, regardless of the purchase date

of the EX Module Product. During the Initial Maintenance Term, Licensee

shall be entitled to Softw are Updates if and w hen made available by Scala.

All use of Scala Softw are provided pursuant to Software Maintenance

coverage shall be subject to the terms of this Agreement. Licensee may elect

to continue Softw are Maintenance beyond the Initial Maintenance Term,

subject to availability, upon payment to Scala (or, as applicable, a Scala

Partner) of the Scala annual maintenance fee in effect at the time of renew al.3.2 Taxes and Duties. Prices to Licensee do not include taxes, duties,

tariff s, handling fees, or other such assessments of any nature. Whenever

imposed, such assessments are payable by Licensee. Income or other taxes

that are required to be paid or w ithheld by Licensee or Scala under the law s

of jurisdictions other than the United States, in connection w ith the license

and other fees paid by Licensee hereunder, are the sole obligation of

Licensee and shall be exclusive of the license and other fees paid by

Licensee.

3.3 Other Services. Licensee acknowledges that any additionalservices offered by Scala, such as installation, customization or professional




77

services, are not provided under this Agreement, and any such services to be

provided by Scala (or, as applicable, a Scala Partner) shall be subject to the

mutual agreement of the parties, the terms and conditions for w hich shall be

set forth in a separate agreement.

4. CONFIDENTIAL INFORMATION, TITLE AND COPYRIGHTS.

4.1 Licensee acknow ledges that the Scala Software, Documentation,

Softw are Updates, enhancements, modifications, additions, new releases of

or to the Scala Software contain confidential information of, are trade secrets

of, and are proprietary to Scala and its licensors and that title to such

materials is and shall remain in Scala and its licensors, as the case may be.

Licensee shall maintain in strict confidence the Scala confidential information,

but, at a minimum, to take those precautions that it utilizes to protect its ow n

conf idential information. Licensee shall have no obligation of confidentiality

w ith respect to information that (i) at the time of disclosure is in or becomes

available to the public through no breach of this Agreement on the part of the

Licensee; (ii) w as lawfully in Licensee’s possession prior to receipt from

Scala; (iii) is received independently from a third party free to law fully disclose

such confidential information to Licensee and w ho does not ow e an obligation

to Scala w ith respect to confidential information; (iv) Licensee independently

develops w ithout the benefit of any confidential information disclosed

hereunder or (v) is required to be disclosed by a government agency;

provided that the Licensee w ill use best efforts to minimize such disclosure

and w ill notify Scala promptly of any such demand, order or judgment in order

to permit Scala to seek an appropriate protective order.

4.2 All applicable rights to patents, copyrights, trademarks and trade

secrets in the Scala Softw are and other proprietary materials are and shall

remain in Scala and its licensors. Licensee shall not assert any right, title or

interest in the Scala Softw are or other materials provided to Licensee under

this Agreement, except for the limited license rights expressly granted to

Licensee hereunder.

4.3 Licensee shall not obscure or remove any copyright or other

proprietary notice or legend contained on or included in the Scala Softw are

and shall reproduce all such information on all copies made hereunder.

Licensee shall not, directly or indirectly, disclose or distribute any technical

information of Scala provided w ith or in the Scala Softw are without the prior

w ritten consent of Scala, which consent may be w ithheld at Scala’s sole

discretion.

5. LIMITED WARRANTIES.




78

5.1 Media and Documentation. Scala w arrants that if the media or

Documentation is in a damaged or physically defective condition at the time

the Scala Softw are is delivered to Licensee, and if such media or

Documentation is returned to Scala w ithin thirty (30) days of the effective date

of this Agreement, Scala w ill provide Licensee w ith a replacement at no

charge.

5.2 Softw are Limited Warranty and Remedy.

A. Provided that Licensee is not in breach of any of its obligations

under this Agreement, and in addition to the w arranty set forth in Section 5.1,

Scala w arrants for a period of thirty (30) days from the Commencement Date

(“Warranty Period”), that the software will substantially conform to the

Documentation provided by Scala w ith the Scala Softw are. Licensee’s sole

remedy and Scala’s and Scala Partner’s sole obligation under this Agreement

for breach of this w arranty is, at Scala’s sole option, (i) the remedy of thenonconformity or (ii) the authorization of a refund for the price paid for the

media and or Scala Softw are by Scala or the Scala Partner from w hich the

Scala Software was originally obtained. Any request for the above remedies

must be made w ithin the Warranty Period and proof of purchase (i.e., copy of

the invoice or receipt) is required to be presented to Scala. In the event of a

refund, this Agreement w ill immediately terminate w ithout further notice, and

Licensee w ill have no further rights or license to use Scala Software or

Documentation.

B. Any replacement sof tware or media w ill be w arranted for the

remainder of the original Warranty Period or for an additional thirty (30) days

w hichever is longer.

C. This limited w arranty is void if nonconformance of the Scala

Softw are results from or is related to the (i) improper installation or operation

of the Scala Softw are by or on behalf of the Licensee, (ii) failure of Licensee’s

hardw are or non-Scala sof tware, (iii) incompatbility of such hardw are and

non-Scala sof tware systems with Scala Software, (iv) alteration, modification

or unauthorized integration of Scala Softw are by or on behalf of Licensee, or

(v) accident, abuse or misapplication of Scala Software.

D. If the Scala Softw are is provided as a trial or evaluation version, the

grant of the license to use the Softw are shall be on an “AS IS” basis and

subject to the express limitations of the trial. Unless Licensee shall have

entered into a separate w ritten license agreement prior to the expiration or

termination of the trial period, Licensee agrees to cease all use of the Scala

Softw are provided on a trial or evaluation basis and to return such Scala

Softw are, or to return any license keys and destroy or permanently delete any

and all copies of such Scala Softw are.

5.3 Disclaimer of Warranties. SCALA AND ITS LICENSORS MAKE

NO WARRANTY, REPRESENTATION OR PROMISE EXCEPT AS




79

SPECIFICALLY SET FORTH IN THIS AGREEMENT. TO THE FULLEST

EXTENT PERMITTED BY LAW, SCALA AND ITS LICENSORS DISCLAIM

AND EXCLUDE ANY AND ALL OTHER WARRANTIES, INCLUDING

WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF

MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR

RESULTS. SCALA AND ITS LICENSORS DO NOT WARRANT THAT THE

SCALA SOFTWARE OR DOCUMENTATION WILL SATISFY LICENSEE’S

REQUIREMENTS; THAT THE SCALA SOFTWARE AND

DOCUMENTATION ARE WITHOUT DEFECT OR ERROR; OR THAT THE

OPERATION OF THE SCALA SOFTWARE WILL BE UNINTERRUPTED.

TO THE MAXIMUM EXTENT PERMITTED UNDER THE LAW, THE UN

CONVENTION FOR THE SALE OF GOODS AND THE UNIFORM

COMMERCIAL CODE DO NOT APPLY TO THIS LICENSE AGREEMENT.

6. LIMITATION OF LIABILITY.

6.1 IN NO EVENT SHALL SCALA OR ITS LICENSORS BE LIABLE

FOR ANY SPECIAL, INCIDENTAL, INDIRECT, PUNITIVE OR

CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, WITHOUT

LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS

INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER

PECUNIARY LOSS). REGARDLESS OF WHETHER SCALA HAS BEEN

ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TO THE MAXIMUM

EXTENT PERMITTED BY LAW, SCALA’S AGGREGATE LIABILITY

ARISING FROM OR RELATING TO THIS LICENSE OR THE SCALA

SOFTWARE AND DOCUMENTATION IS LIMITED TO THE AMOUNT

ACTUALLY PAID FOR THE LICENSE. SOME JURISDICTIONS DO NOT

ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR

CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION OR

EXCLUSION MAY NOT APPLY.

7. INDEMNIFICATION.

7.1 Scala’s Obligation. Subject to the Licensee indemnification set

forth at Section 7.2 and the restrictions and limitations set forth herein, Scala

shall indemnify and hold harmless Licensee, its off icers, directors and

employees from and against any costs or demands aw arded against

Licensee by a court of competent jurisdiction pursuant to a f inal judgment as

a result of a claim or action by a third party against Licensee that the Scala

Softw are or Documentation infringes a registered copyright, trademark, valid

patent or other intellectual property right of a third party in North America,

European Economic Area or Japan. The foregoing indemnity is conditioned

on Licensee (i) promptly notifying Scala of such claim; (ii) permitting Scala to

control the response thereto and the defense thereof , including any




80

agreement relating to the settlement thereof, and (iii) assisting and

cooperating w ith Scala, at Scala’s expense, in the defense or settlement

thereof. Licensee may participate, at its ow n expense, in such defense

directly or through counsel of its choice on a monitoring, non-controlling

basis. Scala shall obtain Licensee’s prior written consent to any compromise

or settlement of any c laim w hich would require an admission of liability on the

part of Licensee or w hich w ould subject Licensee to any injunction or other

equitable relief. Notw ithstanding the foregoing, in no event shall Scala or its

licensors be liable to indemnify, defend, settle or hold Licensee harmless f rom

and against any or all claims w hich allege infringement of intellectual property

that reads upon or is infringed by a generally recognized audio, video,

technology or patent standard, including w ithout limitation MPEG-1, MPEG-2,

MPEG-4, JPEG, DV, Flash, VC-1, AAC, AC-3, DVCPRO or AVS (each

including all profiles, options, parts or levels);

7.2 Scala shall have no obligation under Section 7.1, and otherw ise will

have no liability for, any claim of infringement caused or alleged to be caused

by: (i) the use or combination of the Scala Softw are with non-Scala software,

hardw are, data, or content, including but not limited to software, hardware,

data, or content of Licensee; (ii) infringement that w ould have been avoided

w ithout the use or combination of the Scala Softw are with other non-Scala

sof tware, hardware, content, or data; (iii) the presence of any alteration or

modification of the Scala Softw are by Licensee or any third party acting on

Licensee's behalf; or (iv) the Licensee's continuing the allegedly infringing

activity after being notified thereof or after being informed and provided w ith

modifications that w ould have avoided the alleged infringement.

7.3 In the event that a claim of infringement of a valid North American,

European Economic Area or Japanese software patent or copyright is made

against Scala or Licensee or if Scala reasonably believes that such a claim

w ill be made, Scala, at its option and in lieu of indemnification, may (a)

procure for Licensee the right to use the Scala Softw are without patent or

copyright infringement; (b) modify the Scala Softw are to make it non-

infringing; (c) replace the Scala Softw are with substantially equivalent

sof tware that is non-infringing; or (d) direct Licensee to cease use of the

Scala Software, and refund to Licensee a percentage of the aggregate feesreceived for such Scala Software that are the subject of such a claim, based

on a five (5) year straight line depreciation

7.4 The foregoing Sections 7.1-7.3 set forth the exclusive remedy and

entire liability and obligation of Scala w ith respect to third party claims against

Licensee alleging intellectual property infringement or misappropriation.

7.5 Licensee Obligation. Except for the infringement claims set forth in

Section 7.1, Licensee shall indemnify, defend and hold Scala, its directors,

officers, agents and employees harmless f rom any claims, demands, or

causes of action whatsoever by a third party against Scala arising as a result




81

of Licensee’s use or operation of the Scala Software. For the avoidance of

doubt, and w ithout limiting the scope of the immediately preceding sentence,

Licensee shall indemnify, defend and hold Scala, its directors, of ficers, agents

and employees harmless from any third party claims, demands, or causes of

action whatsoever arising from or related to the display, broadcast,

reproduction, performance or other use or distr bution of audio, visual,

graphical and textual information developed by or on behalf of Licensee and

not included in the Scala Softw are.

8. TERMINATION.

8.1 By Licensee. Licensee may terminate this Agreement at any time

w ithout notice to Scala. The license fee is not refundable and Scala w ill have

no obligation to refund any amounts paid by Licensee under this Agreement

upon its termination (except for any right of refund as set forth in Sections 5

and 7.3).

8.2 Scala. Scala may terminate this Agreement and all licenses

granted hereunder upon thirty (30) days prior w ritten notice if Licensee fails to

comply w ith any of the terms and conditions of this Agreement or any

Schedule to this Agreement, and such noncompliance is not cured w ithin

such thirty (30) day period.

8.3 Return of Softw are. Upon any termination of this Agreement,

Licensee must cease all use of the Scala Softw are, and return to Scala allcopies of the Scala Softw are, including license keys, together w ith the

Documentation, or shall return all license keys and certify to Scala’s

reasonable satisfaction the destruction or permanent deletion of all copies of

the Scala Softw are and Documentation from its computer systems.

9. GENERAL.

9.1 Audit Rights. Scala shall have the right reasonably to audit the

deployment and use of the Scala Softw are by Licensee, including w ithout

limitation Licensee’s conformance with the provisions of Section 3 herein.

Licensee agrees to cooperate w ith Scala’s reasonable request for access to

Licensee’s computer systems to ensure Licensee’s adherence with the

license terms hereunder.

9.2 Purchase in Canada. If Licensee acquired this sof tware in Canada,

Licensee agrees to the follow ing: The parties hereto have expressly required

that the present Agreement and any exhibits hereto be draw n up in the

English language. / Les parties aux présentes ont expressément exigé que la

présente convention et ses Annexes soient rédigées en langue anglaise.




82

9.3 Notices. Any notice required or permitted to be given by Licensee

hereunder shall be in w riting and shall be deemed to have been duly given (i)

upon hand delivery, (ii) on the third day follow ing delivery to the postal service

as certified mail, return receipt requested and postage prepaid, or (iii) on the

f irst day follow ing delivery to a recognized overnight courier service, fee

prepaid and return receipt or other conf irmation of delivery requested. Any

such notice shall be delivered or sent to Scala at the address as set forth

below, or to such other address as Scala may designate from time to time.

Scala, Inc., 350 Eagleview Boulevard, Suite 350, Exton, PA 19341, USA.

NOTICE ABOUT THE MPEG-2 VISUAL STANDARD. This sof tware may

include MPEG-2 visual decoding technology. MPEG LA, L.L.C. requires this

notice: USE OF THIS PRODUCT IN ANY MANNER THAT COMPLIES WITH

THE MPEG 2 VISUAL STANDARD IS PROHIBITED, EXCEPT FOR USE

DIRECTLY RELATED TO (A) DATA OR INFORMATION (i) GENERATED BY

AND OBTAINED WITHOUT CHARGE FROM A CONSUMER NOT

THEREBY ENGAGED IN A BUSINESS ENTERPRISE, AND (ii) FOR

PERSONAL USE ONLY; AND (B) OTHER USES SPECIFICALLY AND

SEPARATELY LICENSED BY MPEG LA, L.L.C. If you have questions about

the MPEG-2 visual standard, please contact MPEG LA, L.L.C., 250 Steele

Street, Suite 300, Denver, Colorado 80206; http://www.mpegla.com.

NOTICE ABOUT THE AVC VISUAL STANDARD. This software may include

AVC visual decoding technology. MPEG LA, L.L.C. requires this notice: THIS

PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO

LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USESIN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE

VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”)

AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A

CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS

OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC

VIDEO. NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY

OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED FROM

MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM

9.4 Governing Law . A. United States Sales. If you acquired the Scala Softw are in the United

States, Pennsylvania state law governs the interpretation of this agreement

and applies to claims for breach of it, regardless of conflict of laws principles.

B. Sales Outside the United States. If you acquired the Scala Softw are in any

other country outside the United States, the law s of the country of the

majority-ow ned Scala subsidiary that sold the Scala Software to you applies,

regardless of such country’s conflicts of law provisions.

9.5 Legal Effect. This Agreement describes certain legal rights. You

may have other rights under the law s of your state or country. You may also




83

have rights w ith respect to the party f rom w hom you acquired the Scala

Softw are. This Agreement does not change your rights under the law s of your

state or country if the law s of your state or country do not permit it to do so.

9.6 U.S. Government Restricted Rights Legend. The Scala Softw are,

hardw are, and Documentation provided under this Agreement bear restrictedrights. Use, duplication, or disclosure by the U.S. Government is subject to

restrictions as set forth in subparagraph (c)(1)(ii) of the rights in technical data

and computer software clause at DFARS 252.227-7013 or subparagraphs

(c)(1) and (2) of the Commercial Computer Softw are Restricted Rights clause

at 48 CFR 52.277-19, as applicable. Scala, Inc., 350 Eagleview Boulevard,

Suite 350; Exton, PA 19341 USA.

9.7 Assignment. Neither party may assign any rights, duties,

obligations or privileges under this Agreement w ithout the prior w ritten

consent of the other party. A change of control or ownership shall not bedeemed to be an assignment under this Section so long as the new ow ner

has expressly assumed in w riting all of the duties and obligations of the

assignor and further provided, that Licensee shall remain liable and

responsible to Scala (and its licensors) for the performance and observance

of all such duties and obligations.

9.8 Severability. Should any part or provision of this Agreement be

held unenforceable or in conflict w ith the law of any jurisdiction, the validity of

the remaining parts or provisions shall not be affected by such holding.

9.9 Limitation on Effect of Waiver. Failure on the part of Scala toexercise, or Scala’s delay in exercising, any of Scala’s rights hereunder shall

not be construed as a w aiver or w aiver of other breaches of this Agreement.

Any single or partial exercise by a party of any right shall not preclude any

other or future exercise thereof or the exercise of any other right in the

Agreement.

9.10 Entire Agreement. This Agreement contains the entire

understanding of the parties w ith respect to the transactions contemplated

and supersedes any prior agreements or understandings among the parties

w ith respect to the subject matter hereof. This Agreement may be amendedonly by a w riting that refers to this Agreement and is signed by both parties.

9.11 Export Law Assurances. Licensee acknowledges that the Scala

Softw are included herewith is subject to restrictions and controls imposed

under the U.S. Export Administration Act and Canadian Exportation Law s.

Licensee must comply w ith all domestic and international export law s and

regulations that apply to the software. These law s include restrictions on

destinations, end users and end use. Licensee hereby expressly agrees to

defend, hold harmless and indemnify Scala, its directors, officers, and

employees, from any claim, suit or dispute alleging that Licensee has




exported the Scala Softw are in violation of any domestic or international

export law s.

9.12 Construction. The headings in this Agreement are for convenience

of the parties only. They do not constitute a portion of this Agreement and

shall not be used in interpreting the construction of this Agreement.

9.13 Third Party Beneficiary. Licensee hereby agrees that the licensors

of Third Party Softw are shall be considered third party beneficiaries of this

Agreement and shall be entitled to bring a direct action against Licensee in

the event of breach of any applicable provisions of this Agreement, pursuant

to the terms and conditions of this Agreement.

9.14 Force Majeure. Neither party shall be in default if failure to

perform any obligation hereunder is caused solely by unforeseen supervening

conditions beyond that party ’s reasonable control, w hich could not have been

prevented by the non-performing party’s reasonable precautions,

commercially accepted processes or substitute services, including acts of

God, civil disturbances, strikes and labor disputes.

9.15 Negation of Agency and Similar Relationships. Nothing contained

in this Agreement shall be deemed to create an agency, joint venture or

partnership relationship.

content manager 5 getting started guide

Documents