Pinnacle Systems Media Distribute - 2.6 Installation Manual

Media | Distribute

Installation and Configuration Guide

Version 2.6

Legal Notices

Product specifications are subject to change without notice and do not represent a commitment on the part 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.

This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents.

This document is protected under copyright law. An authorized licensee of Media | Distribute 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.

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

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)

Media | Distribute enables its users to access certain YouTube functionality, as a result of Avid's licensed use of YouTube's API. The charges levied by Avid for use of Media | Distribute are imposed by Avid, not YouTube. YouTube does not charge users for accessing YouTube site functionality through the YouTube APIs.

Media | Distribute uses the bitly API, but is neither developed nor endorsed by bitly.

Android is a trademark of Google Inc.

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

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 Ignite, 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, Beat Detective, Beauty Without The Bandwidth, Beyond Reality, BF Essentials, Bomb Factory, Bruno, C|24, CaptureManager, ChromaCurve, ChromaWheel, Cineractive Engine, Cineractive Player, Cineractive Viewer, Color Conductor, Command|24, Command|8, Control|24, Cosmonaut Voice, CountDown, d2, d3, DAE, D-Command, D-Control, Deko, DekoCast, D-Fi, D-fx, Digi 002, Digi 003, DigiBase, 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, Do More, 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, HyperSPACE, HyperSPACE HDCAM, iKnowledge, Image Independence, Impact, Improv, iNEWS, iNEWS Assign, iNEWS ControlAir, InGame, Instantwrite, Instinct, Intelligent Content Management, Intelligent Digital Actor Technology, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, InterFX, Interplay, inTONE, Intraframe, iS Expander, iS9, iS18, iS23, iS36, ISIS, IsoSync, LaunchPad, LeaderPlus, LFX, Lightning, Link & Sync, ListSync, LKT-200, Lo-Fi, MachineControl, Magic Mask, Make Anything Hollywood, make manage move | media, Marquee, MassivePack, Massive Pack Pro, Maxim, Mbox, Media Composer, MediaFlow, MediaLog, MediaMix, Media Reader, Media Recorder, MEDIArray, MediaServer, MediaShare, MetaFuze, MetaSync, MIDI I/O, Mix Rack, Moviestar, MultiShell, NaturalMatch, NewsCutter, NewsView, NewsVision, Nitris, NL3D, NLP, NSDOS, NSWIN, OMF, OMF Interchange, OMM, OnDVD, Open Media Framework, Open Media Management, Painterly Effects, Palladium, Personal Q, PET, Podcast Factory, PowerSwap, PRE, ProControl, ProEncode, Profiler, Pro Tools, Pro Tools|HD, Pro Tools LE, Pro Tools M-Powered, Pro Transfer, 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, ScriptSync, SecureProductionEnvironment, Serv|GT, Serv|LT, Shape-to-Shape, ShuttleCase, Sibelius, SimulPlay, SimulRecord, Slightly Rude Compressor, Smack!, Soft SampleCell, Soft-Clip Limiter, SoundReplacer, SPACE, SPACEShift, SpectraGraph, SpectraMatte, SteadyGlide, Streamfactory, Streamgenie, StreamRAID, SubCap, Sundance, Sundance Digital, SurroundScope, Symphony, SYNC HD, SYNC I/O, Synchronic, SynchroScope, Syntax, TDM FlexCable, TechFlix, Tel-Ray, Thunder, TimeLiner, 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, Transit, TransJammer, Trillium Lane Labs, TruTouch, UnityRAID, Vari-Fi, Video the Web Way, VideoRAID, VideoSPACE, VTEM, Work-N-Play, Xdeck, X-Form, Xmon and XPAND! are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

Media | Distribute Installation and Configuration Guide • Created 3/31/16 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

Using This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 1 Installation for Media | Distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installing and Upgrading Media | Distribute in a Cluster Environment . . . . . . . . . . . . . . . . . . . 9

Identifying the Master and Non-Master Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Identifying the Virtual Cluster IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing and Upgrading Media | Distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring Media | Distribute on the Master Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring the Media | Distribute Installation on Non-Master Nodes . . . . . . . . . . . . . . . 15

Restarting PostgreSQL Service and Verifying the Cluster Installation. . . . . . . . . . . . . . . 17

Installing and Upgrading Media | Distribute on a Single Server . . . . . . . . . . . . . . . . . . . . . . . 17

Installing and Upgrading Media | Distribute on a Server . . . . . . . . . . . . . . . . . . . . . . . . . 18

Modifying Media | Distribute to Work with a Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Removing Media | Distribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 2 Configuration for Media | Distribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Verifying Your Media | Distribute Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Assigning Media | Distribute Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

MediaCentral | UX Security for Media | Distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring the Transcode Route. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring the Video Transcoding Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Send to Playback Configuration for Media | Distribute. . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuring a Telestream Vantage Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Validating the Vantage Transcode Route Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring the Harmonic ProMedia Carbon Transcoder . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring a RadiantGrid Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 3 Configuring System Accounts for Media | Distribute. . . . . . . . . . . . . . . . . . . . . 52

Configuring the Bitly Link-Shortening Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring a Twitter Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring a Facebook Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuring a Facebook Page Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Configuring a Vimeo Publication Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configuring a Vimeo V3 Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Configuring a YouTube Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring a YouTube v3 Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Configuring a Brightcove Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Configuring a Kaltura Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configuring an Ooyala Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Configuring an Atex Polopoly Web CMS Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring a WorldNow Web CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring thePlatform Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Configuring a WordPress CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Configuring an InternetBroadcasting CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuring a Generic CMS Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuring a Generic CMS Extended Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configuring a NoOpTranscoder Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Configuring a Generic OVP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 4 Configuring User Profiles for Media | Distribute. . . . . . . . . . . . . . . . . . . . . . . . 109

