
79
D13898.08
MAY 2009
TANDBERG
CONTENT SERVER
ADMINISTRATOR GUIDE
Table of
Contents
Introduction
Installation
Quick Setup
TCS
Administration
Backing up and
Restoring
Administrator
Settings
Conference
Setup
View
Conferences
Appendices
Overview of the process:
1.
Exporting a conference
Export the conference from the source Content Server. Clicking on
Export conference
starts a process where outputs served by the preconfigured
default media servers (Local IIS Web Server and Local Windows Media Streaming Server) and conference metadata are copied and packaged as a
signed proprietary bundled format, .tcb.
Once the .tcb file has been created on the source Content Server, it can be downloaded by the user to an external network location.
2.
Updating a conference
The .tcb file will exist on the source Content Server for a week from the date of exporting.
During that time it is possible to update the information
and outputs for this conference and to export ithe updated version of the conference again by clicking on
Update exported conference
. This will
replace the original export file with an updated one. After a week, the .tcb file will be automatically deleted from the source Content Server.
3.
Uploading a conference
To import a conference, the .tcb file needs to be uploaded to the destination TCS first. There are two ways of uploading the file:
•
through the web interface - for files under 2GB.
•
through Remote Desktop - for files over 2GB.
The TANDBERG Content Server web interface upload functionality checks the files inside the .tcb bundle, their structure and the signature of the
bundle and rejects invalid files. Files with incorrect extensions uploaded directly to the Content Server’s desktop will not even be displayed on the
Import Conference
page.
4.
Importing a conference
All uploaded conferences are listed on the
Import Conference
page. Conferences whose state is
Not imported
have had their .tcb files uploaded to
the Content Server, but have not been imported and therefore are not available for viewing. Clicking on
Import
next to the conference name will start
the process of unpacking the .tcb file. This might take a while, depending on file size.
Once the state of the conference changes to
Imported
, it is available for viewing from the Recorded Conferences page. The conference import file
can then be deleted from the
Import Conference
page, which deletes its .tcb file from disk (but does not affect the imported conference in Recorded
Conferences).
Limitations:
•
This functionality is available only to administrators; conference editors do not have privileges to export or import.
•
Conferences can be exported one at time, batch exporting and importing is not supported.
•
Conferences recorded with pre-S3.0 versions cannot be exported.
•
Conferences with pending outputs are not available for export.
•
Unicode characters in conference names are replaced with underscores when uploaded through the web interface. When a file with unicode
characters in conference name is placed directly in the Imports folder on the TCS desktop, the Import Conference page will not display it.
•
Distribution outputs (eg. Podcast producer) and files stored on external streaming servers are ignored and will not be exported.
•
File upload through the web interface will fail if due to poor network conditions the upload takes longer than 15 minutes.
•
Exporting and importing is not available when the TCS is out of disk space.
Exporting and Importing Conferences
Exporting and Importing Conferences Overview
About Exporting and Importing
Conferences can be copied from one Content
Server to other Content Servers. To do this,
use the export and import functionality
available in S3.3 or higher. For an overview of
this functionality, see
Exporting and Importing
Conferences Overview
.
For more details, see
•
Export Conference
•
Import Conference