1. System Manual . . . . . . . ....

Transcription

http://docs.scala.com/display/CM1003/
1. System Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Content Manager Server Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1.1 Physical Server Hardware Sizing Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1.2 Virtual Server Hardware Sizing Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2.1 Advanced Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.3 A Quick Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4 Home Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Playlists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3 Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 Players . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2 Create Multiple Players . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.3 Player Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.4 Maintenance Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.5 Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.1 Playback Audit Parser Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.3 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.4 Database Configuration (Reports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.1 View API Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.2 Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.3 Hosted Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.4 License Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.5 Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.6 Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.6.1 HTTPS Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.6.2 Using LDAP and Active Directory to Administer Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.1 User Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.2 User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.3 Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.4 Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.5 Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.6 Media Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.7 Player Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.8 Player Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.9 Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.10 Publish Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.11 Framesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Username Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.1 Personal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.2 Switch Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.3 Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2
4
4
6
7
12
21
22
22
23
28
30
30
35
36
38
38
39
40
42
44
46
46
49
53
53
54
54
55
55
57
57
58
59
61
63
64
64
65
65
67
67
68
69
70
71
71
72
72
73
73
73
Page 1
Scala -- Content Manager 10.3 Documentation
System Manual
Welcome to the Scala Enterprise Content Manager System Manual
Please read the Getting Started section prior to installation as well as update notes pertaining to this product.
We know you are anxious to get started and install the software, however this section contains information and instructions required for a
successful installation.
It is important for users to read through this guide BEFORE you install the software so you can understand the options, settings and
configurations of the program.
In this Guide
These topics will help you install and learn the basics about Content Manager:
Overview of Scala Enterprise Content Manager
Planning your installation
The Scala Workflow
Installing Content Manager
Setting up Users, Roles and Workgroups
Adding Players
Creating Channels, Playlists and Schedules
Optional Components
Troubleshooting
Download:
If you would like a PDF of this Content Manager System Manual captured as of July 16, 2014, please click here.
Getting Started
Introducing Content Manager
Scala Content Manager is a powerful application for digital signage content distribution, scheduling and management. It 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. The diagram below is an illustration of the process.
How Do People Use Scala Enterprise Software?
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.
Copyright © 2014 Scala - All logos and trademarks are the property of the respective trademark owners
Page 2
A network administrator uses Content Manager to manage and monitor Players, ensuring content is playing properly.
Planning Your Installation
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.
It is important to plan ahead before configuring and deploying your network. A successful deployment of a network at any size starts at the
beginning. Take into consideration the initial network size and what it might be in the future. Also, take into consideration the size of the content,
the frequency of change of this content and the number of players. Make sure to do the bandwidth calculations to ensure your network can handle
the increased traffic load.
Content Manager can be installed on either physical or virtual server environments. The recommended server sizing guides for deployments in
these environments can be found here.
When deploying larger networks, automation techniques are crucial - including the ingestion of content, the use of smart playlists and possibly
extending the functionality/workflow by using the extensive Web Services API's that come with Scala Enterprise Content Manager.
Go through this checklist to make sure you are ready to install and configure Content Manager.
Make sure you have the USB dongle.
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 other database types, as well as a separate PostgreSQL server. If you plan to use
an existing database server, make sure you have the necessary hostname and credentials to access the database.
You will need to know the Content Manager server hostname 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:
Select the database you are using. If you will be installing the PostgreSQL server, you will be asked for a username 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 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 download a license file and copy it to the Content
Manager server.
After installation you will need to:
Create user accounts.
Add players.
Create channels
Upload and schedule content to play.
Useful Configuration and Setup Tips
1. Before installing Scala Enterprise Content Manager, choose hardware that matches your network size. Please consult the Specifications
Guides.
2. Configure Content Manager to use one port for player traffic. Use a different port for user traffic.
Tune these parameters to match your needs:
Heartbeat rate
Player plan polling interval
Plan status interval
Synchronization settings
Turn off playback logs if you don’t need them
Consider the following for scalability of your network:
1. Run your database on a dedicated machine. Choose your hardware carefully.
2. For reliability and performance, you should consider setting up your database in HA (High Availability) configuration or Master-Master
replication.
3. If using a MySQL database, there are lots of tips and trick available on the internet.
Google the following topics:
a. MySQL master master
b. MySQL HA
c. MySQL scalability
4. Do regular backup and maintenance of your database. This is extremely important.
5. Add a cache server to your network to take the load off Content Manager. Doing so will greatly improve your scalability. Choose a
Page 3
5.
caching strategy that fits you:
a. Central Cache
b. Regional Caches
c. Local Caches
6. Use a dedicated server for caching. Linux is preferred.
Squid-Cache is tested and known to work. Relevant search keywords:
Reverse proxy
Web accelerator
Large Network Deployment
Deploying a large network (100+ players) can be difficult, labor-intensive work. Each player should have local content. Individually created
playlists for each player will not work, but you still want local content on your players.
The answer is player metadata and playlist conditions. Entering metadata for each player, even if you only have to do it once, can be too much
work.
Player metadata can change over time so you need to do regular maintenance. What is the solution? Integrate and automate:
Content Manager makes it possible for you to integrate directly using Web Services APIs
You can link Content Manager to existing Customer Relationship Management (CRM) systems that store metadata.
It lets you automatically create and maintain correct metadata on all your players with little or no manual labor.
Web Services also lets you create and update playlists automatically.
Makes local content on each player easy at any network size.
Content Manager Server Specifications
Content Manager networks work best if certain criteria are met. This page contains link to our document of detailed specifications, which can be
found here:
Physical Server Hardware Sizing Guide
Virtual Server Hardware Sizing Guide
Physical Server Hardware Sizing Guide
Note for Large Networks:
Network-specific design consultation required for deployments with more than 1,000 Players or with large data transfers
Network Size
Small
Medium
Large
<50 Players, less than 1.5
GB/hour of maximum total
network Content updates.
<500 Players, less than 15
Page 4
Minimum Storage
A separate, dedicated, Operating
System Partition of at least
40GB.
System & Log file Storage
Volume of at least 80GB.
A separate, dedicated, Data
Partition of 40GB, or larger, (or:
at least 3X the estimated
maximum amount of total
content to "active on the player
network" at any one time!)
Storage, (Database & Media), of
80GB, or larger, (or: at least 3X
the estimated maximum amount
of total content to "active on the
player network" at any one time!)
Storage partitions should be
implemented on a RAID 1+0,
RAID-6, or RAID-6+0 arrays--a
minimum of four physical storage
devices comprising the two
logical RAID-volumes.
["Software RAID" is not
considered acceptable for
Content Managers with more
than 20 Players.]
A separate Operating System
storage volume, of at least
80GB, which also contains a
partition for the CM
Application/Support Services Log
Files; A separate, dedicated,
Database storage volume of at
least 40GB; A separate
Media-Data storage volume, of
player network" at any one
time!), and which also has a
40GB partition for placement of
the database
“Write-Ahead-Logs/TransactionLogs”
SSD's are strongly encouraged
for the Database volume!
SSD-caching of underlying HDD
RAID-volumes is encouraged!
Storage volumes should be
implemented as RAID-1, 1+0,
RAID-6, or RAID-6+0, arrays.
considered acceptable.]
For a small network, "RAID" is
not a requirement. [it is
encouraged]
The partitions should be
implemented on a RAID-1, 1+0,
or RAID-6, storage volume.
"Software RAID", as
implemented on Intel "RST"
Chipsets, is acceptable for
configurations of RAID-1, or
RAID-1+0, on smaller, < 20,
Player networks.
However: "Software RAID-5" is
_strongly_ discouraged!
Recommended Operating
Systems
DAS: Actual "HW-RAID" from
vendors such as HP
(SmartArray) / DELL (PERC)
/LSI (MegaRAID) /PMC-Adaptec
is required. A minimum of four
physical storage devices, should
be implemented for at least two
logical RAID-storage-volumes
with three partitions each:
[“OperatingSystem” +
“DB-Transaction-Logs/WAL's” +
“Application-Logs”];
[“Temp-Swap"
+"DatabaseTables” +
"Media-Content”]
DAS: Actual "HW-RAID", or
SAN, from vendors such as
EMC, UNISYS, NetApp, HP,
IBM, DELL, LSI, or
PMC-Adaptec is required. A
minimum of eight(HDD) or
six(SSD) storage devices, should
be implemented for at least three
RAID-storage-volumes with two
partitions each:
“Application-Logs"];
["DatabaseTables” +
Temp-Swap"]; ["Media-Content”
+ “DB-Transaction-Logs/WAL's"]
DAS: Actual "HW-RAID", from
vendors such as HP
(SmartArray) /DELL (PERC) /LSI
(MegaRAID) /PMC-Adaptec, is
encouraged.
If SAN: Two LUN's should be
implemented. Example: one
RAID-1 and one RAID-10, six
HDD storage devices, (or four
SSD's for two RAID-1 volumes)
with the various partitions
allocated to the storage volumes
as per the DAS example.
If SAN: At least three LUN's
should be implemented on an
array with a minimum of eight
storage devices,(if HDD—six in
RAID-1 pairs if SSD), with the six
suggested partitions allocated as
per the DAS example.]
Windows Web Server
2008R2sp1(64-bit);
Windows Web Server
2008R2sp1(64-bit);
Windows Web Server
2008R2sp1(64-bit);
Windows Server
2008R2sp1(64-bit);
Windows Server
2008R2sp1(64-bit);
Windows Server
2008R2sp1(64-bit);
Windows 7sp1 Professional/
Enterprise /Ultimate x64.
Page 5
Minimum Processor Type:
Intel Core-i5 2400S or better;
Intel Core-i7 2600K or better;
AMD FX-63##; AMD FX-83##;
AMD Opteron 4334, 4340, 4376,
4386, 43GK HE;
AMD Opteron 4334, 4340, 4376,
4386, 43GK HE;
Quad- or Hex- core Intel XEON
CPU from the following product
series: E3-####, E5-####, or
better. Hyper Threading should
be disabled when < 10MB of L3
cache!
AMD Opteron 6344 ir better.
System Memory: ...the OS is
64-bit:
6GB+, Dual-Bank,
[DDR3-1333(PC3-10600)/1600(
PC3-12800)], or faster.
8GB+, Dual-Bank,
[DDR3-1333(PC3-10600)/1600(
PC3-12800)], or faster. ECC
memory strongly encouraged!
12GB+, Triple or Quad-Bank,
[DDR3-1333(PC3-10600)/1600(
PC3-12800)] or faster. ECC
memory strongly encouraged!
Network Adapter:
Any stable, 100Mbps or faster,
Ethernet PHY/NIC with
WHQL-certified device drivers.
Any stable, 1Gbps or faster,
A "Server-Class" NIC with at
least partial TCP-Offload
Engine(TOE), (or Intel IOAT),
functionality, 1Gbps or faster,
[TSO (TCP Segmentation
Offload) and LRO (Large
Receive Offload)]
Virtual Server Hardware Sizing Guide
Note for Large Networks:
Network-specific design consultation required for deployments with more than 1,000 Players or with large data transfers
Small
Medium
Large
Network Size
<50 Players, less than 1.5
500 Players, less than 15
Minimum Storage
A single Virtual Hard Disk drive
stored on a physical volume
capable of delivering an average
of 400, (4KB Random), IOPS to
the vmCM instance!
Two Virtual Hard Disk drives
stored on a independent physical
storage volumes capable of
delivering an average of 600,
(4KB Random), IOPS to the
vmCM instance!
A separate Operating System
storage volume, of at least
80GB, which also contains a
partition for the CM
Application/Support Services Log
Files; A separate, dedicated,
Database storage volume of at
least 40GB; A separate
Media-Data storage volume, of
player network" at any one
time!), and which also has a
40GB partition for placement of
the database
“Write-Ahead-Logs/TransactionLogs”
A dedicated Operating System
Partition of at least 40GB. A
dedicated Data Partition of
40GB, or larger.
(or: at least 3X the estimated
maximum amount of total
content to "active on the player
network" at any one time!)
System & Log file Storage
Volume of at least 80GB.
Storage, (Database & Media), of
player network" at any one time!)
If HDD: Storage partitions should
be implemented on a RAID 1+0,
RAID-6, or RAID-6+0 arrays--a
minimum of four storage devices
comprising the RAID-volumes.
If SSD: Two devices
implementing RAID-1 can
provide for adequate IOPS and
redundancy!
SSD's are strongly encouraged
for the Database volume!
SSD-caching of underlying HDD
RAID-volumes is encouraged!
Storage volumes should be
implemented as RAID-1, 1+0,
RAID-6, or RAID-6+0, arrays.
considered acceptable.]
Page 6
considered acceptable.] The
Hosting Virtual Machine
HyperVisor—DAS:
considered acceptable.] The
Hosting Virtual Machine
HyperVisor—DAS:
Actual "HW-RAID", from vendors
such as HP (SmartArray) /DELL
(PERC) /LSI (MegaRAID)
/PMC-Adaptec, is required.
Actual "HW-RAID" from vendors
such as HP (SmartArray) / DELL
(PERC) /LSI (MegaRAID)
/PMC-Adaptec is required. A
minimum of four physical storage
devices, should be implemented
for at least two
RAID-storage-volumes with three
partitions each:
For a Virtual-Machine Host, a
“HyperVisor”, HARDWARE RAID
functionality is considered
essential!
The Hosting Virtual Machine
HyperVisor—DAS: Actual
"HW-RAID", or SAN, from
vendors such as EMC, UNISYS,
NetApp, HP, IBM, DELL, LSI, or
PMC-Adaptec is required. A
minimum of eight storage
devices, should be implemented
for at least three RAID-storagevolumes with two partitions each:
“Application-Logs"];
["DatabaseTables” +
Temp-Swap"]; ["Media-Content”
+ “DB-Transaction-Logs/WAL's"].
The virtual disks should be
implemented on a RAID-1, 1+0,
storage volumes--"RAID-5" is
_strongly_ discouraged!.
“DB-Transaction-Logs/WAL's” +
“Application-Logs”];
[“Temp-Swap"
+"DatabaseTables” +
"Media-Content”]
If SAN: One LUN should be
implemented across at least two
storage devices.
If SAN: Two LUN's should be
implemented. Example: one
RAID-1(two-drives) and one
RAID-10(four-drives), six HDD
storage devices, (or four SSD for
two RAID-1) with the partitions
allocated to the storage volumes
as per the DAS example.
If SAN: At least three LUN's
should be implemented on an
array with a minimum of eight
storage devices,(if HDD—six in
RAID-1 if SSD), with the six
suggested partitions allocated as
per the DAS example.]
Recommended Guest Operating
Systems
Windows Web Server
2008R2sp1(64-bit); Windows
Server 2008R2sp1(64-bit);
Windows 7sp1 Professional/
Enterprise /Ultimate x64.
Windows Web Server
Windows Web Server
Minimum Hyper Visor/Host
Processor Type:
Two vCPU's from a HyperVisor
host with an:
AMD Opteron 4334, 4340, 4376,
4386, 43GK HE;
Four vCPU's from a HyperVisor
host with an:
AMD Opteron 4334, 4340, 4376,
4386, 43GK HE;
Four vCPU's from a HyperVisor
host with at least an:
Three Virtual Hard Disk drives
stored on a independent physical
storage volumes capable of
delivering an average of 800,
(4KB Random), IOPS to the
vmCM instance!
Intel Quad- or Hex- core Intel
XEON CPU from the following
product series: E3-####, E5####, or better. (Hyper
Threading should be disabled
when < 10MB of L3 cache);
AMD Opteron 6344 or better.
System Memory: ...the OS is
64-bit:
2GB of vRAM allocated from a
physical host with 6GB+,
Dual-Bank, [DDR3-1333(PC310600)/1600(PC3-12800)], or
faster.
6GB of vRAM allocad from a
physical host with 8GB+,
Dual-Bank, [DDR3-1333(PC310600)/1600(PC3-12800)], or
faster. ECC memory strongly
encouraged!
8GB of vRAM allocated from a
physical host with 12GB+, Triple
or Quad-Bank, [DDR31333(PC3-10600)/1600(PC3-12
800)] or faster. ECC memory
required!
Network Adapter:
Any stable, 100Mbps or faster,
Any stable, 1Gbps or faster,
A "Server-Class" NIC with at
least partial TCP-Offload
Engine(TOE), (or Intel IOAT),
functionality, 1Gbps or faster,
[TSO (TCP Segmentation
Offload) and LRO (Large
Receive Offload)]
Installation
Page 7
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++ 2010 Redistributable
Java Runtime (Content Manager 10.3 now ships with, and requires, Java 7 Update 55)
Apache Tomcat Web Server (Content Manager 10.3 now ships with, and requires, Tomcat 7.0.53)
PostgreSQL Database (if selected)
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, 2012
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 Enterprise Content Manager.
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.
4. Microsoft Visual C++ 2010 Redistributable
Page 8
Caution:
You will see the following note: "Scala Enterprise Content Manager requires Microsoft Visual C++ 2010 redistributable component.
Would you like to install it now?"
Click Yes to continue.
5. Java Runtime
Caution:
You will see the following note: Scala Enterprise Content Manager requires Java Runtime Environment (JRE), and a suitable version is
not installed. Would you like to install it 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
Caution:
You will see the following note: "Scala Enterprise Content Manager requires Apache Tomcat 7 Web Server. Would you like to install it
now?"
Click Yes to continue.
The installer will proceed to install the selected components. Then it will continue with the setup process.
7. End User License Agreement
Select the “I accept the agreement” button. Click Next to continue.
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.
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.
10. PostgreSQL Database Password
Choose a password that will be used for both the database Superuser and Windows service accounts.
Warning:
Page 9
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.
11. PostgreSQL Data Storage Options
The installer will use the PostgreSQL default location or you can specify a custom folder. Click Next to continue.
12. Web Application Configuration
Note:
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, port and connection host address, like in the following
example. Click Next to continue.
The web address you entered must be reachable by your players. Click Yes to continue.
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.
14. Allow Network 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.
15. Allow Network Connections for Apache Tomcat
Leave the box on the screen checked, and click Next to continue to allow network connections for Apache Tomcat.
16. 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 the progress bar. This may take several
Page 10
minutes.
Additional Third Party installations may take place depending on what you selected earlier.
17. Disable Apache Tomcat Default Page
Click Yes to disable the default Apache Tomcat web page.
18. 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.
19. 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.
20. 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.
21. Welcome to the Setup Wizard
The setup process will be completed in a browser. Click Next to continue.
22. 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.
23. Database Configuration
Select the type of 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 Next to continue.
24. Database Monitor
The Database Monitor will establish a connection and create the database schema. Once complete, the system will redirect you to the login page.
25. 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.
26. Specify a Network Name
Page 11
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.
Warning:
Once you select a network name, you cannot change it.
Click Create. Content Manager is now available to use.
Advanced Configuration Options
Jump Directly To
Installation Options
Silent Installation
Common Installation Options
Scala Enterprise Content Manager Installation Options
Scala Publish Automation EX Module Installation Options
Scala Designer Installation Options
Scala Player Installation Options
Preloaded Content for Players
Font Exclusion List
Advanced Customization Options
Scala Enterprise Content Manager features.xml Options
MMOS.INI Options Applying to All Scala Products
Scala Transmission Server and Scala Player MMOS.INI Options
Scala Designer and Scala Player MMOS.INI Options
Scala Designer MMOS.INI Options
Scala Player MMOS.INI Options
Scala EX Module MMOS.INI Options
Installation Options
The Scala installers accept various command-line parameters that affect the installation, or the values used in installation. To use these, open a
command prompt and type:
setup.exe /OPTION1=value /OPTION2=value ...
If value contains spaces, enclose it in quotes, for example:
setup.exe /OPTION1="C:\Temp\My Folder"
Silent Installation
Silent installation can be accomplished by passing /SILENT or /VERYSILENT as command-line arguments. /SILENT installs ask no questions,
but show installation progress./VERYSILENT installs ask no questions and do not show progress during installation.
To assist with silent installs, the installers accept various additional command line parameters given below.
Common Installation Options
Page 12
All the Scala installers accept:
/LOG=filename: Log the results to filename, which can be used to trouble-shoot a silent install.
/DIR=folderpath: Specify the full path where the product should be installed.
/LANGUAGE=language: Select language during installation.
/ROOTDATAFOLDER=path: Specify the path to be used for storing various configuration and data items. This corresponds to the WIN3
2_RootDataFolder keyword in MMOS.INI(see here), but the command-line option is also supported for Content Manager.
Scala Enterprise Content Manager Installation Options
/NODATABASE: When installing, skip installation of PostgreSQL. Useful for silent installs where a different database will be used.
/SUPERPASSWORD=password: When installing PostgreSQL, use this as the super-user password.
/DBDATADIR=datadir: Use datadir as the database storage directory for the PostgreSQL installation.
/NOLOGIN: If the newly installed version needs its database schema updated, the installer normally opens a web browser so that the
Administrator can login so that the database-update can be performed. By specifying /NOLOGIN on the installer command-line, this step
will be skipped. (The database-update still needs to be performed before Content Manager will fully start up.)
/CMDATAFOLDER=path: Use path as the storage location for Content Manager's media and other files. (Note: specifying /ROOTDATA
FOLDER= also changes this location, among other changes.)
/LOGFOLDER=path: Use path as the location for Content Manager's log files. (Note: specifying /ROOTDATAFOLDER= also changes
this location, among other changes.)
/NOSTARTTOMCAT: At the end of installation, Setup will not start Tomcat if this option is specified.
Scala Publish Automation EX Module Installation Options
The Scala Publish Automation EX Module installer also supports these options:
/SERVICE: Install the Publish Automation EX Module as a service (supported only on fresh installs).
Scala Designer Installation Options
The Scala Designer installer also supports these options:
/COMPONENTS="comma-separated list": Specify which components to install. Supported values are:
usersguide: User's Guide
clipart: Clipart library
clipart\4x3: 4x3 (Landscape) Clipart
clipart\4x3\demoscripts: 4x3 Demo scripts
clipart\4x3\templates: 4x3 Template scripts
clipart\4x3\images: 4x3 Image files
clipart\4x3\videos: 4x3 Video files
clipart\16x9: 16x9 (Wide-screen landscape) Clipart
clipart\16x9\demoscripts: 16x9 Demo scripts
clipart\16x9\templates: 16x9 Template scripts
clipart\9x16: 9x16 (Wide-screen portrait) Clipart
clipart\clips: Clip files
clipart\sounds: Sound files
clipart\misc: Other files (tiles, palettes, pointers, ...)
extrafonts: Additional typefaces
Example: /COMPONENTS="clipart\clips,clipart\sounds,extrafonts"
Scala Player Installation Options
The Scala Player installer also supports these options:
/NOSERVICE: Install Player Transmission Client as a process rather than a service (supported only on fresh installs, Release 10 and
newer).
/SERVICE: Install Player Transmission Client as a service rather than a process (supported only on fresh installs, Release 6.1 and
earlier).
Preloaded Content for Players
Scala Players support the notion of preloaded content. This allows you to pre-install media items on the Player systems before putting them in
the field, to optimize away the need for the player to download some or all of their initial content when the player first connects.
Page 13
Note:
Any preloaded content is not made available for use until you add it to the plan (i.e., by putting it into a playlist that is scheduled, or by
marking it as Non-Scheduled Content), and the player picks up and processes that plan.
The way preloaded content works is that when the player goes to download a given media item from Content Manager, it first checks for an exact
match in the PreLoadedContent folder. If found, the preloaded copy is used, and the download is skipped.
An exact match is defined as a file having the same base filename as the media item in the plan (i.e., without the revision number), and the same
MD5 signature.
By default, this folder Player looks in is:
... \All Users\Application Data\Scala\InfoChannel Player 5\Network\PreLoadedContent
but this location can be overridden by adding the following to your MMOS.INI file:
PreLoadedContent=path to the desired folder
Fill this folder with content, for example you can place a file BigVideo.mpg in this folder. If the player's plan requires a revision of a file called Big
Video.mpg, and the MD5 signature of the preloaded copy matches the MD5 signature of the revision needed by the plan, the preloaded copy will
get installed, and the download will be skipped.
When placing files in the preloaded content folder, omit the revision. That is, use BigVideo.mpg rather than BigVideo[12345].mpg.
For ScalaScripts, you need to publish the ScalaScript from Designer to a local folder, then place the top-level SCB file (without its revision), and
also copy the script-media files from the_shared\ subfolder into an equivalent _shared\ subfolder within the preloaded content folder. (Individual
script-media files cannot be made preloaded — you need to preload one or more ScalaScripts that use the script-media files of interest.)
Font Exclusion List
Scala Players use intelligent file transfer to avoid uploading or downloading files that are already present. However, font licensing rules generally
require that fonts be transmitted with their documents (Scala scripts), which defeats the benefit of intelligent file transfer. This is not a big issue
with Western fonts because of their comparatively small size, but with Asian fonts this can be a significant issue.
Scala Designer supports a "font exclusion list". In a Scala network, if a set of fonts is known to be pre-installed on all players, then naming these
fonts in the font exclusion list will cause them to be not included by default when publishing to Scala networks. (By default, fonts not on the
exclusion list are published as normal.)
In the Advanced Publish Options menu, the Include Fonts? option still allows you to exclude all fonts. If you choose to include fonts, the new E
xclude Standard Fonts? option lets you control whether the fonts on the exclusion list are excluded or transmitted.
The list of excluded fonts itself is an XML file that can be found at:
Program Files\Scala\Designer 5\System\FontEmbeddingExclusionList.xml
Modifying this file is straightforward, but care must be taken to only list fonts that are indeed present on all players. Otherwise, a player may
receive a script without all the necessary fonts, which can produce an incorrect display and run-time errors.
Advanced Customization Options
Most Scala products have a variety of advanced configuration options available through the use of the MMOS.INI file. Content Manager uses a
file called features.xml for some of its advanced customization.
MMOS.INI is a file that lives in the program's installation folder, e.g. D:\Scala\Player or C:\Program Files\Scala\Designer, or wherever your
Scala product(s) are installed. Normally, each installation folder can have its own MMOS.INI file with its own settings.
The MMOS.INI file can be UTF-8, in which case it should begin with the UTF-8 byte-order mark, which consists of the hexadecimal values EF BB
BF.
The MMOS.INI file begins with the optional byte-order mark, followed by the word [Scala] as shown inside square brackets, followed by one or
more lines of the form
OptionName = value
Anything after a semi-colon is treated as a comment and is ignored by the Scala applications.
Here is a simple example:
[Scala]
; Open on the desktop in a borderless window
DESKTOP_Borderless = 1
; Force the window to be topmost always
DESKTOP_TopMost = 1
Page 14
and so on.
You may find you already have an MMOS.INI file. If you do, you may wish to review which settings are already in force. But remember, anything
after a semi-colon is a comment and does not have any effect.
If you do not have an MMOS.INI file, it is a simple matter to make one in any text-editor such as Notepad.
Windows 7 (and Newer) Note:
Under Windows 7 and up, if you try to create files inside the Program Files folder, Windows will create a per-user shadow-copy inside
the Windows "Virtual Store". Depending on your system configuration and user rights, you may need to create the MMOS.INI file in a
regular folder, then use Windows Explorer to drag it over to the correct destination inside Program Files.
Scala Enterprise Content Manager features.xml Options
The features.xml file lives in the Windows "application data" location, which is typically C:\ProgramData\Scala\InfoChannel Content Manager
5\conf.
The syntax for the features.xml file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<feature-config>
<features>
<feature>
<name> featurename </name>
<enabled> true/false </enabled>
</feature>
<feature>
<name> featurename </name>
<enabled> true/false </enabled>
</feature>
</features>
</feature-config>
The following options are available:
PlayerProxyIP: When Players are behind a proxy server, the IP address displayed for the Player is the address on behalf of which the
proxy server is forwarding. To restore the original behavior (address of the proxy server), set this feature option to false.
UseTLS: When using the SSL option for email notification, if you also need TLS then set this feature option to true.
PlangenCacheOptimizationsForBroadcast: The plan generator has been optimized to be significantly faster in certain cases,
especially when generating plans for a small number of players at a time, on a Content Manager with a large media library. This
optimization is enabled by default for point-to-point players. To enable this optimization for Broadcast Players, set the PlangenCacheOpt
imizationsForBroadcast feature option to true.
UseXForwardedForIpBanning: Content Manager has defensive logic to block repeated failed login attempts from the same IP address.
When using a web accelerator (reverse proxy), the origin IP address will appear to be the address of the reverse proxy, which could lead
to blocking too much. If your reverse proxy sets the X-Forwarded-For HTTP header, you can tell Content Manager to use the most
recent IP address from that header when making blocking-decisions for failed login attempts. To enable this feature, set theUseXForwar
dedForIpBanning feature option to true.
SKIP_ACCESS_LOGS: The Tomcat access logs can grow quite large on a busy server. By default, they are now no longer included
when using the Download Logs feature. This can be changed by setting the SKIP_ACCESS_LOGS feature option to false.
MMOS.INI Options Applying to All Scala Products
WIN32_RootDataFolder: Control the location of all Scala config files, logs, settings, temporary files, etc.
WIN32_RootDataFolder = path
When set, Scala data that is normally stored under the Windows-standard configuration areas is stored instead under the specified path.
Also the Scala temporary folder appears under the specified path. Thus, most of the locations where Scala reads and writes files can be
controlled.
This is the simplest way to move the locations where such files are stored. There are additional MMOS.INI keywords to move specific
folders such as the Content andLocallyIntegratedContent folder, but it is often better to move them all with this one keyword.
Starting with Release 6, you can install the products specifying /RootDataFolder=path on its command-line, and Setup will set WIN32_Ro
otDataFolder correctly (creating anMMOS.INI file if necessary, otherwise modifying the existing one.)
Starting with Release 6, the Content Manager installer supports /RootDataFolder=path on its command-line. This sets WIN32_RootDataF
older for Content Manager itself, as well as for the Transmission Server and Server Support components. (In those components, the
installer also sets WIN32_CommonProductRootDataFolder, so those components can locate Content Manager's location where needed.
Page 15
Note:
For Content Manager, changes to WIN32_RootDataFolder must be done using the installer, rather than by hand-editing
the MMOS.INI files.
Note:
This option is not yet supported for the Playback Audit Reporting Module.
WININET_EnableServUDirectoryCacheKludge: The directory caching of the Serv-U FTP server can return incorrect results. Scala
recommends that directory caching be disabled when using the Serv-U FTP server. However, if this is not possible you can enable a
workaround by adding this to your MMOS.INI:
WININET_EnableServUDirectoryCacheKludge = 1
(The workaround will hurt media transfer performance.)
TCPIPTOOLS_FTPClientKeepAliveCommandChannel: Setting this instructs the FTP client to set the socket "keep-alive" option on the
FTP command channel. This can resolve certain command-channel timeouts that can sometimes be caused by intervening firewalls or
routers. To enable this, add the following to your MMOS.INI:
TCPIPTOOLS_FTPClientKeepAliveCommandChannel=1
Scala Transmission Server and Scala Player MMOS.INI Options
These MMOS.INI Options apply to both the Scala Transmission Server service and Scala Player:
SSCOMMON_EncryptionKey: Set custom encryption key for protecting usernames / passwords.
The Scala network encrypts all usernames and passwords that are transmitted or stored. Health monitoring messages are also
encrypted, and job command files and responses are sealed as well. You can select your own custom encryption key by setting:
SSCOMMON_EncryptionKey = encryption-key-string
Set this on both Transmission Server and all Players or else things will not function. Note that there is no support for migrating stored
usernames/passwords from one key to another, so this key is best established from the beginning.
encryption-key-string should be 5-7 characters in length (40 to 56 bits).
Scala Designer and Scala Player MMOS.INI Options
These MMOS.INI Options apply to both Scala Designer and Scala Player:
Path Options
MEDIA_Content:
You can override the location of the Content folder by setting:
MEDIA_Content=path
MEDIA_LocalIntegratedContent:
Normally, when a Scala script references some media, that media is sent along with the script when the script is published to a Scala
network. However, any media that isLinked Content is not sent with the script that references it. Such content either needs to be added
separately within Scala Enterprise Content Manager, or needs to be installed, delivered, or generated on the player.
Note:
When installing, delivering, or generating content on the Player, you should read and understand the Locally Integrated
Content support features.
When resolving references to Linked Content, the Scala software first looks in the Content folder, and if the file is not found there, it looks
in the LocallyIntegratedContent folder. The reason for two folders and the essential difference is that:
The Content folder is managed by the Player network engine, i.e., things sent as content from Scala Enterprise Content
Manager are placed there.
The LocallyIntegratedContent folder is for content managed outside of Scala Players, e.g., placed here by any custom
integration application.
Page 16
One big difference is that cleanup of old/unused content will not touch files in the LocallyIntegratedContent folder.
By default, the Content and LocallyIntegratedContent folders are placed side-by-side as
Documents and Settings\All Users\Documents\Scala\Content
Documents and Settings\All Users\Documents\Scala\LocallyIntegratedContent
but the WIN32_RootDataFolder keyword overrides this to
WIN32_RootDataFolder\Documents\Content
WIN32_RootDataFolder\Documents\LocallyIntegratedContent
Display Options
DESKTOP_Borderless/TopMost/CustomPosition: Scala Player can now run on the desktop as a top-most borderless window of
arbitrary or full size. You can specify the left, top, width and height. As an example, add this to your MMOS.INI:
DESKTOP_Borderless = 1
DESKTOP_TopMost = 1
DESKTOP_CustomPosition = 100 50 800 600
Omitting DESKTOP_CustomPosition will make the window fill the primary display.
These options are also supported by Scala Designer.
MM3D_EnsureVBlankDuringPresentKludge: This enables a workaround for certain Direct3D device driver issues. Some device drivers
do not properly maintain frame-synchronization during display updates. Ordinarily, a Direct3D device driver waits for the display device to
enter vertical blank before performing the display update. Playback relies on this for smooth, shear-free animation. Some drivers don't
handle this properly, resulting in jerky animation and/or horizontal shearing. When this workaround is enabled, playback waits for the
display device's vertical blank period instead of relying on the device driver to wait for vertical blank. This workaround was initially added
to address an issue with the Intel 945 graphics chipset, and playback will automatically recognize the Intel 945 chipset and enable this
workaround.
In some preliminary tests, this workaround has also shown a performance improvement to movie playback on multiple display players. If
you enable this workaround, you should probably also disable MM3D_UseBackBufferLockKludge as it will likely interfere with the MM3
D_EnsureVBlankDuringPresentKludge workaround.
To enable this workaround, use:
MM3D_EnsureVBlankDuringPresentKludge=1
MM3D_UseBackBufferLockKludge: This enables a workaround for device drivers that consume a large amount of CPU waiting for
vertical blank. Most Direct3D devices apart from those from nVidia and ATi require this workaround. Playback detects those devices and
will enable this workaround as necessary. You can override that behavior with this setting. Note that the Intel 945 *does not* require this
workaround, other Intel devices (845, 865, 915, 946, 965) currently require this workaround.
To enable this workaround, use:
MM3D_UseBackBufferLockKludge=1
To disable this workaround, use:
MM3D_UseBackBufferLockKludge=0
Due to a driver bug on certain ATI-based systems, some wide text elements or crawl-segments could end up displayed as a white
rectangle. There is now a workaround that can be enabled by setting:
MM3D_UseATIOddTextureSizeKludge=1
in your MMOS.INI file.
Video playback of H.264, MPEG-2, MPEG-1, and WMV/VC-1, as well as most audio playback, is now based on the FFMPEG video
decoder library, for improved performance and compatibility. Updated for the video decoders are now included in the Player and Designer
installers — there is no longer a separate video codecs updater. If for some reason you need the older behavior on a system that already
has the MainConcept codecs installed, use the MMOS.INI setting
DSHOWRENDER_EnableFFMPEG=0
(Added in Release 10)
When playing back H.264 or WMV/VC-1 video on most systems with AMD or NVIDIA graphics, hardware-accelerated video is now used.
This results in better image quality and performance, combined with lower power consumption. This new capability requires Windows 7 or
newer. To force software-based video decode, use the MMOS.INI setting
AllowDXVA=0
Page 17
Most graphics hardware has a resolution limit for hardware-accelerated video, beyond which things may not work, or may even crash. By
default, we limit hardware-accelerated video to 1920x1088 or smaller. If you know your graphics card can go higher, use the MMOS.INI s
etting
MM3D_MaxWidthForDXVA2=width
MM3D_MaxHeightForDXVA2=height
When Video files are not recognized by the new playback subsystem, the system will attempt to play it using other Windows codecs. This
may be useful in rare or obscure cases. In normal systems where you have good control over the media formats used, it can be a good
idea to set the MMOS.INI setting
DSHOWRENDER_FFMPEGFallbackToDirectShow=0
Media-Handling Options
If a video stream has multiple audio tracks, we select the one whose language matches the system's language. This can be overridden
with the MMOS.INI key
DSHOWRENDER_IPTVISO639LanguageID=0xnnnnnn
where nnnnnn is the hex representation of ISO-639 language code, e.g. (0x737061, corresponding to 'spa', for Spanish.)
DSHOWRENDER_UseSafestRecognition: When Scala tries to identify files as video, it sometimes needs to invoke third-party CODECs
installed on the system. Rare combinations of these CODECs with certain media files can crash. By setting
DSHOWRENDER_UseSafestRecognition = 1
Scala will only use more conservative ways to identify video files.
FLASHLOADER_MaxTextureSize: Limits the maximum texture-size (resolution) used for Flash clips, that effectively gives better
performance for slightly fuzzier visual quality, for large Flash clips. Set
FLASHLOADER_MaxTextureSize=n
Where n is at least 400. If the Flash clip is larger than n in either dimension, playback will cut its size in half repeatedly until both
dimensions are less than or equal to n. The Flash clip will be drawn at its correct size, but with reduced detail, enabling higher
performance.
A small number of WMV videos are encoded interlaced, and interlacing artifacts could be visible when played in Scala. Playback of WMV
files can now be forced to progressive mode by setting the following MMOS.INI flag:
DSHOWRENDER_ForceWMVProgressive=1
In the future, this will become the default behavior.
Most WMV or WMA files use 16-bit audio. Fixed a problem where WMV or WMA files that used other-than 16-bit audio played back as
noise. To enable this change, you must set the following in your MMOS.INI:
DSHOWRENDER_FixWMVAudioRemap=1
The "User-Agent" string used for WebClip can be customized using the MMOS.INI setting:
WEBCLIP_UserAgent=string
Scala Designer MMOS.INI Options
(See additional options that apply to both Scala Designer and Scala Player.)
HTREQ_PreserveScalaArt:
Normally, if you add media from the Scala clipart library location, the ScalaScript uses the normal Windows path to that file. But if you set:
HTREQ_PreserveScalaArt=1
then such media will be listed in the script using a path of the form ScalaArt:\folder\file.jpg. This matches IC3 behavior, but only in
certain limited cases is it useful.
SCRIPTXFER_EnableUTF8ContentFiles: When set, forces the publish operation write the top-level Content XML files in UTF8.
SCRIPTXFER_EnableUTF8ContentFiles=1
Page 18
Scala Player MMOS.INI Options
(See additional options that apply to both Scala Designer and Scala Player, and to both Scala Transmission Server and Scala Player.)
Display Options
Added additional logic to restore Player if ever it is minimized from outside Player's control. To enable this, use the following MMOS.INI s
etting:
MM3D_ForceUnminimize=1
Player Start and Exit Handling
There is basic support for requiring a numeric password to exit playback. In your MMOS.INI file, set:
INPUTMGR_EscapeKey=0
INPUTMGR_EscapePassword=12345
To exit, you must then type <Esc>12345<Enter>. The password can be any number from 1 to approximately 4.2 billion.
Typically, you should also disable the Window close function (Alt+F4):
INPUTMGR_WindowClose=0
RUNIC_StartScript: Specifies a custom outermost script that the Player should run, instead of System\icstart.sca. Ultimately, your
custom script should invoke System\icstart.sca. The custom script lets you add certain functionality that must be present at the top-level
context of the playback script. This example causes playback to exit when the mouse moves (but see also
RUNIC_AllowScriptExit below):
!ScalaScript500
:"screenblanker_start.sca"
{
Group:
OnNotification(Mouse.X, Quit(9999));
OnNotification(Mouse.Y, Quit(9999));
Sequence:
// This is where the Scala-standard start script gets run:
Script("ScalaProgram:\System\icstart.sca");
}
NETIC_SkipAdminTest: If you run the Player under a limited-user account, at startup Player normally logs a Problem 7 report about
features that may not work without Administrator rights. The problem report can be suppressed by setting the MMOS.INI flag:
NETIC_SkipAdminTest=1
RUNIC_AllowScriptExit: Normally, if a script deliberately exits playback, the player considers this an error and restarts the PC so that
the display resumes. If you intend to allow exit, set the MMOS.INI keyword
RUNIC_AllowScriptExit=1
NETIC_Reboot: Control whether the Scala Player transmission client reboots or restarts when it processes a Reboot job command. The
normal behavior is to reboot, but if you want the network engine to restart without rebooting, set:
NETIC_Reboot = off
RUNIC_Reboot: Control whether the Scala Player graphical engine reboots or restarts if it abnormally exits.
Normally, if the Scala Player graphical engine exits abnormally, the PC will be rebooted. Set:
RUNIC_Reboot = off
to cause the graphical engine to be restarted without the PC being rebooted.
Path Options
Page 19
MEDIA_Channels:
You can override the location of the Channels folder by setting
MEDIA_Channels=path
(See also MEDIA_Content in the section on Designer and Player.)
PreLoadedContent:
You can override the location of the Channels folder by setting
PreLoadedContent=path
For details, see Preloaded Content for Players.
Response / Reporting Options
You can now override the URL and port number that Player should use for sending heartbeats. This is useful if you set up an additional
connector on Content Manager, so that you can then use network traffic shaping tools to differentially manage heartbeat traffic. To enable
this feature, use the MMOS.INI setting
NETCLIENT_HeartbeatDestinationBaseURL=http:// hostname[:portnum]
Where hostname is the alternate hostname to use, and optional portnum is the port number to use. (Added in Release 10)
SSHEALTH_LogUploadDelayHours: For nightly retrieval of ic.log and playback audit log files, this setting governs the delay after
midnight before the player uploads its logs. Using the mmos.ini setting
SSHEALTH_LogUploadDelayHours=h
tells the player to delay for a random amount up to h hours after startup or midnight, before connecting to upload its log files. (The default
value is 4 hours.)
SSHEALTH_HeartbeatStartupMaximumDelayMinutes: In order to balance network loads (e.g. when players restart at about the same
time due to scheduled reboots, maintenance jobs, etc.), you can instruct Player to delay the first heartbeat after startup. This delay will be
a random amount between zero minutes and the maximum number of minutes you set using the following MMOS.INI keyword:
SSHEALTH_HeartbeatStartupMaximumDelayMinutes=n
By default, there is no delay.
Dial-up Connection Options
NETCLIENT dial-up connection warning-limits: a family of options to set up certain dial-up connection warning-limits, and report an
error back to Scala Enterprise Content Manager if those limits are exceeded. (In order for the network to continue to function, the Player
will continue to dial after the warning-limits are exceeded — the error report back to Scala Content Manager is there to alert the operator.)
Select a combination of settings based on what you are interested in monitoring. In turn, this is usually based on how you pay for
telephone and internet service.
NETCLIENT_ResetDialupStatisticsEveryNHours: Sets the length of the warning-period over which the dial-up connection
warning-limits apply. After this many hours, the measurements are reset. There will be a maximum of one error reported back to
Scala Enterprise Content Manager per period.
NETCLIENT_ResetDialupStatisticsEveryNHours=n
The default value is 24 hours.
NETCLIENT_ErrorIfDialupConnectedMoreThanNHours: Sets a warning-limit based on total connect time. If a player is
connected for this many hours per warning-period, the warning-limit error will be reported.
NETCLIENT_ErrorIfDialupConnectedMoreThanNHours=n
The default value is 0 (unlimited). Use this setting if you are charged based on the amount of time your dial-up connection is
active.
NETCLIENT_ErrorIfDialupAttemptedMoreThanNTimes: Sets a warning-limit based on the number of dial-up attempts. If a
player makes more than this number of attempts per warning-period, the warning-limit error will be reported.
NETCLIENT_ErrorIfDialupAttemptedMoreThanNTimes=n
The default value is 0 (unlimited). Use this setting if you are charged per dial-up attempt (regardless of whether or not the call
succeeded).
NETCLIENT_ErrorIfDialupConnectedMoreThanNTimes: Sets a warning-limit based on the number of successful dial-up
Page 20
connections. If a player makes more than this number of successful connections per warning-period, the warning-limit error will
be reported.
NETCLIENT_ErrorIfDialupConnectedMoreThanNTimes=n
The default value is 0 (unlimited). Use this setting if you are charged per completed dial-up connection (e.g., some minimum
charge for making the connection).
NETCLIENT_ErrorIfDialupFailedMoreThanNTimes: Sets a warning-limit based on the number of failed dial-up connections. If
a player makes more than this number of failed connection attempts per warning-period, the warning-limit error will be reported.
NETCLIENT_ErrorIfDialupFailedMoreThanNTimes=n
The default value is 0 (unlimited). Use this setting if you are having problems with an excessive number of dial-up failures.
However, keep in mind that if a player cannot connect due to dialup failures it will not be able to report this error to Scala
Enterprise Content Manager until it has connected successfully.
Scala EX Module MMOS.INI Options
Publish Automation EX Module
SCRIPTXFER_EnableUTF8ContentFiles: When set, forces the publish operation write the top-level Content XML files in UTF8.
SCRIPTXFER_EnableUTF8ContentFiles=1
VCR EX Module
COMO_Pause: The VCR EX Module waits 1000 ms between successive commands it sends to the MPEG-2@Disk deck. This value can
be adjusted using the new MMOS.INI setting for the MPEG-2@Disk deck:
COMO_Pause=n
The manufacturer recommends a range of 500 to 1000 ms.
COMO_UseStopAfterPlayTrack: Certain MPEG-2@Disk units have special firmware that stops the deck automatically after playing a
single track. With such a device, add the new MMOS.INI setting for the MPEG-2@Disk deck:
COMO_UseStopAfterPlayTrack=0
to prevent Scala from issuing an unnecessary Stop command, which does nothing but add a delay.
A Quick Orientation
Logging on to Content Manager
When you first log on to Content Manager and every subsequent time you access the system, you will be provided with a login screen. All users
will need to enter their Username and Password in order to access the information in Content Manager.
A successful login will take you to the home dashboard where most of the day-to-day operations and actions using Content Manager will occur.
Page 21
Note:
The view in this manual is typically the role of the administrator where all options are available to view.
The menu system and options available to a user are controlled by Roles and users will see options based on the role that the
administrator has set for them. Since much of the content in Content Manager is user driven and user specific, and since Content
Manager uses workflow for assignments and approvals, it is important that all users have separate Usernames and that Passwords are
set according to the security policies of your company in order to keep content secure.
The interface is divided into two distinct areas for use.
1. The Menu Bar, which allows the user to access the tools inside Content Manager. In the Menu bar, the left hand options are those the
user would use on a regular basis and the right hand options are those used infrequently for administrative usage.
2. The Work area. This varies depending on where you are in the program, but on initial login, the home dashboard is presented.
The home dashboard provides a full array of operations for every type of user. Based on user roles and access, information available and tools
available within the dashboard will vary. It provides messaging, workflow activities and links to key areas of Content Manager using the links on
the dashboard.
Home Dashboard
The home dashboard seen by the User will depend on their role and workgroup, and provides them with a general overview of their area of work
interest.
Useful links are located on the right of the dashboard as well as the latest technical updates from the Scala Blog.
To return to the dashboard, the user may click on the Content Manager logo in the menu bar.
Content
Page 22
The Content Menu is the area where the user will upload and manage all content in Content Manager. In this section we will outline how to find
and upload and manage content for use.
Select the Media menu item in the Content menu.
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 either by Dragging-and-Dropping media files into the media panel, or manually uploading them using the New button.
Items created using Scala’s Designer can be published directly into Content Manager, or uploaded as a single file using Designer's publish to ZIP
(SCZ) option.
Media
The Media view seen can either be in the Show List or Show Grid views with the number of items selectable by the drop down menu.
The order of media items displayed may be adjusted by clicking on the column heading, which alternates between ascending and descending
order.
If a media item is being used, then a linkable counter is shown in the Last Modified column. Clicking on it will show you where the item is being
used. If you attempt to delete an item that is "in use," then a similar dialog box appears to show usage.
Warning:
Deleting items in use will remove them from messages and playlists as appropriate.
You can see a larger view of the media item by clicking the thumbnail.
Media files are either uploaded directly into Content Manager or published to Content Manager from Designer.
Uploading Files
Drag-and Drop
The simplest method to upload content is to drag-and-drop files into the Media window. After dropping the files, a dialog box appears requesting
you to select a folder, if required, and optionally remove items to be uploaded for the list. Selecting Upload will start the upload process - a status
Page 23
bar appears in the Menu Bar and upon completion a confirmation status appears. You are able to continue working while you are waiting for
uploads to complete.
Warning:
Closing your browser will terminate your upload session.
+New|Media Upload
The alternative method is to upload files manually using the New|Media Upload option in the toolbar. A dialog box will appear.
Save To: Optionally select the folder in Content Manager to upload to.
Add: Browse to the files directory and select the files to be uploaded.
Select Upload.
Assigning Properties to Media Files
Properties can be set on individual media items by selecting the file and clicking Properties in the menu or by clicking the file name.
This will allow the user to add or edit:
Description(s)
Assign Categories
Assign Workgroups
Page 24
Select or Edit the Valid and End Date(s)
Provides details of when the item was created, who created the item, when the item was modified and who modified the item.
Assign Metadata as required
Category types and Workgroups can be created though the System|Administration Menu. Once created, Media items with categories and or
workgroups can be sorted and searched by selecting the category/workgroup in the Filter section.
Valid Dates
The Content Manager Properties system defaults the valid date–from the date that the item was added to the Content Manager.
The system also defaults to “No end date.” Both the “Start date” and the “End by date” can be adjusted.
Select the calendar icon next to the “Start date” to adjust the date. Choose the radio button next to “End by” to adjust the ending valid date and
select the calendar to adjust the date.
Audio Ducking
Certain media types support Audio Ducking, meaning the player can turn down the volume of other audio (typically background audio tracks)
when another media item is playing.
Full Screen
Setting this option to ON will force the playback of this media item to occupy the complete full screen area defined by the frameset used by the
channel. For example, say you are using a frameset that has three frames, on a 1920 x 1080 'canvas', setting Full Screen to ON will cause the
media item to play in the 1920 x 1080 area.
Volume
Certain media items allow an additional property–Volume. This allows the user to override the volume of a selected media item.
Metadata
Media Metadata labels are first defined in the System|Management Menu.
Media Metadata is primarily used for the creation of Smart Playlists which are automatically generated playlists based on criteria.
Set the Metadata for this media item by simply selecting or entering values appropriately.
Media Information
This tab contains the size, dimensions and duration depending on the media types.
History
The History tab shows the revisions of the media item.
Approval
If the Approval system is enabled then this tab shows the the current status of approval of the media item. The status is either:
Draft
Approved
Needs Approval
Rejected
Depending on the current approval status and the role of the logged in user, buttons will appear to Request Approval, Reject or Approve. The
Draft status only applies to Messages.
Preview
This tab shows a preview of the media item depending on the media type.
Edit Multiple Media Item Properties
For convenience, you are able to modify the properties of multiple media items by selecting multiple files and clicking Edit Multiple. The list of
attributes that can be edited using Edit Multiple will depend on the media items selected and their commonality.
Page 25
Check the attribute you wish to bulk update
Enter/amend the attribute
Save your changes
Generate Thumbnail
This menu selection allows you to regenerate the thumbnail for the media items selected.
Report
Playback audit reports can be generated for the media items selected.
Delete
Deletes the selected items
Note that if items are in use then a dialog will inform you of this fact.
Filtering/Searching Media Items
Filters
Media Items may be filtered to show items of interest by checking the box next to the available options - Filters can be cleared by selecting the
clear button.
File Type
Message
Image
Video
Scala script
Web page
Widget
Flash
Audio
Windows Script
Unknown
Category
Not assigned
Any Assigned
User Defined Categories
Workgroup
Not assigned
Any Assigned
User Defined Workgroups
Approval Status
Page 26
Needs Approval
Approved
Rejected
Draft
Valid Date
Expired
Current - Never Expires
Current - Will Expire
Future
Template Used
Search
Enter the partial name or full name of the media items you are searching for and select the 'magnifying glass' - to clear the search delete the text
the in the search field.
Adding Media Items to an Existing Playlist
Media Items may be added to an existing playlist by selecting 1 or more items and then selecting Add to Playlist button. A dialog box then
appears that shows available playlists. Select the playlist required and click Select
You are then presented the playlist for you to position the media item and apply any attributes required for playback. See the section on Playlists f
or more details.
Adding a Message
From the +New button you can create a new message from a Template
Select the template required and click the Next button.
Enter the Name of the Message and click the Next button
You are presented with a dialog box for you to complete based on the criteria set by the Template Administrator. The Create button will remain
ghosted until all required fields have been completed.
Page 27
Click on Create
You are then taken to the preview tab of the message. Here you are able to see the preview of the message and make additional adjustments
including setting Properties and Metadata for the message.
Click Save or Save and Close if you have made additional changes.
Editing an existing message is easily achieved by selecting the message and selecting either Properties or clicking the name link - this will then
display the Preview tab and then you can amend the message appropriately.
Adding a Web Page
From the +New button you can create a Web page Media Item
Enter the Name and URL of the webpage you wish to view.
Templates
Templates are created and published to Scala using Scala Designer. The template author has created a placeholder for text and/or graphics.
When published to Content Manager, it will display all uploaded templates which can easily be managed.
Templates can also be uploaded by drag-and-drop or using the upload button as detailed below.
Drag-and Drop
The simplest method to upload templates is to drag-and-drop SCZ files (created by Scala designer) into the template window. After dropping the
files a dialog box appears requesting you to select a folder, if required, and optionally remove items to be uploaded for the list. Selecting Upload
will start the upload process - a status bar appears in the Menu Bar and on completion a confirmation status appears. You are able to continue
working while you are waiting for uploads to complete.
Warning:
Closing your browser will terminate your upload session.
Upload
The alternative method is to upload files manually using the New|Media Upload option in the toolbar. A dialog box will appear.
Page 28
Save To: Optionally select the folder in Content Manager to upload to.
Add: Browse to the files directory and select the template SCZ files required
Select Upload
Assigning Properties to Templates
Properties can be set on individual Templates by selecting the file and clicking Properties in the menu or by clicking the file name.
Description(s)
Assign Categories
Assign Workgroups
Category types and Workgroups can be created though the System|Administration Menu. Once created, Templates with categories and or
workgroups can sorted and searched by selecting the category/workgroup in the Filter section.
Template Information
Shows the Size, Dimensions and Duration of the Template
Administration
Template fields can be managed using the template fields administration tool.
To make message creation easier for the user the template Administrator can:
Change the field Label - to make it easier to understand
Specify whether the field is required to be filled in, or not
Specify the maximum Number of Characters that may be entered by the message creator
Adjust the Text Entry Window by setting the Number of Lines for that window - particularly useful when allowing multiple line text areas
Change the field order by dragging-and-dropping the fields into the order desired
Preview
The preview tab shows the page thumbnails of the template. For Multi-page templates you are able to navigate though the pages using the
control buttons.
Edit Multiple Template Properties
For convenience, you are able to modify the properties of multiple Templates by selecting multiple templates and clicking Edit Multiple.
Page 29
The list of attributes that can be edited using Edit Multiple will depend on the media items selected and their commonality.
Check the attribute you wish to bulk update
Enter/amend the attribute
Save your changes.
This menu selection allows you to regenerate the thumbnail for the media items selected.
Generate Thumbnail
This menu selection allows you to regenerate the thumbnail for the templates selected.
New Message
Choose New Message to make a new message from the currently selected template.
Delete
Deletes the selected items
Note that if items are in use, then a dialog box will inform you of this fact.
Planning
The flow of media content through Content Manager is a simple and intuitive process. Media items are sequenced in a Playlist which is assigned
and scheduled to a Frame of a Channel which then plays on a Player, or series of Players.
The Planning Menu is the principal area for the day to day management of:
Playlists: Can be either created manually or automatically by using Smart Playlists.
Schedules: Can be scheduled using a calendar or time triggers.
Channels: Can be created using a predefined frameset and channel settings, to allow for more advanced operations including event
triggering of playlists.
Playlists
The number of playlists viewable is selectable by using the drop down menu.
The order of playlists displayed may be adjusted by clicking on a column heading, which alternates between ascending and descending order.
Page 30
If a playlist is being used, then a linkable counter is shown in the Last Modified column. Clicking on the link will show you where the playlist is
scheduled or contained in other master playlists as a sub-playlist. If you attempt to delete a playlist that is in use, then a similar dialog box
appears to show usage.
Note:
Playlists may have icons indicating that there may be issues contained within it, for example unapproved media or expired content.
Note:
Deleting playlists in use will remove them from schedules or master playlists.
Clicking the thumbnail of the playlist will cycle though the items in the playlist (if applicable)
Creating New Playlists
Playlists are created by selecting the New button
There are three types of playlists that can be created:
Audio
Data
Media
Media Playlists
Media Playlists are the most common form of playlists. In their simplest form, they define the sequence in which media items are displayed.
To create a playlist:
Enter the name of the playlist
Add an optional description
Select Media as the playlist type
Page 31
Click on Create
Items
This tab displays the current list of media items. It is also here that the order of the items can be adjusted, if sequence order is selected, by
dragging and dropping the items into the desired order.
To add items to the playlist click the add button. An Add Media dialog box appears that allows you to select files from the media library.
Check the files required and click Select to add the media items to the items list.
You may now optionally set properties for each playlist item or bulk update them using Edit Multiple.
The properties you can set depend on the playlist item type, but generally have three tabs:
Item Properties - Sets the Item Duration, Transition. Items can also be disabled here.
Schedule - Set valid date and time ranges for micro scheduling
Conditions - Set the playback criteria based on rules such as Player metadata
Page 32
Assigning Properties to Playlists
Description(s)
Assign Categories
Assign Workgroups
Set the Default image duration (7 seconds)
Set the Default webpage/widget duration (30 seconds)
Set the Default transition (None specified = CUT)
Set the Default transition duration (1 second).
Category types and Workgroups can be created though the System|Administration Menu. Once created, Playlists with categories and/or
workgroups can be sorted and searched by selecting the category/workgroup in the Filter section.
Ordering
There are two Order types:
Sequence - play in the order specified, taking into account and conditional playback criteria. On the next iteration, they will play in the
same order.
Shuffle - the media items are shuffled based on rules. The list is then played, taking into account conditional playback criteria, and
before the next iteration shuffled again.
Shuffle:
This option allows you to set the "no repeat within" criteria and is either expressed as a percentage or as a fixed number.
You can also set adjacency rules so that media items do not play next to each other, such as competitive products.
Object History
Shows the date of creation and by whom and the last modified date and by whom.
Once complete click Save and Close.
Page 33
Audio Playlists
Audio playlists can be used for background audio. The creation of an audio playlist is similar to that of a media playlist except that only Audio files
may be added.
Data Playlists
Data playlist are non-visual playlists and cannot be scheduled in a Channels calendar - Data playlists can be used to send data ingested into
Content Manager and distributed to players based on the frequency of plan generation and the players polling interval. Any media type can be
added to a data playlist.
Adding Sub-Playlists
A playlist may contain other playlists (Sub-Playlists). These Sub-Playlists can either be played to completion or may play a fixed number of items
from that playlist.
When a Playlist is open, select the Add Sub-Playlist button Then select a playlist from those listed in the dialog box and click the Select button.
The selected Sub-Playlist is now added to your master playlist in the Playlist Items panel.
To set the number of items to play from the Sub-playlist, select the playlist and click properties. On the Scheduling Tab, set Items to play to either
play all items or play this many items each time and enter a number of items.
You can also set conditions for playback as described earlier.
Creating New Smart Playlists
Smart Playlists are playlists generated automatically based on criteria. There are three types of smart playlists that can be created:
Audio
Data
Media
Click on New Smart Playlists.
Enter the name of the smart playlist
Add an optional description
Select Media, Audio or Data as playlist type
Click on Create
You will see an additional tab called Item Conditions. Selecting this tab allows you to specify how the smart playlist is generated, by setting one
or all of the specific conditions described below.
Limit to: Allows you to set the the Number of items and how they are chosen.
Update automatically every: Allows you to set the the number of minutes between smart playlist generations.
Any/All of the following conditions: When adding conditional criteria, you are able to test the results by clicking Show Matching Items.
Note:
The Items tab shows the currently generated smart playlist and the order cannot be changed.
Filtering/Searching Playlists
Filters
Playlists may be filtered to show playlists of interest by checking the box next to the available options - Filters can be cleared by selecting the
clear button.
Playlist Type
Audio (regular)
Data (regular)
Media (regular)
Audio (smart)
Data (smart)
Media (smart)
Category
Not assigned
Any Assigned
Page 34
User Defined Categories
Workgroup
Not assigned
Any Assigned
User Defined Workgroups
Channel
User defined Channel
Player Groups
User defined Player Group
Search
Enter the partial name or full name of the playlists your are searching for and select the "magnifying glass."
To clear the search, delete the text in the search field and select the "magnifying glass."
Schedules
Selecting Schedules from the Planning menu shows a calendar view of the current channel. A channel must exist in order for this to appear.
If you have more than one channel then you may choose a different channel to schedule by choosing Select a different channel.
If your channel uses a frameset with multiple frames, then you can select the frame to schedule by choosing Select a different frame.
There are three tabs for scheduling:
Calendar: Weekly view where timeslots can be created. Each time slot contains a playlist.
Time Triggers: Allows the schedule to be interrupted at specific times, over and above that specified in the Calendar.
Non-Scheduled Content: Used to deliver a data file that is not specifically scheduled via a media playlist.
Adding a New Timeslot
Drag-and Drop
Click and drag a window in the calendar area.
After releasing the mouse, the Timeslot properties dialog appears.
Page 35
Click Change to select a different playlist.
Amend the Valid start and Valid end dates, and the timeslot's Start time and End time as required.
Set the Recurrence pattern to either:
Once
Weekly (default)
Monthly
Yearly
Set Audio Ducking and play Full Screen for the whole playlist if required.
Set for the whole playlist if required.
Once complete click Create.
New Timeslot button: The timeslot properties button appears and can be edited as described above.
Channels
The number of Channels viewable is selectable by the drop down menu.
The order of Channels displayed may be adjusted by clicking on a column heading, which alternates between ascending and descending order.
If a channel is being used, then a linkable counter is shown in the Details column. Clicking the link will show you where the Channel is being
used. If you attempt to delete a Channel that is "in use," then a similar dialog box appears to show usage.
Warning:
Deleting Channels in use will remove them from the assigned players.
Creating New Channels
Channels are created by selecting the New button
Page 36
There are three types of channels that can be created:
Audiovisual
Audiovisual with separate audio track
Audio track only
Audiovisual channels are the most common form of channels.
Enter the name of the channel
Select Audiovisual as the Channel type
Select a Frameset from the dialog
Click on Create
Assigning Properties to Channel
Optionally add a Channel description
Audiovisual
This tab allows you to alter the frameset for this channel only. Any additions or modifications are not saved back to the master frameset.
Page 37
Player Metadata
Setting Player Metadata on a channel can elevate the wrong channel being assigned to a player.
Variables
Set the channel variables by selecting the Variables tab at the top of the Channel Variables tool in the right hand side of the dashboard. This
allows you to select variables that are attached to the channel that can be selected in the set up of the channel.
Channel Variables is the way to link a control script to a channel.
Network
The Network Menu is the area for controlling and monitoring the important activities of your network:
Players: Define, Configure and Monitor playback devices
Player Health: View and Monitor Player activity including error resolution
Maintenance Jobs: Plan and Monitor routine maintenance tasks
Distribution: Shows a summary of the status of data transfer between Content Manager and the active players
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. Any players already added will appear in the center pane of the dashboard.
Once you have created channels in Content Manager, you may then create Players to display them. When you create players in Content
Manager, they must also be configured on the playback device to be able to communicate with Content Manager.
Page 38
On the player side, the Player Configuration utility relies on the correct setup being established in Content Manager, so it is important that this
step be done first.
Clicking on the Players button will open the Players panel. The first time you open this panel, the list of players will be blank, so you will have to
create one by clicking on the New button at the top of the panel. Input the player name and description properties and select a channel where it
will play at the bottom of the panel.
Content Manager allows the user to manage different types of Player devices including Audio only players.
Note:
All hardware specific information related to supported playback devices can be found in the Player Manuals.
These devices provide a wider range of options and types of players the list shown will be based on your license rights:
The full list of supported playback devices changes from time to time.
Create Multiple Players
If your player naming convention has a sequence, then you can take advantage of this by creating multiple players simultaneously and applying
common attributes, such as Channel, in one operation.
Start by selecting Create Multiple Players from the menu bar.
Select the Player type you wish to create multiple players and then fill in the dialog box.
In this example, 3 players will be created with the name starting with Site Lobby and then ### will be replaced with 001, 002 and 003 - since the
Start At is set to 1.
Page 39
Click Create
In the following dialog, check the item you wish to add to all players. In this case the Channel is selected and all players will bet set to that
channel.
Lastly, select Save and Close and the resulting Player List will show your new players.
Player Health
The Player Health dashboard provides detailed information about problems and network activity.
The Player Health summary screen allows the user to access any errors that have been reported by player(s).
Page 40
Once you have a player configured and running a scheduled plan, you can monitor the player’s “health” and network activity. You can configure
the player to send a “heartbeat” at predetermined intervals so the system will recognize that it is still operating efficiently.
If the player does not send a heartbeat signal at a predetermined time, an optional email can be sent to one or more users. You could then create
a new maintenance task, for instance, one to reboot the player.
By default, Content Manager lists every problem that has not been cleared from Content Manager. To view more details about a problem, select
the problem, and click the Details button.
Select the details tab to see more information on the specific error.
Select the Reported By tab to see which players are experiencing this error.
To clear a problem, select the problem and click the Clear button. Note that clearing the problem in Content Manager does not fix the problem
which has occurred with the player. It simply removes the item from the Uncleared Problems list.
You must resolve the problem on your player, otherwise the problem will reappear in Content Manager at a later time. To clear all problems, click
Page 41
the Clear All Problems button.
The Player Health summary screen also has the ability to show the current Network Activity.
Here you can see players reporting heartbeats and collecting plans.
Maintenance Jobs
Selecting Maintenance Jobs from the Network menu displays the Maintenance Job dashboard, which will be blank for new installations.
Create a new maintenance job by selecting New.
The first dialog requires you to define the Player Type this maintenance job is for and how you wish to select the subset of players, by Player
Name or by Player Group.
Page 42
The tasks that can be performed through maintenance jobs will depend on the Player Type.
Select a task type and then continue. In this example the Scala Player, Install Software Update is being shown.
At this point, the files required may be uploaded or selected.
After the files have been uploaded successfully, they may be selected.
Once the task has been defined, then the schedule for when this job will run.
Page 43
Once complete, the Maintenance job will be added to the plans for the corresponding players at the next plan generation.
The status of maintenance jobs can be monitored on the Maintenance Jobs dashboard.
Maintenance jobs that fail to execute can be resubmitted, as illustrated below.
Distribution
The number of Distribution Servers viewable is selectable by the drop down menu.
The order of Servers displayed may be adjusted by clicking on a column heading, which alternates between ascending and descending order.
The Distribution list shows a summary of the status of data transfer between content manager and the active players.
Modifying the Distribution Server
The default distribution Server is called Main. The properties of the distribution server may be modified to optimize performance.
Properties:
Allows the modification of general setting including the frequency of heartbeats.
Note that these settings need to be tuned to meet the needs of your network.
Page 44
Schedule
Plan Generation mode: Set to manual or Scheduled - the default is Scheduled every 10 minutes
If manual is selected, then plans are only generated on demand.
Plans can be generated for all active players on a scheduled basis of:
At Interval: plans are generated for Players at timed intervals with the option of setting a Starting At time.
Daily: plans are generated for Players at a specific time each day.
Weekly: plans are generated for Players at a specific time on a specify day of the week.
To create a new schedule:
Media Distribution Monitor
Show a list of media items currently being distributed.
You may inspect the media item and see which players have downloaded or still need to download the media item.
Plan Generation History
This tab shows a list of the plans generated and their status.
Submitted: when the plan was generated.
Type: whether the plan generation was automatic or manually generated.
Result: Status of the transfer.
Time to Generate: Indicates the time taken to generate the plans.
Transfer: shows the amount of data transferred.
Page 45
Files: Number of files associated to the transfer.
Players: Number of Players that plans were generated for.
Reporting
The user can generate Playback Audit reports using Content Manager. There are several types of Reports that the system supports:
Media Item reports
Player reports
Audit reports
The user may choose the level of detail and specify the selection criteria for these reports.
Prior to using the reporting module, the Playback Audit Module needs to be installed and configured, if it was not done at the time of initial
installation.
Note:
When installing the Reporting Module (Playback Audit Module) for the first time on an existing system, care should be taken to prevent
Content Manager from becoming overwhelmed with the quantity of historic "Billing" files that are waiting to be processed. Moving the
Billing files to an alternative location prior to installation is recommended.
Using the Web Services API's, advanced users are able to pull playback audit data back into their own systems, for further processing, or highly
customized reports. This allows integrations for business analytics, and custom reporting. Individual playback times (not just aggregated
information) are available through web services.
Normally Players return their proof-of-play data nightly. There is an option on the Network > Distribution screen for more frequent data-returns.
Playback Audit Parser Installation
Before reports can be generated, the Playback Audit Parser should be Installed and the Database Configured.
Prior to Installation you will need to:
1. Create a User account for the Playback Audit Parser to use, making sure it has the appropriate permissions.
2. Enable the Legacy Web Service.
Installation Steps
Click Next.
The following warning message should be heeded.
Page 46
Select Yes.
Once you have accepted the license agreement, select Next.
Select the folder and click Next.
Page 47
Filling the credentials of a user with the appropriate role required and click Next.
Enter the Legacy Web service credentials and select Next.
Allow Scala to connect trough the firewall and click Next.
Check the selections you have made and then click Install.
Page 48
You may cancel the installation at any point during the installation.
Complete the Playback Audit Parser installation by selecting Finish.
You can now continue with setting up the reporting module.
Reports
The reports dashboard allows you to generate a new report or view previously generated reports.
Page 49
To generate a new report select New, step though several dialog boxes to specify your criteria based on the type of report required.
In the Create Report Dialog, you are able to specify the general settings of the report, including the Date Range.
and the type of report required
Selecting Next will then allow you to specify the criteria of your report starting with Channels and Frames.
Select specific Channels/Frames or Skip over this step.
Page 50
The next dialog allows you to either choose Players by Player Groups, Metadata or by manually selecting them, as in this example.
The last part is to specify the Media items of interest either by using Workgroups, Metadata or Categories, alternatively you can manually select
media.
When using criteria the number of selected items is shown in the dialog.
Page 51
The report generated can then be viewed either as a PDF or HMTL page.
Page 1 of the report shows the criteria that generated the report.
and subsequent pages show the remainder of the report
Page 52
Reports may be generated from existing reports by selecting a report and clicking New from Existing.
To delete reports select the report and then click Delete.
Settings
This section allows you to configure the general settings for reports.
The properties tab allows you to set the Language and the Header and Footer information.
The Logo Media tab allows you to specify the logo and position for the reports.
Database Configuration (Reports)
Select the database type and then fill in the form with the appropriate details.
You will need to have available the credentials you use to access the database.
Page 53
The Test Connection button can be used to check the connection.
Click on Save and Close.
System
The System Menu contains the Administrative and Management activities associated with Scala Enterprise Content Manager.
These activities are usually performed on an infrequent basis.
Administration
This section contains information for setting up and reviewing:
Page 54
View API Documentation
Network Settings
Hosted Networks
License Status
Database Configuration
Server Settings
View API Documentation
Scala Enterprise Content manager has a full set of Web Services APIs, which allow for the creation of custom interfaces and workflows.
The API documentation describes each method and allows the programmer to see the results of the individual calls.
Network Settings
Content Manager allows you to view and modify various settings for your Network.
Approval Settings
You can enable message approval by checking the Enable Message Approval option.
You can enable media items approval by checking the Enable Media Items Approval option.
When enabled, you can request approval of media and messages before they are shown on a player.
If the option is not enabled, then the media items and messages will not require approval before being shown on a player.
Miscellaneous Settings
Page 55
Users can choose to change the maximum number of threads downloaded from remote publish locations.
Max Threads: The maximum number of threads that are available for use to download from a remote publish location. The default value
is one (1). If you change this setting, you MUST stop/start the Apache Tomcat service in order for the new setting to take effect.
First Day of Week: Allows you to select the first day of the week. The two choices are Sunday or Monday. The default value is Sunday.
Player Authentication
The player authentication settings are the username and password that your player(s) use when connecting to Content Manager.
Player username: The username player(s) use to connect to Content Manager. The default value is player_<networkname>.
Player password: The password player(s) use to connect to Content Manager. The default value is scala.
Confirm password: Requires you to re-enter a password for confirmation. The default value is scala.
Mail Server Settings
The SMTP settings allow you to configure Content Manager to use a mail server to send you email alerts when a player problem occurs. The
settings are:
SMTP Server Address: IP address or machine name of the SMTP server you want to use.
SMTP Server Port: Port of the SMTP server. The default value is twenty-five (25).
Use SSL: Set to yes if your the mail server requires the use of SSL.
Email Sender Address: Email address that will appear in the From line of the email.
SMTP Username – If the mail server requires authentication, enter the username.
SMTP Password – If the mail server requires authentication, enter the password for the account.
Confirm Password – Requires you to re-enter a password for confirmation.
Legacy Web Services
Scala Enterprise Content Manager uses REST based Web Services APIs 2.x and above.
You can view the documentation of the APIs from the Menu Bar-System|Administration|View API Documentation
Page 56
This option allows you to enable the SOAP based Web Service API 1.x for authentication of custom application using API 1.x
The web services authentication settings are the username and password that third party application uses when connecting to Content Manager.
Username: Username used to connect to Content Manager. This username must be unique.
Password: Password used to connect to Content Manager.
Confirm Password: Requires you to re-enter a password for confirmation.
Hosted Networks
Users that have purchased the Multi-Network Content Manager can access multiple Hosted Networks sites from a single sign on.
This option displays the list of available Hosted Networks as defined in your license.
You can view the network properties of a Hosted Network by selecting it.
In the Network Properties tab, you can add a description and set the First Day of Week for the scheduling of that network.
The Add Users tab allows you to add existing users to that hosted network or to add new user accounts for that network only.
When logging on to a Content Manager with a user account that is associated with multiple Hosted networks, the last logged-into network is
logged into. The user can switch between networks from the Menu Bar User|Switch Network.
License Status
Page 57
The status screen provides detailed information related to your Scala Enterprise Content Manager license including the number of available
licenses, and the modules your license contains.
Whenever you add additional playback devices, additional modules, or renew, your Scala Maintenance license will need updating before they
take effect.
The following options appear under License Status:
Get License File Online: Content Manager will retrieve the latest License from the Scala license server.
Import License File: If you have manually downloaded your License from the Scala license server, then you can import it using this
option.
Print License: You may optionally print a copy of your license for your records.
Software Updates
From time to time software updates will be made available for download at www.scala.com/updates. These updates are available for customers
on software maintenance program called Scala Maintenance.
If your software maintenance has expired, 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.
Database Configuration
Scala Enterprise uses a back end database and ships with PostgreSQL. Other databases are supported, and these include MySQL and MS SQL
Server.
This option allows you to view and modify the current database configuration settings that were provided during installation.
You are able to modify the type of database and can do so by entering the host, port and other relevant information.
Page 58
Under the Advanced tab, options can be set to fine tune the performance of the database.
Note:
Any changes made to these settings will modify the database and the original settings of your existing installation. Changes should be
made ONLY in consultation with or by the Network Administrator. Complete understanding of configuration options is necessary for
ANY changes in order to maintain the system.
Server Settings
Some Server Settings in Content Manager are not editable as they were set during installation.
System Information
This page shows an overview of the versions or software installed and the database configuration.
Software Versions
Operating System: Operating system version and architecture.
Java VM: Java virtual machine version. (Content Manager 10.3 now ships with, and requires, Java 7 Update 55)
Web server: Apache Web server version. (Content Manager 10.3 now ships with, and requires, Tomcat 7.0.53)
Scala Enterprise Content Manager: Content Manager version.
System Paths
Application directory: Where the web application is installed.
Configuration directory: Where the configuration files are stored.
Data directory: Where the data directory is located.
Web server directory: Where the Apache Tomcat web server is installed
Status
This page shows information regarding memory usage and connection details.
Maximum server memory: Maximum amount of memory available to the Java Virtual Machine (JVM).
Free memory: Amount of free memory within the JVM.
Number of processors: Number of processors available to the JVM.
Allocated memory: Amount of memory currently allocated by the JVM.
Page 59
Connector
This page shows information regarding connections used to access Scala Enterprise Content Manager.
Select the connector you wish to view or modify.
Port number: Port number the connector will bind to. You can only bind one connector to each port on each IP address.
Maximum Threads – Maximum number of concurrent threads this connector can use. The connector will not be able to serve more
simultaneous requests than it has threads. The default value is 150. You should set this based on how many players are directly
connected to Content Manager. To ensure stable content delivery, this value should be set to about 4/3 the number of connected players.
Specifying a value of more than 1000 has little effect on Windows Operating systems, because there is a limit to the number of
threads available to each process.
Max keep alive - Maximum number of requests that can be kept alive waiting for subsequent requests on this connector. The default is
100, and a value of 1 disables this setting. Generally, Scala recommends disabling this setting on networks with more than 50 players.
Min spare threads - Minimum number of spare threads for the thread pool on this connector. This setting is the number of threads that
are available to serve requests when they arrive. The default value is 4. If your network contains more than 50 players, this setting should
be set to 25.
Lookups - If enabled, Tomcat will attempt to resolve the hostnames of clients (such as players). Enabling this setting can negatively
affect performance.
If you edit any of the connector settings, make sure to click the Save button. Then click the Restart Server button to use your new settings.
You can create new connectors by using the New button.
Client Connector
Note:
If you make any changes to the client connections, your player(s) might not be able to connect back to Content Manager. Meaning that
you will need to reconfigure any existing players in the field to use the new settings!
When you install Content Manager, the client connection settings are pre-configured. You can edit them post installation:
Virtual Folder: Path that Content Manager uses within the webserver. For example, the full path after the hostname and port would
be: www.myhost.com:8080/VirtualFolder
Port: Port number the Content Manager will listen for requests.
Hostname: Hostname the Content Manager will tell players to connect to.
Connection port: Port number the Content Manager will tell players to connect to. If you are using port forwarding, you can specify a
different port.
Any changes that you make need to be saved by clicking the Save button. Once any changes are made, select the Restart Server button.
LDAP Config
Scala Enterprise Content Manager integrates with Microsoft’s Active Directory or LDAP servers for user-authentication (verification of
username/password) and user-authorization (roles and workgroups) from the central directory servers. This is described in more detail below.
Server Monitoring
Scala Enterprise Content Manager allows access to a Server Monitoring screen that contains performance graphs and statistic
Click on Open Server Monitoring to see them.
Page 60
Firewalls and Security
Almost all data transferred in a Scala Content Manager network uses HTTP. When Content Manager is installed, by default, port 8080 will be
used. If you choose the default port, you must ensure that port 8080 is open between your Content Manager and Player machines.
If you specified another port as part of the installation process, please be sure that port is available.
Microsoft OS enables a software firewall by default. However, as part of the installation process, the installer asks you if it is okay to add
exclusions to the Microsoft software firewall.
If you chose not to do so, you must add those exclusions manually. Otherwise your player(s) will not be able to communicate with Content
Manager. For more information, please consult Microsoft’s Windows Firewall documentation.
Many Anti-Virus packages also install (or have available) a software firewall, you must be sure that the Anti-Virus software firewall also allows
your network traffic to pass through.
Note:
The FTP protocol is only used when you specify Player-Direct FTP. This option applies for both Content Manager and Player. If you are
not using this plan delivery type, then you do not have to add exceptions for FTP.
HTTPS Connectors
Content Manager is able to utilize secure HTTPS connectors.
Generate a Certificate
A certificate must be generated first. The Sun Java Development Kit (JDK) and Java Runtime Environment (JRE) distributions include the
application keytool.exe that creates a certificate.
The keytool.exe application exists in the JRE bin directory that Content Manager installs (JRE 1.6_03). Your installed JRE or JDK bin directory
might differ, so you would need to modify it to reflect that difference. To generate a certificate, open a command line and navigate to this folder:
C:\Program Files\Java\jre1.6.0_03\bin
and execute this command:
keytool -genkey -alias cm -keyalg “RSA” -keystore “C:\Documents And Settings\All Users\Application
Data\Scala\InfoChannel Content Manager 5\Conf\tomcat.keystore”
This will create a password protected keystore and add the certificate to it. The keytool will prompt you for information about the certificate:
Enter keystore password: The password that will protect the keystore.
What is your first and last name?: The URL you’ll use when accessing the Content Manager over HTTPS. For
example: www.yourdomain.com.
What is the name of your organizational unit?: Your department name. For example – Engineering.
What is the name of your organization?: Name of the organization. For example - Scala, Inc.
What is the name of your City or Locality?: City or locality in which you reside. For example - Exton.
What is the name of your State or Province? - State or province in which you reside. For example - Pennsylvania.
What is the two-letter country code for this unit?: The two letter country code in which you reside. For example, the United States of
America is: US
Generate a Certificate Signing Request
In order to make Designer publish to Content Manager using HTTPS, you have to have a signed certificate. But first, you have to generate a
certificate signing request.
To generate a Certificate Signing Request open the command prompt and navigate to this folder:
might differ, so you would need to modify it to reflect that difference.
Page 61
keytool -certreq -keyalg “RSA” -alias cm -file “C:\cm_certreq.csr” - keystore “C:\Documents And
Settings\All Users\Application Data\Scala\InfoChannel Content Manager 5\Conf\tomcat.keystore”
This action will prompt you to enter the keystore password before a certificate signing request file is generated. Once generated, you can then
send the file:
C:\cm_certreq.csr
to a Certificate Authority that will create a signed certificate for you. Proceed to the next section to install the signed Certificate.
Installing the Signed Certificate
When you receive the signed certificate from your Certificate Authority it must be installed into the keystore. The Certificate Authority should
provide instructions for this procedure. However, below is some general information that might help.
First, you must download the Chain Certificate or Root Certificate from your Certificate Authority, and import it into the keystore. To do this, open a
command prompt and navigate to this folder:
might differ, so you would need to modify it to reflect that difference.
and type this command:
keytool -import -alias root -file “CHAIN_CERTIFICATE_PATH” -keystore “C:\Documents And Settings\All
Users\Application Data\Scala\InfoChannel Content Manager 5\Conf\tomcat.keystore” -trustcacerts
The CHAIN_CERTIFICATE_PATH is the full path to the Chain Certificate that you downloaded from your Certificate Authority.
For PKCS#7 formatted certificate replies, the supporting certificate chain is included in the certificate, so you don’t have to install the Chain or
Root certificate.
To import your new Certificate:
Type the following:
keytool -import -alias root -file “YOUR_CERTIFICATE_PATH” -keystore “C:\Documents And Settings\All
Users\Application Data\Scala\InfoChannel Content Manager 5\Conf\Conf\tomcat.keystore” –trustcacerts
Where YOUR_CERTIFICATE_PATH is the full path to the Certificate that you downloaded.
Creating a HTTPS Connector
Once a signed Certificate has been obtained and installed, you need to create a new HTTPS connector
When you add a new HTTPS connector, there are a number of options that can be set:
Port number: Port number the connector will bind to. You can only bind one connector to each port on each IP address. For HTTPS this
is usually port 443.
IP address: This setting currently cannot be changed.
Key alias: Alias of the certificate in the keystore that Tomcat uses for the connector. If not specified, the first key read from the keystore
will be used. Note: You must use the same key alias that you specified when you generated your self-signed certificate.
Key password: Password Tomcat will use when retrieving the certificate from the keystore. The default value is changeit. You must use
the same key password that you specified when you generated your self-signed certificate.
Keystore file: Full path of the keystore file (that contains the certificate Tomcat should use) for this connector. If not specified, the
connector will use a file named.keystore in the user’s home directory.
Note:
If you followed the instructions for generating a self-signed certificate this path is: C:\Documents And Settings\All
Users\Application Data\ Scala\InfoChannel Content Manager 5\Conf\tomcat.keystore
Optional Settings
The following options can also be set, but doing so is optional:
Max threads: (Optional) The maximum number of concurrent threads this connector can use. The connector will not be able to serve
more simultaneous requests than it has threads. The default value is 150.
You should set this based on how many players are directly connected to Content Manager. To ensure stable content delivery this value
Page 62
should be set to about 4/3 the number of connected players. Specifying a value of more than 1000 has little effect on Windows
32-bit operating systems, because there is a limit to the number of threads available to each process. Windows operating systems that
have 64-bit support can use more than 1000 threads.
Max keep alive: (Optional) The maximum number of requests that can be kept alive waiting for subsequent requests on this connector.
The default is 100, and a value of 1 disables this setting. Generally Scala recommends disabling this setting on networks with more than
50 players.
Min spare threads: (Optional) The minimum number of spare threads for the thread pool on this connector. This setting is the number of
threads that are available to serve requests when they arrive. The default value is 4. If your network contains more than 50 players, this
setting should be set to 25.
Max spare threads: (Optional) The maximum number of spare threads for the thread pool on this connector. This setting is the
maximum number of idle threads that can live in the pool before the server begins to close them. The default value is 50. If your network
contains more than 50 players, this setting should be set to 100.
Lookups: (Optional) If enabled, Tomcat will attempt to resolve the hostnames of clients (such as players). Enabling this setting can
negatively affect performance.
Once the HTTPS connector has been configured, you should configure the client connections to use the HTTPS connector.
Using LDAP and Active Directory to Administer Users
Scala Enterprise Content Manager integrates with Microsoft’s Active Directory (AD) or LDAP servers for user-authentication (verification of
username/password) and user-authorization (roles and workgroups) from the central directory servers. When the user tries to log in, the directory
server is consulted to verify some information about the user, including that the account is still active, that the password is correct, and what the
user's role(s) and workgroups are.
The use of LDAP and Active Directory allows for such capabilities as:
Centralized password management
Centralized enforcement of password rules (e.g., minimum password complexity, mandatory password change every 30 days, etc.)
Centralized disabling/enabling of user accounts
Centralized management of roles and workgroups.
Importing of existing users from the central directory server.
Configuring an Active Directory/LDAP Connection
Configure a connection to the Active Directory or LDAP server using either LDAP, or LDAPS (which is LDAP encrypted over SSL) by:
Specify the LDAP Host URL and Connection Distinguished Name (DN) and password (credentials) with which to connect. This can
include an optional port number (i.e. ldap://server:portnum or ldaps://server:portnum)
Specify the Base DN, which is the place within the directory services structure under which the users of interest live.
Connection Types
Content Manager supports an authenticated connection to the directory server, by specifying the Connection DN and Connection
password.
An anonymous connection to the directory server is supported by leaving these fields blank.
Multiple Domain Trees/Multiple Forests
The configuration user interface lets the administrator specify the Base DN (distinguished name) under which all the users are to be found. At this
time, Content Manager does not support multiple domain trees within a single forest, or multiple forests. (There are proxying products that can
represent multiple such trees as one.)
Connection Testing
The Test Connection button verifies that all the connection information works and that the directory server is reachable.
Mapping
The user's workgroup and role from within the LDAP/Active Directory server is achieved by making your Active Directory users members of
carefully-named Active Directory groups (or by making your LDAP users have carefully-named LDAP attributes), those users become members of
the matching named Content Manager workgroups and roles.
Permissions attribute: the name of the LDAP attribute to check, for role and workgroup membership. For Active Directory, use
memberOf.
Role permissions prefix: the prefix of the LDAP attribute or Active Directory group corresponding to a Scala role. For example, if the
Role prefix is "ScalaRole_", then a user who is a member of the Active Directory group "ScalaRole_Graphic Designer" would have the
Content Manager role "Graphic Designer", etc. A user can have one or more roles.
Workgroup permissions prefix: the prefix of the LDAP attribute or Active Directory group corresponding to a Scala workgroup. For
example, if the Role workgroup is "ScalaWorkgroup_", then a user who is a member of the Active Directory group
"ScalaWorkgroup_Marketing" would have the Content Manager role "Marketing", etc. A user can have one workgroup.
Page 63
Note:
Both the Role and Workgroup names used need to be defined in Content Manager for the mapping to be successful.
User Lookup Testing
The Test Lookup button lets the administrator enter a sample username and password, and verify that this user can be found and
authenticated using the directory server.
Management
This section contains information for setting up and reviewing:
User Activity
User Profiles
Roles
Workgroups
Categories
Media Metadata
Player Groups
Player Metadata
Folders
Publish Locations
Framesets
User Activity
Selecting User Activity shows a list that contains the following information
Username: Username of the person.
IP: IP address of the user
Type: Type of action performed.
Time – Time the action was performed.
Details: Action the user performed.
Page 64
The number of lines shown per page can be changed as well as a filter by Type.
User Profiles
Roles and Workgroups should be created prior to adding users.
This is especially important if you are using LDAP or Active Directory to administer Users, Roles and Workgroups. Please see the the section in
system setting to establish the connection first prior to importing users.
To create a new user select New
The panel will allow you to add user – assigning a username and password– and assign roles. After selecting create, additional information can
be added to assign the Workgroup, Regional Settings and other Miscellaneous Settings.
You are also able to sort the user list by Name.
Note:
Miscellaneous settings allow the administrator to inactivate user accounts and control user access and actions around content
approvals (workflow), passwords and email notifications.
Roles
Page 65
Prior to adding users, it is important for users to understand the “roles” that they will be assigned to and how to modify roles using the roles tool.
Additionally, Workgroups should also be configured prior to users being added to the system.
Select the roles option from the System|Management menu. This will provide a list of available and predetermined roles.
Each of those roles has a fixed set of actions that will limit what actions and activities the user will be allowed to take when using Content
Manager. The role also adjusts the menu structure so only options that the user can perform are offered.
Each predetermined role has prescribed actions that allow that role to accomplish the work of role.
The Administrator can change and modify the actions and resources on a role by role basis to meet system needs.
To change the name, access and resources that a particular role has, select the role, review the access and resources and make selections
based on access required for that role and once done select "Save and Close"
It is recommended that the predetermined roles are left unaltered and new roles created.
To create a new role, Select New and enter the name of the new role.
Select the access level required for this role and then select Save & Close
Page 66
Once saved this role may then be applied to a user and the Menu system will adapt to show only those ares of the program for which the user has
permissions.
System Administrator Note:
The System Administrator is a set role. In addition, it is the only role that cannot be managed.
Workgroups
A Workgroup is a simple way of associating one or more users to a particular collection of other users. This can be helpful in creating
associations between content, playlists and groups of users. A user will only see content that their workgroup either "owns" or has been given
permission to "use/view" by other workgroups. It is recommended that you select names that clearly identify the purpose of the workgroup.
If Workgroups have already been created they will appear in a "tree structure," which can be expanded/collapsed at each node.
To create a "root" Workgroup, select New at the top of the panel.
If you want to create sub-workgroups select the + next to the name of the workgroup.
Define the name of the Workgroup and its description in the appropriate fields.
Note:
Workgroups are assigned at the user level when you create a new or edit an existing user.
Categories
Page 67
Categories allow the user to initiate a category search for items in the Media library, which enables the user to more effectively tag and locate
items as the list of media items grows over time.
To create a category, select New at the top of the panel.
If you want to create sub-category select the + next to the name of the category.
Once the Category types have been defined and assigned to Media items, a filter can be applied in the filter panel in the Media Library.
Media Metadata
The primary usage of media metadata is in creating Smart Playlists where media is automatically added to a playlist based on matching selected
criteria.
.
Page 68
To add new Media Metadata, select New at the top of the panel.
In the panel that appears enter the Name and type Metadata.
Metadata types are:
String: simple Text strings that can be entered as any text value or restricted to a "pick list"
Integer: Whole Numbers
Boolean: Also known as logical (true/false represented as Checked/Unchecked)
Note on Pick Lists:
Text values can be entered and ordered alphabetically (ascending/descending) or by dragging and dropping them into the order
required.
Player Groups
Page 69
Creating Player groups has many benefits, including conditional playback of media items, playlists and maintenance job distribution.
To create a new Player Group, select +New, enter a unique name, optionally add a description and select Create.
Player Metadata
The primary usage of Player Metadata is in creating conditional playback rules for media items in playlists and sub-playlists. A secondary use
exists for Channels, which can be applied so that Channels cannot be assigned to the wrong player device.
To add new Player Metadata select ' New' at the top of the panel.
In the panel that appears enter the Name and type
Page 70
Metadata types are:
String: simple Text strings that can be entered as any text value or restricted to a 'pick list'
Integer: Whole Numbers
Boolean: Also known as logical (true/false represented as Checked/Unchecked)
Note on Pick Lists:
Text values can be entered and ordered alphabetically (ascending/descending) or by drag and dropping them into the order required.
Folders
To assist in the physical storage of media you can create a folder structure inside the media library.
Select New to create the folder in the root of your library.
Select the + next to a folder to create a sub-folder.
Enter the name of the folder.
When uploading media by either drag and drop or though browsing you can select the destination folder.
Folders can also be used as criteria for the creation of Smart Playlists.
Publish Locations
Publish locations enable you to automatically ingest content into your content manager from either an FTP site or a UNC path on your network.
This is particularly useful for content being generated by third parties.
Page 71
Once the base connection details are entered into the panel, you may select other administrative options and test the connection.
From a performance point of view you should adjust the Check interval to an appropriate frequency based on the change of that publish location.
Framesets
Framesets allow the user to define the layout that is associated with a channel.
There are a number of pre-defined layouts or you can create your own by specifying the screen size and frame properties for a frameset. The
order of the frames defines the layers, with the top most frame being at the top of the frame list. To change the order, drag the frame name in the
list to the desired position. The preview area shows the graphical representation of the frameset.
Frame properties allow you to position the frame and determine the scaling options for how media is displayed within that frame.
Note:
Once a frameset is applied to a Channel the attributes are copied to that channel.
Username Menu
Hovering over the logged in user name will offer you the ability to change:
Page 72
Personal Settings
Switch Networks (Option only available in Multi-Network Content Manager Edition)
Logout
Personal Settings
Selecting Personal Settings allows you to access personal information, manage passwords and set regional settings.
To change name, password or regional settings, fill in the appropriate fields or select the appropriate drop downs and select Save & Close at the
top of the page.
If you are using LDAP or Active Directory to administer Users, Roles and Workgroups, then some options may be ghosted.
The Administrator username is assigned by the system and cannot be changed by the user.
Switch Network
Users that have purchased the Multi-Network Content Manager can access multiple Hosted Networks sites from a single sign on.
When logging on to a Content Manager with a user account that is associated with multiple Hosted networks, the last logged-into network is
logged into.
The user can switch between networks by simply selecting the network required from the dropbox presented.
Logout
Select this option from the Menu Bar to log out of Scala Enterprise Content Manager.
Page 73

1. System Manual . . . . . . . ....

Transcription

Similar documents

SCALA INFOCHANNEL 5

Special offer for Expo 2015_050515

Scala Workflow

Our new Scala Laboratory furniture system

scala crash course

reading and breathing opera

The Wendy`s Company

Case Study – Project Tank und Rast – Scala SEEN MEDIA ISS

Panos - Scala