Pinnacle Systems Media Distribute - 2.2.1 Installation Manual

Media | Distribute

Installation and Configuration Guide

Version 2.2.1

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 4/30/15 • This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

Using This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

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

Installing Media | Distribute in a Cluster Environment. . . . . . . . . . . . . . . . . . . . . . . . 10

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

Identifying the Virtual Cluster IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing Media | Distribute on the Master Node . . . . . . . . . . . . . . . . . . . . . . . . 13

Upgrading Media | Distribute on the Master Node . . . . . . . . . . . . . . . . . . . . . . . 16

Removing Media | Distribute from the Master Node . . . . . . . . . . . . . . . . . . . . . 19

Configuring the Media | Distribute Installation on the Master Node . . . . . . . . . . 20

Installing Media | Distribute on Non-Master Nodes . . . . . . . . . . . . . . . . . . . . . . 22

Upgrading Media | Distribute on Non-Master Nodes . . . . . . . . . . . . . . . . . . . . . 24

Removing Media | Distribute from Non-Master Nodes. . . . . . . . . . . . . . . . . . . . 25

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

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

Installing Media | Distribute on a Single Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Installing Media | Distribute on a Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Upgrading Media | Distribute on a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Removing Media | Distribute from a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

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

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

Verifying Your Media | Distribute Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Assigning Media | Distribute Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

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

Configuring the Transcode Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring MediaCentral | UX for Media | Distribute. . . . . . . . . . . . . . . . . . . . . 49

Configuring the Video Transcoding Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

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

Configuring a Telestream Vantage Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Validating the Vantage Transcode Route Configuration . . . . . . . . . . . . . . . . . . 62

Configuring the Harmonic ProMedia Carbon Transcoder . . . . . . . . . . . . . . . . . 68

Configuring a RadiantGrid Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

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

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

Configuring a Twitter Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configuring a Facebook Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configuring a Facebook Page Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . 89

Configuring a Vimeo Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Configuring a YouTube Publication Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Configuring a Brightcove Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configuring a Kaltura Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

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

Configuring a WorldNow Web CMS Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Configuring a WordPress CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring an InternetBroadcasting CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . 116

Configuring a Generic CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Configuring a Generic OVP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

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

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

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

Appendix A Media | Distribute Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

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

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

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

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 MediaCentral

| UX, see the Avid MediaCentral | UX Administration Guide.

| UX Help. For administrative information for

1 Installation for Media | Distribute

The supported configuration for Media Distribute requires you to install Media Distribute on your MediaCentral installation information, see the Avid MediaCentral Platform Services Installation and Configuration Guide.

Before you install Media Distribute, you must install and configure your MediaCentral server. If you plan to process video or to use a content management system (CMS) account profile, you must also install the Interplay Web Services. See “Installing Software for Interplay Web Services” in the Interplay

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

page 10

| UX server, which is part of your MediaCentral configuration. For

| Production Software Installation and Configuration Guide.

“Installing Media | Distribute in a Cluster Environment” on

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

on a Single Server” on page 28

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

• Avid MediaCentral Platform Services v2.2.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.6.1 driver

• Red Had Enterprise Linux (RHEL) v6.5

• Avid Interplay Web Services

• MediaCentral Distribution Service

“Installing Media | Distribute

Installing Media | Distribute in a Cluster Environment

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 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 and “Identifying the Virtual Cluster IP” on page 12).

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

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.

For master node installation procedures, see the following topics:

• “Installing Media | Distribute on the Master Node” on page 13

• “Upgrading Media | Distribute on the Master Node” on page 16

“Identifying the Master and Non-Master Nodes” on page 11

Installing Media | Distribute in a Cluster Environment

• “Removing Media | Distribute from the Master Node” on page 19

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

For non-master node installation procedures, see the following topics:

• “Installing Media | Distribute on Non-Master Nodes” on page 22

• “Upgrading Media | Distribute on Non-Master Nodes” on page 24

• “Removing Media | Distribute from Non-Master Nodes” on page 25

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

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.

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:

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 ]

crm resource status

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:

Installing Media | Distribute in a Cluster Environment

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

The output will look similar to the following:

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

ifconfig

lo Link encap:Local Loopback

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

Installing Media | Distribute in a Cluster Environment

collisions:0 txqueuelen:0

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

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.

Installing Media | Distribute on the Master Node

You must install Media Distribute 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.

If you want to upgrade an existing version of Media Distribute, see “Upgrading

