Pinnacle Systems Media Distribute - 2.10 Installation Manual

Media | Distribute

Installation and Configuration Guide

Version 2.10

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.

The content of this guide is copyright protected guide and is made available for personal use. It may not be reproduced or distributed, in whole or in part, without permission of Avid. Reasonable care has been taken in preparing this guide, however, it may contain omissions, technical inaccuracies, or typographical errors. Avid Technology, Inc. disclaims liability for all losses incurred through 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

Avid, the Avid Logo, Avid Everywhere, Avid DNXHD, Avid DNXHR, Avid Nexis, AirSpeed, Eleven, EUCON, Interplay, iNEWS, ISIS, Mbox, MediaCentral, Media Composer, NewsCutter, Pro Tools, ProSet and RealSet, Maestro, PlayMaker, Sibelius, Symphony, and all related product names and logos, are registered or unregistered trademarks of Avid Technology, Inc. in the United States and/or other countries. The Interplay name is used with the permission of the Interplay Entertainment Corp. which bears no responsibility for Avid products. All other trademarks are the property of their respective owners. For a full list of Avid trademarks, see:

http://www.avid.com/US/about-avid/legal-notices/trademarks.

Media | Distribute Installation and Configuration Guide • Created 5/15/17 • 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

Preparing the Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Creating the USB Installation Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Mounting the USB Installation Drive on the MCS Server. . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing or Upgrading Media | Distribute on a Single Server . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing or Upgrading Media | Distribute in a Cluster Environment. . . . . . . . . . . . . . . . . . . . 13

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

Identifying the Virtual Cluster IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing or Upgrading Media | Distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

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

Configuring Media | Distribute on Non-Master Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

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

Verifying the Connection to ServiceMix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Modifying Media Distribute to Work with a Proxy Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Using the Social Messages and Web Story Panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Using the Distribution Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Removing Media Distribute. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

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

Verifying Your Media | Distribute Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Assigning Media | Distribute Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

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

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

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

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

Configuring a Telestream Vantage Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Validating the Vantage Transcode Route Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configuring the Harmonic ProMedia Carbon Transcoder . . . . . . . . . . . . . . . . . . . . . . . . 44

Configuring a RadiantGrid Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Configuring a MAM Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring an E-mail Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

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

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

Configuring a Twitter Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring a Facebook Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring a Facebook Page Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Configuring a Vimeo Publication Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Configuring a Vimeo V3 Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Configuring a YouTube v3 Publication Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Configuring a Brightcove Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Configuring a Kaltura Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Configuring an Ooyala Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Configuring a Flickr Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

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

Configuring a WorldNow Web CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Configuring thePlatform Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Configuring a WordPress CMS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Configuring an Amazon S3 Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Configuring a Generic CMS Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Configuring a Generic CMS Extended Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configuring a NoOpTranscoder Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Configuring a Generic OVP Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

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

Configuring a User Profile for an Amazon S3 Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Configuring a User Profile for an E-Mail Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

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

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

Configuring a User Profile for a Personal Flickr Account . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

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

Configuring a User Profile for a Personal Vimeo V3 Account. . . . . . . . . . . . . . . . . . . . . . . . 126

Configuring a User Profile for a Personal YouTube v3 Account. . . . . . . . . . . . . . . . . . . . . . 128

Delegated Publishing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Appendix A Media | Distribute Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

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

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

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

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

Appendix F Custom Configuration for Avid Publish Services. . . . . . . . . . . . . . . . . . . . . . . 148

Installing Avid Publish Services Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Configuring the Avid Publish Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Appendix G Deleting Packages from Packages Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

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

Media Distribute is installed on the MediaCentral Platform Services (MCS) server as a plug-in that offers additional functionality within MediaCentral UX. The Media Distribute installation procedure assumes that you have a fully configured and functional MediaCentral Platform Services environment. If your MCS server or servers have not been installed and configured, see the Avid MediaCentral Platform Services Installation and Configuration Guide for detailed instructions.

