Installation Reference
Application Server 1.8.1 12-March-2009
Application Server 1.8.1 Installation Reference
Publication Information © 2014 Imagine Communications Corp. Proprietary and Confidential. Imagine Communications considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine Communications. All others uses are illegal. This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product.
Trademarks Product names and other brands (such as ADC™, D-Series™, Nexio®, Nexio® Insight, Nexio® Motion, PowerSmart®, Versio™) are trademarks or trade names of Imagine Communications or its subsidiaries. Microsoft® and Windows® are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies.
Contact Information Imagine Communications has office locations around the world. For domestic and international location and contact information see: http://www.imaginecommunications.com/contact-us/
Support Contact Information For domestic and international support contact information see:
Support Contacts: http://www.imaginecommunications.com/services/technical-support/ eCustomer Portal: http://support.imaginecommunications.com
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 2 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Contents
Contents About the Application Server and Clients ......................................... 5 Application Server ....................................................................................................................... 5 Client Applications ....................................................................................................................... 5 Installation Prerequisites ............................................................................................................. 6 Installation CDs ...................................................................................................................... 6 Customer-Provided/Loaded Components .............................................................................. 7 Computer Clock Synchronization across the System ............................................................. 7
Application Server Installation ........................................................... 8 Install Process Summary ............................................................................................................ 8 JRE 1.5 ........................................................................................................................................ 8 Install Java 2 Standard Edition Runtime Environment ........................................................... 8 Set System Variables .............................................................................................................. 9 Tomcat ...................................................................................................................................... 10 To Install Tomcat .................................................................................................................. 10 SQL Server 2005 Express ........................................................................................................ 10 Installing .NET Framework v2.0 ............................................................................................ 11 Install SQL Server 2005 Express SP2 (9.0.3042) ................................................................ 11 Install SQL Server Management Studio Express SP2 (9.0.3042) ........................................ 13 Configure SQL Server 2005 Express TCP/IP Settings ......................................................... 14 Application Server Installation Wizard....................................................................................... 15 Wizard Button Operation Reference ..................................................................................... 15 To Install the Application Server & Components .................................................................. 15 (If Required) To Remove an existing Application Server Installation ................................... 19 (If Required) To Modify an existing Application Server Installation ...................................... 20 (If Required) To Repair an Existing Application Server Installation ...................................... 20 Set up a Shared Proxy Folder ................................................................................................... 21 Set up a Monitored Folder ......................................................................................................... 21 Configure the Application Server .............................................................................................. 21 Start the Application Server ..................................................................................................... 22
Managing Storage Devices ............................................................. 23 Adding and Removing Storage Devices ................................................................................... 23 Configure Additional Telestream Factories ............................................................................... 23 (Optional) Multiple Pathfire Sources Delivering to Multiple Destinations .................................. 23 Transcode Server ................................................................................................................. 23 App Server ............................................................................................................................ 24 Automatic Ingest: System Configuration: Pathfire Config..................................................... 24 (Optional) Configuring Media Trimming .................................................................................... 26 (Optional) Configuring Proxy Generation from MDS or Video File Servers .............................. 27 To Specify Proxy Creation From MDS’ for all Video File Servers ........................................ 27 To Specify Proxy Creation From an MDS for a Specific Video File Server .......................... 28 Delete all media copies from a storage device volume............................................................. 29
Configuration Properties using the JSP Pages ................................ 31 Adding a New Property to a Configuration File ......................................................................... 31 To Access Configuration Files .............................................................................................. 31 To Add a Property ................................................................................................................. 32 To Remove a Property .......................................................................................................... 32 To Refresh the Display ......................................................................................................... 33
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 3 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Contents
Automatic Ingest Clients Installation ............................................... 34 About the Client Workstation .................................................................................................... 34 Installing .NET Framework v2.0 ................................................................................................ 34 Download .NET Components from Microsoft’s Website ....................................................... 34 To Install .Net Framework 2.0 ............................................................................................... 34 To Install Automation System Application Clients .................................................................... 35 To Install the Application Clients ........................................................................................... 35 To Uninstall the Application Client ........................................................................................ 36 (Optional) Review Application CFG File Settings ................................................................. 36 (Optional) Set a Default Application UserName & Password ............................................... 37 (Optional) Setting a New Application Server IP Address...................................................... 37 (Optional) Setting a New Communications Host Port ........................................................... 38 (Optional) Specify the Minimum Client Display Resolution Setting ...................................... 38 (Optional) Enable Automatic Ingest Error Logging ............................................................... 39 Installing the Contour Shuttle Pro2 ........................................................................................... 39 Installation and Setup ........................................................................................................... 39 Media Ingest Shuttle Pre-configured Controls ...................................................................... 40 Installing the LCP24 Panel ........................................................................................................ 40
Appendix A ...................................................................................... 42 Updating IP Addresses on Automation Servers ........................................................................ 42 Application Server Configurations ........................................................................................ 42 Transcode Server Configurations ......................................................................................... 47
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 4 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
About the Application Server and Clients
About the Application Server and Clients Application Server The Application Server comes standard with the following software components: Important: This document reflects system functionality available at the time of its release. Any subsequent changes to system functionality are addressed in follow-up addendums.
Tomcat J2EE applications are hosted on application servers, such as Tomcat. Tomcat is an open source, Java based application server that can be used on any operating system that supports Java. Computer programs written in Java can run on any platform type (including set-top boxes), as long as they contain a Java Virtual Machine.
Material Database Automation is designed to be database agnostic (its first version supports SQLServer). The material database can be populated or referenced by Automation components to maintain a consistent and persistent material database for program segment and commercial timings.
Application Server The Automation application server provides basic core services such as user management, media movement, storage management, database management, external system interfaces and resource management as well as other shared services. It is available with interfaces to external systems that support dynamic interaction that enable traffic and scheduling systems to request changes and status as well as enable operators to control play-out of remote equipment or efficiently manage centralized broadcast operations.
Client Applications The Client Workstations come standard with the following software components: Important: This document reflects system functionality available at the time of its release. Any subsequent changes to system functionality are addressed in follow-up addendums.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 5 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
About the Application Server and Clients
Automatic Ingest Automatic Ingest, a client-based media preparation application, offers a simple control panel and streamlined user interface to perform the automatic ingest of material from MDS’s, such as Vyvx. User Manager and System Configuration views provide system administrators with the tools necessary for configuring Automatic Ingest and creating user profiles and access.
CDF The Client Development Foundation (CDF Windows Forms) is required for the accurate rendering for Automatic Ingest application views. It is used by components to provide a standard Desktop interface for all applications, and to ensure compatibility with the Platform.
Installation Prerequisites Setting up the applications requires you have access to and/or have been provided the following…
Installation CDs applications are installed from the following installation Disk folders.
Disk#
This DISK Contains…
Folder
Disk 1: Automatic Ingest Installers 1.8
Application Server Installer
\AppServerInstaller1.8.1.X
Transcode Installer
\TranscodeServerInstaller 1.8.1.X
Client Installer
\ClientInstaller1.8.1.X Automation Client installer
Disk 2: Automation Support SW AI 1.8
CDF
\.CDF.Windows.Release. msi
Apache Tomcat
\Tomcat
Telestream Traffic Manager
\Telestream
Java 2 Standard Edition Runtime Environment
\Java
Pathfire DMG Master and DMG Transfer Service components
\Pathfire
Notification Agent
\NotificationAgent2.0.0.13 (includes installation documentation)
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 6 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Disk#
Disk 3: Automatic Ingest Documentation
About the Application Server and Clients
This DISK Contains…
Folder
FlipFactory 5.1 SP1-5
\Third Party SW Patches
.NET Framework version 2.0 Redistributable
\dotNET Framework version 2.0 Redistributable
Applications Server Install
\AI 1.8.1 Documentation
Transcode Server Install Automatic Ingest Operations AI System Administration Reference Automatic Ingest Release Notes Recovery Guide Security Plan Automation System Specification j2se-1_5_0thirdpartyreadme.txt
\Third Party SW Licenses
jdk-1_5_0_05-license.txt jTDS_license.txt LICENSE-2_0.txt NOTICE.txt
Customer-Provided/Loaded Components The following components are provided by the customers… Component
Description
Adobe Acrobat Reader
Download from Adobe. Used for reading PDF documents. This software is installed on all system Windows-based computers.
Microsoft Windows Operating System
If customer supplied hardware, then customer supplied OS. This software is installed on all system Windowsbased Workstation computers.
Computer Clock Synchronization across the System Ensure the clocks on the Device Controller, Application Server, Transcode Server, and Client Workstations are synchronized. If they are not, operators may observe issues such as logs and messages exhibiting inaccurate timestamps.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 7 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
Application Server Installation Install Process Summary Perform all of the install processes below in the order specified on the application server. Ensure that all the requirements in the Requirements section are met before beginning. Skipping any process or performing process steps out of order can cause the installation to fail. 1) Review the AI Application Release Notes: Before beginning the installation, please read the Release Notes for the current version of the Automatic Ingest (AI) application. 2) Install JRE 1.5 3) Install Tomcat 4) Install SQL Server 2005 Express 5) Install the Automatic Ingest server software. 6) Set up a Shared Proxy Folder 7) Set up a Monitored Folder 8) Configure the Application Server 9) Start the Application Server Contact Technical Support if you encounter any errors or problems during installation.
JRE 1.5 This procedure outlines the installation of the Java 2 Standard Edition Runtime Environment (SUN JS2 JRE 1.5.0.05) on the D:\ drive of the Application Server.
Install Java 2 Standard Edition Runtime Environment Step
Action
1
From DISK 2: H-Class Support SW AI 1.8, navigate to \Java and then click on jre-1_5_0_05-windows-i586-p.exe. The Sun Wizard Preparing Setup dialogs appear. Once the setup preparations conclude, the Welcome screen briefly appears and then the License Agreement screen appears.
2
On the License Agreement screen… Select “I accept the terms of the license agreement”
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 8 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Application Server Installation
Action Then select Next.
3
On the ‘Setup Type’ screen, select Custom.
4
On ‘Custom Setup screen select Change.
5
On Change Destination screen modify the install path to install to D:\Java\jre1.5.0_05
6
Select OK. Returns to Custom Setup screen.
7
Select Next.
8
On the Browser Registration screen, leave Internet Explorer checked and select Next.
9
On the ‘Ready to Install’ screen, select Next. An Install status screen appears with a progress bar. On completion an “Install Complete’ screen appears.
10
On the Install Complete Screen, select Finish
Set System Variables Use this procedure to set new System variables on the Application Server computer.
Step
Action
1
From the Microsoft Desktop select Start > Control Panel > System
2
On the System Properties screen select the Advanced Tab
3
From the Advanced display select Environment Variables. The Environment Variables display is comprised of two dialogs: User variables and System variables
4
Beneath the System variables dialog select New. A dialog appears.
5
In the New System Variable dialog, enter: Variable Name = JAVA_HOME
(case sensitive)
Variable Value = path to the JRE installation (i.e. D:\Java\jre1.5.0_05) 6
On the New System Variable dialog, click OK.
7
On the Environment Variables display, click OK.
8
On the System Properties screen, click OK.
9
Close the Control Panel display
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 9 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
Tomcat To Install Tomcat Loading Tomcat Step
Action
1
From DISK 2: H-Class Support Software Installation, copy /Tomcat/ jakarta-tomcat-5.5.12.exe to a temporary folder on the AppServer.
2
Run the jakarta-tomcat-5.5.12.exe and accept all defaults (login is admin, no password). Confirm: The install directory is D:\Tomcat
3
On the last screen, select “run Apache Tomcat”. Tomcat automatically starts.
4
Point your web browser to http://localhost:8080. A "Congratulations" page should appear.
5
Stop the Tomcat server. Browse to: control panel\admin tools\services, select Tomcat, and click Stop Service.
6
Once the install is confirmed complete, remove (delete) the directory: \webapps\root
Optimizing Tomcat’s Memory Allocation For optimum performance, use this procedure to ensure Tomcat’s memory allocation is configured for 1-1.5GB. Step
Action
1
Go to D:\Tomcat5.5\bin, and double-click tomcat5w.exe.
2
Select the Java tab.
3
Set the Initial memory pool (in MB). Enter 1024.
4
Set the Maximum memory pool (in MB). Enter 1536.
5
Click OK to close the Apache Tomcat properties window.
SQL Server 2005 Express Automatic Ingest uses its own database for storing content, media, ingest requests, purge requests, and status information. SQL Server 2005 Express is used as the database engine, and is installed and run on the same system (application server) as the Automatic Ingest server application. The instructions below explain how to install and setup the database component for use with Automatic Ingest. Note: Although Automatic Ingest can be configured to connect to different database engines or engines installed on other systems, the above configuration is the only
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 10 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
supported and recommended configuration. If another configuration is necessary for some reason, please contact Technical Support to for alternate options.
Requirements Microsoft .NET Framework 2.0 (32bit)
Requires Windows Installer 3.1 which is included in Windows Server 2003 SP1.
Install Process Summary Perform all of the install processes below in the order specified on the application server. Ensure that all the requirements in the Requirements section are met before beginning. Skipping any process or performing process steps out of order can cause the installation to fail. 1) Install Microsoft .NET Framework 2.0 (32bit) 2) Install SQL Server 2005 Express SP2 (9.0.3042) 3) Install SQL Server Management Studio Express SP2 (9.0.3042) 4) Configure SQL Server 2005 Express TCP/IP Settings Contact Technical Support if you encounter any errors or problems during installation.
Installing .NET Framework v2.0 Automatic Ingest requires the Microsoft .NET Framework 2.0 (32bit) utility be downloaded from Microsoft’s website and then installed on the Application Server. Note: Requires Windows Installer 3.1 which is included in Windows Server 2003 SP1. Step
Action
1
Access Microsoft’s website: www.Microsoft.com and download Microsoft .NET Framework 2.0 (32bit) to the Application Server.
2
From its local download location, double click on dotnetfx.exe.
3
This starts the .NET Installation Wizard.
4
Follow the system prompts to install. Accept all defaults. The application is installed on your computer. Important: The customer must accept any license agreement terms presented during the install. (i.e. the .NET Framework EULA that pops up when dotnetfx.exe is executed )
Note: To remove .Net Frameworks, from your Desktop select Start>Settings>Control Panel>Add/Remove Programs, and then select to remove .Net Frameworks.
Install SQL Server 2005 Express SP2 (9.0.3042) In general, select all defaults except: •
On the feature selection page, expand the Database Services, select Data Files and click Browse to set the path to D:\SQLServerData\.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 11 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
•
Application Server Installation
On the authentication mode page, select Mixed Mode and set the password to “” or “123”.
Step
Action
1
Run SQLEXPR32.EXE.
2
Wait for the setup files to be extracted.
3
Check the box and click Next to accept the licensing terms and conditions.
4
Wait for the prerequisites to be installed.
5
Click Next after the prerequisites are installed.
6
Wait for the system configuration to be checked.
7
Click Next at the welcome screen.
8
Click Next after verifying that all (13) system configurations check out successfully.
9
Click Next after confirming the registration information. (advanced config should be hidden)
10
Expand the Database Services feature, select Data Files and click Browse to set it’s installation path to D:\SQLServerData\, then click Next on the feature selection page.
11
Select Mixed Mode and set the password to “” or “123”, then click Next on the authentication mode screen.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 12 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
Step
Action
12
Click Next to accept the default Configuration options.
13
Click Next to accept the default Error and Usage Reporting Settings.
14
Click Install on the Ready to Install page.
15
Wait for the component to complete setup.
16
Click Next after confirming that setup finished for all components.
17
Wait for the Microsoft SQL Server to be installed.
18
Click Finish after reviewing the Completing Microsoft SQL Server Setup page.
Install SQL Server Management Studio Express SP2 (9.0.3042) In general, select all defaults. Step
Action
1
Run SQLServer2005_SSMSEE.msi.
2
Click Next at the welcome screen.
3
Check the box and click Next to accept the licensing agreement.
4
Click Next after confirming the registration information.
5
Click Next on the feature selection page.
6
Click Install on the Ready to Install page.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 13 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
Step
Action
7
Wait for the Microsoft SQL Server Management Studio Express to be installed.
8
Click Finish after reviewing the Completing Microsoft SQL Server setup page.
Configure SQL Server 2005 Express TCP/IP Settings Step
Action
1
Run Start>Programs>Microsoft SQL Server 2005\Configuration Tools\SQL Server Configuration Manager.
2
Expand the SQL Server 2005 Network Configuration and select Protocols for SQLEXPRESS in the left pane.
3
Double-click the TCP/IP protocol in the right pane to open the TCP/IP properties window.
4
In the Protocol tab, set the Enabled property to Yes.
5
In the IP Addresses tab, clear (blank) all the TCP Dynamic Ports properties and set all the TCP Port properties to 1433.
6
Click OK to save set setting changes, and click OK to acknowledge the notice.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 14 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
Step
Action
7
Select the SQL Server 2005 Services in the left pane and then rightclick SQL Server in the right pane and select Restart to restart the service.
8
Ensure the SQL Server service is running and the SQL Browser service is stopped.
9
Close SQL Server Configuration Manager.
Application Server Installation Wizard This section provides the instructions for using the AppServerInstall Wizard to…
Install the Application Server components: Tomcat, SQL Database, Application Server software Remove/Uninstall an Existing Installation Modify an Existing Installation Repair an Existing Installation
Wizard Button Operation Reference This table lists buttons available across the Install Wizard screens. Not all buttons are available on all screens or dialogs. Button
When Active and Available on a screen, select…
Back
Back to go back one screen.
Cancel
Cancel to abort the operation.
Change
Change to change an installation path.
Finish
Finish to conclude the operation.
Install
Install to start the application installation.
Next
Next to accept the entry and move to the next operation screen.
OK
OK to accept an entry or operation and continue.
Print
Print to print the specified information to a configured printer.
To Install the Application Server & Components Installation Notes:
For any entries that do not apply to the specific system configuration, accept the default value settings. For example, if there is no HD Broadcast Server, the HD Broadcast Server IP address should be left as 0.0.0.0. Similarly, if
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 15 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
there is only 1 Pathfire DMG Server, the Pathfire2 and 3 IP addresses should be left as 0.0.0.0.
The default configuration for the system assumes only 1 (Commercial) transcode server for processing commercial content and 1 (either the same or different) transcode server for processing Pathfire Content and that all Pathfire content. It also assumes that all SD content goes to one VFS and all HD content goes to another. Any differences from the default configuration will need to be addressed by modifying the pathfire configuration after the application server is installed and running.
Pathfire Device Names refer to the device names specified in the Pathfire Transfer Service on the (Pathfire) transcode server (used for processing Pathfire content). Step
Action
1
Ensure the Tomcat server is stopped. -
If running as a service: Browse to: control panel\admin tools\services, select Tomcat, and click Stop Service.
-
If running in standalone mode: Select the command prompt window where Tomcat is running – press CTRL+C to stop tomcat.
2
On DISK 1: H-Class Installers AI 1.8 disk, navigate to the \AppServerInstaller1.8.0.X folder, and copy this folder to the application server.
3
Navigate to the \AppServerInstaller1.8.0.X folder on the application server, and double-click Setup.Exe. This starts the Application Server Installation Wizard. The Preparing Setup Screen appears displaying a progress bar. Once the setup preparations conclude, the Welcome Screen appears.
4
On the Welcome screen, select Next.
5
On the License Agreement screen… Select “I accept the terms of the license agreement” (Option) Select Print to printout a copy of the License Agreement. Then select Next.
6
On the Select Tomcat Location screen, perform one of the following operations: Accept the Default Location (recommended) a) Select Next to accept the default location: “Install H-Class Application Server to: D:\tomcat” b) The ‘Additional Information’ screen appears. (OR Option) Specify a New Location Path To install Tomcat to a different location… a) Select Change. The Choose Folder dialog appears.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 16 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Application Server Installation
Action
b) On the Change Path dialog specify a new path. c) Select OK. Returns to the Select Tomcat Location screen. d) On the Select Tomcat Location screen, select Next to accept the new path and progress to the ‘Additional Information’ screen. 7
The Additional Information screen is displayed. Note 1: The Additional Information page shown below assumes the system is using separate VFS's for SD and HD content, 3 Pathfire DMG servers, and only 1 transcode server for Pathfire content. If the actual system has a different Pathfire configuration, the Pathfire configuration may needed to be updated again after the installation. Note 2: Omneon MDS IP Address is not currently listed. It must be added from the AI Home tab > System Administartion > /Ingest Service/DestinationMapPropertiesList.
On the Additional Information screen… a) Specify names and IP addresses of factories and servers set up during Transcoder installation and setup.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 17 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Application Server Installation
Action Entry syntax must match exactly and is case sensitive. Check to ensure there are no leading or trailing spaces. If an entry is not known or used/needed, leave the default value. Do NOT reuse/duplicate values. b) Once all entries are made, select Next. The ‘Ready to Install’ screen appears. Important: Specifications for the entries are required or the wizard will not advance. At minimum the system requires entries for Broadcast Server IP Address, Transcode Server IP Address, and Transcode Server Host Name.
8
-
Standard default settings are provided for the factory and account names.
-
If required, to verify hostnames and IP Addresses, go to the specific system, launch a COMMAND window, and perform an IPCONFIG -all" to view configured entries.
On the ‘Ready to Install’ screen, select Install. The ‘Setup Status’ screen appears with progress bar. On completion, the ‘Database Server Login’ screen appears.
9
On the Database Server Login Screen (an example screen is provided for reference)…
a) Specify the location and access information for the SQL database: -
SQL Server Location: Customer provided IP Address for the FileServer/DB machine.
-
Port: 1433 (current default)
-
Database Name: hrs (current default)
-
Select the appropriate database option:
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 18 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Application Server Installation
Action o
To create a new database, Enable (check) Create a New HRS database.) Default setting.
o
To remove an existing database, Enable (check) Delete database, and recreate a new HRS database.
o
To modify the settings of an existing empty database, Enable (check) Modify an empty database.
o
To upgrade an existing database from the previous release version to this version, Enable (check) Upgrade existing database.
-
Login ID: Specify the appropriate username which has the correct permissions for the given database and the desired actions. (For Example: sa)
-
Password: Specify the appropriate password which has the correct permissions for the given database and the desired actions. (For Example: ‘leave the entry blank’)
b) Then select Next About the Notification Agent If installing the SQL database on a File Server, after finalizing this installation, install the Notification Agent on the File Server. This application and its installation instructions are located on the Installation DISK 2: H-Class Support Software under /NotificationAgent 2.0.0.13. If installing the SQL database on the Application Server, the Notification Agent application is not required. 10
A message dialog appears indicating: “Connection to Database Established”. On the dialog box, select OK.
11
A message dialog appears indicating: “Database Created Successfully”. On the dialog box, select OK.
12
A message dialog appears: “New Database Tables Successfully Created!” On the dialog box, select OK. When the installation completes the InstallShield Wizard Complete screen appears.
13
On the InstallShield Wizard Complete screen, select Finish.
(If Required) To Remove an existing Application Server Installation This procedure is not required for the installation. It is provided here in case this operation should be needed. Step
Action
1
Navigate to the /AppServerInstaller 1.8.0.X folder on the application server, and double-click Setup.Exe. This starts the Application Server Installation Wizard. The Preparing Setup Screen appears displaying a progress bar. Once the setup preparations conclude, the Welcome Screen appears.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 19 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
Step
Action
2
On the Welcome screen… Select Remove and then Select Next. A message dialog appears requesting remove confirmation. Select Yes. The Setup Status screen appears with progress bar. The system removes all Application server components installed by this Wizard from the computer. On completion, the Uninstall Complete screen appears.
3
On the ‘Uninstall Complete’ screen, select Finish.
(If Required) To Modify an existing Application Server Installation This procedure is not required for the installation. It is provided here in case this operation should be needed. Step
Action
1
Navigate to the /AppServerInstaller 1.8.0.X folder on the application server, and double-click Setup.Exe. This starts the Application Server Installation Wizard. The Preparing Setup Screen appears displaying a progress bar. Once the setup preparations conclude, the Welcome Screen appears.
2
On the Welcome screen, select Modify and then select Next.
3
On the Select Features screen select (check) any additional features to install, and then select Next. The ‘Setup Status’ screen appears with progress bar. The Wizard installs all selected features. On completion, the Maintenance Complete screen appears.
4
On the ‘Maintenance Complete’ screen, select Finish.
5
Delete the previous hrs.log file which exists in the Tomcat folder.
(If Required) To Repair an Existing Application Server Installation This procedure is not required for the installation. It is provided here in case this operation should be needed. Step
Action
1
Navigate to the /AppServerInstaller 1.8.0.X folder on the application server, and double-click Setup.Exe. This starts the Application Server Installation Wizard. The Preparing Setup Screen appears displaying a progress bar. Once the setup preparations conclude, the Welcome Screen appears.
2
On the Welcome screen, select Repair and then select Next.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 20 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Application Server Installation
Action The ‘Setup Status’ screen appears with progress bar. The system reinstalls basic Application Server components. On completion, the Maintenance Complete screen appears. On the ‘Maintenance Complete’ screen, select Finish.
3
Set up a Shared Proxy Folder Set up a shared proxy folder on the Application Server, D: Drive. (Example: D:\Proxies) Step
Action
1
On Application Server, create a Proxies folder in the D: drive
2
Right mouse click on created Proxies folder and select Sharing and Security.
3
Select the sharing tab, select share this folder option.
4
Share name should default to the name of the folder, and maximum user limit allowed.
5
Select permissions button. Under permissions for everyone, select Full Control.
Set up a Monitored Folder Dub lists and Purge lists are created by the traffic department and copied to a configured folder on the file (DB) server or Application Server. This directory is monitored at a regular interval by the List Converter plugin for new files. Step
Action
1
Create a directory on the file server called \trafficservice and share it with “Full Control” (i.e. From within the “Sharing” tab, set permission for “Everyone” to “Full Control”.)
2
Map a local drive on the application server to the trafficservice share on the file server. (For example: “X: = \\fileserver_ip_address\trafficservice”) Note: Ensure ‘Reconnect at Log on’ is selected.
Configure the Application Server To use Automatic Ingest, requires the Application Server be configured to communicate properly with the devices involved. Use the Automatic Ingest Administration options to configure the Application Server:
Ingest Configuration Settings
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 21 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Application Server Installation
Telestream Configuration Settings Automatic Ingest Workflow Configuration Settings Storage Configuration User Settings and User Management
The procedures for performing these actions are detailed in the AI System Administration Reference.
Start the Application Server Once all configurations outlined in the sections have been made, on the Application Server computer start Application Server. Step
Action
1
On the Desktop, click the Application Server icon.
This starts Application Server in a standalone mode (a minimized window appears). The installer/admin should ensure this window is minimized at all times. 2
Access Application Server Open a browser to http://localhost:8080/hrsApp to verify that the server is running.
3
-
If the install was successful, the Application Server home page appears.
-
If an error page appears, then one of the configurations above is incorrect.
When prompted, login to the system with your UserName and Password. (entries are case sensitive) This access requires System Administrator level permissions. Example: user name: SysAdmin / password: sysadmin
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 22 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Managing Storage Devices
Managing Storage Devices Adding and Removing Storage Devices For details on adding and/or removing storage devices see AI v1.8.1 System Administration Reference, section Configuring Storage Devices. Note: If configuring more than 1 Video File Server is required, then – in addition to creating a storage device on the JSP – the installation requires creating a separate factory by using Suite Manager to edit the FactoryConfig and TelestreamConfig entries. Rule: Always match the case sensitive volume on the actual device in all configured locations (Note: The slash direction may vary: back slash in registry, forward slash in factory, and forward slash in app server).
Configure Additional Telestream Factories Note: If more than one Video File Server (VFS) configuration is necessary, please consult with a Customer Support Engineer (CSE) for assistance.
(Optional) Multiple Pathfire Sources Delivering to Multiple Destinations Automation Ingest system supports multiple transcode servers for transferring pathfire content from one or more source Pathfire DMG server to one or more destination video file servers. In other words, allows multiple Pathfire sources delivering to multiple destinations (still 1 destination per content). Note: Transcoding of all other content (other than Pathfire) can still only be done on a single transcode server. Pathfire content can also be done on that same server if desired. Support for processing other content via multiple transcode servers is planned for a future release.
Transcode Server Step
Action
1
Configuration on the Transcode Server. For details reference Transcode Installation Reference, section Setting up the FlipFactory Environment : Pathfire Changes : (Optional) Multiple Pathfire Sources Delivering to Multiple Destinations.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 23 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Managing Storage Devices
App Server Step
Action
1
On the Application Server, add the pathfire MDS and the 2 destination VFS's as storage devices on the appserver.
2
Configure all settings as appropriate.
Automatic Ingest: System Configuration: Pathfire Config Configure the pathfire configuration properties appropriately. To accommodate this, two of the have been updated and one new property has been added to Step
Action
1
From the Automatic Ingest System Configuration view, expand pathfire in the left hand navigation pane and from the expanded list select pathfireconfig Configuration entries for that selection appear in the right hand pane.
2
Confirm the following three entries properly specify the transcode servers available and define the logical mapping between source(s), the transcode server(s), the pathfire device(s) and the destination(s): destination_To_Pathfire_Device_Map: This property defines a mapping between the various pathfire destination devices and the actual destination video file servers by IP address. pathfire_Device_To_TranscodeServer_HostName_Map: This property defines a mapping between the various pathfire destination devices and the associated transcode server hostname. source_To_PathFire_Device_Map: This property defines a mapping between the various source pathfire DMG servers and the various pathfire destination devices
3
Confirm all other properties are correctly set, and then select Save. Note: If you make a change to any field entry, move to another entry in the list to ensure the Save button is enabled.
Pathfire Notes Note 1: A “pathfire destination device” is configured on the transcode server in the transfer.xml file of the pathfire configuration. Once configured correctly, they appear in the pathfire DMG client as a “destination” including both the device name and the transcode server host name. If they do not appear, there is probably a problem with the configuration and pathfire transfers will not work correctly. Although the pathfire destination device names only need to be unique on an individual transcode server, to avoid confusion we recommend to keep them unique amongst all servers. Ie. Pathfire Device 1 on transcode server 1 = T1PFD1 and Pathfire Device 1 on transcode server 2 = T2PFD1 Note 2: Pay careful attention to the values of the properties and the use of colon’s (:), equal’s signs (=) and comma’s. Incorrect values will result in failed jobs. Also make sure to match exactly when specifying the device and host names (spaces and case). Below are example system configurations using one or more source, destination, and transcode servers and the appropriate property settings values.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 24 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Managing Storage Devices
Note 3: In addition to the pathfire configuration values displayed below, all the configuration values in other parts of AI (ie. DestinationMapPropertyList, transfer.xml, skippy.properties, storage devices, etc.) need to set properly for transfers to succeed.
Example1: Single DMG, Single Transcode Server, Single VFS
destination_To_Pathfire_Device_Map: 10.0.0.10=T1PFD1 pathfire_Device_To_TranscodeServer_HostName_Map: T1PFD1=TXCD1 source_To_PathFire_Device_Map: 10.0.0.1=T1PFD1:10.0.0.2=T1PFD1 destinationExtensionMap: 10.0.0.10=mov
Example 2: Multiple DMG’s, Single Transcode Server, Single VFS
destination_To_Pathfire_Device_Map: 10.0.0.10=T1PFD1 pathfire_Device_To_TranscodeServer_HostName_Map: T1PFD1=TXCD1 source_To_PathFire_Device_Map: 10.0.0.1=T1PFD1:10.0.0.2=T1PFD1 destinationExtensionMap: 10.0.0.10=mov
Example 3: Multiple DMG’s, Multiple Transcode Servers, Single VFS
destination_To_Pathfire_Device_Map: 10.0.0.10=T1PFD1,T2PFD1 pathfire_Device_To_TranscodeServer_HostName_Map: T1PFD1=TXCD1:T2PDFD1=TXCD2 source_To_PathFire_Device_Map: 10.0.0.1=T1PFD1:10.0.0.2=T2PFD1 destinationExtensionMap: 10.0.0.10=mov
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 25 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Managing Storage Devices
Example 4:
destination_To_Pathfire_Device_Map: 10.0.0.10=T1PFD1:10.0.0.20=T2PFD1 pathfire_Device_To_TranscodeServer_HostName_Map: T1PFD1=TXCD1:T2PDFD1=TXCD2
source_To_PathFire_Device_Map: 10.0.0.1=T1PFD1:10.0.0.2=T2PFD1 destinationExtensionMap: 10.0.0.10=mov:10.0.0.20=mov
Example 5:
destination_To_Pathfire_Device_Map: 10.0.0.10=T1PFD1,T1PFD2:10.0.0.20=T2PFD1,T2PFD2
pathfire_Device_To_TranscodeServer_HostName_Map: T1PFD1=TXCD1:T1PDFD2=TXCD1:T2PFD1=TXCD2:T2PDFD2=TXCD2
source_To_PathFire_Device_Map: 10.0.0.1=T1PFD1,T1PFD2:10.0.0.2=T2PFD1,T2PFD2
destinationExtensionMap: 10.0.0.10=mov:10.0.0.20=mov
(Optional) Configuring Media Trimming Use this procedure to configure AI to ‘trim’ or ‘not to trim’ (default) the HI-Res media copy during the transcoding process. This setting only trims the slate. Note: To permit trimming of media from the specified Media Delivery System (MDS), Media Processing must be Enabled for that MDS. For details reference: Transcoder Installation Reference: Configuring the Broadcast_Factory: Selecting the Process/Analyze Components.
Step
Action
1
With Application Server running; on the Application Server computer
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 26 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Managing Storage Devices
Action open a browser to http://localhost:8080/hrsApp/ case sensitive)
2
(path is
When prompted, login to the system with your UserName and Password. (entries are case sensitive) This access requires System Administrator level permissions.
3
From the JSP page, click on "Storage" link
4
Locate a prospective Media Delivery System (MDS) by selecting Search for Storage Devices, and then click Find All.
5
On the selected MDS display, for the ‘Trim Required’ checkbox: -
Uncheck the box (Default) to specify no trimming. When a slate is sent by the MDS, adjusts the SOM to the first actual frame and passes this SOM to the ADC. That SOM is also used on the content database.
-
Check the box to enable trimming. Instead of marking the beginning of the clip, trims the beginning of the file so the Slate never reaches the video file server.
Important: Do not add this setting to any Pathfire MDS's. Trimming is not currently supported for Pathfire MDS's. 6
Click on the "Submit" button.
Additional Trimming Values For additional trimming values, frame offsets (offset_start and offset_end) settings must be modified in the Transcoder. For details, reference: Transcoder Installation Reference: (Optional) Modify MDS Frame Offsets.
(Optional) Configuring Proxy Generation from MDS or Video File Servers Use the following procedure to configure the system for generating proxies Globally from MDS, from a corresponding MDS for a specific VFS, or from a specific Video File Server (VFS1). This setting persists between AppServer restarts.
To Specify Proxy Creation From MDS’ for all Video File Servers Step
Action
1
Access Suite Manager
2
From the System tab, expand ingestservice in the left hand navigation pane.
3
From the expanded list select IngestProperties. Configuration entries for that selection appear in the right hand pane.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 27 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Managing Storage Devices
Step
Action
4
Review entries and, if necessary, make any changes as appropriate.
5
Proxyfrommds Set "proxyfrommds" to true. Depending on a station’s workflow requirements, this system wide setting is available to specify the generation of proxies from the MDS devices or from the Video File Servers for all ingests. Important: If enabled, this setting supersedes all other ’proxy creation from MDS’ settings. -
false: Create a proxy from a video disk source (i.e. from a high-res copy).
-
true: Create a proxy from an MDS Source. (This setting supersedes all other proxy generation entry settings.)
Note: A proxy is generated only if a request is made (either by selecting the checkbox during a force ingest or by setting the proxy flag in the dublist). 6
Select Save, and then Ok when prompted. Note: If you make a change to any field entry and then move to another list entry without selecting Save, the system prompts to Save or Cancel the change.
To Specify Proxy Creation From an MDS for a Specific Video File Server Important: Currently, this is only valid for Omneon Video File Servers. Step
Action
1
With Application Server running; on the Application Server computer open a browser to http://localhost:8080/hrsApp/ (path is case sensitive)
2
When prompted, login to the system with your UserName and Password. (entries are case sensitive) This access requires System Administrator level permissions. Example: user name: SysAdmin / password: sysadmin
3
From the JSP page, click on "Storage" link
4
Click on "Search for Storage Devices"
5
Click the "Find All" button
6
Click on the Edit image/link for the Video File Server (VFS) under consideration. (Currently, only Omneon VFS is supported for this function.)
7
On the selected VFS display, for the ‘Proxy NOT Supported’ checkbox: -
Check the box (Default) to indicate the VFS does not support proxy creation, so the proxy must be generated by the MDS.
-
Uncheck the box to indicate the VFS supports proxy creation, so the proxy can be generated by the VFS. (Currently, only Omneon
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 28 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Managing Storage Devices
Action VFS is supported for this function.) Requirement: For this operation to work, the "proxyfrommds" tag in IngestProperties must be set to false (Suite Manager> Systems tab under /IngestService/ IngestProperties). Note: A proxy is generated only if a request is made (either by selecting the checkbox during a force ingest or by setting the proxy flag in the dublist).
8
Click on the "Submit" button
Delete all media copies from a storage device volume When a volume is removed (from storage jsp or UI) and saved, the volume is deleted from the Database. If there are media copies on the volume the save action will fail. To delete the device volume the media copies must first be removed. Step
Action
1
To remove the media copies, search the device in the storage jsp and select the edit option. For each volume there will be a link to generate media removal events.
2
Select Generate Media Removal Event If there are active jobs (ingest/purge) associated with any media copy, a media removal event won’t be generated for that media copy. For others, media removal events are generated.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 29 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Managing Storage Devices
Step
Action
3
To remove the media copies that have active jobs cancel the active jobs or allow them to complete and then again generate the removal events.
4
When a storage device is deleted, if there are media copies associated with it, the delete action will fail. In that case, follow the procedure mentioned in step 1-3 to remove all the media copies.
5
To generate media removal events for media copies separately, find the device using the storage jsp and select the view link. Beside each media there will be a link to generate media removal event. If there is no active purge/ingest job associated with it, the event will be generated.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 30 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Configuration Properties using the JSP Pages
Configuration Properties using the JSP Pages Adding a New Property to a Configuration File If required, additional properties can be added to any configuration file using the JSP pages on the Application Server. The procedure for adding a property is the same for all configuration files.
To Access Configuration Files Step
Action
1
With Application Server running; on the Application Server computer open a browser to http://localhost:8080/hrsApp/ (path is case sensitive)
2
When prompted, login to the system with your UserName and Password. (entries are case sensitive) This access requires System Administrator level permissions. Example: user name: SysAdmin / password: sysadmin
3
From the JSP page, click on "Configuration Manager" link. This displays a list of links to available configuration files.
4
Select the required configuration file link. This opens the parameter
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 31 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Configuration Properties using the JSP Pages
Action settings for that configuration file. (For example: adc100\adc100config)
To Add a Property Adding a property is done in the Operations section of the configuration file update screen. This section is located below the Attributes section.
Step
Action
1
Enter the new Property Name. Generally the Property Name could be any string of characters, but for some configuration files, certain rules must be followed.
2
Enter the Property Value for the new property. The format for the specific configuration file property value can be seen in the Suite Manager entry for the specified configuration file.
3
Enter the Property Type. The typical property type entry (e.g. java.lang.String) for the specific configuration file can be seen on the JSP pages for the specified configuration file. This field is case-sensitive.
4
Click Add.
5
Click Save. The property can now been seen in the Attributes section of the configuration file update screen and in the Suite Manager entry for the specified configuration file.
To Remove a Property Removing a property is done in the Operations section of the configuration file update screen. Step
Action
1
Enter the exact Property Name to be removed.
2
Click Remove.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 32 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Configuration Properties using the JSP Pages
Step
Action
3
Click Save. The property is now removed from the App Server and the removal is reflected in the Suite Manager entry for the specified configuration file.
To Refresh the Display If a change is made to a Config file using Suite Manager, the entry will not automatically appear on the App Server unless the App server display is refreshed. To ensure all current property settings are displayed, select Refresh from the Operations section of the configuration file update screen.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 33 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Automatic Ingest Clients Installation
Automatic Ingest Clients Installation About the Client Workstation System applications reside on the Client Workstations.
If purchased from as part of the AI system, then these workstations come preset with all required O/S and base applications.
If these workstations are provided by the customer, then the customer must confirm they meet the base system requirements as specified in About the Automation System: System Requirements: Client Components And Customer Supplied Components.
Installing .NET Framework v2.0 Clients require the following Microsoft utility and Security Update be downloaded from Microsoft’s website and then installed on the Client Workstation.
.NET Framework 2.0 (dotnetfx.exe) .NET Framework 2.0 Security Update (NDP 2.0 ASP.NET KB917283-x86.exe)
Download .NET Components from Microsoft’s Website Step
Action
1
Access Microsoft’s website: www.Microsoft.com
2
Search for and download the following .NET components to your local PC: - .NET Framework 2.0 (dotnetfx.exe) - .NET Framework 2.0 Security Update (NDP 2.0 ASP.NET KB917283-x86.exe)
To Install .Net Framework 2.0 Step
Action
1
From its local download location, double click on dotnetfx.exe.
2
This starts the .NET Installation Wizard.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 34 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Automatic Ingest Clients Installation
Step
Action
3
Follow the system prompts to install. Accept all defaults. The application is installed on your computer. Important: The customer must accept any license agreement terms presented during the install. (i.e. the .NET Framework EULA that pops up when dotnetfx.exe is executed )
Note: To remove .Net Frameworks, from your Desktop select Start>Settings>Control Panel>Add/Remove Programs, and then select to remove .Net Frameworks.
To Install Automation System Application Clients Use the following procedure to install System applications on a client computer. Installed System applications include: Resource Manager, Media Ingest Manager, and Suite Manager.
To Install the Application Clients Step
Action
1
On DISK 1: H-Class Installers AI 1.8 disk, navigate to /ClientInstaller1.8.0.X, and locate Setup.exe Note: If the installer finds a previous version of software, you must uninstall it first before proceeding.
2
Copy Setup.exe to a local folder so it is available later for repair or removal of the application client, if necessary. Note: It is recommended that the folder be named with the application and version.
3
Double-click Setup.exe.
4
On the Welcome screen, select Next.
5
On the License Agreement screen… Select “I accept the terms of the license agreement” (Option) Select Print to print out a copy of the License Agreement. Then select Next.
6
On the “Select Installation Folder” screen, perform one of the following operations: Accept the Default Location (recommended) a) Select Next to accept the default settings: Location: “e.g. C:\Program Files\ Corporation\Automatic Ingest 1.8.0.#\” Install for: Ensure it is set to Everyone b) The Communication Settings screen appears. (OR Option) Specify a New Location Path
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 35 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Automatic Ingest Clients Installation
Action To install the application client to a different location… a) Select Browse. The “Browse for Folder” dialog appears. b) Browse for a new folder location/path. c) Select OK. Returns to the “Select Installation Folder” screen. d) On the Choose Destination Location screen, select Next to accept the new path and progress to the Communication Settings screen.
7
On the Communication Settings screen enter the IP Address of the Application Server, and then select Next.
8
On the Ready to Install screen, select Install. The Setup Status screen appears with progress bar. On completion, the InstallShield Wizard Complete screen appears.
9
On the InstallShield Wizard Complete screen, select Finish.
To Uninstall the Application Client The following procedure is recommended when it is necessary to remove the application on a client computer, such as prior to installing a new version of the client. It can also be used if you feel you have made a mistake during the installation or just want to remove the applications from the computer. Warning: Use this procedure to remove the applications. Do not use the Windows Control Panel Add/Remove program as it does not completely remove the applications and may impede the ability to reinstall the applications.
Step
Action
1
On each application client PC, navigate to the local folder where Setup.exe was copied during the installation.
2
Double-click on Setup.exe
3
Select radio button: Remove
4
Select Next
5
Confirm removal of the application by clicking Yes
6
Click Finish. The applications are removed from the computer.
7
If required, delete the folder where the client application was located: ”(e.g. Delete C:\\ Clients)
(Optional) Review Application CFG File Settings Before running any client for the first time, you can review and, if required, edit the application configuration files. Step
Action
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 36 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Automatic Ingest Clients Installation
Step
Action
1
Go to the install location on you Computer (Default location is: C:\Program Files\\Automatic Ingest)
2
Locate the application configuration files. Note: These files currently appear with an .config extension. Look for a file description type as ‘Config File’.
3
Use a text editor (such as TextPad or WordPad) to open a configuration file. (e.g. AutomaticIngest.exe.config)
4
Within the configuration file confirm the following: “CommunicationsHostIPAddress" to the App Server IP Address (e.g. 128.181.5.500)
(Optional) Set a Default Application UserName & Password To speedup staff access entry, a station may want client applications to always launch using a specific User name and Password. Step 1
Action Go to the install location on your Computer (Default location is: C:\Program Files\\ Automatic Ingest)
2
Locate the application configuration files. Note: These files currently appear with an .config extension. Look for a file description type as ‘Config File’.
3
Use a text editor (such as TextPad or WordPad) to open a configuration file. (e.g. AutomaticIngest.exe.config)
4
To set a default login and password for an application, within each application’s config file modify the two entry keys located under and then : Update the default values to the desired username and password. These can be the same for all applications or unique to each application or each client station. Important: This requires the specified user(s) be already set up in Suite Manager.
(Optional) Setting a New Application Server IP Address As required, a station may need to point the clients to a different App Server IP address. Step
Action
1
Ensure that all the client applications are closed before moving to next step.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 37 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Automatic Ingest Clients Installation
Step
Action
2
Go to the install location on you Computer (Default location is: C:\Program Files\\ Automatic Ingest)
3
Locate the application configuration files. Note: These files currently appear with an .config extension. Look for a file description type as ‘Web Configuration File’.
4
Use a text editor (such as TextPad or WordPad) to open a configuration file. (e.g. AutomaticIngest.exe.config)
5
To change the App Server IP Address for a application, modify the entry key located under and then within each application’s config file: Note: The initial App Server IP address setting is done from the Client Installation Wizard.
(Optional) Setting a New Communications Host Port As required, a station may need to point the clients to a different Communications Host Port on the Application Server. Step
Action
1
Ensure that all the client applications are closed before moving to next step.
2
Go to the install location on you Computer (Default location is: C:\Program Files\\ Automatic Ingest)
3
Locate the application configuration files. Note: These files currently appear with an .config extension. Look for a file description type as ‘Web Configuration File’.
4
Use a text editor (such as TextPad or WordPad) to open a configuration file. (e.g. AutomaticIngest.exe.config)
5
To change the App Server IP Port for a application, modify the entry key located under and then within each application’s config file: Note: The default setting for this parameter at initial client installation is 4445.
(Optional) Specify the Minimum Client Display Resolution Setting Setting the desktop display to (1280 x 1024) resolution ensures all application operation buttons are viewable. Use standard Microsoft Windows procedures to set the desktop display resolution. Step
Action
1
From the Desktop select Start>Control Panel, then double click on the
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 38 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Automatic Ingest Clients Installation
Action Display icon. OR Right click on an empty area of the Microsoft Windows desktop, and then from the popup menu select Properties.
2
From the Display Properties dialog, select the Setting tab.
3
(Optional) Use the Screen Resolution slide to set the screen resolution to 1280 x 1024.
4
Select Apply. The display resets itself to the new setting.
5
Click Ok to close the dialog.
(Optional) Enable Automatic Ingest Error Logging Step
Action
1
Ensure that all the client applications are closed before moving to next step.
2
Go to the install location on you Computer (e.g. C:\Program Files\\ Automatic Ingest)
3
Locate the application configuration files. Note: These files currently appear with an .config extension. Look for a file description type as ‘Web Configuration File’.
4
Use a text editor (such as TextPad or WordPad) to open the configuration file ".Automation.UI.Client.exe.config".
5
Change 'enabled' value to 'true' or 'false' in the line below to enable/disable the log. ""
6
Save and close the file.
Installing the Contour Shuttle Pro2 The Contour Shuttle Pro2, can be used as the primary ingest tool for moving material into the transmission system. To provide this functionality, the device is used in conjunction with the Media Ingest Workstation.
This device can be configured to use most of the Media Ingest Device Control Interface (Dub Control) controls.
Installation and Setup Step
Action
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 39 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Automatic Ingest Clients Installation
Step
Action
1
Plug in ShuttlePro2 device to available usb port.
2
Execute cdi_shuttle_win_2.6.5.exe to install drivers.
3
Open ShuttlePro control panel: Start -> Contour Shuttle -> Shuttle Configuration.
4
Select ShuttlePro v2 tab.
5
Press “Options” button.
6
Select “Import settings”
7
Select “MediaIngestVer2.pref” setting file. Once the setting file is selected you should see MediaIngest as a listed item in the Application setting dropdown.
8
Once MediaIngest application has focus, the software control panel will listen to the shuttle controls.
Media Ingest Shuttle Pre-configured Controls The following controls are preset hard-coded keys to Media Ingest. Note: Do not reconfigure these controls.
F1 = PLAY F2 = JOG/FWD F3 = JOG/REV F4 = SHUTTLE/FFWD F5 = SHUTTLE/RRWD F6 = MARK IN F7 = MARK OUT F8 = STOP F9 = CUE SOM F10 = CUE EOM
For information on mapping available buttons, refer to Manufacturer documentation.
Installing the LCP24 Panel The LCP24 panel is supported in Automatic Ingest v1.8. It is configured for use using the LCP2Win proxy client. The LCP2Win application does not support simultaneous multi-session mechanism. Only one application can interact with it at the same time. Assumption: The LCP24 panel is cabled (serial connection) and plugged into the Media Ingest client workstation. Step
Action
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 40 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Automatic Ingest Clients Installation
Step
Action
1
Confirm the LCP2Win proxy client is installed. The default path where application is installed is “C:\Program Files\\LCP2Win”. If not, install it accepting all defaults.
2
Once installed, from desktop select Start>Programs>>lcp2win.
3
Select LCP2Win.exe. A session list dialog appears.
4
Select the Diag button. A Diagnostic window opens.
5
In the lower section of the pane, verify the serial port connection, and select the correct COM port connection of the computer.
6
Verify the LCP type.
7
From the pull-down menu, select the correct control panel.
8
Select the Start button to accept the changes.
9
From the list of sessions, select Media Ingest, and then select the Start button. This Launches LCP2Win proxy client, and the running application is minimized to an icon in the systems tray.
10
Press the Settings button on LCP24 Jog Shuttle control panel. A dialog appears on the screen with connect options.
11
Select "Connect Serial LCP Device."
Note: The following procedure can be used to create an easier way to restart LCP2Win, whenever it is necessary, by creating a shortcut in the startup folder. When the PC reboots, it will automatically launch LCP2Win, which will wait for the Media Ingest client to start, and automatically connect to it.
Step
Action
1
Create a new shortcut in C:\Documents and Settings\Administrator\Start Menu\Programs\Startup folder.
2
When prompted by the wizard to “Type the location of the item,” enter the following exactly as it is including all spaces and quotation marks: "C:\Program Files\\LCP2Win\LCP2Win.exe" "Media Ingest"
3
Click Next.
4
Click Finish.
System applications reside on the Client Workstations.
If purchased from as part of the AI system, then these workstations come preset with all required O/S and base applications. If these workstations are provided by the customer, then the customer must confirm they meet the base system requirements as specified in About the Automation System: System Requirements: Client Components And Customer Supplied Components.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 41 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Appendix A
Appendix A Updating IP Addresses on Automation Servers Internet Protocol (IP) addresses may need to be changed on occasion to satisfy an organization’s security requirements. This appendix contains instructions for updating automation software configurations as a result of those changes. The table below indicates the procedure(s) to follow for each type of change as well as the order for completion. Important: No jobs can be processing when changes are made to IP addresses. These changes must be made by a system administrator only. Some changes, as noted, may require the system to be rebooted. AS = Application Server
TS = Transcode Server
Type of IP Address
Procedure(s) to Follow in Order
Database File Server
Database file server’s IP address AS – ADC100 Configuration AS – Database File Server Configuration
MDS Device
TS – _Monitor Factory Destinations MDS device’s IP address AS – Storage Devices AS – MDS Configuration for the appropriate MDS AS – Ingest Service Destination Map Property List
Destination Device
Destination device’s IP address AS – Storage Devices AS – Ingest Service Destination Map Property List
Application Server Configurations Storage Devices All changes to storage device IP addresses are completed through the JSP pages. Step
Action
1
Log on to the Application Server as the system administrator.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 42 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Appendix A
Step
Action
2
Verify that no jobs are processing on the Application Server.
3
Select Storage.
4
Select Search for Storage Devices.
5
Search for the storage device by name or click Find All.
6
Locate the storage device to be updated, and click the Edit icon.
7
Update the IP address.
8
Click Submit to save the changes.
System Configurations ADC100 Configuration Use this section when changing the database file server’s IP address.
Step
Action
1
Log on to the Application Server as the system administrator.
2
Verify that no jobs are processing on the Application Server.
3
Select Configuration Management.
4
Select adc100\adc100config.
5
In the serverName field within Attributes, enter the new IP address for the database file server.
6
Click update.
7
Within Operations, click Save.
8
Restart the Application Server to cause the changes to take effective.
Ingest Service Destination Map Property List Use this section when changing IP addresses for MDS devices and/or destination devices.
Step
Action
1
Log on to the Application Server as the system administrator.
2
Verify that no jobs are processing on the Application Server.
3
Select Configuration Management.
4
Select ingestservice\DestinationMapPropertyList.
5
For each MDS, enter the new values in the Add section within Operations: a) Enter the Property Name following the example of previous entries (e.g. 128.181.6.43_ProgramContent and 128.181.6.43_CommercialContent).
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 43 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Step
Appendix A
Action b) Enter the Property Value by entering the new IP address of the destination server followed by a colon and the IP address of the Application Server. c) Enter the Property Type similar to the existing Property Type (e.g. java.lang.String).
6
Click Add.
7
After entering the new value in the Add section, enter the corresponding Property Name of the value that is being replaced in the Remove section.
8
Click Remove.
9
When all IP addresses have been added and removed, click Save.
MDS Configuration Important: If possible, change the IP address within FlipFactory before changing the MDS. If the IP address of the MDS has already been changed, update the AI system next and FlipFactory last. All changes to MDS device addresses are completed through the JSP pages. Pathfire
Step
Action
1
Log on to the Application Server as the system administrator.
2
Verify that no jobs are processing on the Application Server.
3
Disable the monitoring of the MDS storage device within the Application Server. a)
Select Storage.
b)
Select Search for Storage Devices.
c)
Search for the storage device by name or click Find All.
d)
Locate the storage device to be updated, and click OFF icon).
(Turn Monitoring
4
Click hrsApp Home to return to the Application Server Home Page.
5
Select Configuration Management.
6
Select pathfire\pathfireconfig.
7
Change the IP address in the destinationExtensionMap field.
8
Click update for that field.
9
Change the IP address in the destinationFactoryMap field.
10
Click update for that field.
11
Click Save.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 44 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Appendix A
Step
Action
12
Click hrsApp Home to return to the Application Server Home Page.
13
Re-enable the monitoring of the MDS storage device within the Application Server. a)
Select Storage.
b)
Select Search for Storage Devices.
c)
Search for the storage device by name or click Find All.
d)
Locate the storage device to be updated, and click ON icon).
(Turn Monitoring
Venaca This step is only necessary when there is an Omneon MDS configuration of the system and you are using FTP.
Step
Action
1
Log on to the Application Server as the system administrator.
2
Verify that no jobs are processing on the Application Server.
3
Disable the monitoring of the MDS storage device within the Application Server. a)
Select Storage.
b)
Select Search for Storage Devices.
c)
Search for the storage device by name or click Find All.
d)
Locate the storage device to be updated, and click OFF icon).
(Turn Monitoring
4
Click hrsApp Home to return to the Application Server Home Page.
5
Select Configuration Management.
6
Select storage\venaca\venacaconfig.
7
Change the IP address in the metaDataPath field.
8
Click update.
9
Click Save.
10
Click hrsApp Home to return to the Application Server Home Page.
11
Re-enable the monitoring of the MDS storage device within the Application Server. a)
Select Storage.
b)
Select Search for Storage Devices.
c)
Search for the storage device by name or click Find All.
d)
Locate the storage device to be updated, and click ON icon).
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 45 of 48
(Turn Monitoring
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Appendix A
Telestream Factory Configuration
Step
Action
1
Log on to the Application Server as the system administrator.
2
Verify that no jobs are processing on the Application Server.
3
Disable the monitoring of the MDS storage device within the Application Server. a)
Select Storage.
b)
Select Search for Storage Devices.
c)
Search for the storage device by name or click Find All.
d)
Locate the storage device to be updated, and click OFF icon).
(Turn Monitoring
4
Click hrsApp Home to return to the Application Server Home Page.
5
Select Configuration Management.
6
Select telestream\FactoryConfig.
7
For each factory, change the IP address in the Value field.
8
Click update for that field.
9
When all factories have been updated, click Save.
10
Click hrsApp Home to return to the Application Server Home Page.
11
Re-enable the monitoring of the MDS storage device within the Application Server. a)
Select Storage.
b)
Select Search for Storage Devices.
c)
Search for the storage device by name or click Find All.
d)
Locate the storage device to be updated, and click ON icon).
(Turn Monitoring
Database File Server Configuration The JDO Properties file needs to be updated when changes are made to the following: Database file server IP address Database username & password DB Port 1433 Step
Action
1
Browse to the following location in your install directory: \Tomcat 5.5\webapps\hrsApp\WEB-INF\classes\org\springframework\core\io
2
Double-click the JDO Properties file to open it in a text editor such as Notepad.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 46 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Appendix A
Step
Action
3
Change the appropriate data and select File > Save.
4
Restart the Application Server to cause the changes to take effective.
Transcode Server Configurations _Transcode Factory Destinations Use this section any time an MDS or destination device’s IP address changes.
Step
Action
1
On the Transcode Server, open FlipFactory.
2
Log in to the _Transcode factory.
3
Click Manager Factories.
4
Expand Factories.
5
Expand the factory to be modified (i.e., Proxy_Factory , Broadcast_Factory, Slate_Factory, Pathfire_Broadcast_Factory or AudioAnalysis_Factory).
6
Expand Products > Product > Destinations.
7
For Proxy_Factory, Slate_Factory, or AudioAnalysis_Factory, select Network Folder. For Broadcast_Factory or Pathfire_Broadcast_Factory, select the name of the server.
8
For Proxy_Factory, Slate_Factory, or AudioAnalysis_Factory, change the IP address in the Destination Folder field. For Broadcast_Factory or Pathfire_Broadcast_Factory, change the IP address in the Server Name field.
9
Click Save.
10
Modify any other factory destinations by repeating steps 5-9 in this procedure for each.
11
Close the Manage Factory window.
12
Click Logout.
_Monitor Factory Destinations Use this section any time an MDS or destination device’s IP address changes.
Step
Action
1
On the Transcode Server, open FlipFactory.
2
Log in to the _Monitor factory.
3
Click Manager Factories.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 47 of 48
Proprietary and Confidential Release, 12-March-2009
Application Server 1.8.1 Installation Reference
Appendix A
Step
Action
4
Expand Factories > Monitor_Factory > Monitors.
5
Select the name of the MDS device to be modified.
6
For Vyvx, change the IP address in the Monitored Folder field. For DG Systems, change the IP address in both the Server Name field and the Monitored Folder field.
7
Click Save.
8
Modify any other monitors by repeating steps 5-7 in this procedure for each.
9
Close the Manage Factory window.
10
Click Logout.
Cop yright © 2014 Im agine Communications C orp. Doc No: 802005-04
Page 48 of 48
Proprietary and Confidential Release, 12-March-2009
