Pinnacle Systems Interplay Central - 1.0 Installation Manual

Interplay® Central

Installation and Configuration Guide

Legal Notices

Product specifications are subject to change without notice and do not represent a commitment on the par t of Avid Technology, Inc.

This product is subject to the terms and conditions of a software license agreement provided with the software. The product may only be used in accordance with the license agreement.

Avid products or portions thereof are protected by one or more of the following United States Patents: 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601; 5,644,364; 5,654,737; 5,724,605; 5,726,717; 5,745,637; 5,752,029; 5,754,851; 5,799,150; 5,812,216; 5,828,678; 5,842,014; 5,852,435; 5,959,610, 5,986,584; 5,999,406; 6,038,573; 6,057,829, 6,069,668; 6,141,007; 6,211,869; 6,336,093, 6,532,043; 6,546,190; 6,596,031;6,728,682, 6,747,705; 6,763,523; 6,766,357; 6,847,373; 7,081,900; 7,403,561; 7,433,519; 7,441,193, 7,671,871; 7,684,096; D352,278; D372,478; D373,778; D392,267; D392,268; D392,269; D395,291; D396,853; D398,912. Other patents are pending.

Avid products or portions thereof are protected by one or more of the following European Patents: 0506870; 0635188; 0674414; 0752174; 0811290; 0811292; 0811293; 1050048; 1111910; 1629675. Other patents are pending.

Avid products or portions thereof are protected by one or more of the following United States Patents: 5,267,351; 5,309,528; 5,355,450; 5,396,594; 5,440,348; 5,467,288; 5,513,375; 5,528,310; 5,557,423; 5,577,190; 5,584,006; 5,640,601; 5,644,364; 5,654,737; 5,724,605; 5,726,717; 5,745,637; 5,752,029; 5,754,851; 5,799,150; 5,812,216; 5,828,678; 5,842,014; 5,852,435; 5,986,584; 5,999,406; 6,038,573; 6,141,007; 6,211,869; 6,532,043; 6,546,190; 6,596,031; 6,747,705; 6,763,523; 6,766,357; 6,847,373; 7,081,900; 7,403,561; 7,433,519; 7,555,557; 7,562,099; D352,278; D372,478; D373,778; D392,267; D392,268; D392,269; D395,291; D396,853; D398,912. Other patents are pending.

Avid products or portions thereof are protected by one or more of the following European Patents: 0506870; 0635188; 0674414; 0752174; 1111910; 1629675. Other patents are pending.

This document is protected under copyright law. An authorized licensee of JENNINGS may reproduce this publication for the licensee’s own use in learning how to use the software. This document may not be reproduced or distributed, in whole or in part, for commercial purposes, such as selling copies of this document or providing support or educational services to others. This document is supplied as a guide for [product name]. Reasonable care has been taken in preparing the information it contains. However, this document may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. does not accept responsibility of any kind for customers’ losses due to the use of this document. Product specifications are subject to change without notice.

The following disclaimer is required by Apple Computer, Inc.:

APPLE COMPUTER, INC. MAKES NO WARRANTIES WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING THIS PRODUCT, INCLUDING WARRANTIES WITH RESPECT TO ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.

The following disclaimer is required by Sam Leffler and Silicon Graphics, Inc. for the use of their TIFF library:

Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.

THE SOFTWARE IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

The following disclaimer is required by the Independent JPEG Group:

This software is based in part on the work of the Independent JPEG Group.

This Software may contain components licensed under the following conditions:

Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. This software is provided "as is" without express or implied warranty.

Permission to use, copy, modify, distribute, and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Daniel Dardailler not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Daniel Dardailler makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the suppor ting documentation for such software.

THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.

This product includes software developed by the University of California, Berkeley and its contributors.

The following disclaimer is required by Nexidia Inc.:

© 2010 Nexidia Inc. All rights reserved, worldwide. Nexidia and the Nexidia logo are trademarks of Nexidia Inc. All other trademarks are the property of their respective owners. All Nexidia materials regardless of form, including without limitation, software applications, documentation and any other information relating to Nexidia Inc., and its products and services are the exclusive property of Nexidia Inc. or its licensors. The Nexidia products and services described in these materials may be covered by Nexidia's United States patents: 7,231,351; 7,263,484; 7,313,521; 7,324,939; 7,406,415, 7,475,065; 7,487,086 and/or other patents pending and may be manufactured under license from the Georgia Tech Research Corporation USA.

The following disclaimer is required by Paradigm Matrix:

Portions of this software licensed from Paradigm Matrix.

The following disclaimer is required by Ray Sauers Associates, Inc.:

“Install-It” is licensed from Ray Sauers Associates, Inc. End-User is prohibited from taking any action to derive a source code equivalent of “Install-It,” including by reverse assembly or reverse compilation, Ray Sauers Associates, Inc. shall in no event be liable for any damages resulting from reseller’s failure to perform reseller’s obligation; or any damages arising from use or operation of reseller’s products or the software; or any other damages, including but not limited to, incidental, direct, indirect, special or consequential Damages including lost profits, or damages resulting from loss of use or inability to use reseller’s products or the software for any reason including copyright or patent infringement, or lost data, even if Ray Sauers Associates has been advised, knew or should have known of the possibility of such damages.

The following disclaimer is required by Videomedia, Inc.:

“Videomedia, Inc. makes no warranties whatsoever, either express or implied, regarding this product, including warranties with respect to its merchantability or its fitness for any particular purpose.”

“This software contains V-LAN ver. 3.0 Command Protocols which communicate with V-LAN ver. 3.0 products developed by Videomedia, Inc. and V-LAN ver. 3.0 compatible products developed by third parties under license from Videomedia, Inc. Use of this software will allow “frame accurate” editing control of applicable videotape recorder decks, videodisc recorders/players and the like.”

The following disclaimer is required by Altura Software, Inc. for the use of its Mac2Win software and Sample Source Code:

The following disclaimer is required by Ultimatte Corporation:

Certain real-time compositing capabilities are provided under a license of such technology from Ultimatte Corporation and are subject to copyright protection.

The following disclaimer is required by 3Prong.com Inc.:

Certain waveform and vector monitoring capabilities are provided under a license from 3Prong.com Inc.

The following disclaimer is required by Interplay Entertainment Corp.:

The “Interplay” name is used with the permission of Interplay Entertainment Corp., which bears no responsibility for Avid products.

This product includes portions of the Alloy Look & Feel software from Incors GmbH.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product may include the JCifs library, for which the following notice applies:

Avid Interplay contains components licensed from LavanTech. These components may only be used as part of and in connection with Avid Interplay.

This product includes FFmpeg, which is covered by the GNU Lesser General Public License.

This product includes software that is based in part of the work of the FreeType Team.

This software is based in par t on the work of the Independent JPEG Group.

This product includes libjpeg-turbo, which is covered by the wxWindows Library License, Version 3.1.

P41-RR02188 by the National Institutes of Health.

Portions relating to JPEG and to color quantization copyright 2000, 2001, 2002, Doug Becker and copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, Thomas G. Lane. This software is based in part on the work of the Independent JPEG Group. See the file README-JPEG.TXT for more information. Portions relating to WBMP copyright 2000, 2001, 2002 Maurice Szmurlo and Johan Van den Brande.

Permission has been granted to copy, distribute and modify gd in any context without fee, including a commercial application, provided that this notice is present in user-accessible supporting documentation.

This does not affect your ownership of the derived work itself, and the intent is to assure proper credit for the authors of gd, not to interfere with your productive use of gd. If you have questions, ask. "Derived works" includes all programs that utilize the library. Credit must be given in user-accessible documentation.

This software is provided "AS IS." The copyright holders disclaim all warranties, either express or implied, including but not limited to implied warranties of merchantability and fitness for a particular purpose, with respect to this code and accompanying documentation.

Although their code does not appear in gd, the authors wish to thank David Koblas, David Rowley, and Hutchison Avenue Software Corporation for their prior contributions.

Attn. Government User(s). Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or “commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.

Trademarks

003, 192 Digital I/O, 192 I/O, 96 I/O, 96i I/O, Adrenaline, AirSpeed, ALEX, Alienbrain, AME, AniMatte, Archive, Archive II, Assistant Station, AudioPages, AudioStation, AutoLoop, AutoSync, Avid, Avid Active, Avid Advanced Response, Avid DNA, Avid DNxcel, Avid DNxHD, Avid DS Assist Station, Avid Liquid, Avid Media Engine, Avid Media Processor, Avid MEDIArray, Avid Mojo, Avid Remote Response, Avid Unity, Avid Unity ISIS, Avid VideoRAID, AvidRAID, AvidShare, AVIDstripe, AVX, Axiom, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Boom, Bruno, C|24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8, Conectiv, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, Dazzle, Dazzle Digital Video Creator, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 003, DigiBase, DigiDelivery, Digidesign, Digidesign Audio Engine, Digidesign Development Partners, Digidesign Intelligent Noise Reduction, Digidesign TDM Bus, DigiLink, DigiMeter, DigiPanner, DigiProNet, DigiRack, DigiSerial, DigiSnake, DigiSystem, Digital Choreography, Digital Nonlinear Accelerator, DigiTest, DigiTranslator, DigiWear, DINR, DNxchange, DPP-1, D-Show, DSP Manager, DS-StorageCalc, DV Toolkit, DVD Complete, D-Verb, Eleven, EM, Euphonix, EUCON, EveryPhase, Expander, ExpertRender, Fader Pack, Fairchild, FastBreak, Fast Track, Film Cutter, FilmScribe, Flexevent, FluidMotion, Frame Chase, FXDeko, HD Core, HD Process, HDPack, Home-to-Hollywood, HYBRID, HyperControl, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, ISIS, IsoSync, iS9, iS18, iS23, iS36, ISIS, IsoSync, KeyRig, KeyStudio, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, Luna, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack, Massive Pack Pro, M-Audio, M-Audio Micro, Maxim, Mbox, Media Composer, MediaFlow, MediaLog, MediaMatch, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MicroTrack, MIDI I/O, Midiman, Mix Rack, MixLab, Moviebox, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, Nitris, NL3D, NLP, Nova, NRV-10 interFX, NSDOS, NSWIN, Octane, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Ozone, Ozonic, Painterly Effects, Palladium, Personal Q, PET, Pinnacle, Pinnacle DistanTV, Pinnacle GenieBox, Pinnacle HomeMusic, Pinnacle MediaSuite, Pinnacle Mobile Media, Pinnacle Scorefitter, Pinnacle Studio, Pinnacle Studio MovieBoard, Pinnacle Systems, Pinnacle VideoSpin, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, Pro Tools, QuickPunch, QuietDrive, Realtime Motion Synthesis, Recti-Fi, Reel Tape Delay, Reel Tape Flanger, Reel Tape Saturation, Reprise, Res Rocket Surfer, Reso, RetroLoop, Reverb One, ReVibe, Revolution, rS9, rS18, RTAS, Salesview, Sci-Fi, Scorch, Scorefitter, ScriptSync, SecureProductionEnvironment, Serv|LT, Serv|GT, Session, Shape-to-Shape, ShuttleCase, Sibelius, SIDON, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, Solaris, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, Strike, Structure, Studiophile, SubCap, Sundance Digital, Sundance, SurroundScope, Symphony, SYNC HD, Synchronic, SynchroScope, SYNC I/O, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, Titansync, Titan, TL Aggro, TL AutoPan, TL Drum Rehab, TL Everyphase, TL Fauxlder, TL In Tune, TL MasterMeter, TL Metro, TL Space, TL Utilities, tools for storytellers, Torq, Torq Xponent, Transfuser, Transit, TransJammer, Trigger Finger, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Velvet, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, VTEM, Work-N-Play, Xdeck, X-Form, Xmon, XPAND!, Xponent, X-Session, and X-Session Pro are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

Footage

Arri — Courtesy of Arri/Fauer — John Fauer, Inc. Bell South “Anticipation” — Courtesy of Two Headed Monster — Tucker/Wayne Atlanta/GMS. Canyonlands — Courtesy of the National Park Ser vice/Department of the Interior. Eco Challenge British Columbia — Courtesy of Eco Challenge Lifestyles, Inc., All Rights Reserved. Eco Challenge Morocco — Courtesy of Discovery Communications, Inc. It’s Shuttletime — Courtesy of BCP & Canadian Airlines.

Nestlé Coffee Crisp — Cour tesy of MacLaren McCann Canada. Saturn “Calvin Egg” — Courtesy of Cossette Communications. “Tigers: Tracking a Legend” — Courtesy of www.wildlifeworlds.com, Carol Amore, Executive Producer. "The Big Swell" — Courtesy of Swell Pictures, Inc. Windhorse — Courtesy of Paul Wagner Productions.

Arizona Images — KNTV Production — Courtesy of Granite Broadcasting, Inc., Editor/Producer Bryan Foote. Canyonlands — Courtesy of the National Park Service/Department of the Interior. Ice Island — Courtesy of Kurtis Productions, Ltd. Tornados + Belle Isle footage — Courtesy of KWTV News 9. WCAU Fire Story — Courtesy of NBC-10, Philadelphia, PA. Women in Sports – Paragliding — Courtesy of Legendary Entertainment, Inc.

News material provided by WFTV Television Inc.

Avid Interplay Central Installation and Configuration Guide • 9329-65180-00 Rev B• Created 10/17/11 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

If You Need Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Avid Training Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Interplay Central Middleware Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Load Balancing Dual-Server Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Interplay Central Playback Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Interplay Central Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

System Setup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Checklist: Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Gather Site Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Licensing Requirements and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing the Interplay Production License for Interplay Central . . . . . . . . . . . . 23

Verifying Interplay Central Licenses on iNEWS . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configure iNEWS for Integration with Interplay Central . . . . . . . . . . . . . . . . . . . 26

Editing SYSTEM.CLIENT.VERSIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Editing SYSTEM.CLIENT.WINDOWS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Setting up the Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 2 The Interplay Central Middleware Server. . . . . . . . . . . . . . . . . . . . . . . . . 31