Media | Distribute on the Master Node” on page 16.

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 Media Distribute on the master node:

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.

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:

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 Media | Distribute in a Cluster Environment

5. Verify the USB key has been mounted:

df -h

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

password of

resudpm

. The necessary database tables and schema in PostgreSQL database are

also created.

mpduser

and a

9. Follow the prompts to install Media Distribute.

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

rpm -qa | grep ‘mpd\|servicemix’

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

Installing Media | Distribute in a Cluster Environment

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 the MediaCentral Configurator completes, a dialog box opens.

12. Press Enter to select No.

The Configurator closes.

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

14. To verify the version of Media Distribute installed on your system, 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.2.0.20150122_114231 MPD UI Version: 2.2.0.20150122_114231

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

Installing Media | Distribute in a Cluster Environment

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

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

a. Type

list

, and press Enter.

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

cd /

directory.

logout

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

b. Type the following:

rm -rf [target_directory] umount /media/usb

c. Remove the USB drive from the server.

Upgrading Media | Distribute on the Master Node

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

from the Master Node” on page 19.

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.

The Media Distribute 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.

“Removing Media | Distribute

Installing Media | Distribute in a Cluster Environment

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

To upgrade Media Distribute on the master node:

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

“Configuring System Accounts for Media | Distribute” on page 75.

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.

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

df -h

dmesg

mkdir /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

Installing Media | Distribute in a Cluster Environment

8. Run the installation script:

./install.sh

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

rpm -qa | grep ‘mpd\|servicemix’

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

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

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

crm resource restart AvidIPC

12. To verify the version of Media Distribute installed on your system, 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.2.0.20150122_114231 MPD UI Version: 2.2.0.20150122_114231

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

a. Type the following

ssh Administrator@localhost -p 8101

b. Type the default password

avid

Installing Media | Distribute in a Cluster Environment

c. Type

list

, and press Enter.

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

d. To quit ServiceMix, type

logout

14. To restore the Servicemix configuration files, do 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.rpmsav e com.avid.acs.bus.broker.rabbitmq.RabbitMqBusAccessFactory.cfg

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

a. Type

cd /

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

directory.

b. Type the following:

rm -rf [target_directory] umount /media/usb

c. Remove the USB drive from the server.

Removing Media | Distribute from the Master Node

If you want to remove Media Distribute, you can use the procedure described in this section. If you need to reinstall Media Distribute, see

page 13.

“Installing Media | Distribute on the Master Node” on

Installing Media | Distribute in a Cluster Environment

To remove Media Distribute on the master node:

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

rpm -qa | grep ‘mpd\|servicemix’

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 by typing the following commands:

rpm -e avid-media-central-mpd-[Version].[Build]-avid.el6.1.noarch.rpm rpm -e avid-mpd-[Version].[Build]-avid.el6.1.noarch.rpm

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:

crm resource restart AvidIPC service avid-interplay-central restart

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

MediaCentral

UX.

rpm -e

Configuring the Media | Distribute Installation on the Master Node

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

Once you configure Media Distribute on the master and non-master nodes, you must perform a failover operation to restart the PostgreSQL service and validate the mpduser configuration. For more information, see

page 28.

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:

“Restarting PostgreSQL Service and Verifying the Cluster Installation” on

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.

Installing Media | Distribute in a Cluster Environment

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 Return to write

and quit the text editor.

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

cd /etc/apache-servicemix

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

vi avid-mpd-wrapper.conf

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

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

erase the

10. Delete the virtual cluster IP address

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

(comment indicator).

hostname or IP

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

— for example,

set.default.DB_HOST=123.45.67.89

:wq

and press Return to write

and quit the text editor.

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

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, type i (lower case “i”) to enter insert mode,

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 address as the host for this configuration file

https://123.45.67.89:10443/ws/rest

https://localhost:10443/ws/rest

— for example, type

. Use the virtual cluster IP

Installing Media | Distribute in a Cluster Environment

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

To modify the MCS configuration file:

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

/etc/apache-servicemix

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 i (lower case “i”) to enter insert mode, and then type a valid URL for the MediaCentral connection.

The default value is for this configuration file

amqp://localhost/acs

— for example,

amqp://123.45.67.89/acs

. Use the virtual cluster IP address as the host

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

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

service avid-mpd clean-restart

Installing Media | Distribute on Non-Master Nodes

:wq

and press Return to write

brokerConnectURL

:wq

and press Return to write

You must install Media Distribute and edit several configuration and property files on all non-master nodes in your cluster before you can use Media Distribute.