Configuring a User Profile for a Personal Twitter Account . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configuring a User Profile for a Personal Facebook Account. . . . . . . . . . . . . . . . . . . . . . . . 111

Configuring a User Profile for a Personal Facebook Page Account . . . . . . . . . . . . . . . . . . . 113

Appendix A Media | Distribute Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Appendix B Working with Media | Distribute Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Appendix C Modifying the Transcoder Monitoring Interval . . . . . . . . . . . . . . . . . . . . . . . . . 125

Appendix D Modifying the Settings for Interlaced Graphics . . . . . . . . . . . . . . . . . . . . . . . . 127

Appendix E Sample XSL for the Generic CMS Extended Profile . . . . . . . . . . . . . . . . . . . . . 128

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Using This Guide

This guide is intended for users of MediaCentral | UX with the Media | Distribute feature. This guide describes the installation and configuration procedures for Media Distribute, such as installing the Media Distribute software and configuring system accounts.

For information on using the publishing features of Media Distribute, see the Media | Distribute User’s Guide or the MediaCentral | UX Help. For administrative information for MediaCentral | UX, see the Avid MediaCentral | UX Administration Guide.

1 Installation for Media | Distribute

The supported configuration for Media Distribute requires you to install Media Distribute on your MediaCentral | UX server, which is part of your MediaCentral installation and configuration. For installation information, see the Avid MediaCentral Platform Services Installation and Configuration Guide.

The Media Distribute installation procedures assume you have installed Avid MediaCentral Platform Services (MCS). You must extract the Media Distribute installation package from Media_Distribute_[version]Build[xx]_Linux.tar.gz. You run the installation file itself from a shell script called install.sh. This installs the plug-in needed for MediaCentral UX to access the Media Distribute functionality, as well as the avid-mpd service which provides the functionality for Media Distribute workflows.

The procedures for installing Media Distribute depend on whether you install the application components in a cluster environment or on a single MediaCentral server.

• If you deploy MCS and components on a master node and one or more non-master nodes in a cluster configuration, see “Installing and Upgrading Media | Distribute in a Cluster

Environment” on page 9.

• If you deploy all MCS and components on a single server, see “Installing and Upgrading

Media | Distribute on a Single Server” on page 17.

If necessary for security considerations, you can configure Media Distribute to communicate with the Internet through a proxy server. For more information, see “Modifying Media | Distribute to Work

with a Proxy Server” on page 20.

The following installed components are necessary for the current version of Media Distribute:

• Avid MediaCentral Platform Services v2.6.x (if you work with a cluster configuration, you need to ensure that all nodes in the cluster function properly)

• iNEWS 3.4.3 or later (for MCS configurations with iNEWS)

• Avid ISIS v4.7.6 driver

• Red Had Enterprise Linux (RHEL) v6.5

• MediaCentral Distribution Service

You also need to ensure that the following are available for Media Distribute:

• Interplay Media Services Engine

• Interplay Transfer engine

• At least one installed transcode provider

• STP encoder

• Internet connection for publishing to social media sites

Installing and Upgrading Media | Distribute in a Cluster Environment

The procedures in this section assume you have already installed and configured your MediaCentral Platform Services on your clustered servers. For more information on configuring a MediaCentral cluster environment, see the Avid MediaCentral Platform Services Installation and Configuration Guide. To configure Media Distribute, you require the following:

• RHEL and MediaCentral software components are installed on all servers in the cluster.

• All servers are set up and configured correctly for the cluster.

• Failover processes work correctly.

Installing Media Distribute entails the following steps:

• Copying the Media Distribute installation files to a USB drive.

• Identifying the master and non-master nodes in your configuration, and identifying the virtual cluster IP address (see “Identifying the Master and Non-Master Nodes” on page 10 and

“Identifying the Virtual Cluster IP” on page 10).

• Installing Media Distribute on the master and all non-master nodes in your cluster configuration.

• Setting up the Media Distribute database on the master node of the cluster. You must install Media Distribute on all nodes, but you only configure the database once.

• Modifying the MCS configuration file to change the host address to the virtual cluster IP of the cluster.

If you deploy all MCS and components on a single server, see “Installing and Upgrading

Media | Distribute on a Single Server” on page 17.

After you have installed and configured Media Distribute on your master and non-master nodes, you need to restart some MediaCentral Platform and Media Distribute services.

If you need to remove Media Distribute, see “Removing Media | Distribute” on page 22.

For installation procedures, see the following topics:

• “Installing and Upgrading Media | Distribute” on page 11

• “Configuring Media | Distribute on the Master Node” on page 14

• “Configuring the Media | Distribute Installation on Non-Master Nodes” on page 15

The Media Distribute software installation package file (Media_Distribute_[version]Build[xx]_Linux.tar.gz) is available to Avid Support representatives only and can be downloaded from the Avid Gold Build repository.

To prepare and mount a USB drive for Media Distribute installation:

1. On a Windows system, format a USB drive as a FAT32 volume.

2. Get the Media Distribute installation package file (Media_Distribute_[version]Build[xx]_Linux.tar.gz) from your Avid representative.

3. Copy the compressed installation file to the USB drive.

4. Remove the USB device from the Windows system.

Installing and Upgrading Media | Distribute in a Cluster Environment

Identifying the Master and Non-Master Nodes

You can use the cluster resource monitoring command, crm, to verify which server functions as the master node and which as the non-master nodes.

To identify the master and non-master nodes, do the following:

t Log in to any node in the cluster as root and open the cluster resource monitoring utility by

typing the following:

crm resource status

The status of all cluster-related services on all nodes displays in the terminal window.

The master and non-master nodes are indicated as the Master/Slave Set — for example:

Master/Slave Set: ms_drbd_postgres [drbd_postgres] Masters: [ morpheus-hp1 ] Slaves: [ morpheus-hp2 ]