Checklist: Set up Interplay Central Middleware Server. . . . . . . . . . . . . . . . . . . . . . . 32

Install the ISIS Client Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Install Avid Service Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Optional Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Install the Interplay Central Distribution Service. . . . . . . . . . . . . . . . . . . . . . . . . 38

Install the Interplay Central User Management Service. . . . . . . . . . . . . . . . . . . 40

Run the Interplay Central Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Checklist: Configure Interplay Central Middleware Server. . . . . . . . . . . . . . . . . . . . 46

Set up the Remote Host for ISIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Specify a Lookup Locator for Avid Service Framework. . . . . . . . . . . . . . . . . . . 48

Run DNS Tests against Hosts in the Network. . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configure System Settings for iNEWS Integration . . . . . . . . . . . . . . . . . . . . . . 49

Configure System Settings for Interplay Integration . . . . . . . . . . . . . . . . . . . . . 50

Creating a Cluster for User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Changing Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Set the Backup Location for User Management Database Files. . . . . . . . . . . . 53

Configuring the Application Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . 54

Deploying Another Certificate to the Middleware Server. . . . . . . . . . . . . . . . . . 57

Chapter 3 The Interplay Central Playback Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Checklist: Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Checklist: Set up Interplay Central Playback Server . . . . . . . . . . . . . . . . . . . . . . . . 59

The Wiring Diagram for the Interplay Central Playback Servers . . . . . . . . . . . . 60

Installing the Operating System and Interplay Central Playback Services . . . . 61

Copying the .iso File to the USB drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Accessing the BIOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Booting Server from USB drive and Running the Installer . . . . . . . . . . . . . 64

Configure the Interplay Central Playback Service. . . . . . . . . . . . . . . . . . . . . . . 66

Configure Preferences for Interplay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configure Preferences for ISIS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Configure the Load Balancer for the Playback Server . . . . . . . . . . . . . . . . . . . 71

The Master Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Defining a Master Node for Playback Nodes . . . . . . . . . . . . . . . . . . . . . . . 72

Confirming the Master Node’s Cluster List . . . . . . . . . . . . . . . . . . . . . . . . . 73

Adding a Node to an Existing Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Removing a Dead Node from an Existing Cluster . . . . . . . . . . . . . . . . . . . 74

Restart Interplay Central and ISIS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Retrieve Interplay Central Playback Service Logs . . . . . . . . . . . . . . . . . . . . . . 74

Changing Compression Level Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 4 The Mobile Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Connection Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Checklist: Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

iNEWS Configuration for Mobile Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Editing SYSTEM.CLIENT.MOBILE-VERSIONS . . . . . . . . . . . . . . . . . . . . . . . . 79

Editing SYSTEM.CLIENT.MOBILE-IDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Adding Mobile Devices to the iNEWS Configuration File. . . . . . . . . . . . . . . . . . 81

Install Interplay Central on the Blackberry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Modifying Your Phone’s Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Interplay Central Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Using This Guide

This guide is intended for all Avid®Interplay® Central administrators who are responsible for installing and configuring an Avid Interplay Central system. This guide describes product set up and configuration procedures related to core components and some third-party hardware or software, such as load balancers used in high availability set-ups.

For initial administration and maintenance, see the Avid Interplay Central Administration Guide.

Symbols and Conventions

Avid documentation uses the following symbols and conventions:

Symbol or Convention Meaning or Action

> This symbol indicates menu commands (and subcommands) in the

(Windows), (Windows only), (Macintosh), or (Macintosh only)

Bold font Bold font is primarily used in task instructions to identify user interface

Italic font Italic font is used to emphasize certain words and to indicate variables.

A note provides important related information, reminders, recommendations, and strong suggestions.

A caution means that a specific action you take could cause harm to your computer or cause you to lose data.

A warning describes an action that could cause you physical harm. Follow the guidelines in this document or on the unit itself when handling electrical equipment.

order you select them. For example, File > Import means to open the File menu and then select the Import command.

This symbol indicates a single-step procedure. Multiple arrows in a list indicate that you perform one of the actions listed.

This text indicates that the information applies only to the specified operating system, either Windows or Macintosh OS X.

items and keyboard sequences.

Symbol or Convention Meaning or Action

If You Need Help

Courier Bold font

Ctrl+key or mouse action Press and hold the first key while you press the last key or perform the

If You Need Help

If you are having trouble using your Avid product:

1. Retry the action, carefully following the instructions given for that task in this guide. It is especially important to check each step of your workflow.

2. Check the latest information that might have become available after the documentation was published:

- If the latest information for your Avid product is provided as printed release notes, they

are shipped with your application and are also available online.

- If the latest information for your Avid product is provided as a ReadMe file, it is

supplied on your Avid installation USB drive as a PDF document (README_product.pdf) and is also available online.

You should always check online for the most up-to-date release notes or ReadMe because the online version is updated whenever new information becomes available. To

view these online versions, select ReadMe from the Help menu, or visit the Knowledge Base at www.avid.com/readme.

Courier Bold font identifies text that you type.

mouse action. For example, Command+Option+C or Ctrl+drag.

3. Check the documentation that came with your Avid application or your hardware for maintenance or hardware-related issues.

4. Visit the online Knowledge Base at www.avid.com/onlinesupport. Online services are available 24 hours per day, 7 days per week. Search this online Knowledge Base to find answers, to view error messages, to access troubleshooting tips, to download updates, and to read or join online message-board discussions.

Avid Training Services

Avid makes lifelong learning, career advancement, and personal development easy and convenient. Avid understands that the knowledge you need to differentiate yourself is always changing, and Avid continually updates course content and offers new training delivery methods that accommodate your pressured and competitive work environment.

Avid Training Services

For information on courses/schedules, training centers, certifications, courseware, and books, please visit www.avid.com/support and follow the Training links, or call Avid Sales at 800-949-AVID (800-949-2843).

1 Getting Started

Interplay Central requires a minimum of two servers, one used as a Web application server, and the other as the playback server. Avid can supply the server hardware or the customer can supply their own hardware as long as it meets the minimum specifications outlined by Avid.

The following main topics describe the components and software available for an Interplay Central system as well as important, initial preparation for setting up your system.

• System Components

• System Setup Tasks

• Checklist: Before You Begin

• Gather Site Information

• Licensing Requirements and Setup

• Setting up the Load Balancer

System Components

Your Avid Interplay Central system may include some or all of the following:

• Interplay Central Middleware Server—the Web application server used for hosting the Web pages, and handling all communications to and from APIs of other Avid products.

• Interplay Central Playback Server—the server that runs the Interplay Central Playback service. It concurrently reads multiple media assets and sequences residing on an ISIS, and compresses that media for playback on internet-connected clients. In an Interplay Central system, a site can “cluster” multiple ICP servers to scale horizontally.

Load balancers are also recommended for sites with multiple middleware and playback servers.

For middleware servers, a hardware load balancer is used for fault tolerance only. For playback servers, a software load balancer distributes user connections, which results in CPU balancing.

• Interplay Central Workstation—the Web-based client that communicates with the Interplay Central middleware server, the Interplay Central playback server, and other servers for MOS integration. A workstation can be a Windows-based personal computer or laptop running a browser such as Google Chrome, or any Apple computer with a Macintosh operating system and the Safari browser.

System Components

For current specifications regarding minimum requirements and version compatibility, see the

latest ReadMe provided by Avid with your product.

• Modules—software applications that provide functionality and connectivity to various systems. An example of a module is the Interplay Central mobile application, installed on Blackberry smart phones.

• Avid iNEWS newsroom computer system—a back-end system that provides journalists, producers, directors, and various technical personnel in the newsroom with an array of tools to make their job easier. It is primarily made up of iNEWS Workstations, linked together via a local or wide area network, and the iNEWS Server(s), which manages all the day-to-day activities of the newsroom.

• Avid Interplay Production system—a back-end system that combines an asset database with workflow management software, both of which are integrated with Avid shared storage and Avid archive solutions. Interplay Production provides tools that let journalists and producers add rich media to stories and send the assembled video sequence to a playout server.

• ISIS 7000—An Avid shared storage server.

System Components

The following diagram illustrates a basic sampling of components within an Interplay Central system, including an optional Active X server, such as a server running the DekoMOS Gateway service. Your site might have more components not depicted in this illustration.

For the best performance, Avid recommends the middleware server(s) be located in Zone 3 on the

network, closest to the workstations and mobile devices. The playback server(s) can be in Zone 1 with a direct connection (10GigE or 1GigE) to ISIS or in Zone 2, connected to the ISIS through a switch.

Interplay Central Middleware Server

Avid offers the AS3000 as the Web application server known as the Interplay Central middleware server. The middleware server could also procured separately from a third-party vender, such as an HP DL360, running Microsoft Server technology.

For the most current Avid Interplay Central system hardware and software specifications, see the

system requirements listed online at www.avid.com for the Avid Interplay Central system, or contact your Avid Sales representative.

The middleware server runs the following services:

• Interplay Central service

• Interplay Central User Manager service

• Interplay Central Distribution service

• Send to Playback service (STP)

• Avid Service Framework (ASF)

If the middleware server has Internet Information Services (IIS) installed, ensure that it is

disabled so there is no port usage conflict.

System Components

Load Balancing Dual-Server Systems

Avid recommends running Interplay Central Server service on two identically configured Interplay Central middleware servers to help ensure high availability and failover protection. High availability is achieved by using a load balancer, such as the LoadMaster 2200 by Kemp Technologies, which monitors the health of the servers and provides failover functionality in case one of the servers or its services goes down.

With a dual-server system, the Interplay Central middleware servers are directly connected to the load balancer and set up to run in their own subnets. The load balancer acts like a router between the existing network and each middleware server’s subnet.

System Components

Each Interplay Central middleware server gets its own IP address in its subnet—shown as numbers 4 and 5 in the previous diagram. During the hardware installation, the load balancer is assigned multiple IP addresses:

1. An IP address facing the network

2. An IP address facing the middleware server in subnet A

3. An IP address facing the middleware server in subnet B

Plus, it gets one virtual IP address (not numbered in the diagram) that is used by the clients to access Interplay Central. The load balancer will route client requests from the virtual IP address to one of the Interplay Central middleware servers and send responses from the middleware servers back to the clients. All client traffic is handled and balanced by the load balancer. Interplay Central clients are not allowed to connect from the servers’ subnets.

Procedures for installing and configuring your load balancer could vary, so Avid recommends referring to the documentation provided by the hardware manufacture. However, as an example, steps for setting up the LoadMaster 2200, manufactured by Kemp Technologies, is provided in this guide. For more information, see “Setting up the Load Balancer” on page 28.

Interplay Central Playback Server

The Interplay Central Playback Service software is installed on an HP DL380G7 server (procured separately) running the Red Hat Enterprise Linux operating system. Additionally, this HP server requires specific GigE and/or 10GigE network interface cards to support ISIS storage connectivity.

It runs the following:

• Interplay Central playback service

For the most current Avid Interplay Central system hardware and software specifications, see the

system requirements listed online at www.avid.com for the Avid Interplay Central system, or contact your Avid Sales representative.

Modules

An Interplay Central module contains front-end elements or both front-end and back-end elements. Front-end elements can include the panes or controls that integrate with existing panes in the user interface. The back-end elements can include services, connectivity to back-end systems, or both.

System Components

For instance, the Interplay Central Mobile module is not the same thing as the iNEWS client software, but like the iNEWS client software, this module provides iNEWS functionality as well as connectivity to iNEWS systems.

Some modules are installed on servers while others run on clients, and third-party developers can create Interplay Central modules for increased functionality.

The following is a list of some modules offered by Avid for Interplay Central systems:

• Interplay Central Module

• Avid Service Framework Module

• iNEWS API Module

• iNEWS Module

• Interplay Central Mobile Module

Interplay Central Workstation

The Interplay Central Workstation communicates with the iNEWS server and the Interplay Workgroup database through the Interplay Central servers.It can be a computer or laptop, running a Windows-based or Macintosh-based operating system, located within a site’s firewall

or securely connected to the network through VPN. There is no special software to install, but the computer must have a supported Web browser, such as Google Chrome for Windows or Safari for a Macintosh computer.

System Setup Tasks

The following table is provided as a convenient checklist to ensure a complete and successful installation of an integrated Interplay Central system. You can print this page to use as a guide during the installation and configuration process.



Tasks Refer to...

Complete all pre-installation tasks. “Checklist: Before You Begin” on page 21



Set up the Interplay Central middleware server(s). “Checklist: Set up Interplay Central



System Setup Tasks

Middleware Server” on page 32

Configure the Interplay Central middleware



server(s).

Set up and configure the Interplay Central



playback server(s).

Configure the Interplay Administration settings



used by Interplay Central.

Configure the system for send to playback (STP). The Avid Interplay Central Administration



An Interplay Production Transcode Server is required for STP and Mixdown. The audio

transitions/effects will be rendered by the transcode service in preparation for STP, and sequences will be flattened by the transcode service during a mixdown operation.

(Optional) Install and configure devices for mobile



integration.

(Optional) Install and configure active-X plug-ins. The documentation that came with your



“Checklist: Configure Interplay Central Middleware Server” on page 46

“Checklist: Set up Interplay Central Playback Server” on page 59

“Configuring the Application Database Settings” on page 54

Guide

“The Mobile Application” on page 77

plug-in

Checklist: Before You Begin

Before you start to install software and configure the Avid Interplay Central server(s), ensure the following tasks are completed.



Tasks Refer to...

Checklist: Before You Begin

Gather all site information needed during the setup,



installation, and configuration processes.

For dual-server sites, install and configure the load



balancer for the middleware servers.

Configure iNEWS for licensed integration with Interplay



Central.

Install the Interplay Production license for Interplay



Central

“Gather Site Information” on page 22

The manufacturer’s documentation that came with your load balancer, such as the Quick Start Guide for the LoadMaster 2200 by Kemp Technologies. See also “Load

Balancing Dual-Server Systems” on page 17.

• “Verifying Interplay Central