The Media Distribute installation package is delivered as “Media_Distribute_<version>_Linux.zip”. You run the installation file itself from a shell script called 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.

Because Media Distribute requires access to the Internet to publish packages to public websites, direct Internet access is often granted to the MediaCentral server. However, Media Distribute can also be configured to communicate with the Internet through a proxy server for additional security. For more information, see “Using the Social Messages and Web Story Panes” on page 21.

Depending on your workflow, the following components might be required by Media Distribute:

• iNEWS (for MCS configurations with iNEWS)

• Interplay Production Engine (for MCS configurations with Interplay Production)

install.sh

. This installs the plug-in

• Interplay MAM (for MCS configurations with Avid Interplay Media Asset Manager)

• Avid Shared Storage Client

MediaCentral Platform Services includes a copy of both the Avid ISIS Client and the Avid NEXIS

Client software. Verify the version of the Avid NEXIS or Avid ISIS client required for your environment and upgrade the client software if necessary. For more information, see the Avid MediaCentral Platform Services Installation and Configuration Guide.

• MediaCentral Distribution Service

• Interplay Transfer Engine

• Interplay Production Services Engine

• Interplay Production Transcode provider (for creating video or audio mixdowns of Avid assets)

• Interplay Production STP Encode (only required if working with LongGOP media assets)

• An FTP server (for transferring assets between systems)

• A video transcoding host server such as Telestream Vantage or Harmonic ProMedia Carbon (depending on the workflow)

• Internet connection for publishing to social media sites

For specific information on software version compatibility, see the Avid Knowledge Base:

http://avid.force.com/pkb/articles/en_US/compatibility/Avid-Video-Compatibility-Charts

If you ever need to remove Media Distribute, see “Removing Media Distribute” on page 24.

Preparing the Installation Package

The Media Distribute software installation package (Media_Distribute_<version>_Linux.zip) is available to Avid Support representatives only and can be downloaded from the Avid Gold Build repository.

Creating the USB Installation Drive

Media Distribute is installed on the MediaCentral Platform Services server through a USB drive. The following process provides instructions to prepare the USB drive for use with the MCS server.

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

1. On a Windows system, format a USB drive of at least 1GB in size as a FAT32 volume.

2. Obtain the Media Distribute installation package file (Media_Distribute_<version>_Linux.zip) from your Avid representative.

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

4. Remove the USB device from the Windows system.

Mounting the USB Installation Drive on the MCS Server

After the Media Distribute installer has been copied to a USB drive, the drive must be connected and mounted on the MCS server. The package must also be uncompressed to extract the installer script.

To mount the USB drive on the MCS server:

1. Connect the Media Distribute installation USB drive to the MCS server. If you are running a clustered configuration, connect the device to the cluster master node. Once the installation is complete on the master node, you must repeat this procedure for all non-master nodes.

root

2. Log into the MCS server (at the Linux prompt) as the

user.

3. Use the display message command to verify the name of the USB device:

dmesg

Information relating to the hardware appears on the screen.

Information for the USB drive appears at the end of the output, in the list of SCSI devices. The name of the USB drive is found inside square brackets (for example, sdc). This is the name you use to mount the drive.

The

dmesg

command displays a great deal of information which can be difficult to review in the

Linux console. You can reduce the amount of information that dmesg returns by using the Linux

grep

command to show only items that contain certain text (such as “sd”). The following

command can be used as an alternative:

dmesg | grep sd

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

mkdir /media/usb

If this directory already exists, the following message is displayed:

mkdir: cannot create directory `/media/usb': File exists

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

mount -t vfat /dev/<volume><partition> /media/usb

Installing or Upgrading Media | Distribute on a Single Server

The mount command requires you to specify the volume and a partition on the volume that needs to be mounted. The process of formatting the USB device in Windows creates this partition.

In the following example,

mount -t vfat /dev/sdc1 /media/usb

The USB device is now mounted and available for use.

6. Verify the USB key has been mounted:

Information is displayed about all mounted file systems and devices, and should include information about the USB drive, similar to the following (some output omitted for clarity):

Filesystem Size Used Avail Use% Mounted on /dev/sdc1 7.5G 5.3G 2.2G 71% /media/usb

7. Navigate to the mount point for the USB drive:

cd /media/usb

8. Unzip the Media Distribute installer package by typing the following command:

unzip Media_Distribute_<version>_Linux.zip

The installer is compressed within a .tar.gz container which must be unpacked to reveal the Media Distribute installer script.

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

tar -xzf Media_Distribute_<version>_<build>_Linux.tar.gz

The compressed file extracts to a subfolder within the target directory called Media_Distribute_<version>_<build>_Linux.

sdc

is the volume and 1 (one) is the partition number:

df -h

The process for installing Media Distribute is different for single-server and clustered environments.

• If you are running MCS on a single-server, see “Installing or Upgrading Media | Distribute on a

Single Server” on page 10 to continue the installation process.

• If your configuration consists of a set of clustered MediaCentral servers, see “Installing or

Upgrading Media | Distribute in a Cluster Environment” on page 13 to continue the installation

process.

Installing or Upgrading Media | Distribute on a Single Server

The following process details the steps required to install or upgrade Media Distribute on a single MediaCentral Platform Services server. During the installation, the PostgreSQL database is updated for use with the Media Distribute service.

The procedure for upgrading Media Distribute follows the same process as that of a new installation. The existing packages are simply overwritten with new versions during the upgrade process.

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

not need to create new settings. However if the software update 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 59.

Installing or Upgrading Media | Distribute on a Single Server

The process of installing Media Distribute includes a restart of some core services. This process disconnects all users logged in to MediaCentral UX. Ensure that all users save their sessions and log off during the installation or upgrade procedures.

To install or upgrade Media Distribute:

1. Complete the process for “Mounting the USB Installation Drive on the MCS Server” on page 9.

2. Navigate to the installation directory on the USB drive:

cd Media_Distribute_<version>_<build>_Linux

3. Run the installation script:

./install.sh

The period-slash “./” in this command tells Linux to look for the script in the current directory.

The PostgreSQL database is updated with a custom user name of

resudpm

4. Once the installation process is complete, verify that the packages have been installed by typing

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

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.9.0.20161221_164247 MPD UI Version: 2.9.0.20161221_164247

mpduser

and a password of

Additional service packages might also be listed when using this command.

5. Type the following to open the MediaCentral UX Configurator:

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

An asterisk symbol indicates that a particular option is enabled. Verify that the Media Distribute plug-in is enabled within the Configurator as shown above.

6. Select OK to exit the MediaCentral UX Configurator.

A dialog box opens and asks if you want to restart the MediaCentral services. Use the Tab key to select Yes and press Enter.

When you restart the services, all users currently logged on to MediaCentral UX are logged out. Restarting the services is a required step in this process. Do not simply select Cancel and exit the tool.

Installing or Upgrading Media | Distribute on a Single Server

7. With the Media Distribute installation complete, it is important to verify the connection to the ServiceMix tool. To verify the connection, complete the following steps:

a. Type the following:

ssh Administrator@localhost -p 8101

If prompted to verify the DSA key fingerprint, type ServiceMix interface.

b. Enter the Administrator password:

A successful connection to the ServiceMix tool should look similar to the following:

c. Verify that the services are running properly by entering the

Enter.

If the ServiceMix installation is successful, all account endpoints should be listed as “Active” and the “Social Media Integration Routes” endpoint should be listed as “Started.”

avid

yes

to continue to connect to the

list

command, and pressing

If all endpoints are not active or if the “Social Media Integration Routes” endpoint is not started,

ServiceMix might not have completed restarting. Wait a moment and then retry these steps.

d. Type

8. Unmount the USB drive from the MediaCentral server by completing the following steps:

a. Type

b. Type the following to unmount the volume:

c. Physically remove the USB drive from the server.

logout

mount.

umount /media/usb

to quit the ServiceMix tool.

to change to the Linux root directory and navigate away from the USB drive

Installing or Upgrading Media | Distribute in a Cluster Environment

The procedures in this section assume you have already configured your MediaCentral Platform Services servers in a clustered environment and that you have verified failover functionality. For more information on configuring the MediaCentral servers in a cluster, see the Avid MediaCentral Platform Services Installation and Configuration Guide.

The procedure for upgrading Media Distribute follows the same process as that of a new installation. The existing packages are simply overwritten with new versions during the upgrade process. If necessary, you can restore some of the original files by using the backup configuration files already in your configuration once the upgrade completes. For other files — for example, the Avid Publish Service configuration files — you must edit the new versions if you made any customizations to the original configuration.

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

Installing Media Distribute in a cluster entails the following steps:

• “Identifying the Master and Non-Master Nodes” on page 14

Media Distribute is installed on all cluster nodes, but some installation steps are completed on the Master node only, so it is important to know the role of each node before beginning the process.

• “Identifying the Virtual Cluster IP” on page 14

The virtual cluster IP address must be clearly identified as you are required to manually add this information to multiple configuration files after the installation is complete.

• “Installing or Upgrading Media | Distribute” on page 15

This process installs the software on each of the cluster nodes.

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

After the installation, multiple configuration files need to be updated with custom information.

• “Configuring Media | Distribute on Non-Master Nodes” on page 18

This process updates the configuration files on the non-master nodes.

• “Restarting PostgreSQL Service and Verifying the Cluster Installation” on page 19

This process validates changes to the PostgreSQL database and tests cluster failover.

• “Verifying the Connection to ServiceMix” on page 20

Checks the connection to the ServiceMix tool from each cluster node.

Installing or Upgrading Media | Distribute in a Cluster Environment

Identifying the Master and Non-Master Nodes

There are three types of nodes in a cluster: master, slave, and load-balancing. The master “owns” the cluster IP address. The slave assumes the role of master in the event of a failover. Any additional nodes play a load-balancing role, but can never take on the role of master.

Prior to beginning the installation, identify the current role of each cluster node.

To identify the master, slave, and load-balancing nodes:

1. Identify the master node of the cluster through the Cluster Resource Monitor. Log in to any machine in the cluster as root and type:

crm_mon

2. To identify the master and slave, look for the line containing “Master/Slave Set.”

For example:

Master/Slave Set: ms_drbd_postgres [drbd_postgres] Masters: [ wavd-mcs01 ] Slaves: [ wavd-mcs02 ]

In this example, the master node is wavd-mcs01 and the slave node is wavd-mcs02.

3. To identify the load-balancing nodes, look for the line containing “Clone Set.”

For example:

Clone Set: AvidAllEverywhere [AvidAll] Started: [ wavd-mcs01 wavd-mcs02 wavd-mcs03 wavd-mcs04 ]

In this example, the load-balancing nodes are wavd-mcs03 and wavd-mcs04.

4. Exit crm_mon by pressing CTRL-C on the keyboard.

Identifying the Virtual Cluster IP

Some files used in the configuration of Media Distribute require the virtual cluster IP. Prior to beginning the installation, identify the IP address assigned to the cluster.

To identify the virtual cluster IP:

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

The following is an 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 192.168.10.50:

eth0 Link encap:Ethernet HWaddr 00:26:55:E6:83:E1 inet addr:192.168.10.51 Bcast:192.168.10.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:44:E6:83:E1

inet addr:192.168.10.50 Bcast:192.168.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:38 Memory:fbde0000-fbe00000

ifconfig

Installing or Upgrading Media | Distribute in a Cluster Environment

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 collisions:0 txqueuelen:0 RX bytes:8040287442 (7.4 GiB) TX bytes:8040287442 (7.4 GiB)

Installing or 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 process updates the PostgreSQL database for the Media Distribute service. These updates can only be completed on the node running PostgreSQL service. After completing the installation of Media Distribute on the master node, you must repeat the process to install the software on all non-master nodes.

Prior to installing Media Distribute in a cluster, make sure that all cluster nodes are online. During the installation, changes are made to the PostgreSQL database. If the cluster is in standby mode, this does not occur and the installation fails.

To install or upgrade Media Distribute:

1. Complete the process for “Mounting the USB Installation Drive on the MCS Server” on page 9.

2. Navigate to the installation directory on the USB drive:

cd Media_Distribute_<version>_<build>_Linux

3. Run the installation script:

./install.sh

The period-slash “./” in this command tells Linux to look for the script in the current directory.

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

mpduser

of database are also created.

4. Once the installation process is complete, verify that the packages have been installed by typing 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.9.0.20161221_164247 MPD UI Version: 2.9.0.20161221_164247

and a password of

resudpm

. The necessary database tables and schema in PostgreSQL

Additional service packages might also be listed when using this command.

Installing or Upgrading Media | Distribute in a Cluster Environment

5. Type the following to open the MediaCentral UX Configurator:

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

An asterisk symbol indicates that a particular option is enabled. Verify that the Media Distribute plug-in is enabled within the Configurator as shown above.

Use the Tab key to select

6. Unmount the USB drive from the MediaCentral server by completing the following steps:

a. Type

mount.

b. Type the following to unmount the volume:

umount /media/usb

c. Physically remove the USB drive from the server.

7. Repeat steps 1 - 6 of this procedure on all non-master nodes.

When installing Media Distribute on the non-master nodes, you might see the following 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.

8. After Media Distribute has been installed on all cluster nodes, restart the AvidIPC cluster resource from any node to restart the avid-interplay-central service and enable Media Distribute:

crm resource restart AvidIPC

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

Restarting the services controlled by the cluster resource might take up to a minute.

to change to the Linux root directory and navigate away from the USB drive

Cancel

and press Enter to exit the Configurator.

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.

Although multiple text editors exist, the tool used throughout this document is “vi”. If needed, a short introduction to vi is included in the MediaCentral Platform Services Concepts and Clustering Guide.

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

1. Using the Linux vi editor, open the PostgreSQL configuration file for editing:

vi /mnt/drbd/postgres_data/pg_hba.conf

Installing or Upgrading Media | Distribute in a Cluster Environment

2. Add the following information on a new line at the end of the file:

host mpd mpduser 0.0.0.0/0 trust

3. Save and exit the vi session. Press

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

<ESC>

and type:

:wq

1. Using the Linux vi editor, open the UMS properties file for editing:

vi /usr/share/apache-servicemix/config/application.properties

2. Remove the “#” character from the beginning of the following line:

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

3. Using the arrow keys, navigate to the line containing the parameter for:

com.avid.osgi.uls.host=

4. Replace the default UMS REST address of

https://localhost:10443/ws/rest

with the

cluster’s virtual IP address. For example:

com.avid.osgi.uls.host=https://192.168.10.50:10443/ws/rest

5. Save and exit the vi session. Press

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

<ESC>

and type:

:wq

1. Using the Linux vi editor, open the Media Distribute database configuration file for editing:

vi /etc/apache-servicemix/avid-mpd-wrapper.conf

2. Locate the following line in the configuration file:

#set.default.DB_HOST=hostname or IP

3. Remove the “#” character from the beginning of this line:

set.default.DB_HOST=hostname or IP

4. Replace the

set.default.DB_HOST=192.168.10.50

5. Save and exit the vi session. Press

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

hostname or IP

value with the cluster’s virtual IP address. For example:

<ESC>

and type:

:wq

1. Navigate to the directory containing the MediaCentral configuration file:

cd /etc/apache-servicemix

2. Using the Linux vi editor, open the following configuration file for editing:

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

3. Using the arrow keys, navigate to the line containing the parameter for:

brokerConnectURL=

4. Replace the default URL of

amqp://localhost/acs

with the cluster’s virtual IP address. For

example:

brokerConnectURL=amqp://192.168.10.50/acs

5. Save and exit the vi session. Press

<ESC>

and type:

:wq

6. After this file has been saved, restart the Media Distribute service:

service avid-mpd clean-restart

Installing or Upgrading Media | Distribute in a Cluster Environment

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 Media | Distribute on Non-Master Nodes

The configuration files that you just edited on the master node also be edited on the non-master nodes. Since the configuration and property files need to be identical on all nodes, you can simply copy the edited files from the master to the non-master nodes.

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

1. From the cluster master node, enter the following commands to copy the configuration files to the non-master nodes:

scp /etc/apache-servicemix/avid-mpd-wrapper.conf root@<hostname>:/etc/apache-servicemix/

Where <hostname> is the host name of your non-master node.

2. After issuing the above command, Linux might display 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)?

If this occurs, type:

yes

The terminal window displays the following message:

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

If prompted for a password, type the password for your

root

user account.

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

3. From the cluster master node, enter the following commands to copy the remaining configuration files to the non-master nodes:

scp /etc/apache-servicemix/com.avid.acs.bus.broker.rabbitmq.RabbitMqBusAcc essFactory.cfg root@<hostname>:/etc/apache-servicemix/

scp /usr/share/apache-servicemix/config/application.properties root@<hostname>:/usr/share/apache-servicemix/config/

Where <hostname> is the host name of your non-master node.

4. Once the three configuration files have been copied, restart the Media Distribute service on the non-master node:

service avid-mpd clean-restart

5. Repeat steps 1 - 4 for each non-master node.

Installing or Upgrading Media | Distribute in a Cluster Environment

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.

For more information about cluster failover procedures, see the Avid MediaCentral Platform

Services Concepts and Clustering Guide.

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 the

2. Open the Cluster Resource Monitor to view the status of the cluster resources:

crm_mon -f

In addition to the resource status information, the Migration Summary and Failed Actions (if applicable) sections displayed at the bottom of the screen shows errors and fail counts per node.

3. Place the master node in standby by typing the following command and pressing Enter:

crm node standby <hostname>

Replace

4. Monitor the Cluster Resource Monitor on the non-master node.

As the master node enters standby, the former slave node becomes the new master. It takes ownership of the cluster IP address, the PostgreSQL database, and other resources.

Be patient as this process takes several moments to complete

5. When the updated cluster is stable, take former master node out of standby mode by typing the following command and pressing Enter:

crm node online <hostname>

Replace

The node is brought back up and takes the role of the cluster slave node.

6. Monitor the Cluster Resource Monitor on the non-master node.

with the hostname of the master node — for example, wavd-mcs01.

with the name of the standby node (e.g. wavd-mcs01).

root

user.

When the standby node comes back online, verify that its status is that of the slave node.

7. Repeat the process to test failover in the opposite direction.

As the master node goes into standby node, the status of the slave node returns to that of the master node. When the standby node comes back online, its status is that of the slave node.

Installing or Upgrading Media | Distribute in a Cluster Environment

Verifying the Connection to ServiceMix

With the Media Distribute installation complete, it is important to verify the connection to the ServiceMix tool. This process must be completed locally on each cluster node.

To verify the ServiceMix installation:

1. Type the following to access the ServiceMix tool:

ssh Administrator@localhost -p 8101

If prompted to verify the DSA key fingerprint, type ServiceMix interface.

2. Enter the Administrator password:

A successful connection to the ServiceMix tool should look similar to the following:

3. Verify that the services are running properly by entering the

avid

yes

to continue to connect to the

list

command, and pressing Enter.

If the ServiceMix installation is successful, all account endpoints should be listed as “Active” and the “Social Media Integration Routes” endpoint should be listed as “Started.”

If all endpoints are not active or if the “Social Media Integration Routes” endpoint is not started,

ServiceMix might not have completed restarting. Wait a moment and then retry these steps.

4. Type

logout

to quit the ServiceMix tool.

Modifying Media Distribute to Work with a Proxy Server

Media Distribute requires a connection to the public Internet to post packages to sites such as Facebook or Twitter. This connectivity requirement 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 Media Distribute and it’s dependent systems use to communicate with the Internet. This solution involves configuration changes only and does not affect the existing Media Distribute installation process. After installing Media Distribute, you need to modify certain configuration file to include the proxy settings to ensure that all requests and responses go through the proxy server. After restarting the appropriate Media Distribute services, external traffic is forwarded to the 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.

Depending on how you use Media Distribute, you might need to alter one or more files to configure the system to operate through a proxy server. The following two sections include information on configuring Media Distribute to use a proxy server:

• Using the Social Messages and Web Story Panes

• Using the Distribution Pane

See the documentation that came with your proxy server for information on how to configure it for proxy operation. The following processes assume that the proxy server is available and fully configured.

If your MediaCentral servers are configured in a cluster, complete the following processes on the master node first. Once complete, repeat the processes on all non-master nodes.

Using the Social Messages and Web Story Panes

When using either the Social Messages or Web Story panes, 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

To modify the configuration file for using ServiceMix 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.

Modifying Media Distribute to Work with a Proxy Server

4. Locate the following lines, type i (lower case “i”) to enter insert mode, and then use the arrow

keys and backspace to erase the

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

proxy user name and proxy password (these are optional parameters):

#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 systems to bypass the proxy server, add the following line:

#wrapper.java.additional.n=-Dhttp.nonProxyHosts=<the proxy hosts>

For example, you might be connecting to a transcode server that is in your network and you do not want or need that traffic passing through the proxy server. In this case, you could add the IP address, short hostname, or FQDN to this line. The server hosting the MediaCentral Distribution Service (MCDS) is another possible example of a machine that might be added to this field.

If you add this line to the file, Avid recommends matching the information that is added to the profile in the MediaCentral UX System Settings. For example, if you enter the transcode server’s IP address in the system settings, add the IP address to this line. If you plan to enter the FQDN, enter the FQDN here.

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.

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

Modifying Media Distribute to Work with a Proxy Server

#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

Using the Distribution Pane

Introduced in Media Distribute v2.7.0, the Distribution pane uses avid-publish-* services rather than the original ServiceMix connectors. If using this pane, you must configure the individual services to communicate with the proxy server.

You only need to configure the services that you plan to use. If you only plan to use the YouTube

service and not the Twitter service for instance, only the YouTube service needs to be adjusted.

To modify configuration files for using the Distribution pane with a proxy server:

1. Navigate to the directory containing the Media Distribute service files:

cd /opt/avid/sbin/

2. Use the Linux directory:

ls avid-publish*

Output similar to the following is displayed:

avid-publish-amazon-s3 avid-publish-flickr avid-publish-vimeo avid-publish-brightcove avid-publish-kaltura avid-publish-youtube avid-publish-facebook avid-publish-twitter

list

command to show the Media Distribute “publish” packages included in this

:wq

and press Return to write and

These are the files that must be altered to enable a proxy server workflow with the Distribution pane.

3. Open the desired configuration file for editing. For example:

vi avid-publish-youtube

4. Locate the following lines in the file (located near the beginning of the file):

# Add default JVM options here. You can also use JAVA_OPTS and AVID_PUBLISH_<connector>_OPTS to pass JVM options to this script.

DEFAULT_JVM_OPTS=""

5. Add the proxy server’s http and https connection information within the quotes:

DEFAULT_JVM_OPTS="-Dhttp.proxyHost=<http_IP> -Dhttp.proxyPort=<http_port>

-Dhttps.proxyHost=<https_IP> -Dhttps.proxyPort=<https_port>"

Where the following variables are used:

<http_IP>

<http_port>

<https_IP>

<https_port>

— The IP address of the proxy server used for HTTP communication.

— The port on the proxy server used for HTTP communication.

— The IP address of the proxy server used for HTTPS communication.

— The port on the proxy server used for HTTPS communication.

Removing Media Distribute

The following example shows a completed configuration change:

DEFAULT_JVM_OPTS="-Dhttp.proxyHost=192.168.10.220 -Dhttp.proxyPort=3128

-Dhttps.proxyHost=192.168.10.220 -Dhttps.proxyPort=3129"

6. Save and exit the vi session. Press

7. To activate the change, restart the service associated with the file you just updated. For example:

service avid-publish-youtube restart

8. Repeat the process above to update additional services as required by your workflow.

<ESC>

Removing Media Distribute

If you need to uninstall the software, Media Distribute v2.10 includes a script that quickly and easily removes the Distribute components for you. If you are uninstalling the software in a cluster configuration, begin the following process from the master node.

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

MediaCentral UX.

To remove Media Distribute:

1. Refer to the process for “Preparing the Installation Package” on page 9 to create a USB drive loaded with the Media Distribute software.

2. Once the software package is unpacked, run the uninstall script from the USB drive:

./uninstall.sh

Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the script in the current

directory. Otherwise you will receive the following error message:

and type:

:wq

-bash: uninstall.sh: command not found

3. If in a cluster configuration, repeat the above two steps on all cluster nodes in any order.

4. To complete the uninstall process, type one of the following commands to restart the MediaCentral services:

t For single-server systems:

t For cluster configurations:

If you need to reinstall Media Distribute, see “Installing or Upgrading Media | Distribute on a Single

Server” on page 10 or “Installing or Upgrading Media | Distribute in a Cluster Environment” on page 13.

service avid-interplay-central restart

crm resource restart AvidIPC

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 assists you with automating 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 25

• “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 54

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

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 below the list of Profile Names and Publication Types and select IPC.

5. Click the + (plus) button to the right of the Publication Type list in the Details section.

Clicking the + (plus) button creates the profile. If you do not click the + button, the profile options are displayed, but the Apply button in the bottom-right corner cannot be selected.

Assigning Media | Distribute Roles

6. Specify the required settings:

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

- Administrator Username

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

Assigning Media | Distribute Roles

3. Click the Layouts pane, select the Media Distribute layout, and drag it to the Layouts section.

The Media Distribute layout is added to the Layouts list.

4. In the Roles pane, double-click Media Distribute Producer.

Information about the role is displayed in the Details pane.

5. Click the Layouts pane, select the Media Distribute layout, and drag it to the Layouts section.

The Media Distribute layout is added to the Layouts list.

6. 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 transfered 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 MediaCentral servers in your Media Distribute configuration.

For more information on specific ports used with MediaCentral Platform Services and Media Distribute, see the Avid Networking Port Usage Guide on the Avid Knowledge Base.

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

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.

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

+ 125 hidden pages

Pinnacle Systems Media Distribute - 2.10 Installation Manual

Contents

Using This Guide

1 Installation for Media | Distribute

Preparing the Installation Package

Creating the USB Installation Drive

Mounting the USB Installation Drive on the MCS Server

Installing or Upgrading Media | Distribute on a Single Server

Installing or Upgrading Media | Distribute in a Cluster Environment

Identifying the Master and Non-Master Nodes

Identifying the Virtual Cluster IP

Installing or Upgrading Media | Distribute

Configuring Media | Distribute on the Master Node

Configuring Media | Distribute on Non-Master Nodes

Restarting PostgreSQL Service and Verifying the Cluster Installation

Verifying the Connection to ServiceMix

Modifying Media Distribute to Work with a Proxy Server

Using the Social Messages and Web Story Panes

Using the Distribution Pane

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