Identifying the Virtual Cluster IP

Some configuration files used in the configuration of your Media Distribute installation require the virtual cluster IP. This is required for the correct configuration of the Media Distribute service in a cluster installation.

To identify the virtual cluster IP:

t Log in to the master node of the cluster and type the following command:

ifconfig

The following is a example of the output of a typical network interface configuration. The virtual cluster IP is the IP assigned to the 'eth0:c10' network adapter. In this example, the virtual cluster IP is 172.24.18.61.

eth0 Link encap:Ethernet HWaddr 00:26:55:E6:83:E1

inet addr:172.24.18.163 Bcast:172.24.18.255 Mask:255.255.255.0

inet6 addr: fe80::226:55ff:fee6:83e1/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:4321802 errors:0 dropped:0 overruns:0 frame:0

TX packets:3628475 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1374391088 (1.2 GiB) TX bytes:1086706641 (1.0 GiB)

eth0:cl0 Link encap:Ethernet HWaddr 00:26:55:E6:83:E1

inet addr:172.24.18.61 Bcast:172.24.18.189 Mask:255.255.255.255

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Interrupt:38 Memory:fbde0000-fbe00000

lo Link encap:Local Loopback

Installing and Upgrading Media | Distribute in a Cluster Environment

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:7331022 errors:0 dropped:0 overruns:0 frame:0

TX packets:7331022 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:8040287442 (7.4 GiB) TX bytes:8040287442 (7.4 GiB)

Installing and Upgrading Media | Distribute

If you install Media Distribute in a cluster environment, you must install it first on the master node of the cluster since the database service runs on this node. The installation includes creating a database for the Media Distribute service. This can only be done on the node with the running PostgreSQL service. After you install the application on the master node, you must install Media Distribute on all non-master nodes.

When you finish the master node installation, you might see a message during the installation on

non-master nodes; “Not running a database PG on localhost. Please enter IP of database server.” If you see this message, press Enter. You do not need to provide an IP address for your database server when installing Media Distribute on a non-master node.

The procedure for upgrading Media Distribute is similar to the one you used initially to install Media Distribute. The upgrade procedure overwrites some configuration files. You can restore these files by using the backup configuration files already in your configuration once the upgrade completes.

When you upgrade your version of Media Distribute, all system and user settings are saved. You do not need to create new settings, but if the newer version includes new features, you might need to modify your settings to activate the features. For a list of new features, see the ReadMe documentation that came with your version of MediaCentral UX. For information on setting up account profiles, see “Configuring System Accounts for Media | Distribute” on page 52.

The Media Distribute installation, upgrade, and configuration disconnects all users logged in to MediaCentral UX when it restarts some services. Ensure that all users save their sessions and log off during the installation or upgrade procedures.

To install or upgrade Media Distribute:

1. Insert the Media Distribute installation USB drive into the server.

2. Verify the name of the device by typing the following command:

Linux information relating to hardware appears on the screen.

Information for the USB device appears near the end of the output, near the list of SCSI devices. The name of the USB device is found inside square brackets (e.g., sdc). This is the name you use to mount the device.

3. Create a mount point for the USB device by typing the following:

dmesg

mkdir /media/usb

Installing and Upgrading Media | Distribute in a Cluster Environment

4. Mount the USB key at the mount point you just created:

mount -t vfat /dev/sdc<?> /media/usb

The name of the USB device (sdc, in this case) takes a 1 (one) in the mount command. This simply

indicates a partition exists on the USB device. Formatting the USB device in Windows created the partition.

The USB device is now mounted and available for use.

5. Verify the USB key has been mounted:

Information displays about all mounted file systems and devices, including information about the USB device, similar to the following:

File system Size Used Avail Use % Mounted on

/dev/sdc1 7.5 G 4.5 G 3.0 G 61 % /media/usb

6. Unpack the Media Distribute installation file by typing the following command:

tar -xzf /media/usb/Media_Distribute_[version]Build[xx]_Linux.tar.gz

The compressed file extracts to a subfolder within the target directory called Media_Distribute_[version]_Build_[xx]_Linux.

7. Navigate to the installation directory:

cd Media_Distribute_[version]_Build_[xx]_Linux

8. Run the installation script:

./install.sh

For master node installations, a default user in the PostgreSQL database is created with a user name

mpduser

of database are also created.

and a password of

resudpm

df -h

. The necessary database tables and schema in PostgreSQL

9. Follow the prompts to install Media Distribute.

10. Do the following to open the MediaCentral Configurator, and then ensure that the Media Distribute plug-in is enabled within the Configurator:

a. Type the following command:

/opt/avid/avid-interplay-central/configurator

b. Select MediaDistribute.

When the MediaCentral Configurator completes, a dialog box opens.

11. Press Enter to select No.

The Configurator closes.

Installing and Upgrading Media | Distribute in a Cluster Environment

12. To restart the MediaCentral service, type the following command:

crm resource restart AvidIPC

When you restart the services, all users currently logged on to MediaCentral UX are logged out.

Restarting the services might take up to a minute.

13. (Master node only) To verify the version of Media Distribute installed on a master node, type the following command:

/usr/share/apache-servicemix/bin/mpd_version

The command returns the installed versions of ServiceMix and Media Distribute. For example:

ServiceMix Version: 4.5.1 MPD Version: 2.6.0.20150122_114231 MPD UI Version: 2.6.0.20150122_114231

14. (Master node only) To verify the ServiceMix installation on a master node, do the following:

a. Type the following

ssh Administrator@localhost -p 8101

b. Type

c. Type

If not all endpoints are active or if the Social Media Integration route is not started, ServiceMix

might not have completed restarting. You can wait a moment and then retry these steps.

d. To quit ServiceMix, type

15. To remove the installation files and unmount the USB drive, do the following:

yes

to continue connecting to the host, and then type the default password