Licenses on iNEWS” on page 24

• “Configure iNEWS for Integration

with Interplay Central” on page 26

“Installing the Interplay Production License for Interplay Central” on page 23

Gather Site Information

Prior to installing Avid Interplay Central, collect the following information and keep it readily available for use during the process. For convenience, you can print the following table and fill in the information unique to your site.

Type of Information Needed Site Specific Notes

Interplay Workgroup name

Interplay Workgroup Lookup services (fully qualified domain names)

ISIS virtual & real hostnames

Interplay/ISIS administrator account and password

iNEWS Server name(s)

iNEWS user account

Interplay Workgroup Media Indexer HAG name

Gather Site Information

Media Services hostname

Transcode hostname

STP Encode hostname

IP address(es) of Interplay Central middleware and playback servers

IP address(es) of load balancer(s) for dual-server systems

Licensing Requirements and Setup

An Interplay Central user requires at least one of the following licenses:

• Interplay Central mobile license: This license allows the user to connect to an iNEWS newsroom computer system through the Interplay Central mobile application.

• iNEWS client license. This license allows the user to connect to an iNEWS newsroom computer system through the Interplay Central middleware server, but does not allow access to an Interplay Production database.

• Interplay Central browse client license: This license includes both an iNEWS client license and an Interplay Production license. The Interplay Production license (J type) allows browsing of media stored in an Interplay Production database.

• Interplay Central full client license: This license includes both an iNEWS client license and an Interplay Production license. The Interplay Production license (G type) allows both browsing of an Interplay Production database and creation of sequences using that media.

Delivery of Licenses on Back-End Systems

An iNEWS client license or an Interplay Central mobile license for a specified number of clients is sent to the customer through email along with specific installation instructions. However, to ensure proper licensed integration between Interplay Central and iNEWS, additional modification to system files in the iNEWS database is also required. For more information on those modification procedures, see “Verifying Interplay Central Licenses on iNEWS” on

page 24, “Editing SYSTEM.CLIENT.VERSIONS” on page 26, and “Editing SYSTEM.CLIENT.WINDOWS” on page 27.

Licensing Requirements and Setup

An Interplay Production license for a specified number of clients is supplied to the customer on a USB flash drive as a file with the extension nxn. For more information, see “Installing the

Interplay Production License for Interplay Central” on page 23.

Configuration on the Front-End

You specify the type of license for each Interplay Central user in the Details tab of the Users layout. For more information, see “Creating a New User or Editing User Details” on page 42.

Installing the Interplay Production License for Interplay Central

The Avid Interplay Administrator is a client application that can be installed on any computer in your network and then used to manage either the Interplay Engine or the Interplay Archive Engine. You can use the Licenses view of the Interplay Administrator to install the Interplay Production license needed for integration with Interplay Central. For more information about this application, see the Avid Interplay Engine and Avid Interplay Archive Engine Administrator’s Guide.

To install the Interplay Production license for Interplay Central:

1. Start and log in to the Interplay Administrator.

2. Make a folder for the license file on the root directory (C:\) of the Interplay Central middleware server. For example:

C:\Interplay_Licenses

3. Insert the USB flash drive into any USB port.

If the USB flash drive does not automatically display:

a. Double-click the computer icon on the desktop.

b. Double-click the USB flash drive icon to open it.

4. Copy the license file (*.nxn) into the new folder you created.

5. In the Server section of the Interplay Administrator window, click the Licenses icon.

6. Click the Import License button.

7. Select the file and click Open. The type of licenses (J or G) are displayed in the License Types area.

Verifying Interplay Central Licenses on iNEWS

Licensing Requirements and Setup

Before you can use Interplay Central to connect to any back-end system, such as an iNEWS newsroom computer system, you must ensure iNEWS is configured with the proper number of Interplay Central devices authorized to connect to the system based on the purchased licenses. You can view iNEWS licensing limits from the iNEWS console.

To display iNEWS licensing limits, at the console, type:

NRCS-A$ status license

Licensing Requirements and Setup

A message similar to the following will appear on your screen:

A is ONLINE and has been CONFIGURED. ID is INWS.

System is AB. Master is A.

Disk status is OK. The database is OPEN.

Site Key............. : 009999

CPUs................. : 3

Workstation addresses : 3000

Workstation resources : 1000

COM resources........ : 5

Web Access resources. : 2

Web Client resources. : 10

Web API resources.... : 5

Wire Server resources : 8

Instinct resources... : 10

Mobile devices allowed: 2000

Community Sessions... : allowed.

The three lines to pay attention to are:

- Workstation addresses—indicates how many IP and/or MAC addresses can be specified

in the SYSTEM.CLIENT.WINDOWS story. This story may be deleted from the iNEWS database if Workstation addresses shows a “site” license and IP-specific restriction is not wanted.

- Workstation resources—the number of clients that can simultaneously connect to

iNEWS, including both iNEWS workstations and Interplay Central workstations.

- Mobile devices allowed—the number of mobile devices that can simultaneously

connect to iNEWS.

Any time the iNEWS newsroom computer system is configured, your licensing information is

checked. An error message appears in iNEWS if the configuration file defines more devices than are licensed.

To change license allowances:

t Contact an Avid sales representative.

Licensing Requirements and Setup

Configure iNEWS for Integration with Interplay Central

Before you can connect to an iNEWS newsroom computer system from an Interplay Central workstation, you must edit a couple of system files in iNEWS so that iNEWS recognizes Interplay Central as a properly licensed device.

The files to edit are:

• SYSTEM.CLIENT.VERSIONS

• SYSTEM.CLIENT.WINDOWS

Additional files must be edited to ensure proper licensing for iNEWS integration with the

Interplay Central mobile application. For more information, see “iNEWS Configuration for

Mobile Integration” on page 79.

Editing SYSTEM.CLIENT.VERSIONS

Some steps in the following procedure are conducted at the iNEWS console in superuser mode. For more information, see “The iNEWS Console” chapter in the iNEWS Installation and Configuration Guide.

To edit the SYSTEM.CLIENT.VERSIONS story in iNEWS:

1. Sign in to an iNEWS workstation as a system administrator, or any user account with write access to the System directory.

2. Navigate to SYSTEM.CLIENT.VERSIONS and open the first story in that queue.

3. On a new line, add the version of the Interplay Central service that will run on the Interplay Central middleware server.

4. Save the story.

5. Reconfigure the system. From the iNEWS console:

a. Select the master computer, which is typically server A.

b. Enter superuser mode, using the correct password.