If you want to upgrade an existing version of Media Distribute, see “Upgrading

Media | Distribute on Non-Master Nodes” on page 24.

To install Media Distribute on a non-master node:

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

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

dmesg

Linux information relating to hardware appears on the screen.

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

mkdir /media/usb

Installing Media | Distribute in a Cluster Environment

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

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

df -h

mount /dev/sdc1 /media/usb

8. Run the installation script:

./install.sh

9. Follow the prompts to install Media Distribute.

During installation, you might see a message; “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.

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

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

a. Type

b. Type the following:

cd /

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

directory.

rm -rf [target_directory] umount /media/usb

Installing Media | Distribute in a Cluster Environment

c. Remove the USB drive from the server.

Upgrading Media | Distribute on Non-Master Nodes

The procedure for upgrading Media Distribute on non-master nodes is similar to the one you used initially to install Media Distribute. If you need to remove Media Distribute, see

Media | Distribute on Non-Master Nodes” on page 22.

“Installing

To upgrade Media Distribute on a non-master node:

1. Insert the Media Distribute installation USB drive into the non-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:

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:

df -h

mount /dev/sdc1 /media/usb

dmesg

mkdir /media/usb

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.

Installing Media | Distribute in a Cluster Environment

7. Navigate to the installation directory:

cd Media_Distribute_[version]_Build_[xx]_Linux

8. Run the installation script to upgrade your Media Distribute installation:

./install.sh

9. Follow the prompts to install Media Distribute.

During installation, you might see a message; “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.

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

rpm -qa | grep ‘mpd\|servicemix’

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

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

a. Type

b. Type the following:

c. Remove the USB drive from the server.

cd /

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

directory.

umount /media/usb

Removing Media | Distribute from Non-Master Nodes

If you want to remove Media Distribute, you can use the procedure described in this section. If you need to reinstall Media Distribute, see

on page 22.

“Installing Media | Distribute on Non-Master Nodes”

Installing Media | Distribute in a Cluster Environment

To remove Media Distribute on a non-master node:

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

rpm -qa | grep ‘mpd\|servicemix’

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 by typing the following commands:

rpm -e avid-media-central-mpd-[Version].[Build]-avid.el6.1.noarch.rpm rpm -e avid-mpd-[Version].[Build]-avid.el6.1.noarch.rpm

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:

crm resource restart AvidIPC service avid-interplay-central restart

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

MediaCentral

UX.

rpm -e

Configuring the Media | Distribute Installation on Non-Master Nodes

After you install or upgrade Media Distribute, 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)?

Installing Media | Distribute in a Cluster Environment

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

3. Type

yes

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

list

, and press Enter.

avid

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

4. To quit ServiceMix, type

logout

Installing Media | Distribute on a Single Server

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.

crm_mon -f

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

node]

crm node standby [master

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]

crm node online

The node on standby resumes the master node status.

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

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 and insert it into the server where you want to install Media Distribute.

Installing Media | Distribute on a Single Server

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

Linux information relating to hardware appears on the screen.

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

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

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.

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

df -h

mount /dev/sdc1 /media/usb

dmesg

mkdir /media/usb

Installing Media | Distribute on a Server

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

If you want to upgrade an existing version of Media Distribute, see “Upgrading

Media | Distribute on a Server” on page 32.

To install 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.

dmesg

Installing Media | Distribute on a Single Server

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.

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.

df -h

mkdir /media/usb

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

password of also created.

9. Follow the prompts to install Media Distribute.

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

rpm -qa | grep ‘mpd\|servicemix’

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

resudpm

. The necessary database tables and schema in PostgreSQL database are

mpduser

and a

+ 113 hidden pages

Pinnacle Systems Media Distribute - 2.2.1 Installation Manual

Contents

Using This Guide

Installing Media | Distribute in a Cluster Environment

Identifying the Master and Non-Master Nodes

Identifying the Virtual Cluster IP

Installing Media | Distribute on the Master Node

Upgrading Media | Distribute on the Master Node

Removing Media | Distribute from the Master Node

Configuring the Media | Distribute Installation on the Master Node

Installing Media | Distribute on Non-Master Nodes

Upgrading Media | Distribute on Non-Master Nodes

Removing Media | Distribute from Non-Master Nodes

Configuring the Media | Distribute Installation on Non-Master Nodes

Installing Media | Distribute on a Single Server

Restarting PostgreSQL Service and Verifying the Cluster Installation

Installing Media | Distribute on a Server