list

, and press Enter.

All account endpoints display as “Active” and the Social Media Integration route displays as “Started.”

logout

avid

cd /

a. Type

b. Type the following:

rm -rf [target_directory] umount /media/usb

c. Remove the USB drive from the server.

to ensure you are not currently on the USB key by changing to the root directory.

Installing and Upgrading Media | Distribute in a Cluster Environment

Configuring Media | Distribute on the Master Node

After you install Media Distribute, you must edit several configuration and property files and restart services on the master cluster node before you can use Media Distribute.

To configure PostgreSQL to allow remote hosts access to the Media Distribute database:

1. Using Linux commands, navigate to the directory containing the PostgreSQL database configuration file:

cd /mnt/drbd/postgres_data

2. Using the Linux text editor, vi, open the pg_hba.conf file for editing:

vi pg_hba.conf

3. Type G to go to the last line of the file, and then Type i (lower case “i”) to enter insert mode and move to the new line.

4. Add the following to the last line:

host mpd mpduser 0.0.0.0/0 trust

5. Press the Escape key to return to command mode, then type

:wq

and press Enter to write and quit

the text editor.

To configure the User Management Service (UMS) properties file (new installation only):

1. Using Linux commands, navigate to the directory containing the UMS properties file:

cd /usr/share/apache-servicemix/config

2. Using the Linux text editor, vi, open the application.properties file for editing:

vi application.properties

3. Navigate using the arrow keys to the next line:

com.avid.mpd.uls.host.retriever=application.properties

4. If the line is commented with a # character, place the cursor over the # character and type x to delete the character and uncomment the line.

5. Navigate using the arrow keys to the line containing the parameter for

com.avid.osgi.uls.host

6. Type a valid UMS REST address.

The default value is

https://localhost:10443/ws/rest

. Use the virtual cluster IP address

as the host for this configuration file — for example, type

https://123.45.67.89:10443/ws/rest

7. Press the Escape key to return to command mode, then type

:wq

and press Return to write and

quit the text editor.

To configure PostgreSQL to allow remote hosts access to the Media Distribute database (new installation only):

1. Navigate to the directory containing the Media Distribute database configuration file:

cd /etc/apache-servicemix

2. Using the Linux text editor, vi, open the avid-mpd-wrapper.conf file for editing:

vi avid-mpd-wrapper.conf

Installing and Upgrading Media | Distribute in a Cluster Environment

3. Locate the following line, and then navigate using the arrow keys and place the cursor on top of the # (comment indicator):

# set.default.DB_HOST=hostname or IP

4. Type i (lower case “i”) to enter insert mode, and then use the arrow keys and backspace to erase

(comment indicator).

the

5. Delete the

hostname or IP

cluster IP address — for example,

6. Press the Escape key to return to command mode, then type

value at the end of the line, and then replace it by typing the virtual

set.default.DB_HOST=123.45.67.89

:wq

and press Return to write and

quit the text editor.

To modify the bus configuration file (new installation only):

1. Using Linux commands, navigate to the directory containing the MediaCentral configuration

cd /etc/apache-servicemix

file:

2. Using the Linux text editor, vi, open the com.avid.acs.bus.broker.rabbitmq.RabbitMqBusAccessFactory.cfg file for editing:

vi com.avid.acs.bus.broker.rabbitmq.RabbitMqBusAccessFactory.cfg

3. Navigate using the arrow keys to the line containing the parameter for

4. Type

(lower case “i”) to enter insert mode, and then type a valid URL for the MediaCentral

brokerConnectURL

connection.

The default value is this configuration file — for example,

amqp://localhost/acs

amqp://123.45.67.89/acs

5. Press the Escape key to return to command mode, then type

. Use the virtual cluster IP address as the host for

:wq

and press Return to write and

quit the text editor.

6. To restart the Media Distribute service, type the following command:

service avid-mpd clean-restart

To restore and move the Servicemix configuration files (upgraded systems only):

t For Media Distribute upgrades, restore the Servicemix configuration files by doing the

following:

a. Type the following to navigate to the Servicemix directory:

cd /etc/apache-servicemix/

b. Type the following commands to restore the backup configuration files:

mv avid-mpd-wrapper.conf.rpmsave avid-mpd-wrapper.conf mv

com.avid.acs.bus.broker.rabbitmq.RabbitMqBusAccessFactory.cfg.rpmsave com.avid.acs.bus.broker.rabbitmq.RabbitMqBusAccessFactory.cfg

Configuring the Media | Distribute Installation on Non-Master Nodes

Once you have installed Media Distribute on the master node, you must install the application on all non-master nodes. For installation procedures, see “Installing and Upgrading Media | Distribute” on

page 11.

Installing and Upgrading Media | Distribute in a Cluster Environment

After the installation or upgrade is complete, you must edit several configuration and property files and restart services on all non-master nodes in your cluster before you can use Media Distribute. Since the edited configuration and property files are identical to the ones you edited on the master node, you can copy those files to the non-master nodes.

To copy the edited Media Distribute files from the master to the non-master nodes:

1. Log in to your non-master node server using the root account.

2. Open a Linux terminal window, and then type the following commands:

scp root@[hostname]:/etc/apache-servicemix/avid-mpd-wrapper.conf /etc/apache-servicemix/

scp root@[hostname]:/etc/apache-servicemix/ com.avid.acs.bus.broker.rabbitmq.RabbitMqBusAccessFactory.cfg /etc/apache-servicemix/

scp root@[hostname]:/usr/share/apache-servicemix/config/ application.properties /usr/share/apache-servicemix/config/

[hostname] is the host name of your master node.

The terminal window displays the following message:

The authenticity of host '[hostname (IP address)]' can't be established. RSA key fingerprint is [fingerprint alphanumerical id]. Are you sure you want to continue connecting (yes/no)?