The dollar sign ($) at the end of the console’s server prompt will change to a pound sign (#).

c. Take the system offline by typing:

d. Reconfigure the system by typing:

e. When the prompt reappears, bring the system back online by typing:

f. Press Ctrl+D to leave superuser mode.

The pound sign (#) at the end of the console’s server prompt will change back to a dollar sign ($).

NRCS-A# offline

NRCS-A# configure

NRCS-A# online

Editing SYSTEM.CLIENT.WINDOWS

The following procedure only applies to sites that are not using a “site” license as Workstation addresses in iNEWS. You can review your site license information from the iNEWS console. For more information, see “Verifying Interplay Central Licenses on iNEWS” on page 24.

To edit the SYSTEM.CLIENT.WINDOWS story in iNEWS:

1. Sign in to an iNEWS workstation as a system administrator, or any user account with write access to the System directory.

2. Navigate to SYSTEM.CLIENT.WINDOWS and open the first story in that queue.

3. Add the IP address of the Interplay Central middleware server to a new line. Use a semicolon to add helpful commentary for future reference to the end of the line.

Licensing Requirements and Setup

For instance, type:

125.1.100.5 ;Interplay Central middleware server

- If there are multiple middleware (Web application) servers, you will need to add the IP

address for each one on individual lines in the story.

- However, if a load balancer is used with the multiple middleware servers, and

communication will always be through the load balancer, then add only the virtual IP address of the load balancer instead.

- And if the load balancer is used, but some direct client-to-server communication is

probable, then add the IP addresses for the load balancer and all middleware servers.

4. Save the story.

5. Reconfigure the system. From the iNEWS console:

a. Select the master computer, which is typically server A.

b. Enter superuser mode, using the correct password.

The dollar sign ($) at the end of the console’s server prompt will change to a pound sign (#).

c. Take the system offline by typing:

d. Reconfigure the system by typing:

e. When the prompt reappears, bring the system back online by typing:

NRCS-A# offline

NRCS-A# configure

NRCS-A# online

f. Press Ctrl+D to leave superuser mode.

The pound sign (#) at the end of the console’s server prompt will change back to a dollar sign ($).

Setting up the Load Balancer

In dual-server systems, a load balancer can be used to ensure high availability and provide failover functionality.

This section covers setup and configuration of a load balancer for the Interplay Central middleware servers.

The LoadMaster 2200, by Kemp Technologies, is used as an example. If your site uses a different

load balancer, refer to the documentation provided by the hardware manufacturer.

The load balancer can be set up initially either by connecting a monitor and keyboard directly to the hardware or by using the Web interface. When connecting via the Web interface, you access the load balancer by a predefined IP address, which can be found in the Quick Start Guide that came with the hardware.

To configure the load balancer, using a keyboard and monitor:

1. The first time you connect, a Quick Setup wizard will appear to walk you through the steps, and the first question might be to provide a license key. If prompted, enter the license key, or you can continue without it temporarily; There is a 30-day trial period.

2. The wizard will then prompt you to set up the network interfaces by entering the IP address of the network side of the load balancer. Type in the IP address including the netmask. The syntax is:

Setting up the Load Balancer

3. Click OK.

4. When prompted, enter the hostname of the load balancer and click OK.

5. Enter the nameserver IP address(es) and click OK. If there is more than one, separate each by a single space.

6. Enter the search domain(s) and click OK. If there is more than one, separate each by a single space.

7. Enter the IP address of the default gateway of the existing network.

8. Click OK.

After the setup wizard finishes, restart the load balancer.

9. Physically connect the load balancer to the network and to the Interplay Central middleware servers. Connect server 1 to the eth1 interface of the load balancer. Connect server 2 to the eth2 interface.

Setting up the Load Balancer

To configure the virtual service, using the Web interface:

1. Connect to your load balancer using the Web interface by typing in the hardware’s predefined IP address.

For a LoadMaster, the Main Menu screen will appear, showing vital statistics, such as IP address, serial number, version, license activation data, and CPU load.

Ensure you are using the recommended version of the load balancer. For the latest specifications, please refer to the Avid Web site or the latest ReadMe for Interplay Central.

2. Select System Configuration and then Interfaces.

a. Configure the network interface settings for eth1 and eth2. For instance, set the interface

address for eth1 to 10.129.106.5/25 and for eth2 to 10.129.106.130/25.

b. Also set Link Status to Automatic.

3. Select Virtual Services.

4. Click Add New.

5. Specify the parameters for the virtual service.

a. In the Virtual Address field, enter the virtual IP address for the load balancer.

b. Set the port to 443.

c. Set the protocol to TCP.

6. Click Add this Virtual Service to confirm the settings.

This will send you to the Basic Properties screen for the virtual service.

7. Set Service Type to HTTP/HTTPS.

8. Set Extra Port to 80.

The virtual service by default is configured on port 443 (the default https port); therefore you will

only be able to connect to the real servers via port 443 if you do not specify this extra port in the settings.

9. Set the Real Server Check Parameters to:

- HTTP Protocol

- Checked Port: 80

- URL: /rest/heartbeat/with-failover?com.avid.central.rest.accept-all

- Uncheck Use HTTP/1.1

- HTTP Method: GET

- Reply 200 Pattern: HEALTHY

10. (Optional) Set the service nickname.

Setting up the Load Balancer

11. Set Persistence Options to:

a. Mode: Source IP Address

b. Timeout: 1 Day

c. Netmask: /32

12. Set Scheduling Method to Fixed Weighting.

13. Set Idle Connection Timeout to 15.

14. Select the Use Address for SNAT checkbox

15. Scroll down to SSL Properties and ensure that SSL Acceleration is not checked.

16. In the last section of the Real Servers for this Virtual Service, select Add New and specify the following parameters:

a. In the Real Server Address field, enter the IP address for the first Interplay Central

middleware server.

b. Set the port to 443.

c. Set Forwarding Method to “nat”.

d. Set Weight to 1000.

17. Click Add This Real Server, then repeat the previous step for the second Interplay Central middleware server, with two exceptions; enter the IP address of the second server instead of the first one, and set the Weight to 500.

18. Physically connect the load balancer to the Interplay Central middleware servers. Connect server 1 to the eth1 interface of the load balancer. Connect server 2 to the eth2 interface.

19. Check the Virtual Services screen, using the load balancer’s Web interface; the status should be green.

2 The Interplay Central Middleware Server

Interplay Central middleware server is the Web application server used to manage communications between Interplay Central workstations and back-end systems, such as the iNEWS newsroom computer system.

The following main topics describe the installation and configuration procedures of the middleware server(s).

• Checklist: Set up Interplay Central Middleware Server

• Checklist: Configure Interplay Central Middleware Server

Checklist: Set up Interplay Central Middleware Server

This checklist assumes all pre-installation steps have been completed as outlined in “System

Setup Tasks” on page 20 and “Checklist: Before You Begin” on page 21.

When you are ready to set up the Avid Interplay Central middleware server(s), ensure the following tasks are completed.



Tasks Refer to...

Install the ISIS Client. “Install the ISIS Client Software” on



page 33

If your site will only use devices running the Interplay Central mobile application and not

the Web application, then you do not need to install ISIS.

Install Avid Service Framework and join the Interplay



workgroup.

Install the Interplay Central distribution service. “Install the Interplay Central



Install the Interplay Central user management service. “Install the Interplay Central User



Run the Interplay Central setup to install the Interplay



Central service and all modules.

Reboot the server.



Verify and/or configure the Interplay Admin settings that



are applicable to Interplay Central

(Optional) Configure custom certificate(s) for the



Interplay Central middleware server.

“Install Avid Service Framework” on page 34

Distribution Service” on page 38

Management Service” on page 40

“Run the Interplay Central Setup” on page 42

“Configuring the Application Database Settings” on page 54

“Deploying Another Certificate to the Middleware Server” on page 57

Install the ISIS Client Software

The ISIS client application is provided as part of the Avid ISIS software installation kit, a USB flash drive containing about 4 GB of data.

You can install the client software in several ways:

• You can take the software kit to each computer separately and install it.

• You can store the client software somewhere on the corporate network and allow everyone who needs the software to gain access to install it.

• You can use a browser to reach the ISIS Management Console and install it from the System Director because it was loaded during the previous installation of the client installers. The following procedure provides details for this method of installation.

Before installing Avid ISIS client software on Windows systems, make sure you are up-to-date

with your Windows critical or “high priority” updates.

To install the client software using a browser:

1. Start your browser application.

2. Go to https://IP address of System Director (or virtual name):5015.

Checklist: Set up Interplay Central Middleware Server

The ISIS Management Console opens.

3. Type your administrator’s password.

4. Click Administration.

The Avid ISIS Installer Downloads screen opens.

5. Click the ISISClient installer named AvidISISClient_Win64_.msi.

The installer might ask if you want to save or run the installation software; either is acceptable.

6. Following the Setup Wizard prompts—accepting the license agreement and default settings—to complete your installation.

t (Optional) During a Windows-based installation, a question could appear asking who

the software is for; select Everyone.

7. After you receive the Installation Complete dialog box, click Close.

The client software is installed.

8. Restart the client system if prompted to do so.

Install Avid Service Framework

Avid Service Framework consists of several applications and services that provide dynamic discovery and lookup mechanisms and other tools used for diagnostics, configuration, and support.

The installer for Avid Service Framework is provided on the Avid Interplay Servers Installer USB flash drive, and not with Interplay Central. The installer can be copied to a network computer and later accessed from there, or used directly from the USB flash drives.

Checklist: Set up Interplay Central Middleware Server

Before installing ASF, ensure that Internet Information Services (IIS)—if installed—is disabled

so they do not interfere with ASF ports. If IIS must remain enabled, change the port used by IIS or used by Interplay Central to avoid a conflict. For more information, see “Changing Port

Configuration” on page 52.

To install the Avid Service Framework software:

1. From the Interplay Server Installer Main Menu, select Individual Optional Installers.

The Optional Installers window opens.

Checklist: Set up Interplay Central Middleware Server

2. Click Avid Service Framework Custom.

The Welcome dialog box opens.

3. Click Next.

The Destination Folder dialog box opens.

4. Accept the default values and click Next.

The Join a Workgroup Name dialog box opens.

Checklist: Set up Interplay Central Middleware Server

5. Type the name of your Interplay workgroup and click Next.

The workgroup name is case sensitive. Use the same name on all Interplay clients.

If you are updating the Service Framework software, the installer remembers the last installed value. If the workgroup name was changed after the install, the installer will not be aware of the change.

The Options dialog box opens.

Checklist: Set up Interplay Central Middleware Server

6. Select the Avid Service Framework Client install option.

7. Click Next.

The Custom Setup dialog box opens with the following applications and services already selected for you:

- Avid Service Configuration

- Avid Diagnostics

- Avid Health Monitor

- Avid Machine Monitor Service

- Avid Time Synchronization Service (optional)

8. Accept the default selections. Click Next.

Do not add components that you don’t need. This can affect system performance.

9. Follow the installation instructions to complete the installation.

You might be required to restart your system to complete the installation.

Optional Applications

The following applications are not included as part of the Interplay Central installation, but can be installed (if licensed) as optional client applications on the Interplay Central middleware server:

• Interplay Access — if you want to install this application, use the same version already licensed for use in your Interplay environment.

• iNEWS — if you want to install the client application, use the same version already licensed for use in your newsroom.

• Google Chrome

These applications are not required; however, since Interplay Central can be used to connect to both iNEWS and Interplay Production databases, the two Avid applications can come in handy on the server to check connectivity to the back-end systems once installation and configuration is complete.

Installing Interplay Access on the middleware server also installs the Interplay Administrator

application, which can be used to verify certain settings applicable to Interplay Central. For more information, see “Configuring the Application Database Settings” on page 54.

Checklist: Set up Interplay Central Middleware Server

Install the Interplay Central Distribution Service

The Interplay Central Distribution service is used to coordinate jobs with Avid Media Services for sequence mixdowns and send to playback.

To install the distribution service:

1. On the Interplay Central installation USB flash drive, navigate to the Central Distribution Service folder.

2. Double-click the Interplay Central Distribution Service Windows installer package.

The Welcome dialog box appears.

3. Click Next.

The License Agreement dialog box appears.

Checklist: Set up Interplay Central Middleware Server

4. After you read the license agreement, select Yes to accept the terms and choose the appropriate jurisdiction. Then click Next.

The Destination Folder dialog box appears.

Checklist: Set up Interplay Central Middleware Server

5. Accept the default values and click Next.

6. When the Ready to Install the Program dialog box appears, click Install.

7. When the process is complete, the InstallShield Wizard will inform you of the successful installation. Click Finish.

Install the Interplay Central User Management Service

Interplay Central User Management is a service that provides the ability to create and manage users and groups, authenticate users across iNEWS and Interplay Production systems, and manage the Interplay Central licenses to which users have access.

To install the Interplay Central User Management service:

1. On the Interplay Central installation USB flash drive, navigate to the Interplay Central User Management setup application and double-click to start it.

After a moment, the Welcome dialog box will appear.

2. Click Next.

The License Agreement dialog box opens.

Checklist: Set up Interplay Central Middleware Server

3. After you read the license agreement, select accept the terms. Then click Next.

The Destination Folder dialog box opens.

Checklist: Set up Interplay Central Middleware Server

4. Accept the default values and click Next.

The Configure Interplay Central User Management Service dialog box opens.

5. Enter the password for the Administrator user account for Interplay Central User Management. Then reenter the password and click Next.

6. When the Ready to Install dialog box appears, click Install to begin the installation.

7. When the process is complete, the InstallShield Wizard will inform you of the successful installation. Click Finish.

Run the Interplay Central Setup

The Interplay Central setup application enables you to install the Interplay Central Server service and its available modules. The setup application can be accessed from the Interplay Central installation USB flash drive, or copied to another location for access over the network.

To install the Interplay Central service and all modules:

1. On the Interplay Central installation USB flash drive, navigate to the Interplay Central setup application and double-click to start it.

If prompted to allow the program to make changes to your computer, click Yes.

The setup application checks the computer to determine if Interplay Central or any of its modules are already installed and then displays the Main Menu screen.

Checklist: Set up Interplay Central Middleware Server

The red X icons located to the left of the buttons are individual indicators to show whether each

service or module is already installed. If a service or module already exists on the computer, a green check icon appears instead. Likewise, the gear icon will have a red square over it when the setup application completes its system check without finding any previous versions installed. The shape is a green triangle over the gear if one or more services or modules are found to be installed.

2. Click Install Interplay Central and all modules.

The InstallShield Wizard prepares to install the Interplay Central Server service and then displays the Welcome dialog box.

3. Click Next.

The License Agreement dialog box opens.

Checklist: Set up Interplay Central Middleware Server

4. After you read the license agreement, select accept the terms and choose the appropriate license language. Then click Next.

The Destination Folder dialog box opens.

Checklist: Set up Interplay Central Middleware Server

5. Accept the default values and click Next.

6. When the Ready to Install dialog box appears, click Install.

7. When the process is complete, the InstallShield Wizard will inform you of the successful installation. Click Finish.

The setup application will then proceed to install each module. Status dialog boxes will appear as the installation processes progress. Additionally, the red X icons on the Main Menu screen will change to green check icons as each one is installed. The gear icon with the red square also changes to reflect the final status of the installation, as shown in the following illustration.

8. After your install, reboot the middleware server.

Checklist: Configure Interplay Central Middleware Server

When you are ready to configure the Avid Interplay Central middleware server(s), ensure the following tasks are completed.



Tasks Refer to...

Set up the remote host(s) for ISIS. This task applies to



sites where the Interplay Central middleware server is in a different subnet than the ISIS system.

Specify a lookup locator(s) for ASF, if needed. “Specify a Lookup Locator for Avid



Ensure forward and reverse DNS lookups work to



Interplay, ISIS, and iNEWS by running DNS tests across the network.

Configure Interplay Central for iNEWS connectivity. “Configure System Settings for iNEWS



Configure Interplay Central for Interplay connectivity. “Configure System Settings for



Create the cluster for the Interplay Central User



Management services. This task applies to sites set-up for high availability.

(Optional) Customize port settings for Interplay Central. “Changing Port Configuration” on



(Optional) Set custom location for backup user



management database files.

“Set up the Remote Host for ISIS” on page 47

Service Framework” on page 48

“Run DNS Tests against Hosts in the Network” on page 49

Integration” on page 49

Interplay Integration” on page 50

“Creating a Cluster for User Management” on page 52

page 52

“Set the Backup Location for User Management Database Files” on page 53

Configure or verify the Application Database settings are



correct for Interplay Central, using the Interplay Admin application.

Configure the Transfer settings for send to playback to



work in Interplay Central.

“Configuring the Application Database Settings” on page 54

The Avid Interplay Transfer Setup and User’s Guide. See the chapter on “Interplay Transfer Configuration”.

Checklist: Configure Interplay Central Middleware Server



Tasks Refer to...

Configure Media Services for the sequence mixdown and



send to playback features in Interplay Central.

Set up the Remote Host for ISIS

After installing the ISIS client software, you will need to specify a remote host for ISIS on the Interplay Central middleware server.

To specify a remote host:

1. Start the Avid ISIS Client Manager by clicking Start > All Programs > Avid > ISIS Client.

2. Click the Remote Host Settings button, as highlighted in the following illustration.

The Avid Interplay Media Services Setup and User’s Guide. See the sections “Working in the Transcode Service” and “Exporting and Transferring Long GOP OP1a Media in the Background”.

The Remote Hosts dialog box opens.

Checklist: Configure Interplay Central Middleware Server

3. Enter the hostname for the remote ISIS server and click the Add (+) button.

The ISIS server will appear in the Host list.

Ensure that you typed the hostname correctly before applying your changes.

4. Click the Apply button (green checkmark).

Specify a Lookup Locator for Avid Service Framework

After installing Avid Service Framework and after joining the Interplay workgroup, you should not need to specify a lookup locator for ASF on the Interplay Central middleware server. It should be provided to the server automatically. However, you should verify that this occurs and if necessary be prepared to manually specify them.

To view and/or add lookup locators for ASF:

1. Open Avid Workgroup Properties by clicking Start > All Programs > Avid > Avid Service Framework > Avid Workgroup Properties.

2. Select the Lookup tab.

The workgroup and lookup services are listed.

3. (Optional) Only if necessary, use the Add button under the Lookup Services section of the dialog box to add lookup locators. Ensure the name you enter is spelled exactly correct. Then click Apply.

4. Click OK.

Checklist: Configure Interplay Central Middleware Server

Run DNS Tests against Hosts in the Network

Avid Workgroup Properties, one of the Avid Service Framework applications, provides a Network tab which you can use to test the DNS lookup capability of the middleware server, to ensure everything is working properly. This network test tool does a forward and reverse lookup for each client in the workgroup from the computer used to initiate the test.

To run a DNS test from the middleware server:

1. Open Avid Workgroup Properties by clicking Start > All Programs > Avid > Avid Service Framework > Avid Workgroup Properties.

2. Select the Network tab.

Ensure that Load host list from Lookup Service is selected and that the appropriate workgroup is chosen.

3. Click Run.

Configure System Settings for iNEWS Integration

You can configure system settings for Interplay Central after signing in with the user name Administrator. The password for the administrator account was set during installation of the Interplay Central User Management service. For more information, see “Install the Interplay

Central User Management Service” on page 40.

The following procedure only pertains to configuring a couple of vital settings related to iNEWS integration with Interplay Central.

Additional settings are available in the iNEWS settings group; however, those are discussed in

more detail in the Interplay Central Administration Guide.

To configure system settings for iNEWS integration:

1. Sign in to Interplay Central as an administrator.

2. Select System Settings from the Layouts drop-down menu.

3. From the list under the Settings tab, select iNEWS.

Checklist: Configure Interplay Central Middleware Server

The Details tab displays the settings for iNEWS.

4. In the Hostname field, enter the name for the server that hosts the iNEWS database.

Typically, the name of each iNEWS server includes a suffix to distinguish one from another, such a WAVD-A and WAVD-B. In the settings for Interplay Central, do not include the suffix when entering the iNEWS server’s hostname.

So, using the previous sample names, you would type

5. In the Path field, specify the location of the folder in the Interplay Production database used to store the sequences created as part of an iNEWS script. You also need to select whether you want sub-folders in the parent folder to be created by Queue name, Date, or Story name.

6. Click Apply before selecting any other group in Settings to modify.

WAVD

Configure System Settings for Interplay Integration

Central User Management Service” on page 40.

The following procedure only pertains to a couple of vital settings related to Interplay Production integration with Interplay Central.

Additional settings are available in the Interplay Production settings group; however, those are

discussed in more detail in the Interplay Central Administration Guide.

only.

Checklist: Configure Interplay Central Middleware Server

To configure settings for Interplay Production integration:

1. Sign in to Interplay Central as an administrator.

2. Select System Settings from the Layouts drop-down menu.

3. From the list under the Settings tab, select Interplay Production.

The Details tab displays the settings for Interplay Production.

4. In the Hostname field, enter the name or IP address for the server that hosts the Interplay Production database.

5. In the Service URL field, specify a secure URL for the server that hosts the Interplay Central Distribution Service. The format for the URL is https://<hostname>:<port number>.

For instance: https://localhost:8443. You can use an IP address instead of the hostname.

6. Click Apply before selecting any other group in Settings to modify.

Checklist: Configure Interplay Central Middleware Server

Creating a Cluster for User Management

For sites wanting a high availability setup, the Interplay Central User Management services are required to run in cluster mode for data synchronization. Before creating the cluster, you must decide which User Management service should be used as master because the data stored in the master will overwrite the one from the slave.

To create a cluster:

1. Sign in to the Interplay Central middleware server on which the User Management service is running.

2. From a command line, navigate to C:\Program Files\Avid\Interplay Central User Management Service\bin

3. Type the Create Cluster command using the following syntax:

IPUMUtils.cmd -cc <master IP address> <slave IP address> <administrative

password>

The -cc is the command to “create the cluster”.

For additional information regarding this command and its options, you can type:

IPUMUtils.cmd --help

After you enter the Create Cluster command, the cluster will be created automatically.

The command creates a backup of the slave database, located in:

%ALLUSERPROFILES%\Avid\Interplay Central User Management Service\db_backup\

Changing Port Configuration

By default, Interplay Central uses port 80 for HTTP and port 443 for HTTPS (secure) communications. This could result in a conflict with IIS, if IIS remains enabled on the Interplay Central middleware server(s). Therefore, if you want to reconfigure your Interplay Central system to use different ports, you can do so by editing the application’s properties.

System application.properties are located at:

C:\Program Files (x86)\Avid\Interplay Central\Server\config

Changes to the configuration settings of this file can be lost after updates are installed.

To customize port configuration settings for Interplay Central:

1. Go to

2. Open the custom application.properties file.

C:\ProgramData\AvidAvidInterplayCentralService\Config

file will overwrite those in the system’s application.properties file.

If it does not exist, create it with the properties you was to change for your system.

. Changes to this

Checklist: Configure Interplay Central Middleware Server

The lines to add or mofidy are:

system.org.osgi.service.https.enabled=true

system.org.osgi.service.https.only=true

system.org.osgi.service.https.port=443

system.org.osgi.service.http.port=80

The “https.enabled” line, if set to true, enables encrypted communications through a secure HTTPS port. The “https.only” line, if set to true, means that when an Interplay Central user connects to the HTTP port, they will be redirected to the secure port automatically, thereby ensuring encrypted communications. If set to false, communication is unencrypted to the server, therefore the user can connect via the HTTP port.

3. Modify the lines accordingly and save your changes.

Set the Backup Location for User Management Database Files

By default, the Interplay Central User Management service stores its backup database files at:

C:\ProgramData\Application Data\Avid\Avid Interplay Central User Management Service\db_backup

do so by modifying the service’s properties file.

. Should you want to store your backup files in a different location, you can

To set a unique backup location for user management database files:

1. On the C: drive, navigate to Program Files > Avid > Interplay Central User Management Service > Config.

2. Open the uls.properties file.

The line to look for is:

uls.db.backup.ha.path=C:\ProgramData\Application Data\Avid\Avid Interplay Central User Management Service\db_backup

3. Modify the line with a new path after the equal sign (=) and save your changes.

You can also specify the frequency of the backups, which by default is set to daily.

Checklist: Configure Interplay Central Middleware Server

Configuring the Application Database Settings

After installing the Interplay Central middleware server for a new site, you need to configure some settings in the Interplay Administrator application that are applicable to Interplay Central. For existing Interplay environments, the settings covered in this section might already be set, but you should still verify whether they are set correctly for Interplay Central.

To check or modify Application Database settings in the Interplay Administrator:

1. Start and log in to the Interplay Administrator application.

If you installed Interplay Access on the middleware server (optional), the Interplay

Administrator application was installed as well. If not, you’ll have to locate the computer in your Interplay environment on which the application was installed.

2. Select Application Database Settings.

A scroll bar is provided to view all of the settings available, most of which apply to Avid Instinct. However, there are several sections on the Editing Settings tab that apply to Interplay Central, as outlined in the following table.

Note: This table is copied in Chapter 1 of the Interplay Central Administration Guide, so make any changes in both places. Conreffing was complicated by the x-ref.

Section Setting Description

Format Video Format Interplay Central does not restrict by format, but uses this setting

to determine the frame rate required for sequence editing. Options include: HD 1080i, PAL, NTSC, Any, and so forth. If set to Any, then a sequence’s framerate will be set by the first clip added to the sequence.

Audio Patching Natural Sound What you choose in the Audio Patching section determines how

many channels are shown (for NAT or SOT) in the context menu options for audio when a user right-clicks on a clip within the Script Editor’s Sequence Timeline.

This setting is the channel count for natural sound. Options include: 1-Channel or 2-Channel.

Sound on Tape This setting is the channel count for sound on tape. Options

include: 1-Channel or 2-Channel.

Audio - Track labels

Natural Sound label

This setting determines the wording or character(s) used as a label for the natural sound track control in the Audio pane as well as the header for the natural sound column in the Script Editor’s Sequence Timeline. By default, NAT is used.

Checklist: Configure Interplay Central Middleware Server

Section Setting Description

Audio - Source audio patching

Audio - Storyline audio patching

Sound on Tape label

This setting determines the wording or character(s) used as a label for the sound on tape track control in the Audio pane as well as the header for the sound on tape column in the Script Editor’s Sequence Timeline. By default, SOT is used.

Voice Over label This setting determines the wording or character(s) used as a

label for the voice over track control in the Audio pane as well as the header for the voice over column in the Script Editor’s Sequence Timeline. By default, VO is used.

Natural Sound tracks 1 & 2

Sound on Tape tracks 1 & 2

These settings determine which two tracks are used for natural sound from the source media.

These settings determine which two tracks are used for sound on tape from the source media.

Voice Over track This setting determines which track is used for voice over audio

from the source media.

Natural Sound tracks 1 & 2

These settings determine which two tracks are used for natural sound on the output sequence. Each track for natural sound and sound on tape must be unique. For instance, do not set the first track for natural sound to A1 if the first track for sound on tape is already set to A1.

Sound on Tape tracks 1 & 2

These settings determine which two tracks are used for sound on tape on the output sequence. Each track for natural sound and sound on tape must be unique. For instance, do not set the first track for sound on tape to A1 if the first track for natural sound is already set to A1.

Voice Over track This settings determines which track is used for voice over audio

Audio - General settings

Media Creation workspace

Sample bit depth Set this to 16 for Interplay Central.

Ducking [-db] When audio must be ducked because of overlapping tracks, this

Dynamic Relink Dynamic Relink

Enabled

on the output sequence.

This is the name of the location on ISIS where Interplay Central creates voice over files.

setting (in decibels) is what determines the reduction in audio level.

This setting is not configured for Interplay Central in this location of the Interplay Administrator application. Instead, this setting is configured on the Interplay Central playback server. For more information, see “Configure the Interplay Central Playback

Service” on page 66.

Checklist: Configure Interplay Central Middleware Server

Section Setting Description

Audio Effects Dissolve Duration

[frames]

Brief dissolves between audio tracks are used to make audio edits sound smooth. Set this to the number of frames you want dissolves between audio edits to last.

Center-Panned

This setting is not used for Interplay Central. Sound on Tape and Voice Over

3. Click Apply to save any modifications made to your settings.

Checklist: Configure Interplay Central Middleware Server

Deploying Another Certificate to the Middleware Server

On an installed Interplay Central middleware server the default 'non-trusted' self-signed certificate key store gets generated on the first startup of the server. It resides at this location:

%programdata%\Avid\AvidInterplayCentralService\ssl\jetty.keystore

However, you might want to configure your own, possibly trusted certificate. For instance, existing certificates might be wanted to get imported into the existing key store, or a new key store with a certificate that has been signed by a trusted certificate authority (CA) could be provided. If you want to configure your own, you must provide a custom keystore file that meets the requirements of a JKS (Java key store), and complete the following steps:

To deploy another certificate:

1. Modify the following file:

%ProgramFiles(x86)%\Avid\Interplay Central\Server\config\application. properties

Add the corresponding attributes with its appropriate values:

Attribute Description

• system.org.osgi.service.ssl.password

• system.org.osgi.service.ssl.keypassword

• system.org.osgi.service.ssl.algorithm The current default decryption algorithm is 'RSA'. So

• system.org.osgi.service.https.keystore.path This is the file name of the new keystore file that needs

These are the passwords that go along with the certificate generation process. The passwords might be 'Jetty obfuscated'.

this attribute could be omitted if it matches already.

to be put at: %programdata%\Avid\AvidInterplayCentralService\ssl\

2. Restart the Interplay Central service to pick up the new keystore.

3 The Interplay Central Playback Server

Interplay Central playback server reads multiple media assets and sequences via Interplay, and MXF files residing on an ISIS, and then compresses that media for playback on Internet-connected clients. In an Interplay Central system, a site can “cluster” multiple playback servers to scale horizontally.

The following main topics describe the installation and configuration procedures of the playback server(s).

• Checklist: Before You Begin

• Checklist: Set up Interplay Central Playback Server

- The Wiring Diagram for the Interplay Central Playback Servers

- Installing the Operating System and Interplay Central Playback Services

- Configure the Interplay Central Playback Service

- Restart Interplay Central and ISIS Services

- Changing Compression Level Configuration

Checklist: Before You Begin

Before you begin, make sure you have the following items on hand:



Item

The Interplay Central playback server(s)



The Redhat Linux operating system (RHEL 6.0) installation .iso file or DVD media



The Interplay Central playback services installation USB drive



A laptop or destop computer running the Windows XP, Vista or Windows 7 operating system.



Checklist: Set up Interplay Central Playback Server

The server on which you are installing the Interplay Central Playback services should be physically installed in your engineering environment, and the appropriate network connection(s) to Avid ISIS and/or the house network should be made.

The installation and configuration processes require access to the server’s console:

• Directly by connecting a monitor and keyboard to the server

• Remotely via KVM or comparable solution

When you are ready to set up the Avid Interplay Central playback server(s), ensure the following tasks are completed.





Tasks Refer to...

Physically install the playback servers. “The Wiring Diagram for the Interplay

Central Playback Servers” on page 60

Also, ensure that the raid drive set is configured before installing the operating system.

Install the operating system and Interplay Central Playback services.

Copy the Red Hat Linux operating system to the



USB drive, which is supplied by Avid for Interplay Central Playback service installations.

Start the server and access the BIOS to check



settings

“Installing the Operating System and Interplay Central Playback Services” on page 61

“Copying the .iso File to the USB drive” on page 62

“Accessing the BIOS” on page 63

Checklist: Set up Interplay Central Playback Server





Tasks Refer to...

Boot the server from the USB drive and run the



installer.

The installation process installs the Red Hat operating system and all Avid software components necessary for the playback server. Some configuration is also required during the installation procedure.

Edit configuration files to set up the network



interface. This task occurs during the installation process.

Remove USB drive and reboot



Install & configure the load balancer for the playback server(s).

Configure the Interplay Central Playback service. “Configure the Interplay Central

Restart the services and and test connectivity by loading an asset into the Media pane.

(Optional) Customize the compression levels. “Changing Compression Level

“Booting Server from USB drive and Running the Installer” on page 64

“Configure the Load Balancer for the Playback Server” on page 71

Playback Service” on page 66

“Restart Interplay Central and ISIS Services” on page 74

Configuration” on page 75

The Wiring Diagram for the Interplay Central Playback Servers

The playback servers must be installed and connected to the ISIS via a Zone 1 (direct) or Zone 2 (through a switch) connection.

• For 10GigE connections, use the Myricom 10GigE NIC in PCI slot 4.

• For GigE connections, do not use the on-board Broadcom GigE ports. You should have an Intel PROset quad-port GigE NIC in PCI slot 2. Connect to the left-most port on that NIC.

Checklist: Set up Interplay Central Playback Server

Consult the following wiring diagram for clarification.

1 PCI slot 4

2 PCI slot 2

Installing the Operating System and Interplay Central Playback Services

The server on which Interplay Central Playback services are installed is a specific hardware profile that you have received from Avid or procured independently. For more information, refer to the hardware specifications for Interplay Central on the Avid Web site.

Interplay Central Playback services require a server running the Red Hat Linux operating system. The supported version of this OS is RHEL 6.0. Do not install patches or upgrade the Red Hat operating system on your server. Avid will advise you when patches or upgrades are required.

To install the operating system and the Interplay Central Playback services:

1. Copy the Red Hat operating system (the .iso file) to the USB drive. For more information, see the procedure on page 62.

2. Start the server and access the BIOS to check settings. For more information, see the procedure on page 63.

3. Boot the server from the USB drive and run the installer. For more information, see the procedure on page 64.

Copying the .iso File to the USB drive

Avid does not redistribute the Red Hat Linux operating system media on the USB drive. You must download the .iso file from Red Hat directly—or use the Red Hat OS Installation DVD that comes with your server—then copy the OS installation media to the USB drive Avid provides for Interplay Central Playback service installations.

To copy the operating system installation .iso file to the USB drive:

1. Log in to a Windows-based laptop or desktop computer.

2. Do one of the following:

t Make sure the .iso file is accessible locally, which is recommended, or over the network

from your computer.

t Insert the Red Hat OS Installation DVD into your computer.

If you do not have the .iso file or DVD, you can download the .iso file by logging into

rhn.redhat.com, using your Red Hat account credentials, and get it. Remember to download only the supported version of RHEL. For more information on supported versions and compatibility, see the latest Interplay Central ReadMe available on the Avid Knowledge Base.

3. Open Windows Explorer and navigate to the USB drive.

Checklist: Set up Interplay Central Playback Server

The USB drive contains three files:

- iso2usb.exe

-ks.cfg

- ICPS_installer_v100.tar.gz

4. Double-click the executable file, iso2usb.exe.

The ISO2USB for CentOS/RedHat window appears.

5. Do one of the following:

t If you downloaded the .iso file, select the Diskimage radio button, then click the Ellipses

(...) button and navigate to the .iso file.

t If you inserted the Red Hat OS installation DVD, select the CD Disk radio button.

6. Click OK.

The system copies the .iso file to the USB drive, a process that takes 5-to-10 minutes. After the copy process is complete, the USB drive has everything needed for a complete installation of Interplay Central playback services on the playback server.

Copying the .iso file to the USB drive is a one-time process. If you ever have to reinstall Interplay

Central Playback services, you will not need to repeat this procedure.

Accessing the BIOS

The Interplay Central playback server hardware is frequently shipped with BIOS settings set to Power-Saving mode. Interplay Central Playback services are CPU and memory intensive processes, especially when under heavy load. Avid recommends, for better performance, you ensure that your server is set to operate at Maximum Performance.

While the procedure explained in this section can be done before or after installation of services,

Avid recommends it be completed immediately.

To start the server and access the BIOS to check settings:

1. Power up the server.

2. When the console displays the splash image with an option to enter the Setup menu, press F9.

The main screen of the ROM-Based Setup Utility appears and displays a long list of system-specific options, one of which is called Power Management Options.

You can use the Up Arrow or Down Arrow keys to select an option and press the Enter key to view or modify any of the options.

3. Select Power Management Options.

Checklist: Set up Interplay Central Playback Server

Over the main screen, the options for power management appear.

4. Select HP Power Profile.

A list of settings for the HP Power Profile appears, which are:

- Balanced Power and Performance

- Minimum Power Usage

- Maximum Performance

-Custom

5. Use the Up Arrow or Down Arrow keys to highlight Maximum Performance. Then press Enter to save your selection as the new configuration setting.

You are returned to the previous list of options.

6. Press Escape to return to the main menu of system-specific options.

If you are ready to run the Interplay Central installer, make sure you insert the USB drive into

the server’s USB port before you exit the ROM-Based Setup Utility.

7. Press F10 to save and exit the utility program. The server will reboot with the new configuration settings.

Checklist: Set up Interplay Central Playback Server

Booting Server from USB drive and Running the Installer

The Interplay Central Playback services installation process installs the Red Hat operating system and all necessary Avid software components. It is almost completely automated, although there is some configuration you will need to do during the process.

To boot the server from the USB drive and run the installer:

1. Insert the USB drive.

2. Power on the server.

The Welcome screen will appear, displaying the Red Hat logo and a list of options. The first, Install or upgrade an existing system, is selected by default.

3. Accept the default by pressing Enter.

The first option is used automatically if you do nothing and wait sixty seconds.

The Red Hat operating system packages are installed; this will take 5-to-10 minutes. After the process is complete, you will be prompted to reboot.

4. Do not press Enter. First, remove the USB drive from the server, and then press Enter.

If you press Enter by mistake, remove the USB drive as quickly as possible and before the system boots up again.

Rebooting the server triggers the first-time boot-up on the system drive. The Text Mode Setup Utility appears, displaying the Choose a Tool menu.

5. Use the Tab key to navigate down the menu.

6. Press Enter to select Keyboard configuration and run the tool.

The Keyboard Selection menu appears.

7. Again using the Tab and Enter keys, select the language option for your keyboard.

You are returned to the Choose a Tool menu.

8. Select the Network configuration option.

The Select Action menu appears.

9. If you are setting up a cluster of Interplay Central playback servers, or if you want to set up a static IP, choose the Device configuration option. Static IP is required when setting up a load balanced cluster of servers. Press Enter.

The Select A Device menu appears, displaying a list of network interface ports.

10. Choose the device option corresponding to eth0.

- For GigE connections to the network and ISIS, you must select the Intel Corporation

82545EM (or similar) device on eth0.

Checklist: Set up Interplay Central Playback Server

- For 10GigE connections to the network and ISIS, you must select the Myricom device

on eth0.

- Do not select any Broadcom device; these are on-board GigE ports that are not

supported by ISIS.

11. Press Enter to save your selection.

The Network Configuration screen appears, letting you enter important configuration settings.

12. Enter the network device information in the corresponding fields:

a. Keep the default name: eth0.

b. Keep the default device: eth0.

c. Press the spacebar to disable DHCP.

d. Enter the playback server’s static IP address.

e. Enter the network’s default gateway IP address.

f. Enter the IP addresses for the primary and secondary DNS servers.

13. Select OK and press Enter.

You are returned to the Select A Device menu.

14. Select Save and press Enter.

You are returned to the Select Action menu.

15. Select the DNS configuration option.

The DNS Configuration screen appears, letting you enter important DNS settings.

16. Enter the DNS information in the corresponding fields:

a. Enter the hostname for the DNS server. Syntax: <machine name>

b. Re-enter the IP addresses for the primary and secondary DNS servers.

c. Leave the tertiary DNS server field blank, if there isn’t one.

d. If you did not disable DNS, you must enter the DNS search path domain.

17. Select OK and press Enter.

You are returned to the Select Action menu.

18. Select Save & Quit and press Enter.

You are returned to the Choose a Tool menu.

19. Select Quit and press Enter.

You will be prompted to log in to the server.

20. Log in with root credentials.

Checklist: Set up Interplay Central Playback Server

When configuring the Interplay Central playback server at the Linux console, you do not need to

create a special user account. Use the Root account. The default password is Avid123.

21. At the prompt, enter

The date and time will appear. If necessary, adjust the date by entering the date command again from the command prompt with the proper date in the format For instance, type:

The correct date and time you set will appear.

22. At the prompt, enter:

23. If setting up a cluster of servers, repeat this procedure for each playback server.

You are now ready to configure the Interplay Central Playback services.

date

to check the date and time of the operating system.

date 10041103

service network restart

Configure the Interplay Central Playback Service

When you are ready to configure the Playback service, you can do so from any computer on the network with a browser, by signing in to the service’s Web-based user interface, known as the ICPS Configuration portal.

Avid recommends using the Google Chrome browser, but any are supported. However, do not use

multiple tabs in the browser to configure preferences as this may impact your ability to save modifications.

To configure the Interplay Central Playback service:

1. Log in to the ICPS Configuration portal. For more information, see “Log in to ICPS

Configuration Portal” on page 67.

MMDDhhmm[[CC]YY]]

2. Configure the Interplay Preferences. For more information, see “Configure Preferences for

Interplay” on page 68.

3. Configure the ISIS Preferences. For more information, see “Configure Preferences for ISIS”

on page 70.

4. Configure the load balancer. For more information, see “Configure the Load Balancer for the

Playback Server” on page 71.

Log in to ICPS Configuration Portal

You need access to a computer with a Web browser and network access to the Interplay Central playback servers you are configuring. After logging in, you will have the opportunity to customize your Interplay Central Playback services administrator’s account, such as changing the password.

To log in to the ICPS Configuration portal:

1. Open a browser.

2. Enter the hostname of the Interplay Central playback server you want to configure. The syntax is:

The login screen appears.

http://<hostname>

Checklist: Set up Interplay Central Playback Server

3. Log in for the first time with root credentials, which are case sensitive:

User name:

Password:

You can change the default password for the root account later by clicking the Change Password

link in the top right corner of the Web page.

Administrator

Avid123

Enter a new password, twice in the fields provided, and click Submit. A message appears to indicate when the password is successfully changed.

Configure Preferences for Interplay

Interplay Central Playback services work with Interplay Production. Although Interplay Central users sign in with their own credentials and user their own Interplay credentials to browse media assets, the Interplay Central Playback services use a separate set of Interplay credentials to resolve playback requests and check-in voice-over assets recorded by Interplay Central users.

Checklist: Set up Interplay Central Playback Server

Therefore, a unique set of user credentials are required for Interplay Central Playback services. The set should have the following attributes:

• Be an Interplay administrator account

• Not be used or shared with any human users

• Have permission to read all folders in the workgroup

• Have a user name that indicates the purpose of the user credentials. Avid recommends something like: icps-interplay.

To configure preferences for Interplay:

1. Log in to the ICPS Configuration portal. For more information, see “Log in to ICPS

Configuration Portal” on page 67.

By default, the Interplay tab is displayed at login.

Checklist: Set up Interplay Central Playback Server

2. Do the following in the Interplay Credentials section:

a. In the Host field, type the hostname of the Interplay Engine.

b. In the User field, type the name of the Interplay user account reserved for Interplay

Central Playback services.

c. In the Password field, type the password for the user account.

3. Do the following in the Workgroup Properties section:

a. In the MI Host field, type the hostname (or IP address) for the Media Indexer. For

multiple Media Indexer services, use the following syntax:

b. In the WG Name field, type the name of the Interplay workgroup, which is case

sensitive.

c. In the Lookup Servers field, type the hostnames (or IP addresses) for the computers

running the Lookup services. The syntax is:

4. Make sure the Enable Dynamic Relink is checked so that communication with Media Indexer is enabled. Dynamic Relink is required for multi-resolution workflows.

5. Click Save.

Configure Preferences for ISIS

Interplay Central Playback services use a separate set of ISIS credentials to read media assets for playback and to write audio assets for voice-over recorded by Interplay Central users.

Therefore, a unique set of user credentials are required for Interplay Central Playback services. The set should have the following attributes:

• Be an ISIS administrator account

• Not be used or shared with any human users

• Have permission to read all workspaces, and to write to the workspace flagged as the VO (voice-over) workspace

• Have a user name that indicates the purpose of the user credentials. Avid recommends something like: icps-isis.

To configure the preferences for ISIS:

1. Log in to the ICPS Configuration portal. For more information, see “Log in to ICPS

Configuration Portal” on page 67.

2. Click the ISIS tab.

Checklist: Set up Interplay Central Playback Server

3. Enter the following:

a. In the Host field, type the hostname (or IP address) of the ISIS shared storage server.

b. In the User field, type the name of the ISIS user reserved for Interplay Central Playback

services.

c. In the Password field, type the password for the user account.

4. If your connection to ISIS is via Zone 2 (through a switch as opposed to a direct connection in Zone 1), enable Remote Host. Then in the System Directors field, type the IP addresses for the ISIS System Directors, using the following syntax:

5. In most cases, the only network connection for the Interplay Central playback server will be a single GigE or a 10GigE connection. This is the connection for both the ISIS and to the network for outbound compressed playback media. If you have other network connections, you must indicate which of them are used by ISIS as opposed to other network activity.

a. In the Use IFNames field, enter the network device ID (usually eth0) used by ISIS.

b. In the Ignore IFNames field, enter all other active network devices not used by ISIS,

such as eth1, eth2, etc.

6. Set the Client Mode to:

t 1 Gb Connection—for 1 GigE connections

t 10 Gb Connection—for 10 GigE connections

7. Click Save.

Configure the Load Balancer for the Playback Server

Interplay Central playback servers can be clustered to provide redundancy and scalability. You can cluster up to 16 nodes.

Interplay Central playback server clusters require no specific load balancing hardware, just the servers that comprise the cluster. One server operates as a playback server and a load balancer, distributing user connections to the other nodes in the cluster evenly.

Clustering Interplay Central playback servers is a load balancing solution, not a high

availability solution. Although playback server nodes can fail and sessions will be redirected to operational nodes, there is a risk that the master node fails and all sessions are interrupted until the master node is restored.

Setting up and maintaining a cluster of playback servers involves a few procedures:

To set up load balancing and maintain a cluster of playback servers:

1. Ensure the playback server that will be the master node is installed, connected to ISIS, and configured properly. For more information, see “The Master Node” on page 72.

2. Define a master node for playback nodes. The procedure is on page 72.

3. Confirm the master node’s cluster list by following the procedure on page 73.

4. If you need to add a node to an existing cluster, do the steps on page 73.

5. If you need to remove a dead node from an existing cluster, do the steps on page 74.

The Master Node

Before you can define the master node and set up a cluster, the playback server that will be the master node must be fully installed with connections to ISIS. It is not necessary to configure the nodes using the ICPS Configuration portal, although they too must be connected to the ISIS (in Zone 1 or Zone 2).

The Interplay and ISIS preferences must be configured for the playback service on the server that is the master node, because these settings will be automatically passed to the other playback nodes when you set up the cluster. For more information, see “Configure the Interplay Central

Playback Service” on page 66.

Checklist: Set up Interplay Central Playback Server

Defining a Master Node for Playback Nodes

You must edit a system configuration file to define the hostname or IP address of the master node to add a node to a cluster. The following procedure must be done on each playback server, except the one designated as the master node.

To define a master node for playback nodes:

1. Log in to the playback node using the server’s root credentials.

2. Open the file

/etc/sysconfig/avid-common-params

3. Remove the pound sign (#) from the first line of the file to uncomment it.

The line should read:

export AVID_CONFIG_HOST=”localhost”

4. Change “localhost” to the hostname or IP address of the master node.

The line should read:

export AVID_CONFIG_HOST=”<master hostname>”

hostname> is the real name or IP address of the master node.

5. Save and close the file.

6. In a shell, as root, restart all Interplay Central Playback services. For more information, see

“Restart Interplay Central and ISIS Services” on page 74.

in a text editor.

where <master

Confirming the Master Node’s Cluster List

After you have completed the previous procedure for all playback nodes (except the master node), navigate to the Configuration portal of the master node to confirm the cluster node list.

To confirm the cluster node list:

1. Log in to the ICPS Configuration portal. For more information, see “Log in to ICPS

Configuration Portal” on page 67.

2. Click the Load Balancer tab.

All of the nodes for which you defined a master node in the previous procedure appear in the list.

If only the master node appears, click Update.

3. Click the Show Sessions icon in a node’s row to view its current connection(s).

A list of that node’s connections will appear for you to review.

Adding a Node to an Existing Cluster

You can add a node to a cluster at any time.

Checklist: Set up Interplay Central Playback Server

To add a node to an existing cluster:

1. Log in to the playback node—the one you want to add—using the server’s root credentials.

2. Open the file

3. Remove the pound sign (#) from the first line of the file to uncomment it.

The line should read:

4. Change “localhost” to the hostname or IP address of the master node.

The line should read: hostname> is the real name or IP address of the master node.

5. Save and close the file.

6. In a shell, as root, restart all Interplay Central Playback services. For more information, see

“Restart Interplay Central and ISIS Services” on page 74.

7. Confirm the addition of the node to the cluster by logging in to the ICPS Configuration portal. For more information, see “Log in to ICPS Configuration Portal” on page 67.

8. Click the Load Balancer tab.

The added node should appear in the list.

If you do not see the node, click Update.

/etc/sysconfig/avid-common-param

in a text editor.

export AVID_CONFIG_HOST=”localhost”

export AVID_CONFIG_HOST=”<master hostname>”

where <master

Checklist: Set up Interplay Central Playback Server

Removing a Dead Node from an Existing Cluster

If a node fails, it might not be properly removed from the node list, which means the master will still attempt to send connections to the dead node. Although these connections will eventually find an operational node, keeping the dead node in the list can cause unnecessary delays. You should remove any dead node from the node list until it has been serviced and restored.

To remove a dead node:

1. Log in to the ICPS Configuration portal.

2. Click the Load Balancer tab.

3. Do one of the following:

t If you know which node is dead, click the Remove Node icon in the row of the node you

want to remove.

t Click Reset Settings. This will remove all nodes from the cluster list. Active nodes will

re-add themselves after a few seconds. Clients connected to active nodes will not be affected. Clients connected to any dead nodes will be redirected to active nodes.

Restart Interplay Central and ISIS Services

After completing the installation and configuration of the playback server, restart the services.

Restart all services, including those for ISIS, from the Linux console’s command prompt.

To restart Interplay Central and ISIS services:

1. Log in to the root account.

The command prompt will appear, ending with a pound sign (#).

2. Type:

service avid-all restart

and press Enter. This command restarts all Interplay

Central Playback services.

3. Type:

service avid-isis restart

and press Enter. This command restarts all ISIS

services.

After restarting the services, you can test connectivity by signing in to Interplay Central and trying to load video into the Media pane.

Retrieve Interplay Central Playback Service Logs

This procedure is not required at installation, but as you use Interplay Central you might encounter performance or playback issues. You should report these occurrences to Avid. When you do, Avid Customer Success personnel might ask you to retrieve system and component logs from your Interplay Central playback server(s).

Checklist: Set up Interplay Central Playback Server

To retrieve Interplay Central playback service logs:

1. Log in to the ICPS Configuration portal. For more information, see “Log in to ICPS

Configuration Portal” on page 67.

2. Click the Logs tab.

3. Check the box(es) next to the log(s) you want to retrieve.

4. Choose one of the following:

t All—to retrieve all logs of the corresponding type.

t Current—to retrieve only the latest log since last server restart.

5. Click Download Logs.

The logs are downloaded to the computer you are using as a .zip file. Inside the .zip file is one .log file for each requested log.

Changing Compression Level Configuration

By default, Interplay Central playback server uses compression levels of 40 for good (low), 60 for better (medium), and 80 for best (high). If you want to customize these levels for your site, you can do so by editing the application’s properties on the playback server(s).

Checklist: Set up Interplay Central Playback Server

System application.properties are located at:

C:\Program Files (x86)\Avid\Interplay Central\Server\config

However, changes to the configuration settings of this file can be lost after updates are installed.

To customize compression level configuration settings for Interplay Central:

1. Go to C:\ProgramData\Avid\AvidInterplayCentralService\config.

2. Open the custom application.properties file. If it does not exist you will have to create it.

The line to add or look for is:

com.avid.central.Player.compressionLevels={Low\:40, Medium\:60, High\:80}

Low, Medium, and High in the configuration settings correspond to options available to Interplay Central users. In the user interface, the options are called: Good, Better, and Best, respectively.

3. Modify the numerical values in that line accordingly and save your changes.

Take care when modifying the values. A typo, such as a missing colon (:), will affect playability of assets in the Media pane.

4 The Mobile Application

The Interplay Central mobile application is a native user interface designed to run on your BlackBerry computer system.

The following main topics describe the installation and configuration procedures necessary for the Interplay Central mobile application.

• Connection Basics

• Checklist: Before You Begin

• iNEWS Configuration for Mobile Integration

- Editing SYSTEM.CLIENT.MOBILE-VERSIONS

- Editing SYSTEM.CLIENT.MOBILE-IDS

- Adding Mobile Devices to the iNEWS Configuration File

• Install Interplay Central on the Blackberry

smart phone and enable direct, secure access to your station’s iNEWS newsroom

Connection Basics

The following image shows a basic illustration of how a Blackberry mobile device securely connects to an iNEWS newsroom computer system.

There are various connection options available when using the Interplay Central mobile application:

•WiFi

• Direct TCP (Carrier specific APN)

Connection Basics

• MDS or Blackberry Enterprise Server (BES)

• Blackberry Internet Services (BIS)

•WAP 2.0

The application is designed to automatically select the first available connection from the list of

options according to the priority shown in the list.

Avid requires the use of a Blackberry Enterprise Server. If your site does not plan to use a signed certificate for the the Interplay Central middleware server then users will need to configure their Blackberry devices to use the untrusted certificates by going through Advanced security settings (Proxy TLS) on each handheld.

Checklist: Before You Begin

Before you can enjoy the full functionality and freedom of Interplay Central mobile integration with iNEWS newsroom computer system, you will need to gather some important information and have it at the ready. For convenience, you can print the following table and fill in the information unique to your site.

Type of Information Needed Site Specific Notes

PINs from each Blackberry device

Checklist: Before You Begin

The hostname of the

middleware (Web application) server

Then ensure the following tasks are completed.





Tasks Refer to...

Configure iNEWS for licensed integration with the Interplay Central mobile application.

Install Interplay Central on the mobile device(s). “Install Interplay Central on the

Interplay Central

“iNEWS Configuration for Mobile Integration” on page 79

Blackberry” on page 83

iNEWS Configuration for Mobile Integration

Before you can connect to an iNEWS newsroom computer system from a device running the Interplay Central mobile application, you must edit a couple of system files in iNEWS so that iNEWS recognizes the Interplay Central mobile application as a properly licensed device.

The files to edit are:

• SYSTEM.CLIENT.MOBILE-VERSIONS

• SYSTEM.CLIENT.MOBILE-IDS

• iNEWS configuration file

Editing SYSTEM.CLIENT.MOBILE-VERSIONS

iNEWS Configuration for Mobile Integration

To edit the SYSTEM.CLIENT.MOBILE-VERSIONS story in iNEWS:

1. Sign in to an iNEWS workstation as a system administrator, or any user account with write access to the System directory.

2. Navigate to SYSTEM.CLIENT.MOBILE-VERSIONS and open the first story in that queue.

3. On a new line, add the version of the Interplay Central mobile application that will run on the mobile device.

4. Save the story.

5. Reconfigure the system. From the iNEWS console:

a. Select the master computer, which is typically server A.

b. Enter superuser mode, using the correct password.

The dollar sign ($) at the end of the console’s server prompt will change to a pound sign (#).

c. Take the system offline by typing:

d. Reconfigure the system by typing:

e. When the prompt reappears, bring the system back online by typing:

f. Press Ctrl+D to leave superuser mode.

The pound sign (#) at the end of the console’s server prompt will change back to a dollar sign ($).

Editing SYSTEM.CLIENT.MOBILE-IDS

A user can securely connect to an iNEWS newsroom computer system from any location with cellular service by using a Blackberry smart phone that is running the Interplay Central mobile application, but only if the personal identification number for that phone is recognized by the iNEWS system.

To edit the SYSTEM.CLIENT.MOBILE-IDS story in iNEWS:

1. Sign in to an iNEWS workstation as a system administrator, or any user account with write access to the System directory.

2. Navigate to SYSTEM.CLIENT.MOBILE-IDS and open the first story in that queue. If it does not exist, you will have to create it in the iNEWS database.

NRCS-A# offline

NRCS-A# configure

NRCS-A# online

iNEWS Configuration for Mobile Integration

3. Add the personal identification number (PIN)—one per line—for each mobile device that will use the Interplay Central mobile application to connect to iNEWS. Use a semicolon to add helpful commentary for future reference to the end of the line.

For instance, type:

On a Blackberry smart phone, you can locate your PIN by navigating to Options > Status.

4. Save the story.

5. Reconfigure the system. From the iNEWS console:

a. Select the master computer, which is typically server A.

b. Enter superuser mode, using the correct password.

The dollar sign ($) at the end of the console’s server prompt will change to a pound sign (#).

c. Take the system offline by typing:

d. Reconfigure the system by typing:

e. When the prompt reappears, bring the system back online by typing:

f. Press Ctrl+D to leave superuser mode.

The pound sign (#) at the end of the console’s server prompt will change back to a dollar sign ($).

32145AZ0 ; News director’s cellphone

NRCS-A# offline

NRCS-A# configure

Adding Mobile Devices to the iNEWS Configuration File

The configuration file (/site/config) lists all devices, servers, and resources configured to run on your iNEWS newsroom computer system and how they are connected. If a device is not in the configuration file, the system will not know about it and cannot use it.

NRCS-A# online

The following procedure is conducted at the iNEWS console. For more information, see “The iNEWS Console” and “System Configuration” chapters in the iNEWS Installation and Configuration Guide. Also, some steps require use of ed, the line editor. If you do not know how to use the line editor to modify lines in the file, please see “The Line Editor, ed” in the iNEWS Installation and Configuration Guide.

To edit /site/config for the Interplay Central mobile application:

1. Select all servers.

Whenever you make changes to any iNEWS site file, such as the configuration file, be sure to select all servers in your system at the console. Unlike database stories, site files are not automatically mirrored from one computer’s disk to another.

2. Type:

ed /site/config

iNEWS Configuration for Mobile Integration

After you press Enter, the editor responds by displaying a numerical value indicating the file size expressed as the number of characters, including spaces and returns.

The configuration file has two major sections: the host section and the device section. For Interplay Central mobile integration, you must edit both.

3. In the host section, add a resource list entry.

The format is:

For instance:

For dual or triple server systems, the configuration file will have multiple host sections to define which server handles which devices under various circumstances. Resource list entries should be added to each host section.

4. In the device section, add a resource line for the mobile devices.

The format is:

For instance:

5. Type w to write (save) your changes to disk.

Do not use an uppercase W in this step. Uppercase W will append the file you're editing to the existing file. The resulting file may be unreadable and will lead to problems with running your iNEWS system.

6. Type

7. (Optional) Use the configure command to test your configuration changes.

to quite the line editor.

The syntax is:

For instance, type:

When prompt returns, the configuration file has been checked. If the system detects any errors, it displays appropriate bad configuration messages.

reslist <device # or range> ; <comments>

reslist 2001:2005 ;Interplay Central mobile applications

mbl <device # or range> - gnews <device name> ;<comment>

mbl 2001:2005 - gnews - ;Interplay Central mobile applications

configure /site/config <system> <computer>

configure /site/config ab a

8. Reconfigure the system. From the iNEWS console:

a. Select the master computer, which is typically server A.

b. Enter superuser mode, using the correct password.

The dollar sign ($) at the end of the console’s server prompt will change to a pound sign (#).

c. Take the system offline by typing:

d. Reconfigure the system by typing:

e. When the prompt reappears, bring the system back online by typing:

f. Press Ctrl+D to leave superuser mode.

NRCS-A# offline

NRCS-A# configure

NRCS-A# online

Install Interplay Central on the Blackberry

The pound sign (#) at the end of the console’s server prompt will change back to a dollar sign ($).

Install Interplay Central on the Blackberry

The following procedure assumes licensing, setup, and configuration of the Interplay Central and iNEWS servers have already been completed.

To install Interplay Central on the Blackberry device:

1. Open the phone’s browser.

2. Navigate to the Blackberry folder on your site’s Interplay Central middleware (Web application) server by typing the URL in the following format:

<hostname>/bb/

For instance, if your server’s hostname is InterplayCentral-A, then you would type:

InterplayCentral-A/bb/

3. If prompted about “different domain name”, click Continue.

Some messages mentioned in this procedure might not appear during every installation.

4. The following message might appear:

You are attempting to open a secure connection, but the server’s certificate is not trusted.

If you receive this message, click Continue.

5. A Web page appears similar to the one shown in the following illustration:

Install Interplay Central on the Blackberry

Click the link provided on the Web page to download the native Blackberry mobile application for Interplay Central.

If the page does not appear, or you receive an “Access Denied: Insecure SSL Request” error, you

will need to modify the security settings (Proxy or Handheld TLS) on your Blackberry to allow for the Interplay Central middleware server to be a trusted host. For more information, see

“Modifying Your Phone’s Security Settings” on page 84.

6. When the Download Interplay Central screen appears, click Download.

A progress bar appears during the download after which a second dialog will appear once the application is installed successfully.

7. Click OK.

When the Interplay Central mobile application is installed on your smart phone, an icon representing the application is also installed. Depending on the version of Blackberry operating system, the icon can be found on the main menu of applications of in the Download folder. It can also be moved elsewhere like icons for any other BlackBerry applications.

The first time you start the application, you will be prompted with the following message:

“Would you like to grant Interplay Central trusted application status?” Select Yes.

Modifying Your Phone’s Security Settings

If the Interplay Central middleware server is not updated with a signed certificate, then the security settings (Proxy or Handheld TLS) for each BlackBerry handheld must be modified to allow for the server to be a trusted host.

To add a trusted host:

1. On your Blackberry, press the Menu button.

2. Select Options.

3. Select Security Options.

4. Select Advanced Security Options.

5. Select TLS.

6. Set TLS Default to Proxy.

7. Press the Menu button.

8. Select Add Host.

9. Enter the host name for the Interplay Central middleware (Web application) server.

10. Click OK.

11. Press the Back button.

12. Click Save, when prompted, to save the new settings.

Install Interplay Central on the Blackberry

5 Interplay Central Glossary

Administrators group

A default group used for Interplay Central user management that contains users with administrative privileges.

asset

An object that you can use to create stories and sequences. There are different types of assets, such as video media, audio media, graphics, images, and text. Asset usually refers to objects or also lists of objects, such as rundowns, that are stored in an asset management database.

Asset mode

If you click the Asset button in the Media pane, you can view media for the currently loaded asset and use controls that apply specifically to assets, such as controls for setting In and Out points. Compare with the definition of Output mode.

Assets pane

A pane in the client application that displays assets. These assets can result from a search or from browsing. Assets are displayed in a folder hierarchy, if applicable to the assets displayed.

authentication provider

A server that checks the credentials (user name and password) of a user and allows access. An Interplay Central administrator designates an authentication provider for imported users, such as a Windows Domain server.

Basic layout

A layout that a journalist uses to edit and create stories. You can view media in this layout but you cannot add video or audio to the story.

Contacts list

In the Message bar, a list of iNEWS users from which you can select a recipient of a message.

Cue List

The area in the Script Editor in which the journalist adds or edits production cues and machine control events, such as those for a character generator (CG).

Details pane

A pane in the Users layout and the System Settings layout that displays information and settings for a selected item.

drop zone

The part of an area into which you can move a pane. Each area has five drop zones: center, top, bottom, left, and right.

edit while capture (EWC)

See Frame Chase editing.

Frame Chase editing

A feature that lets you view and edit media while it is being captured from a line feed or ingest device. Also known as edit while capture (EWC).

Imported group

A default group used for Interplay Central user management that contains users imported from a Windows domain.

in-progress clip

A clip that is in the process of being captured. You can use in-progress clips in Frame Chase editing.

Interplay Central middleware server

A Web-application server used to manage communications between Interplay Central workstations and back-end systems.

Interplay Central Distribution service

A service used to coordinate jobs with Avid Media Services for sequence mixdowns and send to playback.

Interplay Central User Management service

A service that provides the ability to create and manage users and groups and authenticate users across multiple systems.

Interplay Central playback server

A Linux® based server that runs the Interplay Central Playback service. It concurrently reads multiple media assets and sequences residing on an ISIS, and compresses that media for playback on Internet-connected clients.

J-K-L play

The J-K-L keys on the keyboard allow you to play and shuttle through media at varying speeds. This feature is also referred to as three-button play or variable-speed play.

Launch pane

A pane in the client application from which you navigate to various locations. This pane displays remote file systems, local files systems, and other locations for assets.

Layout

A collection of panes designed for a specific purpose, such as a layout for journalists or a layout for administrators.

Layout selector

A list from which you select the layout that you want to work in.

L-cut

A split edit between two clips in which the video transition and the audio transition do not occur simultaneously. The audio transition can occur before the video transition or the video transition can occur before the audio transition.

locator

A frame-specific marker that a user can add when logging media. Locators are displayed in the Media Timeline and locator text is displayed as an overlay in the Media viewer.

master clip

A media object that contains pointers to media files in which the actual digital video and audio data is stored.

Match Frame

A feature that lets you load a source clip, a portion of which is contained in a sequence.

Media controls

In the Media pane, controls that let you play and move through an asset and edit an asset for use in creating a sequence. Which controls are displayed depends on the selected asset.

Media pane

A pane in the client application in which you can view and edit media assets, using the Media controls.

Media viewer

The section of the Media pane used to view an asset.

Media Timeline

In the Media pane, a graphical representation of the length and time spans of an asset or sequence.

Message bar

A section of the client application in which you can send and receive messages. The Message bar consists of the To field, the Message field, and the Send button.

Menu bar

A section of the client application from which you can select various menu options.

Message History

In the Message bar, arrow buttons are provided to let you read recent messages. A numerical indicator appears when multiple unread messages exist.

metadata

Data that describes an asset. Metadata includes properties, reservations, restrictions, and other information.

mixdown

A process in which multiple video tracks, multiple audio tracks, and effects are combined into a new master clip with one video track and a reduced number of audio tracks.

NAT (natural sound)

Audio recorded at the same time as the video, often by a microphone built in to a camera. Compare with the definition of SOT (sound on tape).

Output mode

If you click the Output button in the Media pane, you can view media for the currently loaded script sequence and use controls that apply specifically to script sequences, such as voice-over controls. Compare with the definition of Asset mode.

pagination

A system setting the specifies the maximum number of items listed in the Queue/Story pane or the Project/Story pane.

pane

An area can contain one or more panes. Multiple panes are layered within an area with the names of each pane appearing on tabs that the user can select to view.

position indicator

A vertical bar in the Media Timeline that indicates the location of the frame displayed in the Media viewer. You can drag the position indicator to scrub through a clip or sequence.

Progress pane

A pane in the client application that displays the progress and status of Interplay Central processes such as sequence mixdown and send to playback.

Project/Story pane

A pane in the client application that displays the contents of a project, its facets, and any associated stories.

Queue/Story pane

A pane in the client application that displays the contents of a queue with the contents of the story, including the story form.

rundown

A lineup or timed list of scripts indicating the order in which they will be aired during a news program.

Script Editor

A section of the Queue/Story pane in which a journalist creates and organizes the elements of a script. There are four sub-sections of the Script Editor: Story Form, Cue List, Story, and Sequence Timeline.

script

A compilation of elements that include the story that is sent to the teleprompter and read on the air, any video and audio that is broadcast with the story, as well as production cues and machine control instructions associated with the story.

script sequence

A series of video, audio, and images that you compose in the Script Editor and play in the Media pane. Script sequences are saved in the Interplay Production database and can be sent to a playback device.

Search bar

A section of the client application in which you can conduct a search for assets that match specific criteria.

Search pane

Send button

In the Message bar, the button you click to send a message.

1. A pane in the Basic or Video layout that lets a user search for information and assets.

2. A pane in the Users layout that lets an administrator search for Interplay Central groups and users.

segment

1. In a rundown, a portion of the show aired between commercial breaks.

2. A portion of the story body/text. A journalist uses segments to time the text and integrate it with video, audio, and production cues. Multiple timed segments are combined to form the overall story.

send to playback (STP)

The process of transferring a sequence to a playback device or playout server for broadcast.

sequence

Video, images and audio clips, or any combination, arranged in a series.

Sequence Timeline

The area of the Script Editor in which a journalist adds, rearranges, or removes video and audio clips associated with the story.

Settings pane

A pane in the System Settings layout from which you can select a group of settings to view or edit.

shuttle

To view media at speeds slower or faster than real time. In Interplay Central you can use the J, K, and L keys to shuttle through a clip or sequence.

sightline

The yellow bar in the Sequence Timeline that acts as a position indicator when playing a script sequence in the Media pane.

SOT (sound on tape)

Audio recorded at the same time as the video, often by a microphone separate from the one built in to a camera. Compare with the definition of NAT (natural sound).

source clip

A video clip or audio clip that is used as part of a sequence.

story

The text that is read on air. Also, the Story section is part of the Script Editor in which a journalist writes a story or views the text of an existing story.

Story Form

A section of the Script Editor that provides story information in fields that are predetermined by the iNEWS system administrator for each queue in the database.

STP (send to playback)

The process of transferring a sequence to a playback device or playout server for broadcast.

subclip

A clip created by marking IN and OUT points in a master clip and saving the frames between the points. The subclip does not contain pointers to media files. The subclip references the master clip, which contains pointers to the media files.

System Settings layout

A layout that an Interplay Central administrator uses to specify various configuration settings.

Timecode displays

In the Media pane, displays that provide timecode information for the loaded asset or sequence.

Timing taglines

Horizontal lines with pale yellow tags that appear in the Sequence Timeline to display estimated read times for story segments.

trim indicator

In the Sequence Timeline, a mark that appears at the beginning or end of a clip in the video column or audio column when hovering over that area with the mouse pointer. You can trim video and audio together, or you can trim them separately to create an L-cut.

Unassigned group

A default group used for Interplay Central user management that includes users that were removed from a group but are not members of any other groups.

User Management service

A service that provides administrators with the ability to create and manage users and groups, and authenticate users across multiple products with a single user name and password.

User Tree pane

A pane in the Users layout that displays groups and users in a hierarchical layout.

Users layout

A layout for Interplay Central user management that an Interplay Central administrator uses to import, create, and manage users and group.

Video layout

A layout that a journalist uses to edit and create stories that include video and audio.

Voice-over controls

Controls that let you record a voice over and adjust its volume.

window

The primary user interface element of the application.

zoom bar

In the Media pane, a control located below the Media Timeline that lets you enlarge a section of the Media Timeline so you can work more easily with long clips.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index

Index

Symbols

.iso file 62

Application database settings 54 ASF

install aps and services 34 lookup locators 48

Avid

online support 12 training services 12

Avid Service Framework

installation 34 lookup locators 48

back-end systems 15 backup database files 53 BIOS settings 63 Blackberry Enterprise Server (BES) 78 Blackberry Internet Services (BIS) 78 Blackberry security settings 84

certification

deploying 57 mobile application 78

Checklists

before you begin 21 configure middleware server 46 mobile application

before you begin 79

playback server

before you begin 59

setup checklist 59 prior to installation 22 set up middleware server 32 system setup tasks 20

cluster list 73 clusters, creating 52 compression levels 75

Distribution service 38 DNS testing 49 dual-server systems 17

set up load balancer 28

high availability 52

ICPS Configuration portal 66 iNEWS

adding mobile devices 81 configure licensing 26 mobile application configuration 79 system settings configuration 49 view licensing limits 24

Interplay Administrator 54 Interplay Central

adding mobile devices to iNEWS 81 checklist to configure middleware server 46 checklist to set up middleware server 32 getting started 14

Index A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

install distribution service 38 install service and modules 42 install the User Management service 40 installing on a Blackberry 83 middleware server 17, 31

database settings 54

mobile application 77

connection basics 78 modifying Blackberry security settings 84 optional applications 38 playback server 58

wiring diagram 60 playback service logs 74 run set up application 42 system components 15 workstation defined 15

Interplay preferences 68 Interplay Production

installing the license 23 system settings configuration 50

ISIS

install client software 33 restarting services 74 set up remote host 47

ISIS preferences 70

defining 72

Middleware server

defined 15 deploying certification 57 DNS testing 49 explained 17 load balancing 17 port configuration 52

mobile application 77

checklist for before you begin 79 connection basics 78 iNEWS configuration 79 modifying Blackberry security settings 84

modules

defined 15 types of 19

non-trusted certification 57

Online support 12

Licensing 23

configuring iNEWS 26 installing Interplay Production license 23 viewing iNEWS limits 24

Load balancer

adding nodes to cluster lists 73 configuring 71 confirm master node cluster list 73 defining master node 72 dual-server systems 17, 19 master node 72 removing dead nodes 74 setting up 28

log files 74 lookup locators 48

master node 72

Playback server

accessing the BIOS 63 before you begin checklist 59 boot from USB drive 64 configure Interplay preferences 68 configure ISIS preferences 70 configure the service 66 defined 15 installing the OS and playback services 61 load balancing 71 set up server checklist 59

Playback service

configuring 66 restarting 74

port configuration 52

Red Hat operating system 61

copying the .iso file 62

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index

SYSTEM.CLIENT.MOBILE-IDS 80 SYSTEM.CLIENT.MOBILE-VERSIONS 79 SYSTEM.CLIENT.VERSIONS 26 SYSTEM.CLIENT.WINDOWS 27

Training services 12 Troubleshooting 12 trusted certification 57

User Management

backup for database files 53 creating clusters for high availability 52

User Management service 40

Index A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

100

Pinnacle Systems Interplay Central - 1.0 Installation Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Using This Guide

Symbols and Conventions

If You Need Help

Avid Training Services

1 Getting Started

System Components

Interplay Central Middleware Server

Load Balancing Dual-Server Systems

Interplay Central Playback Server

Modules

Interplay Central Workstation

System Setup Tasks

Checklist: Before You Begin

Gather Site Information

Licensing Requirements and Setup

Installing the Interplay Production License for Interplay Central

Verifying Interplay Central Licenses on iNEWS

Configure iNEWS for Integration with Interplay Central

Editing SYSTEM.CLIENT.VERSIONS

Editing SYSTEM.CLIENT.WINDOWS

Setting up the Load Balancer

2 The Interplay Central Middleware Server

Checklist: Set up Interplay Central Middleware Server

Install the ISIS Client Software

Install Avid Service Framework

Optional Applications

Install the Interplay Central Distribution Service

Install the Interplay Central User Management Service

Run the Interplay Central Setup

Checklist: Configure Interplay Central Middleware Server

Set up the Remote Host for ISIS

Specify a Lookup Locator for Avid Service Framework

Run DNS Tests against Hosts in the Network

Configure System Settings for iNEWS Integration

Configure System Settings for Interplay Integration

Creating a Cluster for User Management

Changing Port Configuration

Set the Backup Location for User Management Database Files

Configuring the Application Database Settings

Deploying Another Certificate to the Middleware Server

3 The Interplay Central Playback Server

Checklist: Before You Begin

Checklist: Set up Interplay Central Playback Server

The Wiring Diagram for the Interplay Central Playback Servers

Installing the Operating System and Interplay Central Playback Services

Copying the .iso File to the USB drive

Accessing the BIOS

Booting Server from USB drive and Running the Installer

Configure the Interplay Central Playback Service

Log in to ICPS Configuration Portal

Configure Preferences for Interplay

Configure Preferences for ISIS

Configure the Load Balancer for the Playback Server

The Master Node

Defining a Master Node for Playback Nodes

Confirming the Master Node’s Cluster List

Adding a Node to an Existing Cluster

Removing a Dead Node from an Existing Cluster

Restart Interplay Central and ISIS Services

Retrieve Interplay Central Playback Service Logs

Changing Compression Level Configuration

4 The Mobile Application

Connection Basics

Checklist: Before You Begin

iNEWS Configuration for Mobile Integration

Editing SYSTEM.CLIENT.MOBILE-VERSIONS

Editing SYSTEM.CLIENT.MOBILE-IDS

Adding Mobile Devices to the iNEWS Configuration File

Install Interplay Central on the Blackberry

Modifying Your Phone’s Security Settings

5 Interplay Central Glossary

Index

Symbols