3. Type

yes

The terminal window displays the following message:

Warning: Permanently added '[hostname, IP address]' (RSA) to the list of known hosts.

4. If prompted for a password, type the password for your root user account.

The edited files are copied to the non-master node.

5. To restart the Media Distribute service, type the following command:

service avid-mpd clean-restart

To verify the ServiceMix installation, do the following:

1. Type the following

ssh Administrator@localhost -p 8101

2. Type

yes

to continue connecting to the host, and then type the default password

avid

Installing and Upgrading Media | Distribute on a Single Server

3. Type

4. To quit ServiceMix, type

list

, and press Enter.

All account endpoints display as “Active” and the Social Media Integration route displays as “Started.”

logout

Restarting PostgreSQL Service and Verifying the Cluster Installation

Before you verify your Media Distribute installation on the master and non-master nodes, you need to perform a failover of the servers. This restarts the PostgreSQL service and validates the mpduser. It also tests your new installation and verifies that both Media Distribute and MediaCentral Platform Services are running properly.

To perform a failover and verify your installation:

1. Open a terminal window and log in to any non-master node in the cluster as root and check the cluster resource status by typing the following:

The status of all cluster-related services on all nodes displays in the terminal window. The Migration summary also displays at the bottom of the screen, which can be useful to view errors and fail counts per node.

2. On the master node, type the following, and then press Enter:

node]

3. Monitor the cluster information displayed on the slave node as it updates its information.

As the slave node becomes the master node, it takes ownership of the PostgreSQL database. This process takes several seconds to complete.

4. When the updated cluster is stable, type the following and press Enter:

[master node]

The node on standby resumes the master node status.

crm_mon -f

crm node standby [master

crm node online

Installing and Upgrading Media | Distribute on a Single Server

The Media Distribute software installation package file (Media_Distribute_[version]_Build_[xx]_Linux.tar.gz) is available to Avid Support representatives only and can be downloaded from the Avid Gold Build repository.

Installing and Upgrading Media | Distribute on a Single Server

If you deploy MCS and components on a master node and one or more non-master nodes in a cluster configuration, see “Installing and Upgrading Media | Distribute in a Cluster

Environment” on page 9.

To prepare and mount a USB drive for Media Distribute installation:

1. On a Windows system, format a USB drive as a FAT32 volume.

2. Get the Media Distribute installation package file (Media_Distribute_[version]_Build_[xx]_Linux.tar.gz) from your Avid representative.

3. Copy the compressed installation file to the USB drive.

4. Remove the USB device from the Windows system.

Installing and Upgrading Media | Distribute on a Server

You can install or upgrade Media Distribute on a single server The installation includes creating a database for the Media Distribute service.

The procedure for upgrading Media Distribute is similar to the one you used initially to install Media Distribute. If you need to remove Media Distribute, see “Removing Media | Distribute” on page 22.

When you upgrade your version of Media Distribute, all system and user settings are saved. You do

not need to create new settings, but if the newer version includes new features, you might need to modify your settings to activate the features. For a list of new features, see the ReadMe documentation that came with your version of MediaCentral UX. For information on setting up account profiles, see “Configuring System Accounts for Media | Distribute” on page 52.

The Media Distribute installation and configuration disconnects all users logged in to MediaCentral UX when it restarts some services. Ensure that all users save their sessions and log off during the installation or upgrade procedures.

To install or upgrade Media Distribute:

1. Insert the Media Distribute installation USB drive into the master node server.

2. Verify the name of the device by typing the following command:

Linux information relating to hardware appears on the screen.

3. Create a mount point for the USB device by typing the following:

4. Mount the USB key at the mount point you just created:

mount -t vfat /dev/sdc<?> /media/usb

The name of the USB device (sdc, in this case) takes a 1 (one) in the mount command. This simply indicates a partition exists on the USB device. Formatting the USB device in Windows created the partition.

The USB device is now mounted and available for use.

dmesg

mkdir /media/usb

Installing and Upgrading Media | Distribute on a Single Server

5. Verify the USB key has been mounted:

Information displays about all mounted file systems and devices, including information about the USB device, similar to the following:

File system Size Used Avail Use % Mounted on

/dev/sdc1 7.5 G 4.5 G 3.0 G 61 % /media/usb

6. Unpack the Media Distribute installation file by typing the following command:

tar -xzf /media/usb/Media_Distribute_[version]Build[xx]_Linux.tar.gz

The compressed file extracts to a subfolder within the target directory called Media_Distribute_[version]_Build_[xx]_Linux.

7. Navigate to the installation directory:

cd Media_Distribute_[version]_Build_[xx]_Linux

8. Run the installation script:

./install.sh

A default user in the PostgreSQL database is created with a user name of

resudpm

9. Follow the prompts to install Media Distribute.

. The necessary database tables and schema in PostgreSQL database are also created.

df -h

mpduser

and a password of

10. To verify the package has been installed, type the following:

/usr/share/apache-servicemix/bin/mpd_version

The output should include the following lines:

apache-servicemix.noarch 0:4.5.1-avid.el6.5 avid-mpd-[Version].[Build]-avid.el6.1.noarch.rpm avid-media-central-mpd-[Version].[Build]-avid.el6.1.noarch.rpm

11. Type the following to open the MediaCentral Configurator, and then ensure that the Media Distribute plug-in is enabled within the Configurator:

/opt/avid/avid-interplay-central/configurator

When you exit MediaCentral Configurator, you are asked to restart the MediaCentral services. When

you restart the services, all users currently logged on to MediaCentral UX are logged out.

12. To verify the ServiceMix installation, do the following:

a. Type the following

ssh Administrator@localhost -p 8101

b. Type

yes

to continue connecting to the host, and then type the default password

avid

Modifying Media | Distribute to Work with a Proxy Server

c. Type

d. To quit ServiceMix, type

13. To unmount the USB drive, do the following:

a. Type

b. Type the following:

list

, and press Enter.

If the ServiceMix installation is successful, all account endpoints display as “Active” and the Social Media Integration route displays as “Started.”

logout

cd /

to ensure you are not currently on the USB key by changing to the root directory.

rm -rf [target_directory]

umount /media/usb

c. Remove the USB drive from the server.

Modifying Media | Distribute to Work with a Proxy Server

Media Distribute installations include an instance of ServiceMix that requires external connectivity to the Internet — for example, to post packages to Facebook or Twitter. Both Media Distribute and ServiceMix reside on the MediaCentral server connected to your internal network. This might create potential security issues for certain customers. For secure deployment considerations, you can configure Media Distribute to communicate with the Internet through a proxy server.

Using a proxy server — such as a Squid server or any other proxy server running on another machine in the network — allows you to restrict the ports that ServiceMix uses and the specific Internet sites with which it communicates. This solution involves configuration changes only and does not require changes to the existing Media Distribute installation process. After installing Media Distribute, you need to modify the Service Mix configuration file to include the proxy settings to ensure that all requests and responses go through the proxy server. When you restart Media Distribute services, any ServiceMix communication is forwarded to the proxy server.

When you have configured Media Distribute to use a proxy server, you must configure the proxy server with the following information:

• IP addresses of all ServiceMix instances, so that only data originating from Media Distribute are allowed to the proxy server

• Social media targets for the destination domains — for example, api.twitter.com

Modifying Media | Distribute to Work with a Proxy Server

You can also specify some systems in your configuration to bypass the proxy server. This can be useful in some configurations where you need to access the intranet — for example, when using a Vantage transcoder — where direct access works better.

See the documentation that came with your proxy server installation for more information on how to configure it for proxy operation.

The following procedure describes how to modify the ServiceMix properties file. It assumes you have set up and configured a proxy server.

To modify the ServiceMix configuration file for using Media Distribute with a proxy server:

1. Navigate to the directory containing the Media Distribute database configuration file:

cd /etc/apache-servicemix

2. Using the Linux text editor, vi, open the avid-mpd-wrapper.conf file for editing:

vi avid-mpd-wrapper.conf

3. Locate the section called Proxy configuration, and then type i (lower case “i”) to enter insert mode.

4. Locate the following lines, type keys and backspace to erase the proxy user name and proxy password (these are optional parameters):

(lower case “i”) to enter insert mode, and then use the arrow

(comment indicator) on all lines except those for setting the

#wrapper.java.additional.n=-Dhttp.proxySet=true #wrapper.java.additional.n=-Dhttp.proxyHost=<the proxy host> #wrapper.java.additional.n=-Dhttp.proxyPort=<the proxy port> #wrapper.java.additional.n=-Dhttp.proxyUser=<the proxy username> #wrapper.java.additional.n=-Dhttp.proxyPassword=<the proxy password> #wrapper.java.additional.n=-Dhttps.proxySet=true #wrapper.java.additional.n=-Dhttps.proxyHost=<the proxy host> #wrapper.java.additional.n=-Dhttps.proxyPort=<the proxy port> #wrapper.java.additional.n=-Dhttps.proxyUser=<the proxy username> #wrapper.java.additional.n=-Dhttps.proxyPassword=<the proxy password>

5. (Optional) If you want to specify some systems to bypass the proxy server, erase the # (comment indicator) on the following line:

#wrapper.java.additional.n=-Dhttp.nonProxyHost=<the proxy host>

You can add systems to this exclusion by separating them with a pipe symbol (|).

6. Delete the numeral variable (.n) and number the lines for which you have removed the comment indicator.

7. Delete the <proxy host> or <proxy port> variable and then replace it by typing the IP address of your proxy server or by typing the port configured by your proxy server for both the HTTP and HTTPS settings.

Typically the proxy port is 3128.

Removing Media | Distribute

The modified configuration should look like the following example:

wrapper.java.additional.1=-Dhttp.proxySet=true wrapper.java.additional.2=-Dhttp.proxyHost=12.345.67.89 wrapper.java.additional.3=-Dhttp.proxyPort=3128 #wrapper.java.additional.n=-Dhttp.proxyUser=<the proxy username> #wrapper.java.additional.n=-Dhttp.proxyPassword=<the proxy password> wrapper.java.additional.4=-Dhttps.proxySet=true wrapper.java.additional.5=-Dhttps.proxyHost=12.345.67.89 wrapper.java.additional.6=-Dhttps.proxyPort=3128 #wrapper.java.additional.n=-Dhttps.proxyUser=<the proxy username> #wrapper.java.additional.n=-Dhttps.proxyPassword=<the proxy password>

8. Press the Escape key to return to command mode, then type quit the text editor.

9. To restart the MediaCentral service, type the following command:

service avid-mpd restart

Removing Media | Distribute

If you want to remove Media Distribute, you can use the procedure described in this section. If you need to reinstall Media Distribute, see “Installing and Upgrading Media | Distribute in a Cluster

Environment” on page 9 or “Installing and Upgrading Media | Distribute on a Single Server” on page 17.

To remove Media Distribute on the master node:

1. To check the correct version and build numbers for your installation, type the following:

/usr/share/apache-servicemix/bin/mpd_version

The output should include the following lines:

apache-servicemix.noarch 0:4.5.1-avid.el6.5 avid-mpd-[Version].[Build]-avid.el6.1.noarch.rpm avid-media-central-mpd-[Version].[Build]-avid.el6.1.noarch.rpm

2. Remove the Media Distribute services by typing the following commands:

:wq

and press Return to write and

rpm -e avid-media-central-mpd rpm -e avid-mpd

You can copy the lines from the output in the previous step and paste them after the

command.

3. To restart the MediaCentral services, type the following commands:

t For cluster configurations:

t For single-node systems:

When you remove Media Distribute, the Media Distribute Producer role remains in

MediaCentral UX.

crm resource restart AvidIPC

service avid-interplay-central restart

rpm -e

2 Configuration for Media | Distribute

Before you use Avid Media Distribute to publish your content to multiple channels and devices, you need to configure MediaCentral | UX for each platform or service you want to use for publishing. This allows you to link your media packages and iNEWS stories with distribution to the Web and to social media outlets and helping you to automate file preparation and transcoding.

Before you configure your system accounts, you need to need to configure MediaCentral UX for Media Distribute. For more information, see the following topics:

• “Assigning Media | Distribute Roles” on page 23

• “Configuring the Transcode Route” on page 30

You can then configure your system and user accounts for Media Distribute:

• “Configuring System Accounts for Media | Distribute” on page 52

• “Configuring User Profiles for Media | Distribute” on page 109

Once you have configured your platforms and services, users can log in to MediaCentral UX and start working with the application. For more information on using MediaCentral UX, see the Avid MediaCentral UX User’s Guide.

Verifying Your Media | Distribute Installation

Before you start to configure Media Distribute, you can test your installation to verify that all Media Distribute components are functioning correctly.

To verify your Media Distribute installation:

1. Sign in to MediaCentral UX as an administrator.

2. Click the Layout selector and select Media Distribute.

If Media Distribute has installed correctly, the following panes display in the Media Distribute layout:

- Social Message

-Web Story

- Packages

Assigning Media | Distribute Roles

Media Distribute provides two basic roles for publishing to multiple platforms and managing the layouts and permissions associated with them. Before you assign roles, you need to set up an administrative account for Media Distribute. Once this administrative account appears in the System Settings, the necessary roles are available for Media Distribute.

Assigning Media | Distribute Roles

If your MediaCentral configuration includes iNEWS, you need to assign an Advance License to the two Media Distribute roles before you assign these roles to users. For Interplay Production configurations, you can use the default Basic License type for these roles.

For more information about licenses and roles, see the Avid MediaCentral | UX Administration Guide.

When you have set up an administrative account and assigned the appropriate license type, you can then assign either the Advance Journalist or the Media Distribute Producer role to Media Distribute users. Only Media Distribute Producers have access to the review and approval features in the Packages pane.

You can assign roles in two ways:

• In the Role Details pane

• In the User or Group Details pane.

If you are upgrading from Media Distribute v1.8 to v2.x, you need to add the Media Distribute layout to the Advance Journalist role and to modify the legacy Interplay Pulse Producer role.

To set up an administrative account for Media Distribute:

1. Sign in to MediaCentral UX as an administrator.

2. Select System Settings from the Layout selector.

The System Settings layout opens.

3. In the Settings pane select Media Distribute > Profiles.

The Settings pane displays the settings in that group.

4. Click the Publication Type menu and select IPC.

5. Click the + (plus) button in the Details section.

Assigning Media | Distribute Roles

6. Specify the required settings:

- Profile Name (type a descriptive name for your administrative profile)

- Administrative Username

- Administrative Password

7. Click Verify Profile Settings to validate the profile settings.

If your profile is valid, a message displays: “Profile configurations is valid.” If any settings are incorrect, a message displays and indicates which fields are incorrect. All invalid settings names change to red.

The setting, “Transform iNEWS stories to lower case,” applies only to Media Distribute accounts

that publish packages containing iNEWS stories. The option does not affect this setting.

8. Click Apply to save the profile.

The profile displays in the Details section with the new information.

If you are editing a profile, click Revert to return to the original settings. If you want to delete a profile, select the profile and click the minus (-) button in the Details section.

To assign an Advance License to the Media Distribute roles in the Role Details pane (iNEWS configurations only):

1. Select Users from the Layout selector.

2. In the Roles pane, double-click either Advance Journalist or Media Distribute Producer to assign to a user or group.

Information about the role is displayed in the Details pane.

3. In the Details pane, select Advance License as the License Type for the following roles:

- Advance Journalist

- Media Distribute Producer

4. Click Apply to save your changes or click Revert to cancel your changes.

Assigning Media | Distribute Roles

To assign a Media Distribute role to a user in the Role Details pane:

1. Select Users from the Layout selector.

2. In the Roles pane, double-click either Advance Journalist or Media Distribute Producer to assign to a user or group.

Information about the role is displayed in the Details pane.

3. Click the User Tree pane.

4. Select the user or group to which you which you want to assign the role and drag it to the Users and Groups by MediaCentral Zone section of the Details pane.

MediaCentral UX User Settings, with the User Tree and Roles panes.

5. Click Apply to save your changes or click Revert to cancel your changes.

To assign the Media Distribute layout and create the Media Distribute Producer role (for MediaCentral UX upgrade installations only):

1. Select Users from the Layout selector.

2. In the Roles pane, double-click Advance Journalist.

Information about the role is displayed in the Details pane.

3. In the Layouts pane, click the edit button.

The Add or Remove Layouts dialog box opens.

4. Select Media | Distribute, and then click the Close button.

Assigning Media | Distribute Roles

5. Click Apply to save your changes or click Revert to cancel your changes.

6. In the Roles pane, double-click Interplay Pulse Producer.

Information about the role is displayed in the Details pane.

7. Modify the role name in the Role Name text box by typing the following:

Media Distribute Producer

8. Modify the description in the Description text box by typing the following:

Media Distribute Producer

9. In the Layouts pane, click the edit button.

The Add or Remove Layouts dialog box opens.

MediaCentral | UX Security for Media | Distribute

10. Select Media | Distribute, and then click the Close button.

11. Click Apply to save your changes or click Revert to cancel your changes.

To assign a role in the User or Group Details pane (iNEWS configuration only):

1. Select Users from the Layout selector.

2. In the Roles pane, double-click either Advance Journalist or Media Distribute Producer to assign to a user or group.

Information about the role is displayed in the Details pane.

3. Click the User Tree pane.

4. Select the user or group to which you which you want to assign the role and drag it to the Users and Groups by MediaCentral Zone section of the Details pane.

MediaCentral UX User Settings, with the User Tree and Roles panes.

5. Click Apply to save your changes or click Revert to cancel your changes.

MediaCentral | UX Security for Media | Distribute

A MediaCentral client requires user login credentials in order to gain access to the underlying functionality. All data transfer to and from the MediaCentral client (user credentials, session information, user configuration settings, media images and files, text, and machine instructions) are transported in a secure manner to the MediaCentral server using HTTPS protocol.

MediaCentral clients that connect through the public Internet require a virtual private network (VPN) access to the server network. All connections pass through the VPN router/firewall through identified ports. Once the data has passed into the “house network” it is secured using the customer’s existing network security infrastructure.

For Media Distribute, ports are used for outgoing HTTP traffic and pass through a network firewall. In some cases, a platform or a system account might require a separate port for outgoing FTP data. Media Distribute does not require any ports for incoming data.

Do not enable a firewall on the servers in your Media Distribute configuration.

MediaCentral | UX Security for Media | Distribute

The following tables list the ports used by MediaCentral UX and Media Distribute that should be allowed through the VPN and network firewalls.

VPN Firewall Port Settings

Component Port Usage

MediaCentral UX Web application 80 MediaCentral Platform Playback Services (MCPS)

HTTP calls

443 MediaCentral HTTPS calls

843 Loading the Flash Player for playback

26000 Inbound MCPS data

5000 Serving outbound JPEG images to the Flash player

21 Outgoing FTP data

Communication over port 21 is only required

for XML transfer to generic CMS or OVP endpoints or for media transfers to the WorldNow CMS system and is not required as part of any installation that uses standard Media Distribute third-party connectors.

MediaCentral UX mobile applications 80 MCPS HTTP calls

443 MediaCentral HTTPS calls

Network Firewall Port Settings

Component Port Usage

MediaCentral UX (these ports are used for outbound communication with configured endpoints such as Facebook, Twitter, or YouTube)

Outbound ACLs should be used to allow packets from the MediaCentral Platform Services (MCS)

server to the MediaCentral client over “established” TCP sessions only.

80 MediaCentral Platform Playback Services (MCPS)

HTTP calls

443 MediaCentral HTTPS calls

Note that the Interplay Web service and MediaCentral UX application services operate on the same server, so there are no proxies or firewalls between these components. Access to the MediaCentral database is also direct, with no database firewall protection required.

Only MediaCentral UX Administrators can access and modify the system data stored within the user management database (user credentials, user settings, and system attributes).

For more information on MediaCentral security, see the Avid MediaCentral | UX Security Architecture and Analysis.

Configuring the Transcode Route

Media Distribute delivers video to the configured online video platforms using the following workflow. An understanding of this workflow might help to complete the Send to Playback settings.

• The user publishes a bundle to endpoints that include video assets — for example, YouTube and Vimeo. The source videos are stored in Interplay Production.

• To start the publishing process, Media Distribute sends the source video to the MediaCentral Distribution server in a send-to-playback operation.

• The Interplay Production media files are mixed down to MXF-wrapped OP1a media. In the Packages pane, Media Distribute monitors the process as the status displays as “mixing down.”

You can send only sequences for mixdown and transfer to an FTP location.

• The Transfer Manager moves the MXF file to the FTP location specified in the Mixing Down FTP Path in the Send to Playback system settings — see “Send to Playback Configuration for

Media | Distribute” on page 36.

This location is independent of the transcoder. The system supports multiple transcode

configurations which you can assign to various endpoints. By not delivering the video directly to a transcode watch folder, the transcode route is built in a manner that allows for support of multiple transcode endpoints.

Configuring the Transcode Route

• The Media Distribute orchestration engine monitors the FTP location. Once the MXF media arrives at the FTP location, Media Distribute delivers it to the appropriate transcoder /in folder, based on the configuration for your transcoder service (ftp://<transcoder>/transcoding/in).

• Media Distribute submits the transcoding job to the transcoder:

- The File Share in Path value (\\<transcoder_hostname>\avid\transcoding\in) should be

configured and mapped to the FTP “in” path (ftp://<transcoder>/transcoding/in). The file share folder must have the appropriate read/write permissions set. For more information, see

“Configuring the Video Transcoding Host” on page 32.

- The transcoder workflow should be configured to provide output to the

ftp://<transcoder>/transcoding/out folder.

• After transcoding, the Media Distribute orchestration engine obtains the transcoded video file from the transcoder “out” folder and delivers it to the designed online video provider (OVP) endpoint for publication.

In order to enable this workflow, you must configure the Send to Playback system settings to provide the necessary information.

+ 103 hidden pages

Pinnacle Systems Media Distribute - 2.6 Installation Manual

Contents

Using This Guide

1 Installation for Media | Distribute

Installing and Upgrading Media | Distribute in a Cluster Environment

Identifying the Master and Non-Master Nodes

Identifying the Virtual Cluster IP

Installing and Upgrading Media | Distribute

Configuring Media | Distribute on the Master Node

Configuring the Media | Distribute Installation on Non-Master Nodes

Installing and Upgrading Media | Distribute on a Single Server

Restarting PostgreSQL Service and Verifying the Cluster Installation

Installing and Upgrading Media | Distribute on a Server

Modifying Media | Distribute to Work with a Proxy Server

Removing Media | Distribute

2 Configuration for Media | Distribute

Verifying Your Media | Distribute Installation

Assigning Media | Distribute Roles

MediaCentral | UX Security for Media | Distribute

Configuring the Transcode Route