OpenText Media Management 16.3 - Installation Guide English (MEDMGT160300-IGD-EN-07) PDF

OpenText™ Media Management
Installation Guide
This document provides instructions for installing OpenText

Media Management.
MEDMGT160300-IGD-EN-07
OpenText™ Media Management
Installation Guide
Rev.: 2018-May-02
This documentation has been created for software version 16.3.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: https://support.opentext.com
For more information, visit https://www.opentext.com
Copyright © 2018 Open Text. All Rights Reserved.

Trademarks owned by Open Text.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
Table of Contents
1 Overview ................................................................................... 11
1.1 Media Management system and its components ............................... 11
1.1.1 Architecture .................................................................................... 11
1.1.2 Terminology .................................................................................... 12
1.1.2.1 OTDS terminology ........................................................................... 12
1.2 Recommended configuration ........................................................... 13
2 Installation Overview ............................................................... 17

2.1 Installation order ............................................................................. 17
2.2 Phases of the installation process .................................................... 18
2.2.1 Phase 1 - OTDS ............................................................................. 19
2.2.1.1 Verify the OTDS installation ............................................................. 19
2.2.2 Phase 2 - Core Media Management ................................................. 19
2.2.3 Phase 3 - Post-installation software .................................................. 20
3 Core Media Management Installation Preparation ............... 23

3.1 Requirements ................................................................................. 23
3.2 Install prerequisites ......................................................................... 23
3.2.1 Installing and configuring JBoss ....................................................... 24
3.2.1.1 Installing and configuring JBoss EAP ............................................... 25
3.2.1.2 Installing and configuring Wildfly ...................................................... 25
3.2.2 Installing and configuring TomEE ..................................................... 25
3.3 Database setup ............................................................................... 26
3.3.1 Confirming the database server requirements ................................... 26
3.3.1.1 Preparing the SAP HANA database .................................................. 27
3.3.1.2 Preparing the SQL Server database ................................................. 27
3.3.1.3 Preparing the Oracle database ......................................................... 28
3.3.1.4 Preparing the PostgreSQL database ................................................ 31
3.3.2 Preparing the application server ....................................................... 34
3.4 Configuring OTMM resources in OTDS ............................................. 35
3.5 Preparing the installation configuration file ........................................ 36
3.6 Proceeding to Windows or Linux installation ..................................... 37
4 Installing on Windows ............................................................. 39

4.1 Installing OTMM on Windows ........................................................... 39
4.1.1 Installing OTMM using the setup screens .......................................... 40
4.1.2 Installing OTMM using the console ................................................... 45
4.1.3 Installing OTMM silently ................................................................... 45
4.1.4 Monitoring and troubleshooting tips during installation ....................... 46
4.2 Installing and configuring Solr on Windows ....................................... 47
4.2.1 Installing Solr on a remote server (recommended) ............................. 47
OpenText Media Management – Installation Guide iii

Table of Contents
4.2.2 Installing Solr on the Media Management host .................................. 50

4.2.3 Converting a remote Solr instance to HA .......................................... 52
5 Installing on RedHat Enterprise Linux .................................. 53

5.1 Installing OTMM on Linux ................................................................ 53
5.1.1 Installing OTMM using the setup screens .......................................... 54
5.1.2 Installing OTMM using the console ................................................... 59
5.1.3 Installing OTMM silently ................................................................... 59
5.1.4 Monitoring and troubleshooting tips during installation ....................... 60
5.1.5 Setting the OTMM user environment ................................................ 61
5.1.6 Changing the Media Management directory ownership ...................... 62
5.2 Installing ImageMagick on Linux ....................................................... 62
5.3 Installing X Virtual Framebuffer on Linux ........................................... 63
5.4 Installing and configuring Solr on Linux ............................................. 64
5.4.1 To install Solr on a remote server (recommended) ............................ 64
5.4.2 To install Solr on the Media Management host .................................. 67
5.4.3 Converting a remote Solr instance to HA .......................................... 69
6 Post installation tasks ............................................................. 71

6.1 Editing the service configuration file on Linux .................................... 71
6.2 Configuring TomEE ......................................................................... 71
6.3 Configuring JBoss ........................................................................... 72
6.3.1 Configuring the JBoss Recovery Module for Oracle ........................... 73
6.4 Updating PROVIDER_HOST ........................................................... 74
6.4.1 Updating the PROVIDER_HOST property for JBoss .......................... 74
6.4.2 Updating the PROVIDER_HOST property for TomEE ........................ 74
6.5 Installing MediaInfo ......................................................................... 75
6.6 Updating workflows in Vantage ........................................................ 75
6.7 Configuring the Media Management user partitions in OTDS ............. 77
6.8 Securing the application .................................................................. 77
6.8.1 Securing OTMM from clickjack attacks ............................................. 77
6.8.2 Securing asset import ...................................................................... 78
6.8.3 Enabling secure session cookies ...................................................... 78
6.8.4 Deleting SQL log files ...................................................................... 79
6.9 Creating Property Templates ........................................................... 79
6.10 Generating thumbnails for Postscript files ......................................... 79
6.11 Editing the legal terms and conditions text ........................................ 80
7 Verifying and Configuring Push Connector for Media

Management ............................................................................. 81
7.1 Testing the Push Connector configuration for Media Management ..... 81
8 Installing OpenText Media Management Rich Media

Analysis Service ...................................................................... 83
iv OpenText Media Management – Installation Guide

Table of Contents
8.1 Preparing to install .......................................................................... 83

8.1.1 Prerequisites .................................................................................. 83
8.2 Installing Rich Media Analysis Service .............................................. 84
8.2.1 Installing on Windows using the setup screens .................................. 84
8.2.2 Installing on Windows silently ........................................................... 85
8.2.3 Installing on Linux using the setup screens ....................................... 86
8.2.4 Installing on Linux silently ................................................................ 87
8.2.5 Verifying the install .......................................................................... 88
8.3 Post-installation .............................................................................. 88
8.3.1 Installing Erlang on Linux ................................................................. 88
8.3.2 Installing Socat on Linux .................................................................. 89
8.3.3 Installing RabbitMQ on Linux ........................................................... 89
8.3.4 Configuring Rich Media Analysis Service install properties ................. 90
8.3.4.1 Encrypting the Pivotal RabbitMQ® password .................................... 91
8.4 Starting and stopping the service ..................................................... 91
8.5 Uninstalling Rich Media Analysis Service .......................................... 92
8.5.1 To uninstall Rich Media Analysis Service using screens .................... 92
8.5.2 To uninstall Rich Media Analysis Service silently ............................... 92
8.6 Troubleshooting .............................................................................. 93
8.6.1 The service was not created during a Linux install ............................. 93
8.6.2 The mediaanalysis.log file does not show up after starting the
service on a Linux install .................................................................. 94
8.6.2.1 To diagnose the issue ..................................................................... 94
8.6.2.2 To resolve this issue if it is due to permissions .................................. 95
8.6.2.3 To resolve this issue if it is due to version of Java .............................. 96
8.6.3 HTTP 403 status code when trying to call the service ........................ 97
8.6.4 Error: org.springframework.amqp.AmqpConnectException:
java.net.ConnectException: Connection refused: connect .................. 98
8.6.5 Determining the IP address of the clients that are submitting
requests to access Rich Media Analysis Service ............................... 98
8.6.6 Error when trying to uninstall the service on Windows ........................ 99
9 Installing OpenText Media Management Adaptive Media

Delivery ................................................................................... 101
9.1 Preparing to install ........................................................................ 101
9.1.1 System requirements .................................................................... 102
9.1.2 Software prerequisites ................................................................... 102
9.1.3 Creating the database user ............................................................ 102
9.1.4 Creating an OTMM user account .................................................... 103
9.1.5 Installing Data Collector ................................................................. 103
9.2 Installing Adaptive Media Delivery .................................................. 103
9.2.1 Installing Adaptive Media Delivery using the setup screens .............. 104
9.2.1.1 To install Adaptive Media Delivery using the setup screens .............. 105
OpenText Media Management – Installation Guide v

Table of Contents
9.2.2 Installing Adaptive Media Delivery using the console ....................... 107
9.2.2.1 To install Adaptive Media Delivery using the console ....................... 107
9.2.3 Installing Adaptive Media Delivery silently ....................................... 108
9.2.3.1 To install Adaptive Media Delivery silently ....................................... 108
9.2.4 Performing post-installation tasks ................................................... 109
9.2.4.1 Installing ImageMagick .................................................................. 109
9.2.4.2 Configuring notification settings ...................................................... 109
9.2.4.3 Configuring the amd.properties file ................................................. 110
9.2.4.4 Configuring application server libraries ........................................... 111
9.3 Starting and stopping the Adaptive Media Delivery server ................ 111
9.4 Upgrading Adaptive Media Delivery ................................................ 112
9.4.1 Before you upgrade ....................................................................... 112
9.4.1.1 To back up Adaptive Media Delivery ............................................... 112
9.4.2 To upgrade Adaptive Media Delivery using the setup screens .......... 113
9.4.3 To upgrade Adaptive Media Delivery using the console ................... 114
9.4.4 To upgrade Adaptive Media Delivery silently ................................... 115
9.4.5 Troubleshooting the upgrade ......................................................... 116
9.4.5.1 To continue after an upgrade error ................................................. 116
9.4.6 Performing post upgrade tasks ....................................................... 116
9.4.6.1 Upgrading ImageMagick ................................................................ 117
9.4.6.2 Verifying and configuring the communication type ........................... 117
9.4.6.2.1 To verify the communication type is REST-based or OTMM SDK ..... 117
9.5 Performing additional advanced configurations for Adaptive Media
Delivery ........................................................................................ 118
9.5.1 Configuring ImageProfiles.xml ....................................................... 118
9.5.2 Configuring ProfileCollections.xml .................................................. 119
9.5.3 Configuring amd.properties ............................................................ 119
9.5.3.1 Database ...................................................................................... 119
9.5.3.2 DataCollector ................................................................................ 119
9.5.3.3 HTTP Response Headers .............................................................. 120
9.5.3.4 OTMM Properties .......................................................................... 120
9.5.3.5 Zookeeper Properties .................................................................... 120
9.5.3.6 Adaptive Media ............................................................................. 121
9.5.4 Configuring credential _SEC.cfg and db_SEC.cfg ........................... 121
9.6 Integrating Adaptive Media Delivery with Content Delivery Network .. 121
9.6.1 Notifying CDN to purge an asset or rendition ................................... 122
9.6.1.1 Writing a custom implementation class ........................................... 122
9.6.1.1.1 To write a custom implementation class .......................................... 122
9.6.1.2 Configuring Adaptive Media Delivery to use the default
implementation of Amazon CloudFront CDNCache Service ............. 123
9.6.1.2.1 To configure the default Amazon CloudFront CDNCacheService ..... 124
vi OpenText Media Management – Installation Guide

Table of Contents

implementation of AzureCDNCacheService .................................... 124
9.6.1.3.1 To configure the default Azure CDNCacheService .......................... 125
9.7 Troubleshooting ............................................................................ 125
9.7.1 Troubleshooting installation issues ................................................. 125
9.7.2 Seeing outdated content ................................................................ 126
9.7.3 Not receiving notification for asset level changes ............................. 126
9.8 Uninstalling Adaptive Media Delivery .............................................. 126
10 Integrating Media Management and Data Collector ........... 129

10.1 To integrate iHub for with OTDS user management ......................... 130
10.2 To configure a dedicated iHub user for OTMM ................................ 130
10.3 To grant the new user read-execute permission to the iHub
dashboards and reports ................................................................. 130
10.4 Creating iHub credentials ............................................................... 131
11 Configuring video and audio ................................................ 133

11.1 Configuring the Transcode server .................................................. 133
11.1.1 Transcoding terminology ............................................................... 133
11.1.2 Media Management configuration parameters ................................. 134
11.1.3 Setting up a shared transcoding user account ................................. 142
11.1.4 Setting up shared folders for transcoding ........................................ 143
11.1.4.1 Windows shared storage example .................................................. 144
11.1.4.2 Central shared storage example ..................................................... 145
11.1.4.3 Media Management on Linux shared storage example .................... 146
11.2 Configuring video with Rhozet Carbon Coder .................................. 148
11.2.1 Installing Rhozet Carbon Coder ..................................................... 148
11.2.2 Setting up video transformations in Rhozet Carbon Coder ............... 148
11.2.3 Configuring Rhozet Carbon Coder .................................................. 150
11.2.4 Integrating Media Management and Rhozet .................................... 152
11.3 Configuring video with Telestream FlipFactory ................................ 156
11.3.1 Installing Telestream FlipFactory .................................................... 157
11.3.2 Setting up video transformations in FlipFactory ............................... 157
11.3.3 Configuring Telestream FlipFactory ................................................ 159
11.3.4 Integrating Media Management and FlipFactory .............................. 161
11.4 Configuring video with Telestream Vantage .................................... 164
11.4.1 Integrating Media Management with Vantage .................................. 166
11.5 Configuring video using FFmpeg .................................................... 169
11.5.1 Installing FFmpeg ......................................................................... 170
11.5.2 Integrating Media Management with FFmpeg .................................. 171
11.5.3 Configuring the FFmpeg transcoder to run locally ............................ 174
11.5.4 Installing and configuring the FFmpeg Transcode service to run in a
multi-tenant environment or externally ............................................ 174
OpenText Media Management – Installation Guide vii

Table of Contents
11.5.4.1 Preparing to install the FFmpeg Transcode service ......................... 175

11.5.4.2 Installing FFmpeg Transcoder service using the setup screens ........ 176
11.5.4.3 Installing FFmpeg Transcoder service using the console ................. 178
11.5.4.4 Installing FFmpeg Transcoder service silently ................................. 179
11.5.4.5 Starting the FFmpeg Transcode service ......................................... 180
11.5.5 Uninstalling the FFmpeg Transcode service .................................... 181
11.6 Video configuration for clip assets .................................................. 181
11.7 Configuring the Streaming server ................................................... 182
11.7.1 Configuring IIS for video ................................................................ 182
11.7.2 Configuring the Wowza Streaming Engine ...................................... 183
11.7.3 Configuring Apache on Linux ......................................................... 184
11.7.4 Installing Adobe Media Server (AMS ) ............................................ 185
11.7.4.1 Configuring Adobe Media Server .................................................... 186
11.7.4.2 Setting up AMS application video ................................................... 186
11.7.4.3 Setting up Windows users ............................................................. 187
11.7.4.4 Setting up the base URL for the AMS streaming server ................... 188
11.7.4.5 Network configuration for streaming and Apache downloads ............ 188
11.7.4.6 Securing AMS playback in Media Management ............................... 189
11.8 Optional video configurations ......................................................... 189
12 Completing optional installation activities ......................... 191

12.1 Disabling use of Global Unique Identifiers (GUIDs) for asset
identifier ....................................................................................... 191
12.2 Installing additional image transformers .......................................... 191
12.2.1 Image conversions ........................................................................ 192
12.2.2 Installing additional transformers .................................................... 192
13 Starting OTMM ....................................................................... 193

13.1 Starting Media Management as a Windows service ......................... 193
13.2 Starting Media Management on Linux ............................................. 193
13.3 Starting the OpenText Indexer as a service ..................................... 194
14 Upgrading Media Management ............................................ 195

14.1 Upgrading OTMM ......................................................................... 195
14.1.1 Planning the OTMM upgrade ......................................................... 196
14.1.2 Upgrading using the setup screens on Windows ............................. 197
14.1.3 Upgrading using the setup screens on Linux ................................... 198
14.1.4 Upgrading using the console .......................................................... 200
14.1.5 Upgrading using silent mode .......................................................... 201
14.1.6 Continuing after upgrade errors ...................................................... 202
14.2 Post-upgrade configurations .......................................................... 203
14.2.1 Updating license files .................................................................... 203
14.2.2 Clearing the JBoss cache .............................................................. 203
viii OpenText Media Management – Installation Guide

Table of Contents
14.2.3 Migrating Categories to Folders ..................................................... 203

14.2.4 Updating the transcode content target location ................................ 205
14.2.5 Updating the video configuration .................................................... 205
14.2.6 Upgrading ImageMagick ................................................................ 205
14.2.7 Configuring FFmpeg ...................................................................... 206
14.2.8 Regenerating the Tasset.dtd file ..................................................... 206
14.2.9 Rectifying corrupt mime type data for asset previews and thumbnails ...
206
14.3 Integrating Media Management and Secure MFT ............................ 207
14.4 Upgrading OpenText Information Hub ............................................ 207
14.4.1 To back up the OTMM16 applications folder ................................... 208
14.4.2 To upgrade iHub ........................................................................... 208
14.4.3 To integrate iHub with OTDS user management .............................. 208
14.4.4 To remove the OTDS RSSE service from iHub ............................... 209
14.4.5 To reset the iHub credentials file .................................................... 209
14.5 Upgrading the FFmpeg Transcode service ...................................... 210
14.6 Verifying the upgrade .................................................................... 211
14.7 Upgrading Creative Review ........................................................... 211
15 Verifying the OTMM installation ........................................... 213

15.1 Troubleshooting the OTMM installation ........................................... 213
15.1.1 Command Prompt window disappears during install ........................ 213
15.1.2 Application deployment issues ....................................................... 214
15.1.3 OTMM Sign-in issues .................................................................... 214
15.1.4 Import issues ................................................................................ 215
15.1.5 Indexer and Search issues ............................................................ 215
15.1.6 Transcoding of video and audio assets fails .................................... 217
15.1.7 Analytics ....................................................................................... 218
15.1.8 Adaptive Media Delivery ................................................................ 218
15.1.9 Thumbnails do not appear in Mobile or Web Desktop Client ............. 218
15.1.10 PDF preview is not generated for assets ......................................... 219
15.1.11 Videos do not play ......................................................................... 219
16 Configuring for High Availability ......................................... 221

16.1 What is HA? ................................................................................. 221
16.1.1 References and other reading ........................................................ 222
16.2 Providing HA support .................................................................... 222
16.2.1 General HA best practices ............................................................. 222
16.2.2 Overview of Media Management processes .................................... 223
16.2.3 Media Management application server ........................................... 223
16.2.3.1 Enabling Session Replication ......................................................... 224
16.2.4 Apache Solr (search engine) .......................................................... 225
16.2.5 Indexer ......................................................................................... 226
16.2.6 Database ...................................................................................... 226
OpenText Media Management – Installation Guide ix

Table of Contents
16.2.7 Solr index files .............................................................................. 227

16.2.8 Database data files ....................................................................... 227
16.2.9 Asset repository ............................................................................ 227
16.3 Recommended HA configuration .................................................... 228
16.3.1 Shared storage requirements ......................................................... 229
16.3.2 Setting up HA ............................................................................... 229
16.4 OTMM cluster ............................................................................... 230
16.4.1 Installing Media Management on the first cluster node ..................... 231
16.4.2 Installing Media Management on other cluster nodes ...................... 231
16.4.3 Configuring Media Management on all cluster nodes ....................... 232
16.4.3.1 Configuring OTMM with JBoss on all cluster nodes ......................... 232
16.4.3.2 Configuring OTMM with TomEE on all cluster nodes ....................... 234
16.4.3.3 Enabling failover of the client API (optional) .................................... 238
16.4.4 Testing Media Management on the first node .................................. 239
16.4.5 Media Management Indexer configuration on the cluster nodes ....... 240
16.4.6 Creating and starting the scheduler indexer monitor job ................... 245
16.4.7 Solr configuration on cluster nodes ................................................. 249
16.4.7.1 Solr master configuration ............................................................... 249
16.4.7.2 Solr slave configuration ................................................................. 250
16.4.7.3 Configuring Solr on a remote host for HA ........................................ 250
16.4.7.4 Solr master failover ....................................................................... 250
16.5 Risks ............................................................................................ 252
17 Appendix A ‒ Uninstalling the Media Management

application .............................................................................. 253
17.1 Uninstalling Media Management .................................................... 253
17.1.1 Uninstalling the Media Management database ................................ 255
17.1.2 Uninstalling Solr ............................................................................ 256
17.2 Reinstalling Media Management .................................................... 258
18 Appendix B ‒ Validation checks .......................................... 259
19 Appendix C – Deploying the OpenText Private Help

Server ..................................................................................... 261
19.1 Implementing the OpenText Private Help Server for OpenText
Media Management ...................................................................... 261
19.1.1 Downloading the OpenText Private Help Server Kit and product
online help files ............................................................................. 262
19.1.2 Deploying the Private Help Server .................................................. 262
19.1.2.1 Troubleshooting the Private Help Server ......................................... 269
19.1.3 Configuring Media Management to use the OpenText Private Help
Server .......................................................................................... 269
x OpenText Media Management – Installation Guide

Chapter 1
Overview
This guide will step you through a complete installation of OpenText™ Media
Management (OTMM), including a description of the overall architecture of an
OTMM system along with the requirements and configuration options for each
component.
1.1 Media Management system and its components

1.1.1 Architecture
A Media Management system requires several OpenText products to deploy the
overall solution. In addition to the OpenText products, there are several products
that are licensed or bundled with the solution. The following figure shows the
OTMM solution and its major components for a basic (non-High Availability, non-
replicated) Media Management system.
Figure 1-1: Media Management architecture
Note: Secure MFT works only with MS SQL Server.
Figure 1-1 does not include the relational database, which is used to store persistent
data. For more information, see “Database setup” on page 26.
The primary focus of this guide is to install the core OTMM software. This guide
provides an overview of the required software necessary to create a functional
OpenText Media Management – Installation Guide 11

Chapter 1 Overview
OTMM system, but it does not provide details for installing other required software.
Refer to the appropriate installation guide when installing the other prerequisite
software such as the OpenText and third party products. When appropriate, this
guide will provide guidance for installing other software when specific OTMM-
related choices need to be made.
1.1.2 Terminology
The following terminology is used throughout this document:
• The server where the Media Management application software is installed will
be referred to as the Application Server.
• The server where the database is installed will be referred to as the Database
Server.
• The server where video Transcode server is installed will be referred to as the
Transcode Server.
• The server where OpenText™ Directory Services (OTDS) is installed will be
referred to as the OTDS Server.
This guide covers installation instructions for both Windows and RedHat Enterprise
Linux (Linux). When specific example commands are given, they are specified with
either Linux or Windows syntax. You need to replace TEAMS_HOME with the OTMM
installation directory.
In these instructions, <TEAMS_REPOSITORY_HOME> should be replaced with the

repository folder you selected during the installation procedure.
Part of the installation process is ant-driven. Apache Ant™ is bundled and does not
need to be installed separately to execute the specified Ant targets. For more
information, see http://ant.apache.org/.
Note: References to the Media Management Web Client or OTMM Web Client
mean the HTML5 UI, which was introduced in version 10.5.
1.1.2.1 OTDS terminology

The following list describes some of the OTDS terminology used in this guide.
User Partition
User partitions are self-contained copies of user information that allow you to
organize your users into a structured hierarchy of users, groups, and
organizational units. A user partition within Directory Services is represented by
a unique name. You can have multiple, concurrent user partitions within
Directory Services. There are three types of user partitions:
• Synchronized - Synchronized user partitions are synchronized with an
identity provider such as Active Directory (AD) or Lightweight Directory
Access Protocol (LDAP). A synchronized user partition contains users,
groups, and organizational units that are imported from the identity
12 OpenText Media Management – Installation Guide

1.2. Recommended configuration
provider when the user partition is created. A synchronized user partition

can be automatically kept up-to-date with its source directory. Users who are
imported from an identity provider into a synchronized user partition are
authenticated by the identity provider.
• Non-synchronized - Non-synchronized user partitions are created and
maintained manually. Unlike a synchronized user partition, a non-
synchronized user partition does not have an identity provider from which
its users and groups are imported. Users and groups in a non-synchronized
user partition are maintained entirely through the OTDS Web Client. Users
who are created and maintained manually in a non-synchronized user
partition are authenticated by Directory Services.
• Non-synchronized Admin - The non-synchronized administrative user
partition, otds.admin, is installed by default when a Directory Services
server is installed. This special non-synchronized user partition cannot be
deleted. Groups within this partition may contain members from any
partition. The predefined administrative user otadmin@otds.admin, which is
created when OTDS is installed, is a member of the otadmins group within
the otds.admin user partition. The otadmins group is automatically given
access to any resource created by the otadmin user.
Resource
Resources represent each multi-user component that you want to connect to
your Directory Services server for synchronization and authentication. Each
resource within Directory Services is represented by a unique name and
resource identifier. When you create a resource, Directory Services automatically
creates an access role allowing the user that created the resource to access it.
Push Connector
An OTDS Framework that allows Users/Groups to be synchronized with
applications that traditionally stored Users/Groups in Database.
OTDS Web Client

A web-based administration client in which all the user management and
configuration operations can be performed.
1.2 Recommended configuration

While there is no technical limitation to install the entire OTMM system on a single
server, OpenText recommends multiple servers to support the core Media
Management system. Each server can be a physical computer or a virtual computer
which is dedicated to a specific function within the Media Management system.
The server roles are as follows:
Media Management server

Media Management is an Enterprise-level, digital asset management application
and framework that provides access and flexibility to capture, manage, and
dynamically use digital assets including images, video, audio, text, layouts, and
graphics.

Chapter 1 Overview
Media Management contains the Media Management Indexer component,

which allows you to create a search index using Apache Solr™ as the search
engine.
Note: Media Management needs to share its repository folder with the
Audio/Video streaming server.
OpenText™ Media Management Rich Media Analysis Service

OpenText™ Media Management Rich Media Analysis Service (Rich Media
Analysis Service), leverages OTMM by using the service to process images and
return metadata information. If Rich Media Analysis Service is installed,
activated and configured, it is used to analyze assets through a scheduled job or
to analyze new assets through a workflow that is triggered during an ingest
processes.
Note: You can optionally install Rich Media Analysis Service.
OpenText™ Media Management Adaptive Media Delivery

External applications use OpenText Media Management Adaptive Media
Delivery (Adaptive Media Delivery) to deliver assets in multiple formats.
External applications use URLs generated by OpenText™ Media Management
(OTMM) to deliver assets and/or renditions in a responsive manner, based on
the requesting device and additional asset parameters (for example, aspect ratio,
size). This enables approved media assets to be delivered to multiple channels
(such as PIM and multiple websites), and responsive design allows the assets to
be displayed properly on the user's device.
Using the Adaptive Media Delivery Administration page, you register an
external application to the Adaptive Media Delivery service to consume the
asset renditions. When an external application requests a rendition, the delivery
server checks if the rendition is available in the repository. If the rendition is not
available, it will check if the original file is available. If original file is available, it
will generate the rendition, store it in the repository. If original file is not
available, it will stage the original file from OTMM, and register the asset
identifier with OTMM, so that OTMM can send notification of any future
changes to the asset.
If a registered asset or a particular version is purged from OTMM, it will notify
all delivery servers, and the asset/rendition or the purged version (and its
renditions) in the Adaptive Media Delivery server repository will be deleted.
The rendition requests are audited by posting the request details to the
OpenText™ Experience Analytics Data Collector Data Collector service.
Notes
• You can optionally install Adaptive Media Delivery.
• You can integrate Adaptive Media Delivery with Data Collector to help
track the asset and rendition usage on external applications. Adaptive
Media Delivery integrates with Data Collector separately from OTMM.

1.2. Recommended configuration
Database server
A relational database server required by OpenText products. For more
information about supported database engines, see OpenText Media Management
Technical Specifications (https://knowledge.opentext.com/knowledge/llisapi.dll/
open/69371555).
OpenText Directory Services server

Media Management integrates with OTDS for user authentication and user
management. OTDS is the central Single-Sign-On (SSO) and authentication
service provider for OpenText products. OTDS will synchronize with your
existing Active Directory Services or LDAP server. This authentication service
helps to increase the security of the overall system and reduce the
administration effort at the same time.
Audio/Video Transcode server

A server that performs the audio and video transcoding tasks.
For more information about supported Transcode servers, see OpenText Media
Management Technical Specifications (https://knowledge.opentext.com/knowledge/
llisapi.dll/open/69371555).
Streaming Server
IIS or Apache HTTPD can be used to provide progressive download of audio/
video content in OTMM. Media Management also supports the Adobe® Media
Server and Wowza Streaming Engine™ to provide streaming capabilities for
long running audio and video assets in Media Management.
Note: When using a Video Transcode Server, you will need to provide a
shared data area where Media Management and the Video Transcode
Server can stage video assets. For more information about setting up audio
and video, see “Configuring video and audio“ on page 133.
Apache Solr™ Search Server

Media Management integrates with the Open Source Apache Solr (Solr) search
engine to provide full-text searching of all managed media assets. Solr search
provides faceted search, making it easier to navigate assets in a search result set.
OpenText recommends that you install Solr on a separate server to better
support Media Management searching and indexing.
The following are OTMM product options:
OpenText™ Secure MFT for Media Management

OpenText Secure MFT (Secure MFT) enables users to securely import and export
large-size media asset files in and out of their Media Management repository.
The integration allows Media Management end users to securely and, in an
accelerated fashion, upload to and download content from Media Management.
For more information about installing OpenText Secure MFT for Media
Management, see OpenText Secure MFT for Media Management - Enablement Guide
(MEDMGTPO-IMF).

Chapter 1 Overview
OpenText™ Media Management Creative Review

OpenText Media Management Creative Review (Creative Review) provides a
comprehensive media review process management that includes annotation and
markup and approval capability for documents, images, audio, and video.
Secure, controlled access is provided for internal and external users or agencies
to collaborate in the creative, review, and approve processes. All actions and
edits are saved, including user, action type, and date/time of all annotations and
markups that are created, modified, or deleted.
For more information about installing and configuring Creative Review, see
OpenText Media Management Creative Review - Installation Guide and Release Notes
(MEDMGTPO-ACR).
OpenText™ Experience Analytics Data Collector

OTMM is compatible with OpenText Experience Analytics Data Collector (Data
Collector). To use the Analytics feature in OTMM, you must install Data
Collector and the OpenText Analytics products, and then follow the instructions
in section 2.11 “Analytics” in OpenText Media Management - Administration Guide
(MEDMGT-AGD) to enable the feature.
For more information about what you need to install to use the Analytics feature
in OTMM, see OpenText Experience Analytics Data Collector - Installation and
Configuration Guide (CRA160201-IGD).
OpenText™ Media Management Connector for Adobe Creative Cloud

OpenText™ Media Management Connector for Adobe Creative Cloud enables
seamless integration of Adobe Creative Cloud™ (Adobe CC) applications with
OpenText™ Media Management. When connected to a Media Management
server, you can access remote assets using an Extension panel within Adobe CC.
For more information about installing and configuring OpenText Media
Management Connector for Adobe Creative Cloud, see OpenText Media
Management Connector for Adobe Creative Cloud - Installation Guide and Release
Notes (MEDMGTPO-ICC).
Important
The time clock for all the servers must be synchronized for the software
components to work together effectively. To keep the time consistent on all
machines, set up the Windows Time Service or Network Time Protocol
(NTP ).

Chapter 2
Installation Overview
This chapter provides an overview of the Media Management installation process.
2.1 Installation order

The following diagram (Figure 2–1) shows a standard installation sequence of the
components in a standard Media Management installation. If you are installing in a
High Availability (HA) environment or have multiple servers, the order may vary.
As you progress with the installation, at certain points you should stop and perform
any required configurations and test or verify the functionality of what you have
installed up to that point before continuing on.
Figure 2-1: Standard Installation order of Media Management System
Figure 2–2 shows a typical installation order of the third-party software

prerequisites along with the OpenText components. Follow the installation guides
for the other products in the overall solution. Where applicable, guidance will be
provided when specific choices will be required.

Chapter 2 Installation Overview
Figure 2-2: Installation Order and Prerequisites of Media Management

Components
2.2 Phases of the installation process

The following are the installation phases:
1. OTDS
For more information, see OpenText Directory Services - Installation and
Administration Guide (OTDS160204-IWC).
2. Core Media Management
For more information, see “Phase 2 - Core Media Management” on page 19.
3. Post-installation software
For more information, see “Phase 3 - Post-installation software” on page 20.
Note: For more information, see OpenText Media Management Technical

Specifications (https://knowledge.opentext.com/knowledge/llisapi.dll/open/
69371555).

2.2. Phases of the installation process
2.2.1 Phase 1 - OTDS

Download OTDS from OpenText My Support (https://support.opentext.com).
Notes
• OTDS Web Client is included in the installation.
• For more information, see OpenText Media Management Technical Specifications
(https://knowledge.opentext.com/knowledge/llisapi.dll/open/69371555).
• When you are using Apache TomEE (TomEE) as the application server and
you are installing OTDS and OTMM on the same server, do not set the
CATALINA_HOME global environment variable. OTDS and OTMM services
will not start correctly when CATALINA_HOME is set globally. Both Apache®
Tomcat™ (Tomcat) and TomEE refer to this variable in their scripts.
2.2.1.1 Verify the OTDS installation

To verify the OTDS installation:
1. Start OTDS by starting Tomcat.
2. Test the OTDS installation by launching a web browser and pointing to the
following:
<http_or_ https>://<OTDS>:<Tomcat_port>/otds-admin
where
OTDS is the server where OTDS is installed
Tomcat_port is the Tomcat port on which OTDS is running
Note: Ensure that the web interface is available.
2.2.2 Phase 2 - Core Media Management

Use the OTMM Installer to install Media Management as described in:
• “Core Media Management Installation Preparation“ on page 23
• “Installing on Windows“ on page 39
• “Installing on RedHat Enterprise Linux“ on page 53

Chapter 2 Installation Overview
2.2.3 Phase 3 - Post-installation software

1. Install the following software packages after you complete the installation of the
OpenText components.
Note: For more information about versions, see OpenText Media

Management Technical Specifications (https://knowledge.opentext.com/
knowledge/llisapi.dll/open/69371555).
Solr
See one of the following:
• “Installing and configuring Solr on Windows” on page 47

• “Installing and configuring Solr on Linux” on page 64
ImageMagick®
“Installing ImageMagick on Linux” on page 62
Note: The Windows installer installs ImageMagick automatically.
Video Transcoder
Might require a separate license.
• Harmonic Rhozet™ Carbon Coder™ (Rhozet) and Carbon Server

http://www.harmonicinc.com/product/promedia-carbon
• Telestream FlipFactory® (FlipFactory ) and Telestream FactoryArray®
(FactoryArray)
http://www.telestream.net/flipfactory/overview.htm
• Telestream Vantage® (Vantage)
http://www.telestream.net/vantage/overview.htm
• FFmpeg
This is open source.
http://ffmpeg.org/
Streaming Server (optional video and audio streaming software)

Might require a separate license.
Adobe Media Server, Wowza, IIS, Apache HTTPD
• http://www.adobe.com/products/
• http://www.wowza.com/products/streaming-engine/
• http://httpd.apache.org/
2. Perform the post-installation tasks. For more information, see “Post installation
tasks“ on page 71.

2.2. Phases of the installation process
3. Verify and configure the push connector. For more information, see “Verifying
and Configuring Push Connector for Media Management“ on page 81.

Chapter 3
Core Media Management Installation Preparation
This chapter provides an overview of the installation of the core Media Management
system.
3.1 Requirements
Media Management and the OpenText components are supported for the following
platforms:
Operating System
• Windows Server
• RedHat Enterprise Linux®
• CentOS
Relational Database
• Oracle
• SQL Server
• PostgreSQL
• SAP HANA
For more information, see OpenText Media Management Technical Specifications

3.2 Install prerequisites

Assemble the following software packages and respective licenses before beginning
the Media Management system installation:

69371555).
OTDS
Download OTDS from OpenText My Support (https://support.opentext.com)
and install it.
Java Development Kit (JDK)

Download latest JDK from:
http://www.oracle.com/technetwork/java/javase/downloads/index.html

Chapter 3 Core Media Management Installation Preparation
Set the JAVA_HOME environment variable to the location of the JDK installation
and add %JAVA_HOME%\bin to the path environment variable. For example, C:
\Program Files\Java\jdk1.8.0_66.
Application server
Red Hat® JBoss® Application Server Enterprise Application Platform (JBoss
EAP)
JBoss EAP requires separate licensing.
http://www.redhat.com/en/technologies/jboss-middleware/application-
platform
Notes
• Windows - Use the JBoss EAP Installer method, as Media
Management supports this method only.
• Linux - Use the JBoss EAP Installer or ZIP version methods.
• You must install and configure JBoss EAP. For more information, see
“Installing and configuring JBoss” on page 24.
Red Hat® Wildfly (Wildfly)

Download Wildfly from:
http://wildfly.org/downloads/
You must install and configure Wildfly. For more information, see
“Installing and configuring JBoss” on page 24.
Apache TomEE TomEE
Download TomEE from:
http://tomee.apache.org/downloads.html
You must install and configure TomEE. For more information, see
“Installing and configuring TomEE” on page 25.
3.2.1 Installing and configuring JBoss

This section describes the JBoss configuration to be performed for a fresh install or
an upgrade. While you should follow the installation instructions provided with
each particular product, below you will find some guidance when answering some
installation prompts and what the requirements are for OTMM.
Notes
• You must perform these configurations on all Media Management nodes.
• For more information about versions, see OpenText Media Management
Technical Specifications (https://knowledge.opentext.com/knowledge/
• If you are upgrading, take any necessary actions on pending or unconsumed
JMS messages, as they will not be migrated to the upgraded version of
OTMM.

3.2. Install prerequisites
3.2.1.1 Installing and configuring JBoss EAP

OTMM supports JBoss Enterprise Application Platform. OpenText recommends that
you do the following:
• Download JBoss EAP, and set the JBOSS_HOME environment variable to map to
the path of the JBoss installation folder. For example:
C:\jboss-eap-6.4
Notes
• Windows - Use the JBoss EAP Installer method, as Media Management
supports this method only.
• Linux - Use the JBoss EAP Installer or ZIP version methods.
• If you use the JBoss installer to install JBoss, use the default selections and
install it.
For more information about the installation, see https://access.redhat.com/

documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/
Installation_Guide/chap-Installation_Instructions.html.
• Check the following technical specifications to ensure that you have the
minimum patch level, if not you must download and install it:
OpenText Media Management Technical Specifications (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/69371555).
3.2.1.2 Installing and configuring Wildfly

Download Wildfly and add the JBOSS_HOME environment variable to map to the
path of the folder located in the extracted Wildfly directory. For example:
C:\wildfly-9.0.2.Final
For more information, see https://docs.jboss.org/author/display/WFLY9/Getting

+Started+Guide.
3.2.2 Installing and configuring TomEE

By default, OTMM installs a compatible version of TomEE during the OTMM
installation.
However, you can use an existing instance of TomEE.
To use an existing instance of TomEE:
• Add the TOMEE_HOME environment variable to map the path of the folder that is
located in the TomEE instance. For example:
C:\apache-tomee-plus-7.0.2

Notes
• You must perform these configurations on all OTMM nodes.
• Do not to use spaces in the path of the TOMEE_HOME install folder.
3.3 Database setup

A relational database (Oracle, SQL Server, PostgreSQL, or SAP HANA) is required
by the various OpenText products included in this installation. This section
describes how to set up your database prior to installing Media Management. If you
are using Windows, all of the databases are supported.
See the following sections for your database type.
Notes
• The application server must be running on a Windows platform to use SQL
Server as a database.
3.3.1 Confirming the database server requirements

The following database installation information is provided only for a quick start
reference. These steps must be performed prior to installing the Media Management
software and are intended to allow a user to install a base instance for use with
Media Management.
These instructions are not intended to provide the appropriate installation or

configuration settings for an enterprise database server installation. Consult a
qualified Database Administrator (DBA) for any sort of production or development
or testing environment. In many organizations, the database installation and
configuration is controlled by a central DBA group. It is recommended that you
consult this group directly to ensure that your database installation is correctly
configured.

3.3. Database setup
3.3.1.1 Preparing the SAP HANA database

To prepare the SAP HANA database:
1. Install SAP HANA.

For more information about the supported version of the database, see OpenText
Media Management Technical Specifications (https://knowledge.opentext.com/
2. Verify the disk space requirements for your data files.

Ensure that there is enough disk space and allocated database space on your
database server for the Media Management schema. Your requirements will
vary depending on the number and type of assets you will be storing. OpenText
recommends that, for a production environment, you should allocate disk space
based on your requirements for the number and type of assets.
Note: The Media Management schema installation uses these credentials

to create the database owner, database schema required by Media
Management.
4. Decide on a database owner name for the database owner and password.
The owner name must be unique to your installation and to the
mediamanagement_config.txt file, When the schema is created, it is created
with these user credentials.
Note: By default, the database owner name is towner.
3.3.1.2 Preparing the SQL Server database

Complete the following steps on the SQL Server database server to prepare to install
your application:
To prepare the SQL Server database:
1. Determine your data file location and sizes.

OpenText recommends that you consult a SQL Server DBA for
recommendations on size and placement of the data files.

vary depending on the number and type of assets you will be storing. OpenText
recommends that for a production environment, you should allocate resources
based on your requirements for the number of assets.
3. Install SQL Server and create a named/default SQL Server instance.

Before installing SQL Server, it will ask you for some configuration settings.
Make sure you follow these steps when installing:
• Install all prerequisites, including SQL Native Client.

• Install the following components by selecting the check box next to each
component in the component selection dialog box:
• Database Engine Services

• Management Tools - Basic
• You can use the default instance or create a named instance.
• Use the built-in System account (Local system).
• Use Mixed Mode authentication (Windows and SQL Server authentication).
• Enter a password for the "sa" user and make a note of the password.
• Accept the default values for the Collation settings,
SQL_Latin1_General_CP1_CI_AS.
Note: Use the SQL Server configuration manager to change the TCP port
of the SQL server to use a unique port. By default, it will be running on
port 1433. Disable the TCP dynamic ports.
4. Verify the installation of SQL Server.

Attempt to sign in to your new SQL Server instance using the SQL Server
Management Studio client tool, using the "sa" user.
3.3.1.3 Preparing the Oracle database

Complete the following steps on the Oracle database server to prepare for your
application installation:
To prepare the Oracle database:
1. Install Oracle.
Ensure that the following Oracle product components are installed on the
Media Management database server:
• Oracle 11g R2 Server/12c Server.
Note: If you plan to use a container database with Oracle 12c, create a
pluggable database and use this database for Media Management. To

3.3. Database setup
do this, specify the service name of this pluggable database during the
Media Management installation, instead of the service name of the
container database.
• OracleNet Services.
• Oracle JDBC/ Interfaces.
• Oracle Database Utilities (SQLPlus used during installation and upgrade).
• Oracle Java Products.

69371555).
2. Verify the disk space requirements for your tablespaces.

vary depending on the number and type of assets you will be storing. It is
recommended that for a production environment you should allocate based on
your requirements for the number and type of assets.
3. Create an Oracle SID that is Unicode compliant by selecting a Unicode

Character Set during the Oracle SID creations.
4. Verify the Oracle NLS_LANG setting.

The character set for Oracle database connections is controlled by the
environment variable NLS_LANG. Select the appropriate NLS_LANG string for
your environment and locale. For more information, see the Oracle
documentation.
5. Check the Oracle init.ora settings.

Change the following database parameters for your database instance. Note that
these parameters are recommended minimum values and may be increased
depending on your needs. Database parameters are typically modified by
calling the ALTER SYSTEM command. For example, ALTER SYSTEM set
processes=100 SCOPE=BOTH, where:
• processes = 100
• open_cursors = 500
• job_queue_processes = 10 (must be 4 or higher; 10 recommended)
6. Obtain the “system” user's password.

Obtain the password or access to DBA personnel with this password. Ask the
DBA to temporarily change it for the installation if they are not comfortable
disclosing it to you. The Media Management schema installation creates the
database owner, database tables, roles, and tablespaces required by Media
Management.

Note: You can create a user or use an existing user with the following set
of roles and system privileges, instead of a system user for installation.
Required roles
1. Connect with Admin option.
2. Resource with Admin option.
Required system privileges

1. CREATE USER, ROLE AND TABLESPACE
2. ALTER USER
3. GRANT ANY PRIVILEGE
4. SELECT ANY DICTIONARY
7. Select a DB Owner name

Decide on a Database Owner name unique to your installation (also in the
mediamanagement_config.txt as database owner default: towner) and a
password. When the Schema is created, it is created with these user credentials.
8. Linux - Verify maximum file descriptor allotment.
a. In a text editor, open the /etc/security/limits.conf file and verify that

all Linux servers that support Media Management have their maximum file
descriptor allotment set to a minimum of least 1024.
b. If the allotment is not set to 1024, shut down applications loaded on the
same server, including Oracle and the web server.
c. Append the following lines to the end of the /etc/security/limits.conf
file:
oracle soft nofile 1024
oracle hard nofile 1024
d. Sign out, and then sign in to Linux for the changes to take effect.
9. Linux - Verify the maximum file descriptor value.
a. Run the following command to test the current maximum file descriptor
value:
cat /proc/sys/fs/file-max
b. To adjust the max file descriptor setting, edit the /etc/sysctl.conf file as
the root (administrative) user by adding a new value for fs.file-max, and
then run the following command to apply the change:
/sbin/sysctl -p
Note: You must set the value of the maximum file descriptor to be
greater than the value that you set for file descriptor allotment in Step
8.
10. Create Media Management tablespaces with appropriate sizes.

3.3. Database setup
This is only necessary if you are not using default sizing.

The Media Management database installation procedure can create tablespaces
within the Oracle database specifically for Media Management objects. By
default, these tablespaces are sized to store about 10 000 assets of typical size
and type. These tablespaces are physically apportioned between two file system
directories. Often, when preparing a production installation, this default is not
appropriate.
If you need to modify the sizing of the tablespaces and you are using the
configuration file for the installation, you must update the value of
CREATE_TABLE_SPACE to 0 in the mediamanagement_config.txt file, or clear
the Create Tablespace check box in the installer and create the tablespaces of
the appropriate size and physical layout before beginning the Media
Management database installation. A total of 12 tablespaces are required, as
follows:
• TEAMS_CATALOG_DATA
• TEAMS_CATALOG_IDX
• TEAMS_CONTEXT_DATA
• TEAMS_CONTEXT_IDX
• TEAMS_CS_DATA
• TEAMS_CS_IDX
• TEAMS_OBJSTACKS_DATA
• TEAMS_OBJSTACKS_IDX
• TEAMS_PM_DATA
• TEAMS_PM_IDX
• TEAMS_UOIS_DATA
• TEAMS_UOIS_IDX
3.3.1.4 Preparing the PostgreSQL database

Complete the following steps on the PostgreSQL database server to prepare for your
application installation.
To prepare the PostgreSQL database:
1. Install PostgreSQL.
Notes
• For more information about the supported version of the database, see
OpenText Media Management Technical Specifications (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/69371555). You
can download the Linux and Windows distributions from http://
www.postgresql.org/download.

• Ensure that there is enough disk space and allocated database space on
your database server for the Media Management schema. Your
requirements will vary depending on the number and type of assets you
will be storing. OpenText recommends that, for a production
environment, you should allocate disk space based on your
requirements for the number and type of assets.
• If you are installing using a binary, confirm that the binary was built
with XML support. If you are building from a source, configure it with
the --with-libxml option.
2. Change the following configuration settings for your database instance.
Note: Change the parameters based on your requirements. The specified

configuration settings and values are enough to get you started. For more
information about the settings, see the PostgreSQL documentation.
a. Configure the listen addresses in the postgresql.conf file by setting the

listen_addresses parameter to a comma separated set of TCP/IP
addresses on which the server will listen for connections from client
applications.
Note: The location of the postgresql.conf file depends on your

installation. For the location of configuration files, refer to your
installation or consult your DBA.
Tip: To bind to all available IP interfaces, set this value to an asterisk

symbol (*) .
b. In postgresql.conf, set max_prepared_transactions to a value that at a
minimum, is as large as the max_connections setting.
c. In postgresql.conf, set the logging configuration according to your
requirements.
d. Configure client authentication.
In pg_hba.conf, set the client authentication method to md5. For example,
the following entry sets up all clients to use an encrypted password that is
based on authentication using md5.
# TYPE DATABASE USER

ADDRESS METHOD
host all all

all md5
Note: The above configuration opens the database for access to all.
You might want to restrict access to only a select group of machines or
users. For more information about how to do this, see the PostgreSQL
documentation.
e. Restart the PostgreSQL service.
3. Obtain the database “Superuser” user and password.

3.3. Database setup
Note: The Media Management schema installation uses these credentials

to create the database owner, database and table-spaces required by Media
Management.
4. Decide on a database owner name that is unique to your installation, and to the
mediamanagement_config.txt file, as the database owner and a password.
When the schema is created, it is created with these user credentials.
Note: By default, the database owner name is towner.
5. Do one of the following to create the Media Management tablespaces:
• Manually create the required tablespaces prior to running the installer.

Proceed to Step 6. Do not perform Step 7.
• Use the installer to create the required tablespaces. To do this, prepare the
required folder structure prior to running the installer. Proceed to Step 7.
Note: The installer creates tablespaces based on a specific folder

structure that you must create prior to running the installer.
6. Create the following tablespaces manually.
• TEAMS_CATALOG_DATA
• TEAMS_CATALOG_IDX
• TEAMS_CONTEXT_DATA
• TEAMS_CONTEXT_IDX
• TEAMS_CS_DATA
• TEAMS_CS_IDX
• TEAMS_OBJSTACKS_DATA
• TEAMS_OBJSTACKS_IDX
• TEAMS_PM_DATA
• TEAMS_PM_IDX
• TEAMS_UOIS_DATA
• TEAMS_UOIS_IDX
Note: You can use the <TEAMS_HOME>/ddl/postgresql/scripts/

tablespaces.sql DDL script file as a reference to create the tablespaces.
During the install, opt out of having the installer create the tablespaces, by
setting the CREATE_TABLE_SPACE option to N on the tablespaces
configuration page.
7. Create the following root directory and subdirectories for each module, and
then run the installer:

Notes
• The installer expects this specific folder structure on the database server.
On Windows, the owner of the PostgreSQL service or process must have
read-write permissions to these folders. On Linux, the user who is
configured to run the PostgreSQL service/process must own these
folders.
• There are six logical modules (CATALOG, CONTEXT, CS, OBJSTACK, PM and
UOIS) that each have data and index tablespaces associated with them.
• During installation, the installer asks for the root directories for the data
tablespaces, <some_location>/data, and <some_location>/index
tablespaces.
Folder structure for /data

<some_location>/data/catalog
<some_location>/data/context
<some_location>/data/cs
<some_location>/data/objstacks
<some_location>/data/pm
<some_location>/data/uois
Folder structure for /index

<some_location>/index/catalog
<some_location>/index/context
<some_location>/index/cs
<some_location>/index/objstacks
<some_location>/index/pm
<some_location>/index/uois
3.3.2 Preparing the application server

Complete the following steps on the application server to prepare for your
application installation:
To prepare the application server:
1. To verify the disk space requirements for the OTMM Application and content
repository, do the following:
• Ensure that there is enough disk space available on your OTMM application
server for the Media Management servers and content repository. The disk
space requirement for the initial installation is approximately 1 GB. Your
requirements will vary depending on the size and type of files you will be
storing in Media Management.

3.4. Configuring OTMM resources in OTDS
2. To create an OS user who will own the OTMM application files, do one of the
following:
• For new Windows installations - Create a Windows user or identify an

existing Windows user. You must sign in as this user when installing the
OTMM application software. This user must have administrative privileges
to run the installation.
• For new Linux installations - Identify an existing Linux group or create a
Linux group for the OTMM Linux user. Make the OTMM user a member of
this group. Identify an existing Linux user or create a Linux user (not
exceeding eight characters in length) for the OTMM application server
software. This account will be the owner of the OTMM server processes and
must be a member of the OTMM group.
3. To verify access to the OTMM software, do the following:
• Locate the OTMM software ISO image and license files and copy or mount
them onto the application server.
3.4 Configuring OTMM resources in OTDS

To integrate Media Management with OTDS, you must configure OTMM resources
in OTDS.
To integrate OTMM with OTDS:
Notes
• As part of the installation process, a resource for OTMM is automatically

created on the OTDS server. The resource name is provided during the
OTMM installation. By default, the name is “Media Management”, however
you can change this name. This resource name might be used on the sign-in
page in line dedicated for instructional text.
• By using the OTMM installer, you can create a non-synchronized user
partition. In this case, the default user, tsuper, is created as part of the
newly created non-synchronized partition.
• If you are not planning to create a non-synchronized partition using the
installer, create the default user, tsuper, in OTDS in either the synchronized
or non-synchronized user partitions, using tsuper as the first and last name.
Manually consolidate the new user to OTMM.
• OTMM requires at least one user partition in OTDS. The OTMM installer can
create one non-synchronized user partition with the default user tsuper.
Note: OTMM provides support for multiple user partitions. The user
partitions can be synchronized, non-synchronized, or a combination of
both.

Before creating the new user partition in OTDS, review the following
information about user partitions for the OTMM Administrator user creation:
All Synchronized
If the security policies allow creation of a non-domain user in LDAP/AD,
then create OTMM Administration user in LDAP/AD. If the security
policies of your organization do not allow creation of a non-domain user in
LDAP/AD, then create a non-synchronized user partition and create the
Administration user in this partition. This partition can be designated as the
“default” partition.
All Non-Synchronized
Create OTMM Administrator user in any of these partitions which can be
designated as the “default” partition.
Hybrid (Non-Synchronized and Synchronized)

Create an OTMM Administrator user in any of the non-synchronized user
partitions which can be designated as the “default” partition. If you do not
intend to create the OTMM Administrator user in a non-synchronized user
partition, refer to the “All Synchronized” section.
Notes
• For more information, see OpenText Directory Services - Installation and
• After installing and configuring OTMM, you can designate a user other
than tsuper as administrator, then disable the tsuper user in OTDS as
well as in the Media Management Administration Client and set the
“System Administrator” Role to the designated user.
3.5 Preparing the installation configuration file

The Media Management installer supports the use of a configuration file. This file
contains all the variable settings needed to install Media Management. By filling out
the file before you begin the installation, your choices from this file will be pre-filled
in the installation when you run the installation program.
Note: Using this file is optional, but it is recommended for administrators who
need to perform multiple installations and keep a reference of parameters for
later use.
A template configuration file, named mediamanagement_config.txt, is provided in

the <Media Management ISO>/OTMM directory of the Media Management ISO. Copy
this file to a working directory on the application server and edit the file to match
your environment. The file contains brief explanations and examples of all settings.

3.6. Proceeding to Windows or Linux installation
3.6 Proceeding to Windows or Linux installation

At this point in the process, you can proceed to one of the following, based upon
your operating system:
Note: In the current version of OTMM, the installer no longer embeds the JVM
for installation. The JRE is automatically picked from the JAVA_HOME
environment variable.

Chapter 4
Installing on Windows
This section describes the steps performed in the Media Management installation
and configuration process. Before installing Media Management, ensure you have
reviewed and performed the necessary steps from the previous chapters before
performing the steps in this chapter.
4.1 Installing OTMM on Windows

The installation program is delivered on the Media Management ISO and guides
you through the installation of the schema and application.
The OTMM installer is available in the Media Management ISO, mediamgmt_16.

3_windows.iso. The mediamanagement_config.txt configuration file is available
in ISO in the following location:
<Media Management ISO>/OTMM/mediamanagement_config.txt
Note: If you select a Unicode database during the installation, the file system
where the OTMM files are shared or stored must support Unicode file names.
You can install OTMM using the following methods:

• Setup screens (GUI mode)
An installer presents you with setup screens where you fill in your install values.
Notes
• OpenText recommends that you use this method to install OTMM.
• To pre-populate the installation screens with default responses, you can
specify values of the installation parameters in the
mediamanagement_config.txt configuration file. You can edit these
values during the install.
• Console
A text-based mode where parameters are read from your configuration file,
mediamanagement_config.txt. You cannot change these values during the
installation process. This mode requires your intervention to proceed to
subsequent steps.
Note: Prior to launching the installer, you must specify the values of the
installation parameters in the mediamanagement_config.txt file. This file
is mandatory if you are installing using console mode.
• Silent

Chapter 4 Installing on Windows
mediamanagement_config.txt. You cannot change these values during the
installation process. This mode requires no user interaction.
is mandatory if you are installing using silent mode.
4.1.1 Installing OTMM using the setup screens

Note: OpenText recommends that you use this method to install OTMM.
To install OTMM using the setup screens:
1. Mount the Windows Media Management ISO, mediamgmt_16.3_windows.iso.

2. Optional To use the mediamanagement_config.txt file, to pre-populate values
on your installation screens, do the following:
a. Copy the mediamanagement_config.txt file from the Windows <Media

Management ISO>/OTMM/mediamanagement_config.txt to a location on
your file system.
b. Populate the values for your installation.
3. At the command prompt, navigate to the OTMM directory that is available in
the mounted location, and then enter the following command:
<Mounted location>\Disk1\InstData\NoVM\install.bat -i gui -f
<PATH_TO_mediamanagement_config.txt>
where
i specifies the mode of installation to be launched. The default mode is gui.
f specifies the configuration file that is used to provide pre-populated values
during the install procedure. The configuration file is optional in this
installation mode.
Note: If you are using the configuration file, you must use the fully-
qualified path name. For example:
G:\OTMM\Disk1\InstData\NoVM\install.bat -i gui -f C:
\mediamanagement_config.txt
4. On the License Agreement page, if you agree with the terms, select I accept the
terms of the License Agreement, and click Next.
5. On the Java/App Server Configuration page, do the following, and then click
Next:
a. In the Java Configuration area, enter the Java home directory.

b. In the Select Application Server area, do one of the following to specify
your application server:

4.1. Installing OTMM on Windows
• To use TomEE, do one of the following:
• Click Install TomEE for the OTMM installer to install a compatible

version of TomEE in the specified TomEE HOME directory.
• Click Use Existing TomEE to choose an existing instance of TomEE.
• Click JBoss EAP and enter the location of the JBoss home directory.
• WildFly and enter the location of the Wildfly home directory.
6. On the Database Selection page, select your database and click Next.
7. On the Choose Product Features page, for a typical installation, select the
Schema and Application check boxes. This installs the Schema and Application,
providing the minimal software to start the Media Management application
after installation.
8. At the Select Install Folder page, select the folder where you want to install the
Media Management application.
Important
Do not use spaces in the installation directory.
9. On the Select Repository Folder page, select the folder where you want to store
the Media Management repository and click Next. If you do not specify a value
for <TEAMS_REPOSITORY_HOME>, the default system location, <TEAMS_HOME>/
data/repository, will be used.
10. On the Database Schema Configuration page, specify the database schema
settings and click Next.
Notes
• If the selected database is SQL Server, then the correct port number
should be mentioned. For example, the port number of the default
instance or named instance on which the Media Management database
will be created.
• Clear the Test Database Connection check box if you do not want to
test the connectivity to the database with the configured parameters.
• Oracle and PostgreSQL users - When specifying the paths for the Data File
Directory and Index File Directory, the path must be a local file path from
the database server perspective. Also, OpenText recommends that you select
the Create table space option
• SQL Server users - Verify that the SQL Server Agent Service is running.
Important
For installations on SQL Server database, it is mandatory to supply the
system administrator credentials at this screen. No other user
credentials, regardless of the level of permissions, can be used.

11. On the Application Configuration page, specify the Application Configuration

settings and click Next.
12. On the OTDS Configuration page, do the following to specify the OTDS
configuration parameters:
a. In the OTDS Base URL box, enter the base URL of OTDS. You must specify
this parameter as follows:
<http or https>://<OTDS>:<Tomcat_port>
where
<OTDS> is the server where OTDS is installed
<Tomcat_port> is the Tomcat port on which OTDS is running
Notes
• If you are using HTTPS, see KB9099470 (https://
knowledge.opentext.com/knowledge/llisapi.dll/kcs/kbarticle/view/
KB9099470) for more information about securing the connection to
OTDS using SSL.
• When OTDS is set up as a cluster (HA deployment), the base URL
should be that of the Load balancer for the cluster.
b. In the OTDS Admin Username box, enter the name of the OTDS
administrator.
Note: You must provide the information of the OTDS administrative

user. The default information is otadmin@otds.admin.
c. In the OTDS Admin Password box, enter the password of the OTDS
administrator.
d. In the OTMM Resource Name box, enter a meaningful name that will be
displayed on the OTDS page to sign in to OTMM.
The OTMM Resource name is the name of the resource that needs to be
created for OTMM in OTDS. If you select the schema install, the name of
the resource provided must not exist in OTDS. For secondary node
installations, ensure that this entry has the same value as the primary node.
Notes
• If you do not edit this resource name, the sign-in page will display
the OTMM resource on the sign-in.
• You need to create the resource name for OTMM in OTDS. If you
select the schema install, the name of the resource provided must
not exist in OTDS. For secondary node installations, ensure that this
entry has the same value as the primary node.
e. In the OTMM Use Partition box, enter the name of the user partition in
OTDS.

By default, this partition is used in OTMM. If you select the Create Non
Synchronized Partition and Default User check box, the installer creates a
partition with the above name, and tsuper user with the specified
credentials. If you select the check box for the schema installations, the
OTMM User Partition references to a non-existing partition in OTDS. For
secondary node installations, these are ignored.
f. Select the Create Non Synchronized Partition and Default User check box
for the installer to create a partition with the name that you used in Step
12.e, and tsuper user with the specified credentials.
g. Do one of the following:
• Select the Complex Password Policy Required check box, enter a

complex password that will be used as the default password. The
complex password must contain alpha numeric, special characters, and
uppercase letters.
• Clear the Complex Password Policy Required check box enter a
password that will be used as the default password using plain text.
h. In the Default User Password box, enter the password for the OTMM user,
tsuper.
Note: This will be the default password for the OTMM user, tsuper.
13. On the Video Transcode configuration page, select the Transcode server that
you want, and then click Next.
• VIDEO_CONFIGURATION - Select one Transcode server from the list.

This list contains the supported Transcode servers.
• Target Path - A shared network path for the Transcode server where the
transcode output files will be written to. The user who executes OTMM
must have read access to this path and the Transcode server must have write
access to this path. For more information, see “Configuring video and
audio“ on page 133.
Note: This is applicable to Rhozet, Vantage, and FFmpeg only.
• Transcode Host - Provide the Transcode server host name to communicate

from Media Management.
• Transcode Category -Provide the name of category where Vantage
workflows are imported and to be used by Media Management
Note: This is applicable to Vantage only.
• Transcode Port - Provide the port number of the Transcode server. The
default port is displayed, but can be changed if necessary.
Note: This is applicable to Rhozet, Vantage, and FlipFactory only.

• Transcode User - Provide the user account details of FlipFactory where your
factories are created. The default user account name that is shipped with
Media Management is displayed.
Note: This is applicable to FlipFactory only.
• Video File Staging Area - Shared location where video/audio assets will be
copied to submit them for transcoding. This shared location must be having
write access to the Media Management user and read access to the
Transcode server. For more information, see “Configuring video and audio“
on page 133.
14. On the Pre-Installation Summary page, review your selections before
continuing. Click Previous if necessary to make any changes. If everything is
satisfactory, click Install to begin the installation process.
15. If any validation errors occur during the installation, an Installation Validation
Errors dialog box appears. If this dialog box appears, review the following files:
• <TEAMS_HOME>/logs/installation/installerValidation.log
• <TEAMS_HOME>/MediaManagement_InstallLog.log
• <TEAMS_HOME>/logs/installation/admin_user.log
• <TEAMS_HOME>/logs/installation/activate_resource.log
Note: This log file will only be generated if you have selected to install
schema and application. This file should contain a message saying
“Resource key is successfully stored” if the resource is successfully
activated and the related information is stored in Media Management.
If this log contains any errors or exceptions, there is no need to reinstall
Media Management. This step can be done manually after finishing the
installation. For more information, see “Verifying the OTMM
installation“ on page 213.
16. After a successful installation, the Install Complete page appears. Note that not
all errors are deemed errors by the installer, so it is generally a good practice to
review the log files after an installation to verify the installation was successful.
For more about debugging errors information, see “Monitoring and
troubleshooting tips during installation” on page 46.
17. At the end of the installation process, you will be prompted to restart the
system. If you do not restart the system, the application may not work or
behave as expected.
18. After the installation has been completed, install your license files. The license
key on the Media Management ISO provides a two-user regular license. The
purpose of this license is to get the system started. You should have also
received your customer-specific license separately. The license consists of two
files: license.dat and license. These two files should be copied to
<TEAMS_HOME>\servers, overwriting the two files placed there during
installation.

4.1.2 Installing OTMM using the console

installation parameters in the mediamanagement_config.txt file.
To install OTMM using the console:

2. Copy the mediamanagement_config.txt file from the ISO to a location on your
file system.
3. In a text editor, open the mediamanagement_config.txt file, and then enter all
of the installation parameters required for your installation.
<Mounted location>\Disk1\InstData\NoVM\install.bat -i console -f
where
i specifies the mode of installation to be launched.
during the install procedure. This option is mandatory in console mode.
Note: You must use the fully-qualified path name for the configuration
file. For example:
G:\OTMM\Disk1\InstData\NoVM\install.bat -i console -f C:
4.1.3 Installing OTMM silently

installation parameters in the mediamanagement_config.txt file.
To install OTMM silently:
1. Mount the Windows Media Management ISO file, mediamgmt_16.

3_windows.iso.
2. Copy the mediamanagement_config.txt file from the ISO to a location on your

file system.
3. In a text editor, open the mediamanagement_config.txt file, and then enter all
of the installation parameters required for your installation.
<Mounted location>\Disk1\InstData\NoVM\install.bat -i silent -f

where

during the install procedure. This option is mandatory in silent mode.
file. For example:
G:\OTMM\Disk1\InstData\NoVM\install.bat -i silent -f C:
4.1.4 Monitoring and troubleshooting tips during installation

During installation, the database scripts in <TEAMS_HOME>/ddl are merged with
your settings, either from the configuration file or entries in the GUI, so that updated
versions of these files are written to <TEAMS_HOME>/ddl_install/. Every time you
run the installation program or one of the installation Ant targets, these files are
merged again and copied again into <TEAMS_HOME>/ddl_install/. Do not edit
these files directly; any manual edits to the files in ddl_install will be lost. The
output from the execution of the DDL scripts is saved in <TEAMS_HOME>/
ddl_install/log.
In GUI mode, you can also check the other command prompt window that opened
when the install program started. This window typically has verbose debug
information. This output window will close automatically when the installer exits,
thus it is important to review the messages before exiting from the installer.
Check the <TEAMS_HOME>/MediaManagement_InstallLog.log and <TEAMS_HOME>/

logs/installation/installerValidation.log files. These files contain detailed
information about any errors that occurred during the installation. The
installerValidation.log file contains validation errors for user entered
parameters during the install.
Note: These log files only get written when you exit the installer.
Another useful file to check is <TEAMS_HOME>/logs/installation/admin_user.

log. One of the final steps in the installation is the creation of the administrator user,
tsuper (by default). If this file does not exist, the installation did not progress to this
point. Or, if this file does not report Administrator successfully created, then
something failed; typically with the database configuration or connectivity. If you
fixed a problem with the administrator user and you want to re-run the step to
create this user, instead of re-running the entire installation, you can run the
following:
C:> cd '%TEAMS_HOME%\install\ant'
C:> ant create-admin-user

4.2. Installing and configuring Solr on Windows
4.2 Installing and configuring Solr on Windows

OpenText recommends that you install Solr on a separate server. However, you can
install it on the OTMM host. You can also convert a remote Solr instance to High
Availability (HA).
Note: By default, the OTMM Indexer updates the Solr index. During
installation, the user name for the OTMM Indexer is set to “tsuper” and the
password is “tsuper”. If you used a different administrative user and
password, you can change the sign-in credentials. For more information, see
section 3.4 “Changing the Indexer sign-in information” in OpenText Media
Management - Administration Guide (MEDMGT-AGD).
4.2.1 Installing Solr on a remote server (recommended)

To install Solr on a remote server:
1. Create a folder for Solr on the server where you will be installing Solr. For
example, C:\SolrInstall.
2. To create a subfolder structure with the root solr-5.3.1, for example, C:

\SolrInstall\solr-5.3.1, do the following:
• Navigate to the Windows Media Management ISO, mediamgmt_16.

3_windows.iso.
• Extract the <Media Management ISO>\SOLR\solr-5.3.1.zip file to the

folder that you created in Step 1.
Note: In the following steps, the solr-5.3.1 folder is referred to as

SOLR_ROOT.
3. On the OTMM server, set up the Solr index that is specific to OTMM, by
running one of the following Ant commands from %TEAMS_HOME%\install\
ant.
Notes
• The Ant command that you use depends on the port number on which
you plan to run Solr. By default, Solr uses 8983 as its port number.
When you configure Solr to run as a Windows service, you will have the
option of configuring an alternate port number.
• Setting up the index creates a Solr index on the Media Management
installation in the <TEAMS_HOME>\solr5_otmm folder and updates all the
configuration files.
• If you will be running Solr on port 8983, run the following Ant command:
ant create-solr-index

• If you will be running Solr on a non-default port number, run the following
Ant command:
ant -DSolr.port=<port number> create-solr-index
4. Copy the solr5_otmm folder created in Step 3 to the Solr server.
Notes
• Leave a copy of the solr5_otmm folder on the OTMM server. You can
use it to configure Solr locally, and then copy the changes to the remote
instance
• In the following steps, the location of the solr5_otmm folder on the Solr
server will be referred to as SOLR5_OTMM_DIR.
5. On the Solr server, configure Solr to recognize the OTMM Solr index area by
doing the following:
a. In a text editor, open the <SOLR_ROOT>\server\solr\solr.xml file.

b. Add the following immediately after the initial <solr> start tag:
<str name="coreRootDirectory"><SOLR5_OTMM_DIR></str>
where
<SOLR5_OTMM_DIR> is the location of the sol5_otmm folder. For example:
<str name="coreRootDirectory">C:\solr5_otmm</str>
6. To configure Solr to run as a Windows service, do the following:
a. Copy the nssm-2.24.zip file from the Windows Media Management ISO
path, <Media Management ISO>\SOLR\nssm-2.24.zip, to the Solr server.
b. Extract nssm-2.24.zip to in a folder that you create. For example, C:
\SolrServiceInstaller.
Note: This creates a subfolder structure with the root nssm-2.24. For
example, C:\SolrServiceInstaller\nssm-2.24.
c. From a command prompt, change to the nssm-2.24 directory.
d. Do one of the following to run Solr on the default port number, 8983, or an
alternate port number:
• To run Solr on the default 8983 port number, run the following
command:
installSolrService <SOLR_ROOT>
where
<SOLR_ROOT> is the SOLR_ROOT directory path.
installSolrService C:\SolrInstall\solr-5.3.1
Note: If this directory path contains spaces, enclose it in double

quotes. For example:

• To run Solr on alternate port number, run the following command:
installSolrService <SOLR_ROOT> <PORT>
where
<SOLR_ROOT> is SOLR_ROOT directory path
<PORT> is the port number you want Solr to run on.
Note: If the directory path contains spaces, enclose it in double

installSolrService "C:\SolrInstall\solr-5.3.1 8994"
Note: To remove the Solr Windows service, run the

uninstallSolrService.bat script at any time. This script does not
take any parameters.
7. Start the Solr Windows service on the Solr server.
8. Use your browser to verify that the Solr Administration user interface is
available:
http://solr_host:8983/solr
Note: Use the port number that you configured the Solr Windows service
to run on. The Solr server log file is available in the <SOLR_ROOT>\server\
logs folder.
9. Update the OTMM installation to refer to the Solr host by editing the SOLR_HOST
and SOLR_URL entries in the Tresource file to point to the remote Solr instance,
as follows:
[COMMON\SOLR]
"SOLR_HOST"="<solr_host>"
"SOLR_URL"="http://<solr_host>:8983/solr"
Notes
• The Tresource file is located in the <TEAMS_HOME>/data/cs/global
directory of each installation.
• Use the port number that you configured the Solr Windows service to
run on.
10. In a text editor, open the <TEAMS_HOME>\install\ant\build.cfg file and edit
it to include the correct Solr location information:
<property name="solr.host" value="<solr_host>"/>
<property name="solr.url" value="http://<solr_host>:8983/solr"/>
to run on.

11. Restart Media Management.
4.2.2 Installing Solr on the Media Management host

To install Solr on the Media Management host:
1. Create a folder for Solr. For example:

C:\SolrInstall
2. To create a subfolder structure with the root solr-5.3.1, for example, C:

\SolrInstall\solr-5.3.1, do the following:
• Navigate to the Windows Media Management ISO, mediamgmt_16.

3_windows.iso.
• Extract the <Media Management ISO>\SOLR\solr-5.3.1.zip file to the

folder that you created in Step 1.
Note: In the following steps, the solr-5.3.1 folder is referred to as

SOLR_ROOT.
3. Set up the Solr index that is specific to OTMM, by running one of the following
Ant commands from %TEAMS_HOME%\install\ant.
Notes
• The Ant command that you use depends on the port number on which
you plan to run Solr. By default, Solr uses 8983 as its port number.
When you configure Solr to run as a Windows service, you will have the
option of configuring an alternate port number.
• Setting up the index creates a Solr index in the %TEAMS_HOME%
\solr5_otmm folder and updates all the configuration files.
• If you will be running Solr on port 8983, run the following Ant command:
• If you will be running Solr on a non-default port number, run the following
Ant command:
4. To configure Solr to recognize the OTMM Solr index area, do the following:
a. In a text editor, open the <SOLR_ROOT>\server\solr\solr.xml file.

<str name="coreRootDirectory"><TEAMS_HOME>\solr5_otmm</str>
where
<TEAMS_HOME> is the location of TEAMS_HOME. For example:
<str name="coreRootDirectory">C:\OTMM\solr5_otmm</str>

5. To configure Solr to run as a Windows service, do the following:
a. Copy the nssm-2.24.zip file from the Windows Media Management ISO
path, <Media Management ISO>\SOLR\nssm-2.24.zip, to the Solr server.
b. Extract the contents of the nssm-2.24.zip in a folder that you create. For
example:
C:\SolrServiceInstaller
c. From a command prompt, change to the nssm-2.24 directory.
d. Do one of the following to run Solr on the default port number, 8983, or an
alternate port number:
• To run Solr on the default 8983 port number, run the following
command:
installSolrService <SOLR_ROOT>
where
<SOLR_ROOT> is the SOLR_ROOT directory path.
Note: If this directory path contains spaces, enclose it in double

installSolrService "C:\SolrInstall\solr-5.3.1"
• To run Solr on alternate port number:

installSolrService <SOLR_ROOT> <PORT>
where
<SOLR_ROOT> is SOLR_ROOT directory path
<PORT> is the port number you want Solr to run on.
Note: If the directory path contains spaces, enclose it in double

installSolrService "C:\SolrInstall\solr-5.3.1 8994"
Note: To remove the Solr Windows service, run the

uninstallSolrService.bat script at any time. This script does not
take any parameters.
6. Start the Solr Windows service.
7. Navigate to the Solr Administrative home page to verify the installation:

http://localhost:<port>/solr
to run on. The Solr server log file is available in the <SOLR_ROOT>\server\
logs folder.

4.2.3 Converting a remote Solr instance to HA

To convert a remote Solr instance to High Availability (HA):
Note: There is a one-to-one mapping between OTMM application nodes and

Solr servers. The following instructions refer to the remote Solr server as this
node’s Solr server.
1. Verify the following on the OTMM server:
a. You have a local, empty Solr data folder called <TEAMS_HOME>\solr5_otmm\

otmmcore\data.
Note: Empty means that the <TEAMS_HOME>\solr5_otmm\otmmcore

\data folder is empty or does not exist.
b. The solr.host and solr.url values in <TEAMS_HOME>\install\ant

\build.cfg refer to the remote Solr host.
c. The SOLR_HOST and SOLR_URL entries configured in the <TEAMS_HOME>\cs\

global\Tresource file refer to the remote Solr host.
2. Run one of the following Ant tasks from <TEAMS_HOME>\install\ant on the

Media Management server to configure the remote slave or master Solr server:
• To set this node’s Solr server as the Master, run the following:
ant configure-solr-master
• To set this node’s Solr server as a Slave, run the following:

ant configure-solr-slave
These Ant tasks update the configuration in the local solr5_otmm index
directory.
Note: There can be only one Solr Master server. If you configure a second
node to be a Master, you will get an error when you run the Ant task.
3. To propagate the Solr configuration changes that you made in Step 2 to the
remote Solr server, do the following:
a. Stop the Solr Windows service on the remote Solr server.
b. Copy the local <TEAMS_HOME>\solr5_otmm index folder to the remote Solr

host.
c. Overlay the new or updated index on top of the solr5_otmm folder on the
Solr server. This is the SOLR5_OTMM_DIR that you created in “Installing
Solr on a remote server (recommended)” on page 47.
d. Restart the Solr Windows service on the remote Solr host.

Chapter 5
Installing on RedHat Enterprise Linux
This chapter describes the steps performed in the Media Management installation
and configuration process. Before installing Media Management, ensure you have
reviewed and performed the necessary steps from the prior chapters before
performing the steps in this chapter. Following the installation, you should check if
any Service Packs are available to install.
5.1 Installing OTMM on Linux

The OTMM installer is available in the Mediamanagement ISO file, mediamgmt_16.

3_linux.iso. The mediamanagement_config.txt configuration file is available in
ISO in the following location:
<Media Management ISO>/OTMM/mediamanagement_config.txt
Notes
• Linux users must mount the ISO as the Linux root user.
• If you select a Unicode database during the installation, the file system
where the OTMM files are shared or stored must support Unicode file
names.
You can install OTMM using the following methods:

Notes

• To pre-populate the installation screens with default responses, you can
specify the values of the installation parameters in the
mediamanagement_config.txt. You can edit these values during the
install.
• On Linux, this mode requires an X-Windows interface. You will need to
set DISPLAY in your environment and have an X-Windows server
running on your local computer.
• Console

Chapter 5 Installing on RedHat Enterprise Linux
mediamanagement_config.txt. You cannot change the values during the
subsequent steps.
is mandatory if you are installing using console mode.
• Silent
mediamanagement_config.txt. You cannot change the values during the
installation process. This mode requires no user interaction.
is mandatory if you are installing using silent mode.
5.1.1 Installing OTMM using the setup screens

Notes
• To use GUI mode on Linux, you need an X-Windows interface. You need to
set DISPLAY in your environment and have an X-Windows server running on
your local computer. For example, if you have connected to the Linux server
from your Windows computer, you need to have software such as
OpenText™ Exceed™ TurboX (ETX) installed and running. Be sure to set
your DISPLAY in your Linux environment prior to running the installation.
For example:
DISPLAY=10.1.2.3:0.0; export DISPLAY
where
10.1.2.3 is the IP address of your local computer
To install Media Management using the setup screens:
1. Mount the Linux Media Management ISO image, mediamgmt_16.3_linux.iso

on the Media Management application server.
2. Optional To use the mediamanagement_config.txt file to pre-populate values on

your installation screens, do the following:
a. Copy the configuration file from Linux <Media Management ISO>/OTMM/

mediamanagement_config.txt to a location on your file system.
b. Populate the values for your installation.
3. On a terminal, navigate to the OTMM directory that is available in the mounted

location, and then enter the following command:

5.1. Installing OTMM on Linux
<Mounted location>/Disk1/InstData/NoVM/install.sh -i gui -f

where
i specifies the mode of installation to be launched. The default mode is gui.
installation mode.
qualified path name. For example:
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.sh -i gui -f
/home/otmmuser/mediamanagement_config.txt
4. On the License Agreement page, after reading the license agreement, click I
accept and click Next.
Next:

• To use TomEE, do one of the following:
• Click Install TomEE for the OTMM installer to install a compatible

version of TomEE in the specified TomEE HOME directory.
• Click Use Existing TomEE to choose an existing instance of TomEE.
• WildFly and enter the location of the Wildfly home directory.
6. On the Database Selection page, select your database and click Next.

7. On the Execution Type page, select Install, and then click Next.
8. On the Choose Product Features page, for a typical installation select the
Schema and Application check boxes. This installs the Schema and Application,
providing the minimal software to 'start' the Media Management application
after installation. Click Next.
9. On the Select Install Folder page, select the folder where you want the Media
Management application installed and click Next.
Important
Do not use spaces in the installation directory.

10. On the Select Repository Folder page, select the folder where you want the
Media Management repository stored and click Next. If you do not specify a
value for <TEAMS_REPOSITORY_HOME>, the default system location, which is
<TEAMS_HOME>\data\repository, will be used.
11. On the Database Schema Configuration page, enter the Database Schema
Configuration and click Next.
Note: When specifying the paths for the Data File Directory and Index
File Directory, the path must be a local file path from the database server
perspective. Also, OpenText recommends that you select the Create table
space option.
12. On the Application Configuration page, set the application configuration

details and click Next.
13. On the OTDS Configuration page, do the following to specify the OTDS
configuration parameters:
a. In the OTDS Base URL box, enter the base URL of OTDS. You must specify
this parameter as follows:
<http or https>://<OTDS>:<Tomcat_port>
where
<OTDS> is the server where OTDS is installed
<Tomcat_port> is the Tomcat port on which OTDS is running
Notes
• If you are using HTTPS, see KB9099470 (https://
knowledge.opentext.com/knowledge/llisapi.dll/kcs/kbarticle/view/
KB9099470) for more information about securing the connection to
OTDS using SSL.
• When OTDS is set up as a cluster (HA deployment), the base URL
should be that of the Load balancer for the cluster.
b. In the OTDS Admin Username box, enter the name of the OTDS
administrator.
Note: You must provide the information of the OTDS administrative

user. The default information is otadmin@otds.admin.
c. In the OTDS Admin Password box, enter the password of the OTDS
administrator.
d. In the OTMM Resource Name box, enter a meaningful name that will be
displayed on the OTDS page to sign in to OTMM.
The OTMM Resource name is the name of the resource that needs to be
created for OTMM in OTDS. If you select the schema install, the name of
the resource provided must not exist in OTDS. For secondary node
installations, ensure that this entry has the same value as the primary node.

Notes
• If you do not edit this resource name, the sign-in page will display
the OTMM resource on the sign-in.
• You need to create the resource name for OTMM in OTDS. If you
select the schema install, the name of the resource provided must
not exist in OTDS. For secondary node installations, ensure that this
entry has the same value as the primary node.
e. In the OTMM Use Partition box, enter the name of the user partition in
OTDS.
By default, this partition is used in OTMM. If you select the Create Non
Synchronized Partition and Default User check box, the installer creates a
partition with the above name, and tsuper user with the specified
credentials. If you select the check box for the schema installations, the
OTMM User Partition references to a non-existing partition in OTDS. For
secondary node installations, these are ignored.
f. Select the Create Non Synchronized Partition and Default User check box
for the installer to create a partition with the name that you used in Step
13.e, and tsuper user with the specified credentials.
g. Do one of the following:
• Select the Complex Password Policy Required check box, enter a

complex password that will be used as the default password. The
complex password must contain alpha numeric, special characters, and
uppercase letters.
• Clear the Complex Password Policy Required check box enter a
password that will be used as the default password using plain text.
h. In the Default User Password box, enter the password for the OTMM user,
tsuper.
Note: This will be the default password for the OTMM user, tsuper.
14. On the Video Transcode configuration page, select the desired Transcode
server and click Next.
• VIDEO_CONFIGURATION – Select one Transcode server from the list.

This list contains the supported Transcode servers.
• Target Path - A shared network path for the Transcode server where the
transcode output files will be written to. The user who executes OTMM
must have read access to this path and the Transcode server must have write
access to this path. For more information, see “Configuring video and
audio“ on page 133.
Note: This is applicable to Rhozet, Vantage, and FFmpeg only.
• Transcode Host – Provide the Transcode server hostname to communicate

from Media Management.

• Transcode Port – Provide the port number of the Transcode server. The
default port is displayed, but can be changed if necessary.
• Transcode User – Applicable to FlipFactory only. Provide the user account
details of FlipFactory where your factories are created. The default user
account name that is included with Media Management is displayed.
• Video File Staging Area – Shared location where video/audio assets will be
copied to for transcoding. This shared location must have write access to the
Media Management user and read access to the Transcode server. For more
information, see “Configuring video and audio“ on page 133.
15. On the Pre-Installation Summary page, verify the installation properties. Click
the Previous button to make changes if necessary, and then click Install.
16. If any validation errors occur during the installation, an Installation Validation
Errors dialog box will open. If this dialog box opens, review the
installerValidation.log file to see a detailed list of the validation errors.
This validation log is located in:
<TEAMS_HOME>/logs/installation/installerValidation.log
You should also review the following installation log:
<TEAMS_HOME>/MediaManagement_InstallLog.log.
Note: For more about what is being checked during validation

information, see “Appendix B ‒ Validation checks“ on page 259.
17. On the Install Complete page, click Done to complete the installation.
Note: The Install Complete page appears if the installation is successful.
18. Sign out, and then sign in using the Linux user account that used to install
Media Management.
19. After the installation has been completed, install your license files. The license
key on the Media Management ISO provides a two-user regular license. The
purpose of this license is to get the system started. You should have also
received your customer-specific license separately. The license consists of the
license.dat and license files. These two files must be copied to
<TEAMS_HOME>/servers, overwriting the two files placed there during
installation.

5.1.2 Installing OTMM using the console

installation parameters in the mediamanagement_config.txt.
To install OTMM using the console:

file.
2. Copy the mediamanagement_config.txt from the ISO to a location and fill all
the installation parameters required for your installation.
3. On a terminal, change to the OTMM directory that is available in the mounted

<Mounted location>/Disk1/InstData/NoVM/install.sh -i console -f
where
during the install procedure. This option is mandatory in console mode.
file. For example:
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.sh -i console -f
$HOME/mediamanagement_config.txt
5.1.3 Installing OTMM silently

installation parameters in the mediamanagement_config.txt.
To install OTMM silently:

file.
2. Copy the mediamanagement_config.txt from the ISO to a location and fill all
the installation parameters required for your installation.
3. On a terminal, change to the OTMM directory that is available in the mounted

<Mounted location>/Disk1/InstData/NoVM/install.sh -i silent -f
where


file. For example:
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.sh -i silent -f
$HOME/mediamanagement_config.txt
5.1.4 Monitoring and troubleshooting tips during installation

During installation, the database scripts in <TEAMS_HOME>/ddl are merged with
your settings (either from the configuration file or entries in the GUI) and updated
versions of these files are written to <TEAMS_HOME>/ddl_install/. Every time you
run the installation program or one of the installation ant targets, these files are
merged and then copied into <TEAMS_HOME>/ddl_install/.Do not edit these files
directly, for any manual edits to the files in ddl_install will be lost. The output from
running the ddl scripts is saved in <TEAMS_HOME>/ddl_install/log.
In GUI mode, you can also check the other Command Prompt window that opened
when the install program started. This window typically has verbose debug
information. This output window closes automatically when the installer has
finished, so it is important to review the messages before exiting from the installer.
Check the <TEAMS_HOME>/MediaManagement_InstallLog.log and <TEAMS_HOME>/

logs/installation/installerValidation.log files. These files contain detailed
information about any errors that occurred during the installation. The
installerValidation.log file contains validation errors for user-entered
parameters during the install.
Note: These log files only get written after you exit the installer.
Another useful file to check is <TEAMS_HOME>/logs/installation/admin_user.

log. One of the final steps in the installation is the creation of the administrator user
(tsuper by default). If this file does not exist, the installation did not progress to this
point. Or, if this file does not report 'Administrator successfully created', then
something failed, typically with the database configuration or connectivity. If you
think have fixed a problem with the administrator user and you want to re-run the
step to create this user, instead of re-running the entire installation, you can do the
following:
% cd '$TEAMS_HOME/install/ant'
% ant create-admin-user

5.1.5 Setting the OTMM user environment

Note: This section is applicable when the root user is performing the OTMM
installation.
Media Management is installed as the root user. Therefore, the root user’s .profile
and .bash_profile files are updated with the OTMM environment variables.
After a successful installation, the OTMM user must copy these OTMM settings to
their local .profile or .bash_profile startup files.
To set the OTMM user environment:
1. Copy the OTMM environment variables to your local.profile

or .bash_profile startup files.
2. Set the following environment variables for the OTMM user:
Note: Enusre that all Media Management environment variables are by

the following comment:
# New environment setting added by MediaManagement on <DATE>
• TEAMS_HOME
• JAVA_HOME
• JBOSS_HOME
Note: Set the environment variable to JBOSS_HOME if the application

server is configured as JBoss.
• TOMEE_HOME
Note: Set the environment variable to if the application server is

configured as TomEE.
• TEAMS_REPOSITORY_HOME
• PATH
• ANT_HOME
• LD_LIBRARY_PATH
• TEAMS_SERVER_DEBUG_LEVEL
• INTERP_SH
• INTERP_PERL
3. Sign in again as a Media Management user for the environment variable

changes to take effect.

5.1.6 Changing the Media Management directory ownership

Note: This section is applicable when the root user is performing the OTMM
installation.
If OTMM is installed by the root user, the ownership of the OTMM and
APP_SERVER_HOME directories must be changed to the OTMM user account.
To change the Media Management directory ownership:
1. If the OTMM user account is, for example otmmuser, then issue the following
commands to change the directory ownership:
JBoss
chown -R otmmuser $JBOSS_HOME
TomEE
chown -R otmmuser $TOMEE_HOME
Note: If $TEAMS_REPOSITORY_HOME is not located within $TEAMS_HOME,

issue the following command to change the directory ownership of the
repository:
chown -R otmmuser $TEAMS_REPOSITORY_HOME
2. If you choose to create separate OS users for Media Management and its related
applications (DB, Tomcat/OTDS/Solr), OpenText recommends to change the
group membership of Media Management files to the Linux group with these
OS users as members. If the Linux group is for example otdam, then you would
issue the following command to change group membership:
chgrp -R otdam $TEAMS_HOME
5.2 Installing ImageMagick on Linux

Notes
• This section is only applicable if OTMM is installed in a Linux environment
• The Linux installation includes the RedHat Package Manager (RPM)
packages required to install ImageMagick on RedHat Enterprise Linux.
To install ImageMagick on Linux:
1. Do one of the following:
• Sign in as the root user to run the following commands.

• Run the commands using sudo to acquire root privileges, for example, sudo
<command>.

5.3. Installing X Virtual Framebuffer on Linux
2. Change directories to <TEAMS_HOME>/install/ImageMagick, and enter the

following commands to install the ImageMagick packages:
yum install -y ImageMagick-libs-7.0.6-5.x86_64.rpm
yum install -y ImageMagick-7.0.6-5.x86_64.rpm
3. Verify that the /usr/bin directory is in the Media Management user’s PATH.
By default, ImageMagick is installed in the /usr/bin directory.
Notes
• ImageMagick uses the ufraw-batch utility to convert dng images. For dng
image conversions, download and install the ufraw rpm. Use the yum
install -y command to install the ufraw RPM package and all its
dependencies.
• Prior to running yum install -y ufraw, you must add a repository that
contains the ufraw package. For example, you can add the Nux repository.
On RHEL 6 the command is: yum install -y http://li.nux.ro/
download/nux/dextop/el6/x86_64/nux-dextop-release-0-2.el6.nux.
noarch.rpm
On RHEL 7 the command is: yum install -y http://li.nux.ro/
download/nux/dextop/el7/x86_64/nux-dextop-release-0-1.el7.nux.
noarch.rpm
5.3 Installing X Virtual Framebuffer on Linux

Media Management uses the Spicer libraries to generate thumbnail images and
previews for PDF and MS Office documents. On RedHat Linux, these libraries
depend on the X Virtual Framebuffer (XVFB) to create the thumbnails.
If you do not already have XVFB installed on your Linux machine, the install
packages are provided with the Media Management installation.
Notes
• This section is only applicable if OTMM is installed in a Linux environment.
• You only need to install this if you want to generate thumbnail and preview
images for PDF and MS Office documents and if you want to generate PDF
previews for MS Office documents. For all other MIME types, ImageMagick
will be used to generate thumbnail and preview images.
• You only need to install this if you want to generate thumbnail and preview
images for PDF and MS Office documents and if you want to generate PDF
previews for MS Office documents. For all other MIME types, ImageMagick
will be used to generate thumbnail and preview images.
To install XVFB:

• Sign in as the root user to run the following commands.

• Run the commands using sudo to acquire root privileges, for example, sudo
<command>.
2. Change directory to TEAMS_HOME/install/xorg.

3. Run the following commands:
yum install -y xorg-x11-server-common-1.13.0-23.el6.x86_64.rpm
yum install -y xorg-x11-server-Xvfb-1.13.0-23.el6.x86_64.rpm
4. To install mesa-libGLU, enter the following command:

yum install -y mesa-libGLU
Note: If you are using RedHat Linux version 7, you must also install mesa-
libGLU.
5.4 Installing and configuring Solr on Linux

OpenText recommends that you install Solr on a separate server. However, you can
install it on the OTMM host. You can also convert a remote Solr instance to High
Availability (HA).
Note: By default, the OTMM Indexer updates the Solr index. During
installation, the user name for the OTMM Indexer is set to “tsuper” and the
password is “tsuper”. If you used a different administrative user and
password, you can change the sign-in credentials. For more information, see
section 3.4 “Changing the Indexer sign-in information” in OpenText Media
5.4.1 To install Solr on a remote server (recommended)

To install Solr on a remote server:
1. From the Media Management ISO, mediamgmt_16.3_linux.iso, copy the

<Mediamanagement ISO>\SOLR\solr-5.3.1.tgz file to the server where you
want to install Solr.
2. To install Solr, do the following:
Note: Solr is installed using the install_solr_service.sh shell script.

You must run this installation script as root.
a. Extract the install_solr_service.sh script from the solr-5.3.1.tgz

file using the following command:
tar xzf solr-5.3.1.tgz solr-5.3.1/bin/install_solr_service.sh
--strip-components=2
b. Verify that the lsof utility is installed by running the following:
yum list installed lsof

5.4. Installing and configuring Solr on Linux
Note: The installation script requires that the lsof utility to be

installed on the machine.
c. If the lsof utility is not installed, install it by running the following
command:
sudo yum install lsof
The installation script has a number of configuration options, all of which
have default values. Each default can be overwritten through a command
line parameter:
Option Default Command line

parameter
Solr Installation Directory /opt -i
Writable Files Directory /var/solr -d
Solr User solr -u
Solr Port 8983 -p
• The Solr Installation Directory is the location underneath which the

distribution archive will be extracted.
• The Writable Files Directory created will contain the Solr log files and
index configuration files.
• The Solr User is the system user that will own all of the Solr files and the
running Solr process.
Note: If the specified user does not exist, the installation script will
create it. If your organization has specific requirements for
creating new user accounts, then you should create the user before
running the script. OpenText recommends that the Solr User does
not have root permissions for security reasons.
• The Solr Port is the port number used by the Solr service.
d. To install Solr with the default options, run the following command:
sudo bash ./install_solr_service.sh solr-5.3.1.tgz
Tip: This is equivalent to using the command line:

sudo bash ./install_solr_service.sh solr-5.3.1.tgz -i /opt
-d /var/solr -u solr -p 8983
3. To set up the Solr index that is specific to OTMM, do one of the following:
• If your Solr installation uses the default port number, 8983, run the
following ant command from $TEAMS_HOME/install/ant:
• If your Solr installation uses an alternate port number, run the following ant
command from $TEAMS_HOME/install/ant:

Note: This creates a Solr index in the $TEAMS_HOME/solr5_otmm

directory and updates all configuration files.
4. Copy this solr5_otmm directory to the Solr server.
Notes
• Leave a copy of the solr5_otmm directory on the OTMM server. You
can use it to configure Solr locally, and then copy the changes to the
remote instance.
• In the following steps, the location of the solr5_otmm directory on the
OTMM server are referred to as SOLR5_OTMM_DIR.
5. Change the permissions of the solr5_otmm directory to be owned by the Solr
user by running the following command from below its parent directory:
chown -R <solr username> solr5_otmm
where
< solr username> is the Solr user that you used when you installed Solr
a. In a text editor, open the solr.xml file located in the /data subdirectory
below the Writable Files Directory that you chose when you installed Solr.
Tip: If you used the default location, it is /var/solr/data/solr.xml.
<str name="coreRootDirectory"><SOLR5_OTMM_DIR></str>
where
<SOLR5_OTMM_DIR> is the solr5_otmm directory copied to the Solr server.
For example:
<str name="coreRootDirectory">/var/solr5_otmm</str>
7. Restart the Solr service by running the following command:

sudo service solr restart

http://localhost:8983/solr
Note: Use the port number that you configured the Solr service to run on.
The Solr server solr.log file is available in the logs subdirectory below
the Writable Files Directory that you chose when you installed Solr. If you
used the default location, it is /var/solr/logs).
9. Update the OTMM installation to refer to the Solr host by editing the SOLR_HOST
and SOLR_URL entries in the Tresource file as follows:

[COMMON\SOLR]
"SOLR_HOST"="<solr_host>"
"SOLR_URL"="http://<solr_host>:8983/solr"
Notes
• The Tresource file is located in the <TEAMS_HOME>/data/cs/global
directory of each installation.
• Use the port number that you configured the Solr service to run on.
10. Edit the <TEAMS_HOME>\install\ant\build.cfg file to include the correct Solr
location information, as follows:
<property name="solr.host" value="<solr_host>"/>
<property name="solr.url" value="http://<solr_host>:8983/solr"/>
5.4.2 To install Solr on the Media Management host

To install the Solr search engine on the Media Management host:
1. To install Solr, do the following:
a. From the Media Management ISO, mediamgmt_16.3_linux.iso, copy the

<Mediamanagement ISO>\SOLR\solr-5.3.1.tgz file to the server where
you want to install Solr.
b. Extract the install_solr_service.sh script from the solr-5.3.1.tgz
file using the following command:
tar xzf solr-5.3.1.tgz solr-5.3.1/bin/install_solr_service.sh
--strip-components=2
Note: Solr is installed using the install_solr_service.sh script.
c. Verify that the lsof utility is installed by running the following:

yum list installed lsof
Note: The installation script requires that the lsof utility to be

installed on the machine.
d. If the lsof utility is not installed, install it by running the following
command:
sudo yum install lsof
The installation script has a number of configuration options, all of which
have default values. Each default can be overwritten through a command
line parameter:

Option Default Command line

parameter
Solr Installation Directory /opt -i
Writable Files Directory /var/solr -d
Solr User solr -u
Solr Port 8983 -p
• The Solr Installation Directory is the location underneath which the

distribution archive will be extracted.
• The Writable Files Directory created will contain the Solr log files and
index configuration files.
• The Solr User is the system user that will own all of the Solr files and the
running Solr process.
Note: When installing Solr on the same machine as OTMM, to

avoid the potential for permissions conflicts Solr should be
installed to use the same OTMM user as Media Management.
• The Solr Port is the port number used by the Solr service.
e. To install Solr to use the OTMM user as the Solr user and use the default
values for all other options, run the following command:
sudo bash ./install_solr_service.sh solr-5.3.1.tgz -u <OTMM
username>
Note: If the OTMM user is <OTMM username>, this is equivalent to

running the following command line:
sudo bash ./install_solr_service.sh solr-5.3.1.tgz -i /opt
-d /var/solr -u otmmuser -p 8983
2. To set up the Solr index that is specific to OTMM, do one of the following:
• If your Solr installation uses the default port number, 8983, run the
following ant command from $TEAMS_HOME/install/ant:
• If your Solr installation uses an alternate port number, run the following ant
command from $TEAMS_HOME/install/ant:
Note: This creates a Solr index in the $TEAMS_HOME/solr5_otmm

directory and updates all configuration files.
a. In a text editor, open the solr.xml file located in the /data subdirectory
below the Writable Files Directory that you chose when you installed Solr.

Tip: If you used the default location, it is /var/solr/data/solr.xml.
<str name="coreRootDirectory"><TEAMS_HOME>/solr5_otmm</str>
where
<TEAMS_HOME> is the TEAMS_HOME location. For example:
<str name="coreRootDirectory">/usr/local/share/otmm/
solr5_otmm</str>
4. Restart the Solr service by running the following command:

sudo service solr restart

http://localhost:8983/solr
The Solr server solr.log file is available in the logs subdirectory below
the Writable Files Directory that you chose when you installed Solr. If you
used the default location, it is /var/solr/logs).
5.4.3 Converting a remote Solr instance to HA

To convert a remote Solr instance to HA:
Note: There is a one-to-one mapping between OTMM application nodes and

Solr servers. The following instructions refer to the remote Solr server as this
node’s Solr server.
1. Verify the following on the OTMM server:
a. You have a local, empty Solr data folder called <TEAMS_HOME>/solr5_otmm/

otmmcore/data.
Note: Empty means that the <TEAMS_HOME>/solr5_otmm/otmmcore/

data folder is empty or does not exist.
b. The solr.host and solr.url values in <TEAMS_HOME>/install/ant/
build.cfg refer to the remote Solr host.
c. The SOLR_HOST and SOLR_URL entries configured in the <TEAMS_HOME>/cs/
global/Tresource file refer to the remote Solr host.
2. Run one of the following Ant tasks from <TEAMS_HOME>/install/ant on the

Media Management server to configure the remote slave or master Solr server:
• To set this node’s Solr server as the Master, run the following:
• To set this node’s Solr server as a Slave, run the following:

These Ant tasks update the configuration in the local solr5_otmm index
directory.
Note: There can be only one Solr Master server. If you configure a second
node to be a Master, you will get an error when you run the Ant task.
3. To propagate the Solr configuration changes that you made in Step 2 to the
remote Solr server, do the following:
a. Stop the Solr service on the remote Solr server by running the following
command:
sudo service solr stop
b. Copy the local <TEAMS_HOME>/solr5_otmm index folder to the remote Solr
host.
c. Overlay the new or updated index on top of the solr5_otmm folder on the
Solr server, the SOLR5_OTMM_DIR that you created in “To install Solr on a
remote server (recommended) ” on page 64.
d. Reset the permissions of the solr5_otmm directory to be owned by the Solr
user by executing the following command from its parent directory:
chown -R <solr username> solr5_otmm
where
<solr username> is the Solr user you configured when you installed Solr
e. Restart the Solr service on the remote Solr host by running the following
command:
sudo service solr start

Chapter 6
Post installation tasks
This section provides information about the tasks that you need to perform after the
installation.
6.1 Editing the service configuration file on Linux

Note: This section is applicable to Linux only.
While starting services, the PATH environment variable is initialized to /sbin:/

usr/sbin:/bin:/usr/bin. Any updates that you make to the PATH variable in
user's '.bahsrc' or '.bash_profile' will be ignored while starting the services.
Edit the ${TEAMS_HOME}/bin/artesia-process-manager-wrapper-unix.conf

service configuration file to specify custom PATH and Library path that will be used
while starting the OpenText Media Manager and OpenText Indexer services.
Edit the configuration property PATH_TO_CUSTOM_EXECUTABLES to append the

PATH variable with the required custom location.
Note: If the executable is already present in any of the "/sbin:/usr/sbin:/

bin:/usr/bin" locations, you are not required to update this configuration.
Edit the configuration property LIBRARY_PATH to specify a custom library location.
As part of installation, these two properties will be updated with pre-configured

configurations. You need to append the custom locations to the value of these
entries instead of replacing the values.
6.2 Configuring TomEE

By default, if multiple OTMM configurations are present in the network, such as
Production, Development, and Testing, you must specify unique values for the node
name and multicast IP address for each these configurations.
To configure the parameter values:
1. To edit the ejbd.properties file, do the following:
a. In a text editor, open the ejbd.properties file, which is located in

%TOMEE_HOME%\conf\conf.d, and then do the following:
b. Update the value of the bind parameter to a resolvable IP or host name,
fully qualified domain name, of the OTMM server. For example:
server = org.apache.openejb.server.ejbd.EjbServer
bind = 10.96.25.95

Chapter 6 Post installation tasks
port = 11099
disabled = ${openejb.profile.custom}
threads = 200
backlog = 200
discovery = ejb:ejbd://{bind}:{port}
gzip = false
2. To edit the multicast.properties file, do the following:
a. In a text editor, open the multicast.properties file, which is located in

%TOMEE_HOME%\conf\.
b. Update value of the bind parameter.
Notes
• This parameter specifies multicast address to use for cluster
information. Ensure that this multicast address is unique for each of
the OTMM configurations in the network.
• In an HA cluster deployment, you must configure all the nodes of
the cluster to have the same value for all the multicast address.
server =
org.apache.openejb.server.discovery.MulticastDiscoveryAgent
bind = 235.25.20.3
port = 6142
disabled = false
group = default
6.3 Configuring JBoss

By default, OTMM is deployed with a High Availability (HA) profile in JBoss. If
multiple OTMM configurations are present in the network, such as Production,
Development, and Testing, each of these configurations must have a unique values
for the node name, multicast IP address, messaging groups and mod cluster.
To configure the parameter values:
1. In a text editor, open one of the following:
WINDOWS
<JBOSS_HOME>/bin/otmm-standalone.conf.bat
UNIX
<JBOSS_HOME>/bin/otmm-standalone.conf
2. Configure the following:
Note: You must ensure that all the configurations have unique values for
the following parameters:
• OTMM_JBOSS_NODE_NAME

6.3. Configuring JBoss
The value of the parameter specifies the unique node name within the
cluster.
• OTMM_JBOSS_DEFAULT_MULTICAST_ADDRESS
The value of the parameter specifies the multicast address to use for cluster
formation. Ensure that this multicast address is unique for each of the
OTMM configurations in the network.
• OTMM_JBOSS_MESSAGING_GROUP_ADDRESS
The value of the parameter specifies the multicast address to use for JBoss
messaging group. Ensure that this multicast address is unique for each of the
OTMM configurations in the network.
• OTMM_JBOSS_MOD_CLUSTER_ADDRESS
The value of the parameter specifies the multicast address to use.
• OTMM_JBOSS_BIND_ADDRESS
The value of the parameter specifies the resolvable IP or host name (fully
qualified domain name) of the OTMM server.
Note: In an HA cluster deployment, you must configure all the nodes of

the cluster to have the same value for all the above parameters, except
OTMM_JBOSS_NODE_NAME and OTMM_JBOSS_BIND_ADDRESS.
Example 6-1: Parameter values
OTMM_JBOSS_NODE_NAME=PRODNODE1
OTMM_JBOSS_DEFAULT_MULTICAST_ADDRESS=232.232.10.79
OTMM_JBOSS_MESSAGING_GROUP_ADDRESS=232.232.11.79
OTMM_JBOSS_MOD_CLUSTER_ADDRESS=232.232.12.79
OTMM_JBOSS_BIND_ADDRESS=10.25.96.25
6.3.1 Configuring the JBoss Recovery Module for Oracle

If OTMM is installed on Oracle and uses JBoss Enterprise, then configure the
Recovery Module as suggested by JBoss Enterprise, as follows:
https://access.redhat.com/documentation/en-US/
JBoss_Enterprise_Application_Platform/6.4/html/
Administration_and_Configuration_Guide/sect-XA_Datasources.html#sect-
XA_Recovery (https://access.redhat.com/documentation/en-US/
Administration_and_Configuration_Guide/sect-XA_Datasources.html#sect-
XA_Recovery )
Notes
• This applies to JBoss EAP and Wilfly.


6.4 Updating PROVIDER_HOST

This section provides information about updating the PROVIDER_HOST property for
JBoss and TomEE.
6.4.1 Updating the PROVIDER_HOST property for JBoss

Note: This section applies to JBoss EAP and Wildfly only.
To update the PROVIDER_HOST property for JBoss:
1. In a text editor, open the Tresource file.
Note: The Tresource file is located in the <TEAMS_HOME>/data/cs/

global folder.
2. Navigate to the [JNDI\CONFIG] and locate the PROVIDER_HOST property.
3. Update the value of the PROVIDER_HOST property with the value of the
OTMM_JBOSS_BIND_ADDRESS parameter or the host name of the OTMM server. If
you specify the host name, ensure that it resolves to the IP address given in the
OTMM_JBOSS_BIND_ADDRESS parameter. For example:
PROVIDER_HOST"="remote://10.96.25.95:11099
Note: For more information about this parameter, see “Configuring JBoss”
on page 72.
6.4.2 Updating the PROVIDER_HOST property for TomEE

Note: This section applies to TomEE only.
To update the PROVIDER_HOST property for TomEE:
1. In a text editor, open the Tresource file.
Note: The Tresource file is located in the <TEAMS_HOME>/data/cs/

global folder.
2. Navigate to the [JNDI\CONFIG] and locate the PROVIDER_HOST property.
3. Update the value of the PROVIDER_HOST property with the value of the host
name of the OTMM server. If you specify the host name, ensure that it resolves
to the IP address given in the bind property in the %TOMEE_HOME%\conf\conf.d
\ejbd.properties file. For example:
"PROVIDER_HOST"="ejbd://10.96.25.95:11099"

6.5. Installing MediaInfo
Note: For more information about this parameter, see “Configuring

TomEE” on page 71.
6.5 Installing MediaInfo

You only need to install MediaInfo if you use Vantage or FFmpeg as a Transcode
server.
You need to install MediaInfo on Linux only. For Windows installations, MediaInfo
is installed as part of the OTMM installation.
To install MediaInfo on Linux:
Note: Perform the following steps on all the cluster nodes individually.
1. Use the following yum commands to install the RPM packages that are available
in the TEAMS_HOME/install/mediainfo folder in the sequence:
Note: Sign in as the root user to run the following command, or run the
commands using sudo to acquire root privileges, for example, sudo
<command>.
a. yum install -y libzen0-0.4.31-1.x86_64.RHEL_6.rpm
b. yum install -y libmediainfo0-0.7.76-1.x86_64.RHEL_6.rpm
c. yum install -y mediainfo-0.7.76-1.x86_64.RHEL_6.rpm
2. Run mediainfo -help to ensure that it works from the terminal.
6.6 Updating workflows in Vantage

To set up workflows in Vantage:
1. Sign in to the server where Media Management is installed.
2. Locate the Vantage transcode configuration file in <TEAMS_HOME>\data\

videotransformer_workflows.zip.
3. Copy <TEAMS_HOME>\data\videotransformer_workflows.zip to the Vantage

server.
4. Verify that the Vantage services are running.
5. Extract the videotransformer_workflows.zip file into a folder.
6. Navigate to the videotransformer_workflows\vantage\Workflows\

MediaMgmt folder in the extracted location and make the following changes in
each file:

a. Replace all occurrences of the string $OTMM_HOST_NAME$ with the Media

Management server details. This can be the name or IP of the OTMM node
or load balancer. The host configured here should be reachable from the
Vantage server.
b. Replace all the occurrences of $OTMM_HTTP_PORT$ with the HTTP port
where the OTMM server was configured. In the case of a single node, the
default value is 11090. If a load balancer or proxy is configured, specify the
port as the HTTP port on which the load balancer or proxy is running. The
OTMM host name and HTTP port configured in the above steps are used to
make web service notifications after a transcode job is executed on the
Vantage server. So make sure the OTMM host configured in the above step
is accessible from the Vantage server over the HTTP port configured above.
7. Open the Vantage Management Console, sign in as a user with the Vantage
administrator role, and perform the following steps:
a. Navigate to Workflow Design Items > Media Nicknames and import all
the media nicknames in the videotransformer_workflows\vantage
\MediaNicknames folder in the extracted location.
b. Navigate to Workflow Design Items > Metadata Labels and import all the
metadata labels in the videotransformer_workflows\vantage
\MetadataLabels folder in the extracted location.
c. Navigate to Workflow Design Items > Attachment Nicknames and import
all the attachment nicknames in the videotransformer_workflows\
vantage\AttachmentNicknames folder in the extracted location.
8. Open Vantage Workflow Designer and sign in as a Vantage user and perform
the following steps to import all the default Vantage Workflows into a category.
a. Select File > Create New Category and create a new category, for example,
MediaMgmt.
b. Import all the workflows in the videotransformer_workflows\vantage
\Workflows\MediaMgmt folder in the extracted location by right-clicking
the newly created category in the left-hand side pane and selecting Import
Workflows.
c. Click File > Batch Workflow Operations and select all the workflows
associated with the above category and click Activate.
For more information, see “To set up workflows in Vantage:“ on page 164.

6.7. Configuring the Media Management user partitions in OTDS
6.7 Configuring the Media Management user

partitions in OTDS
Important
The non-synchronized user partition that was created during the installation
process will be added to the OTMM table, OTDS_USER_PARTITIONS,
automatically.
Administrators must configure the information for each of the Media Management
user partitions configured in OTDS as follows:
• The information must be configured manually in the OTDS_USER_PARTITIONS

table to specify whether the user partition created in OTDS is synchronized or
non-synchronized.
• The column PARTITION_NAME must contain the name of the user partition created
for Media Management in OTDS.
Note: If you are using Active Directory, this column should be populated
with the fully qualified domain name system (DNS) of the current domain.
For more information, see OpenText Directory Services - Installation and
• The column IS_SYNCHRONIZED_PARTITION should contain either Y or N. A value
of Y indicates that the user partition is synchronized and N indicates that the user
partition is non-synchronized. If the user partition information is not configured
in this table, the user partition will be considered as non-synchronized.
Note: If the Media Management installer creates a user partition in OTDS,

OpenText recommends that you edit the password policy of the partition with
your own requirements.
6.8 Securing the application

This section contains information about how to secure the OTMM installation after
you have completed a successful installation.
6.8.1 Securing OTMM from clickjack attacks

To prevent potential clickjack attacks, also known as UI redress attacks, you can
configure the Session Filter to add custom response headers. You can use it to add X-
Frame-Options. OTMM includes the following preconfigured settings:
• X-Frame-Options=SAMEORIGIN
• X-Content-Type-Options=nosniff

The above preconfigured settings prevent the application from being embedded in
another application. If you want the OTMM application to be used in another
application, you must set the headers in the responseheaders.properties file,
which available in the following locations:
For the OTMM Web Administration tool

JBoss EAP and Wildfly - <TEAMS_HOME>/ear/artesia.ear/teams.war/WEB-
INF
TomEE - <TEAMS_HOME>/ear/artesia/teams/WEB-INF
For the Web Desktop or Mobile Client

JBoss EAP and Wildfly - <TEAMS_HOME>/ear/artesia.ear/otmmux.war/WEB-
INF
TomEE - <TEAMS_HOME>/ear/artesia/otmmux/WEB-INF
If you want to embed the OTMM application in a another application, you must set
the X-Frame-Options to ALLOW-FROM http://including.application.com as
follows:
X-Frame-Options=ALLOW-FROM http://including.application.com
Note: You can also use the responseheaders.properties file to set

additional headers for other security issues.
6.8.2 Securing asset import

Using the AssetInterceptor API, you can specify which file types are secure or
ensure that they are virus free before they are added to the system. You can ensure
assets are virus free by implementing virus scanning automatically.
For more information about the AssetInterceptor API, see section 5.10 “Asset
interceptor API” in OpenText Media Management - Integration Guide (MEDMGT-AIN).
6.8.3 Enabling secure session cookies

This section explains how to enable secure session cookies in all OTMM web
applications that are deployed on the following application servers:
• JBoss EAP, located in the <TEAMS_HOME>/ear/artesia.ear/ folder

• Wildfly, located in the <TEAMS_HOME>/ear/artesia.ear/ folder
• TomEE, located in the <TEAMS_HOME>/ear/artesia/ folder
Note: How you enable secure session cookies depends on your configuration.
If you are using a web server in front and are terminating SSL at the web
server, you need to configure secure session cookies in the application server.

6.9. Creating Property Templates
To enable secure session cookies:
• In the WEB-INF/web.xml file, edit session-config by adding <secure>true</

secure> as follows:
<session-config>
<cookie-config>
<http-only>true</http-only>
<path>/</path>
<secure>true</secure>
</cookie-config>
</session-config>
6.8.4 Deleting SQL log files

During the installation, OTMM writes log file files to TEAMS_HOME\ddl_install
\log.
This log files contain plaintext passwords. You can delete it files after completing a
successful installation.
6.9 Creating Property Templates

In the HTML5 UX, property templates are required for users to upload files. Before
users can upload files, they must have access to one or more property templates. For
information about creating property templates, see section 2.6.2.1 “Creating
Property Templates” in OpenText Media Management - Administration Guide
(MEDMGT-AGD).
6.10 Generating thumbnails for Postscript files

ImageMagick uses Ghostscript to generate thumbnails for Postscript files. To have
ImageMagick generate thumbnails for PostScript files, you must download and
install Ghostscript from the following:
http://www.ghostscript.com/download/gsdnld.html
Note: If you installed OTMM on Windows, ImageMagick is installed

automatically. If you installed OTMM on Linux, you need to install
ImageMagick. For more information, see “Installing ImageMagick on Linux”
on page 62.

6.11 Editing the legal terms and conditions text

You can overwrite the default text that end users see for legal terms and conditions
when they download, export, or share assets. For more information, see section 10.3
“Modifying the legal terms and conditions” in OpenText Media Management - HTML5
Integration Guide (MEDMGT-AIG).

Chapter 7
Verifying and Configuring Push Connector for

Media Management
User authentication is handled through OTDS. OTDS is considered the master

source for user identity and authentication, but this user information must be stored
in Media Management because of other user-based functions outside the scope of
OTDS. Therefore, a push mechanism has been established to push all new and
updated user information to Media Management. This chapter discusses the
installation of this connector.
Important
Before configuring the Push Connector, make sure the OpenText Media
Manager service is running.
Note: This section is only required if you cleared the Create Non
Synchronized Partition and Default User check box during the OTMM
installation process. For more information, see “Installing OTMM on
Windows” on page 39.
7.1 Testing the Push Connector configuration for

Media Management
The OTMM installer automatically configures the Push Connector. Perform the steps
in the following procedure to test the configuration.
To configure the Push Connector for Media Management:
1. Verify that the Media Management server is running.
2. Sign in to the OTDS Web Client.
3. Edit the Media Management resource, OTMM_RESOURCE_ID, which is already in

active state. The OTMM_RESOURCE_ID setting is located under the OTDS
\GENERAL component, which belongs to the OTDS configuration group.
Note: The OTDS group is accessible from the Settings page in the Web
Administration tool. For more information, see section 2.13.2.3 “Editing a
component and properties” in OpenText Media Management -
Administration Guide (MEDMGT-AGD).
4. On the Connection Information page, do the following:
a. Confirm the Media Management information:

Chapter 7 Verifying and Configuring Push Connector for Media Management
• Media Management URL: The URL for the Media Management server;
use the fully qualified host name.
Note: For HA configurations, the host and port of the URL should
be the same as the load-balancer to Media Management.
• User name of Administrator: Name of the Media Management
administrator.
b. In the Password of Administrator box, enter the password of the Media
Management administrator.
c. Click Test connection to make sure the connection information works.
5. On the User Attribute Mappings page, click Next.
6. On the User group details page, click Next.
Note: The User Group details will not be pushed to Media Management.
7. Click Finish.
8. Configure the OTDS groups to be synchronized with Media Management by

doing one of the following:
• For User Group memberships to be synchronized to Media Management

through Push Connector, from the web administration menu, navigate to the
Access Roles of Media Management. From the Actions menu, click Include
Groups from OUs. In this case, OTDS raises events for changes in any of the
OTDS groups. For more information, see OpenText Directory Services -
Installation and Administration Guide (OTDS160204-IWC).
• From the web administration menu, navigate to the Access Roles of Media
Management. From the Actions menu, click View Access Role Details.
Navigate to Groups, click Add. Search for the required group, and add the
selected items to the access role, and then save the changes. In this case,
OTDS raises events only for the added groups. For more information, see
OpenText Directory Services - Installation and Administration Guide
(OTDS160204-IWC).
Note: Even though events are only raised for the mapped groups, the
Media Management Administration client displays all of the groups.

Chapter 8
Installing OpenText Media Management Rich Media
Analysis Service
Rich Media Analysis Service analyzes image assets and generates metadata based on
its analysis. After running a Rich Media Analysis Service job, the image asset is
populated with metadata based on the results of the analysis.
Important
After installing the Rich Media Analysis Service on Windows or Linux, you
must perform tasks to activate the service and to make image assets eligible
for analysis. For more information, see section 3.8 “Configuring Rich Media
Analysis Service” in OpenText Media Management - Administration Guide
(MEDMGT-AGD).
8.1 Preparing to install

Prior to installing Rich Media Analysis Service, you must ensure that you have the
prerequisite applications. If you are installing Linux, you must install prerequisite
applications.
After installing you must perform tasks to activate the service and to make image
assets eligible for analysis. For more information, see section 2.10 “Media Analysis”
in OpenText Media Management - Administration Guide (MEDMGT-AGD).
8.1.1 Prerequisites
The following is required on Windows and Linux operating systems.
• Java Runtime environment (JRE) 1.8
Note: On Windows, set the JAVA_HOME environment and point to Java 8,

and include java.exe in the PATH.
The following is required on Linux only.

• Create an account that will be used to run Rich Media Analysis Service. Ensure
that the account is part of the sudo group to allow it to run commands with
elevated permissions.

Chapter 8 Installing OpenText Media Management Rich Media Analysis Service
8.2 Installing Rich Media Analysis Service

The section guides you through the installation of Rich Media Analysis Service. The
installation program is delivered on the Media Management ISO, mediamgmt_16.
3_windows.iso for Windows and mediamgmt_16.3_linux.iso for Linux.
Important
After installing Rich Media Analysis Service, you must perform tasks to
activate the service and to make image assets eligible for analysis. For more
information, see section 2.10 “Media Analysis” in OpenText Media
8.2.1 Installing on Windows using the setup screens

To install on Windows using the setup screens:
1. Verify that the prerequisite applications are installed. For more information, see
“Prerequisites” on page 83.
3. Navigate to \RMA\Disk1\InstData\VM\install.exe and double-click the

install.exe file.
4. On the Introduction page, click Next.
5. On the License Agreement page, accept the terms of the license agreement and
click Next.
6. On the Choose Install Folder page, accept the default location or enter a
location. Click Next.
7. On the RMA Port page, use default value or enter a port. Click Next.
8. On the Azure Details page, enter the proper Azure URL. You must point to the
Azure Computer Vision endpoint and your Azure subscription key. Click Next.
9. Complete the installation.
10. Restart the Rich Media Analysis Service server.
Note: After the install is complete, the Rich Media Analysis Service is
running and the mediaanalysis.log file has been generated. The log file
includes the status of the server startup. In the event of an error, you can
review the log file, which is available in the <Installation Dir>/logs
folder. For more information, see “Troubleshooting” on page 93.

8.2. Installing Rich Media Analysis Service
8.2.2 Installing on Windows silently

To install on Windows silently:
3. Copy the \RMA\richmediaanalysis_config.txt file from the ISO location to a

location on your system.
4. In a text editor, open the richmediaanalysis_config.txt file and enter all of
the installation parameters for your installation.
Note: Ensure that you set USER_INSTALL_DIR to the proper installation

location where Rich Media Analysis Service will be located.
5. At the command prompt, navigate to the Rich Media Analysis Service directory
that is available in the mounted location, RMA\Disk1\InstData\VM\, and then
enter the following command:
<Mounted location>\RMA\Disk1\InstData\VM\install.exe -i silent -f
<PATH_TO_richmediaanalysis_config.txt>
where
file. For example:
G:\RMA\Disk1\InstData\VM\install.exe -i silent -f C:
\richmediaanalysis_config.txt
Tip: When the installation is complete, the command prompt indicates

that the path to the final installation log that was generated.
Note: After the install is complete, the Rich Media Analysis Service is running
and the mediaanalysis.log file has been generated. The log file includes the
status of the server startup. In the event of an error, you can review the log file,
which is available in the <Installation Dir>/logs folder. For more
information, see “Troubleshooting” on page 93.

8.2.3 Installing on Linux using the setup screens

To install on Linux using the setup screens:
2. Sign into the system using an account that will be used to run the service.
Note: This account must be part of the sudo group for installation and to
run the service
3. Mount the Linux Media Management ISO, mediamgmt_16.3_linux.iso.
4. On a terminal, navigate to the Rich Media Analysis Service directory that is

available on the mounted location, /RMA/Disk1/InstData/VM/, and then enter
the following command:
sudo <Mounted location>/RMA/Disk1/InstData/VM/install.bin -i gui
where
5. On the Introduction page, click Next.
6. On the License Agreement page, accept the terms of the license agreement and
click Next.
7. On the Choose Install Folder page, accept the default location or enter a
location. Click Next.
8. On the RMA Port page, use default value or enter a port. Click Next.
9. On the Azure Details page, enter the proper Azure URL. You must point to the
Azure Computer Vision endpoint and your Azure Subscription Key. Click Next.
10. Complete the installation.
11. Log out and then log in to Linux to allow configurations to take effect.
Note: After the install is complete, Rich Media Analysis Service is running and
the mediaanalysis.log file has been generated. The log file includes the

8.2. Installing Rich Media Analysis Service
8.2.4 Installing on Linux silently

To install on Linux silently:
2. Sign into the system using an account that will be used to run the service.
Note: This account must be part of the sudo group for installation and to
run the service
3. Mount the Linux Media Management ISO, mediamgmt_16.3_linux.iso.
4. On a terminal, navigate to the Rich Media Analysis Service directory that is

available on the mounted location, /RMA/Disk1/InstData/VM/.
5. Copy the /RMA/richmediaanalysis_config.txt file from the ISO location to a

location on your system.
6. In a text editor, open the richmediaanalysis_config.txt file and enter all of

the installation parameters for your installation.
Note: Ensure that you set USER_INSTALL_DIR to the proper installation

location where Rich Media Analysis Service will be located.
7. To run the install with elevated permissions, on a terminal, navigate to the Rich
Media Analysis Service directory that is available on the mounted location, /
RMA/Disk1/InstData/VM/, and then enter the following command:
sudo <Mounted location>/RMA/Disk1/InstData/VM/install.bin -i

silent -f <PATH_TO_richmediaanalysis_config.txt>
where

file. For example:
sudo <ISOPATH>/RMA/Disk1/VM/InstData/install.bin -i silent -f
~/richmediaanalysis_config.txt
Note: After the install is complete, Rich Media Analysis Service is running and
the mediaanalysis.log file has been generated. The log file includes the

8.2.5 Verifying the install

To verify the status of the service:
• Do one of the following:
WINDOWS
Verify that the OpenText Media Manager Rich Media Analysis Service is be
present in your system and is running.
LINUX
On a terminal, enter the following command:
systemctl status richmediaanalysis
8.3 Post-installation
This sections provides tasks that you must perform after you install Rich Media
Analysis Service.
After installing Media Analysis Service on Linux, you must install the following in
sequence:
1. Erlang
2. Socat
3. Pivotal RabbitMQ® (RabbitMQ)
If necessary, you can perform post-install configurations by editing the

application.properties file.
8.3.1 Installing Erlang on Linux

To install Erlang on Linux:
1. Navigate to the Rich Media Analysis Service installation directory.
2. Install the Erlang RedHat Package Manager (RPM ), which is located under the
<Installation_Directory>/install/erlang directory.
3. On a terminal, navigate to the <Installation_Directory> directory and enter

sudo rpm -ivfh install/erlang/erlang-19.3.6.3-1.el7.centos.
x86_64.rpm

8.3. Post-installation
8.3.2 Installing Socat on Linux

To install Socat on Linux:
Note: You must configure a repository in your system to download and install
Socat. For a list of configured repositories in your system, run the following:
yum repolist
• To download and install Socat, enter the following command:

sudo yum install socat
8.3.3 Installing RabbitMQ on Linux

To install Pivotal RabbitMQ on Linux:
1. Navigate to the Rich Media Analysis Service installation directory.
2. Install the RabbitMQ RPM, which is located under the

<Installation_Directory>/install/rabbitmq directory.
3. Enter the following command:

sudo rpm -ivfh install/rabbitmq/rabbitmq-server-3.6.12-1.
el7.noarch.rpm
4. Start the RabbitMQ server by entering the following command:

sudo systemctl start rabbitmq-server
5. Stop, and then start the OpenText Media Manager Rich Media Analysis Service.
For more information, see “Starting and stopping the service” on page 91.
Note: Authentication is required to run the service. You will be prompted

for credentials.
Notes
• After the install is complete, Rich Media Analysis Service is running and the
mediaanalysis.log file has been generated. The log file includes the status
of the server startup. In the event of an error, you can review the log file,
• For more information about RabbitMQ, see https://www.rabbitmq.com/
management.html..

8.3.4 Configuring Rich Media Analysis Service install

properties
You can change the properties, as required, using the application.properties
file.
To configure Rich Media Analysis Service properties:
1. In a text editor, open the <Rich_Media_Analysis_HOME>/conf/

application.properties configuration file.
2. Edit any of the following settings accordingly:
server.port The TCP port that is used by Rich Media Analysis Service to listen
for requests.
The default port is 8093.
mediaanalysis. The Azure subscription key, Ocp-Apim-Subscription-Key. For
azure.subscript example:
ion-key 14f1************************c448
mediaanalysis. The Computer Vision API endpoint for Azure Cognitive Services.
azure.cv-url For example:
https://southeastasia.api.cognitive.microsoft.com/
vision/v1.0/analyze
mediaanalysis.c A string that represents the IP addresses of the clients that are
lientiplist authorized to connect to the Rich Media Analytics service. Multiple
client IPs are separated by a comma. For example:
127.0.0.1,10.18.89.107
spring.rabbitm The address of the server that is hosting RabbitMQ. By default, this is
q.host set to 127.0.0.1.
spring.rabbitm The port number for RabbitMQ host. By default, this is set to 5672.
q.port
spring.rabbitm The user name of the RabbitMQ user. By default, this is set to guest.
q.username
spring.rabbitm The password for the RabbitMQ user. By default, this is set to guest.
q.password
Important
Do not change the password through the application.
properties file.
OpenText recommends that you change the default
password. However, you must change the password by
creating an encryption file. For more information, see
“ Encrypting the Pivotal RabbitMQ® password”
on page 91.
3. Restart the OpenText Media Manager Rich Media Analysis Service.

4. Verify that the service started properly.

8.4. Starting and stopping the service
8.3.4.1 Encrypting the Pivotal RabbitMQ® password

If you change the RabbitMQ password, you need to encrypt it. As an administrator,
you can use the RabbitMQ management plugin, http://hostname:15672.
Notes
• If you change the RabbitMQ at a later time, you must perform the encryption
again.
• For more information about RabbitMQ, see https://www.rabbitmq.com/.
To encrypt the RabbitMQ password:
1. Create one of the following files to contain the RabbitMQ password:
Windows
%RMA_HOME%\conf\RabbitMQ_SEC_Srv.cfg
Linux
$RMA_HOME/conf/RabbitMQ_SEC_Srv.cfg
2. In a text editor, open the RabbitMQ_SEC_Srv.cfg file, enter the RabbitMQ

password in plain text and save the file.
3. To encrypt the password file run one of the following:
Windows
%RMA_HOME%\bin\crypt.bat ef %RMA_HOME%\conf\
RabbitMQ_SEC_Srv.cfg
Linux
$RMA_HOME/bin/crypt.sh ef $RMA_HOME/conf/RabbitMQ_SEC_Srv.cfg
4. Restart the OpenText Media Manager Rich Media Analysis Service.
5. Verify that the service started properly.
8.4 Starting and stopping the service

To start and stop the service on Windows:
1. Start the OpenText Media Manager Rich Media Analysis Service.
2. Stop the OpenText Media Manager Rich Media Analysis Service under
Services.
To start and stop the service on Linux:
1. To start the service, run the following:

<Installation Dir>/bin/startRichMediaAnalysis.sh
2. To stop the service, run the following:

<Installation Dir>/bin/stopRichMediaAnalysis.sh
Note: On Linux, Rich Media Analysis Service requires authentication to run.

You will be prompted for credentials when you start or stop the service.
8.5 Uninstalling Rich Media Analysis Service

This section guides you through the uninstall process.
Note: If you installed Rich Media Analysis Service silently, the application
uninstalls silently.
8.5.1 To uninstall Rich Media Analysis Service using screens

To uninstall Rich Media Analysis Service using screens:
1. At a command prompt or on a terminal, navigate to the Rich Media Analysis

Service installation directory.
2. Run the uninstall executable, with elevated permissions, from the Rich Media
Analysis Service uninstall subdirectory. For example:
WINDOWS
C:\RichmediaAnalysis\Uninstall\Uninstall.exe
LINUX
sudo Uninstall/Uninstall
3. On the Uninstall Rich Media Analysis page, click Uninstall.
4. On the Uninstall Complete page, click Done.
8.5.2 To uninstall Rich Media Analysis Service silently

To uninstall Rich Media Analysis Service silently:
1. At a command prompt or on a terminal, navigate to the Rich Media Analysis

Service installation directory.
2. Run the uninstall executable, with elevated permissions, from the Rich Media
Analysis Service uninstall subdirectory. For example:
WINDOWS
C:\RichmediaAnalysis\Uninstall\Uninstall.exe —i silent
LINUX
sudo Uninstall/Uninstall -i silent

8.6. Troubleshooting
8.6 Troubleshooting
Rich Media Analysis Service provides two sets of log types to use to investigate
errors: installation logs and service logs.
Installation logs
These log files provide installation details, such as the action executed and the
status of the action. You can find these files in the <Installation Directory>
\logs\installation directory.
Service logs
These log files provide details about the service operation, such as startup
configuration and service requests processed. You can find these files in the
<Installation Directory>\logs directory.
8.6.1 The service was not created during a Linux install

This error might be associated with your account permissions. You can diagnose the
issue by running the installation service script again.
To resolve this issue:
1. Navigate to the base of the installation directory of Rich Media Analysis Service.
2. Enter the following command:
bin/installRichMediaAnalysis.sh
3. Do the following:
a. In a text editor, open the <Installation Directory>/logs/

installation/
Rich_Media_Analysis_Install_<date_and_timestamp>.log installation
log file.
b. Navigate to the "Installing service..." entry.
c. If the entry is followed by "cp: cannot create regular file ‘/etc/
systemd/system/richmediaanalysis.service’: Permission
denied." , the current user does not have sufficient permissions to create
the service file.
4. To resolve this, enter the following command during the install to run it with
elevated permissions:
sudo bin/installRichMediaAnalysis.sh
5. After installing, verify that the service was installed successfully by doing the
following:
a. In a text editor, open the installation log file.

b. Navigate to the "Installing service..." entry.
c. If the entry is followed by "Enabling service..." , the service file was
installed successfully.

8.6.2 The mediaanalysis.log file does not show up after

starting the service on a Linux install
This issue might be caused due to one of the following:
• A user who does not have sufficient permissions to create the LOG file is running
the service.
• The version of Java that is being used to run Rich Media Analysis Service.
Note: You must install JRE 1.8 prior to installing Rich Media Analysis
Service. For more information, see “Prerequisites” on page 83.
8.6.2.1 To diagnose the issue

To determine if the user who is running Rich Media Analysis Server has
sufficient permissions:
1. On a terminal, run the following command:

cat /etc/systemd/system/richmediaanalysis.service
2. In the output, locate the User= entry to identify the name of the user who is
running the service.
3. Navigate to the Rich Media Analysis Service installation directory and verify
the permissions on the directories by entering the following command:
ls -laR .
Note: If the user who is running the service does not match the user name
that is listed for each of the files and directories, change the permissions to
allow the user who is running the service to be able to edit the files in the
Rich Media Analysis Service installation directory.
To determine if you are running the prerequisite version of Java:
1. To review the log files, run the following command:

sudo journalctl -u richmediaanalysis.service
2. If the log files contain entries that are similar to the following, you are running
an incorrect version of Java:
Starting OpenText Rich Media Analysis Service...
Started OpenText Rich Media Analysis Service.
Exception in thread "main"

java.lang.UnsupportedClassVersionError: com/opentext/
mediaanalysis/MediaAnalysisApplication : Unsupported major.minor
version 52.0

richmediaanalysis.service: main process exited, code=exited,

status=1/FAILURE
Unit richmediaanalysis.service entered failed state.
Stopped OpenText Rich Media Analysis Service.
Starting OpenText Rich Media Analysis Service...

Started OpenText Rich Media Analysis Service.
Exception in thread "main" java.lang.UnsupportedClassVersionError:
com/opentext/mediaanalysis/MediaAnalysisApplication : Unsupported
major.minor version 52.0
:
:
richmediaanalysis.service: main process exited, code=exited,
status=1/FAILURE
Unit richmediaanalysis.service entered failed state.
Stopped OpenText Rich Media Analysis Service.
3. Do the following to confirm the version of Java.
a. Run the following command:

/usr/bin/java -version
b. Read the version of Java that is displayed. If it is not Java 1.8.0_XX, then
the version of Java is not correct.
8.6.2.2 To resolve this issue if it is due to permissions

To resolve this issue if it is due to permissions:
1. Navigate to the Rich Media Analysis Service installation directory and stop the
service by entering the following command:
bin/stopRichMediaAnalysis.sh
2. Enter the following command to change the ownership of all the files and
directories to belong to the user in the service file:
sudo chown -R <user who is running the service>:<group to which user
belongs> .
For example, if the beginning of the output of the richmediaanalysis.
service files contains the following user:
[Unit]
Description=OpenText Rich Media Analysis Service
After=syslog.target

[Service]
User=rmaservice
where
the group for rmaservice is servicegroup
Then the command should be as follows:
sudo chown -R rmaservice:servicegroup .
3. Start the service by entering the following command:

bin/startRichmediaAnalysis.sh
4. Verify that the mediaanalysis.log is in the /logs directory.
8.6.2.3 To resolve this issue if it is due to version of Java

You can resolve this issue using one of the following methods:
1. Change the /usr/bin/java symbolic link. If you use this method, all
applications on the system that use Java, will use version of Java 1.8.0_XX.
2. Change the Rich Media Analysis Service file. If you use this method, only Rich
Media Analysis Service is affected. Other applications that use /usr/bin/java
will continue using a different version of Java.
To resolve this issue by changing the /usr/bin/java symbolic link:
1. Change the /usr/bin/java symbolic link to point to the proper version of Java
1.8.0_XX in the system.
Note: This will affect any application that uses /usr/bin/java to run Java
applications, not just Rich Media Analysis Service.
2. Stop the RMA service by running the following command:

<RMA Installation Dir>/bin/stopRichMediaAnalysis.sh
3. Run the following command:

sudo alternatives --config java
4. Verify that the output of the command prints a list of the available Java
installations in the system. An example of the output is as follows:
Selection Command
-----------------------------------------------
*+ 1 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.51-2.4.5.5.el7.x86_64/
jre/bin/java
2 /usr/java/jdk1.8.0_65/jre/bin/java

3 /usr/java/jre1.8.0_65/bin/java
Enter to keep the current selection[+], or type selection number:
5. Chose the number of the installation that you want to use. You must use a java
1.8.0_XX version.
6. Start the service by running the following command:

To resolve this issue by changing the Rich Media Analysis Service file:
1. Modify the Rich Media Analysis Service file to use a specific version of Java
1.8.0_XX in the system.
Note: This method affects Rich Media Analysis Service only. Other
applications that may be using /usr/bin/java will continue using a
different version of Java.
2. Stop the service by running the following command:

<Installation Dir>/bin/stopRichMediaAnalysis.sh
3. Edit the /etc/systemd/system/richmediaanalysis.service script by

replacing the ExecStart=/usr/bin/java command with the path of Java 1.8.
0_XX in the system. For example, if the path is /usr/java /jdk1.8.0_65,
replace the command with the following:
ExecStart=/usr/java/jdk1.8.0_65/bin/java
4. Run the following command:

sudo systemctl daemon-reload
5. Start the service by running the following command:

8.6.3 HTTP 403 status code when trying to call the service
This issue is commonly associated with the IP Address of the caller of the service. By
default, Rich Media Analysis Service only allows 127.0.0.1 to make calls to the
service. If another server attempts to make a call, the call will be denied.
• Add the IP Address of the calling server, OTMM, in the mediaanalysis.

clientiplist property located in the <Installation Directory>\conf\
application.properties file.
Tip: Separate multiple IP addresses with a comma (,).
If the error persists after the configuration

It is possible that the property was not configured correctly, or there are typos in the
property file which have caused the system to use the default values.
1. In the service log file located in the <Installation Directory>\logs

directory, verify that the property that you configured is being picked up
properly by the system. In the case of client IP addresses, the logs will look
similar to the following:
[INFO ] YYYY-MM-DD hh:mm:ss.ms [main] MediaAnalysisApplication -
SecurityConfig:
[INFO ] YYYY-MM-DD hh:mm:ss.ms [main] MediaAnalysisApplication -

clientip = 127.0.0.1
2. Verify that there are no typos in the property.
8.6.4 Error:
org.springframework.amqp.AmqpConnectException:
java.net.ConnectException: Connection refused:
connect
If the log file shows the following
org.springframework.amqp.AmqpConnectException: java.net.ConnectException:
Connection refused: connect message, verify that you configured Rich Media
Analysis Service with the proper credentials to log in to RabbitMQ. If required,
modify the proper login credentials accordingly.
8.6.5 Determining the IP address of the clients that are

submitting requests to access Rich Media Analysis
Service
Using the Tomcat access log, you can determine the IP address of the clients that are
submitting requests to access Rich Media Analysis Service.
By default, the Tomcat access log is disabled. To enable it, you must perform post
installation configurations in the application.properties file.
To enable access logs to determine the IP address of clients:
1. In a text editor, open the application.properties file which is located in the

conf directory.
2. Specify the subdirectory for the Tomcat access log files by adding the following
property and pointing it to the logs directory Rich Media Analysis Service
installation directory.

Example 8-1: Linux

server.tomcat.accesslog.directory=<Richmedia Installation
Directory>/logs
3. Enable access logging by adding the following property:

server.tomcat.accesslog.enabled=true
4. Specify the following pattern that will be used in the logs:

server.tomcat.accesslog.pattern=common
5. Restart the server.
6. Verify that an access log with the name access_log.<yyyy-mm-dd>.log is

created in the logs directory and that it contains the requests that are being
processed by the system.
8.6.6 Error when trying to uninstall the service on Windows

A LaunchAnywhere Error window opens with the Windows error 2 occurred while
loading the Java VM message when you were uninstalling the service on Windows.
This issue might be related to the usage of an incorrect Java VM by the installer.
1. Verify that the JAVA_HOME environment variable is configured and the value set
to Java 8.
2. Verify that the java.exe is set in the PATH.
3. If the issue persists, try one of the following solutions:
• If C:\ProgramData\Oracle\Java\javapath is in the PATH environment

variable, remove it.
• Use the LAX_VM parameter when you are launching the installer silently by
• Run the Command Prompt as administrator.

• Navigate to the unistall directory. For example C:\RichMediaAnalysis\
uninstall.
• Enter the following command:

Uninstaller.exe LAX_VM <Path to the java.exe in your system>
where
For example: Uninstaller.exe LAX_VM C:\Program Files\Java\
jre1.8.0_144\bin\java.exe

Note: This silently uninstalls the service and might restart your system after it
has completed.

Chapter 9
Installing OpenText Media Management Adaptive
Media Delivery
External applications use Adaptive Media Delivery to deliver assets in multiple

formats.
External applications use URLs generated by OTMM to deliver assets and/or

renditions in a responsive manner, based on the requesting device and additional
asset parameters (for example, aspect ratio, size). This enables approved media
assets to be delivered to multiple channels (such as PIM and multiple websites), and
responsive design allows the assets to be displayed properly on the user's device.
Using the Adaptive Media Delivery Administration page, you register an external
application to the Adaptive Media Delivery service to consume the asset renditions.
When an external application requests a rendition, the delivery server checks if the
rendition is available in the repository. If the rendition is not available, it will check
if the original file is available. If original file is available, it will generate the
rendition, store it in the repository. If original file is not available, it will stage the
original file from OTMM, and register the asset identifier with OTMM, so that
OTMM can send notification of any future changes to the asset.
If a registered asset or a particular version is purged from OTMM, it will notify all
delivery servers, and the asset/rendition or the purged version (and its renditions) in
the Adaptive Media Delivery server repository will be deleted.
The rendition requests are audited by posting the request details to the Data
Collector service.
Note: You can integrate Adaptive Media Delivery with Data Collector to help
track the asset and rendition usage on external applications.
9.1 Preparing to install

This section discusses the software that you need to install Adaptive Media
Delivery.

Chapter 9 Installing OpenText Media Management Adaptive Media Delivery
9.1.1 System requirements

Operating system
• Windows Server
• RedHat Enterprise Linux
• CentOS
Database
• Oracle
• SQL Server
• PostgreSQL
• SAP HANA
9.1.2 Software prerequisites

• ImageMagick® (Linux only)
• OTMM
• Data Collector
Note: You can optionally install Data Collector for the Analytics features.
Prior to installing Adaptive Media Delivery, do the following:
1. Create a database user.

2. Create an OTMM user account.
9.1.3 Creating the database user

The Adaptive Media Delivery installation requires a pre-created database user. You
can create a user or use an existing one. This user must have permissions to create
tables, triggers and views. Ensure that you are able to sign in using this database
user.
Notes
• If you have Data Collector, Adaptive Media Delivery will store minimal data
in the database.
• Database objects are created in the default schema that is configured for the
user.
• If you are using Oracle 12C, in addition to permissions mentioned above the
database user must have permission to use tablespace quota on default
tablespace and create sequence.

9.2. Installing Adaptive Media Delivery
To create a database user in SQL Server:
1. Sign in to SQL Server as Administrator and create a database with a

SQL_Latin1_General_CP1_CI_AS collation. For example, <DATABASE_NAME>.
2. Create a user by selecting the default database, such as <DATABASE_NAME>.
3. Navigate to the User Mapping tab and select <DATABASE_NAME>.
4. Navigate to the Security tab of <DATABASE_NAME> and create a schema.
5. Click the user properties, navigate to the Owned Schemas tab, and select the
schema that you created.
6. Click the database properties and provide the permissions for create table, view,
and triggers.
9.1.4 Creating an OTMM user account

You must install OTMM prior to installing Adaptive Media Delivery. Create an
OTMM user account that Adaptive Media Delivery will use. This user must have
view and export permissions on all assets that are rendered using Adaptive Media
Delivery.
9.1.5 Installing Data Collector

If you plan to use Data Collector to capture the usage details of the rendition
requests, you need to install Data Collector prior to installing Adaptive Media
Delivery. For more information, see OpenText Experience Analytics Data Collector -
Installation and Configuration Guide (CRA160201-IGD).
Note: Installing Data Collector is optional.
9.2 Installing Adaptive Media Delivery

You can install Adaptive Media Delivery any of the following methods:
Note: To pre-populate the installation screens with default responses, you

can specify values of the installation parameters in the
adaptivemedia_config.txt configuration file. You can edit these values
during the install.
For more information, see “Installing Adaptive Media Delivery using the setup
screens” on page 104.

• Console
adaptivemedia_config.txt. You cannot change these values during the
subsequent steps.
installation parameters in the adaptivemedia_config.txt file. This file is
mandatory if you are installing using console mode.
For more information, see “Installing Adaptive Media Delivery using the
console” on page 107.
• Slient
adaptivemedia_config.txt. You cannot modify values during the installation
process. This mode requires no user interaction.
installation parameters in the adaptivemedia_config.txt configuration
file. The configuration file is mandatory if you are installing using silent
mode.
For more information, see “Installing Adaptive Media Delivery silently”

on page 108.
Notes
• The Adaptive Media Delivery installer is available through the Media
Management ISO. The adaptivemedia_config.txt configuration file is
available in the ISO in the following location:
<Mediamanagement ISO>/AMD/adaptivemedia_config.txt
• To add new tenant, use the Adaptive Media Delivery installer to install a
new installation on a different node.
9.2.1 Installing Adaptive Media Delivery using the setup

screens
This section provides information about how to install Adaptive Media Delivery
using the setup screens (GUI mode).

9.2.1.1 To install Adaptive Media Delivery using the setup screens
Note: To use GUI mode on Linux, you need an X-Windows interface. You will
need to set DISPLAY in your environment and have an X-Windows server
running on your local computer. For example, if you have connected to the
Linux server from your Windows computer, you will need to have software
such as OpenText™ Exceed™ TurboX (ETX) installed and running. Be sure to
set your DISPLAY in your Linux environment prior to running the installation.
For example:
where 10.1.2.3 is the IP address of your local computer.
To install Adaptive Media Delivery using the setup screens:
1. Mount the appropriate platform-specific Media Management ISO.
WINDOWS
mediamgmt_16.3_windows.iso
LINUX
mediamgmt_16.3_linux.iso
2. Optional Extract the adaptivemedia_config.txt from the ISO to a location.

Provide the installation parameters required for your installation.
3. At a command prompt, navigate to the AMD directory that is available in the

mounted location, and then enter one of the following commands:
WINDOWS
<Mounted location>\AMD\Disk1\InstData\VM\install.exe -i gui -f
<PATH_TO_adaptivemedia_config.txt>
LINUX
<Mounted location>/AMD/Disk1/InstData/VM/install.bin -i gui -f
<PATH_TO_adaptivemedia_config.txt>
where
-i specifies the mode of installation to be launched. The default mode is GUI, if
no mode is passed. GUI mode launches the setup screens.
-f specifies the configuration file that is used to provide pre-populated values
installation mode.
qualified path name for the configuration file. For example:

G:\AMD\Disk1\InstData\VM\install.exe -i gui -f c:
\adaptivemedia_config.txt
4. On the License Agreement page, if you agree to the terms, click I accept the
5. On the Choose Product Features page, select the Schema and Application
check boxes to install the Adaptive Media Delivery schema and application.
Note: For High Availability (HA) environments - If you are installing on

a secondary node, select Application only.
6. On the Select Install Folder page, enter where you want to install Adaptive
Media Delivery. This will be referred to as ADAPTIVE_MEDIA_HOME.
Note: Do not use spaces in the installation directory.
7. On the Enter DB Details page, enter the database configuration, and click Next.
8. On the Configure OpenText Experience Analytics page, click Yes if you

installed Data Collector.
a. If you clicked Yes, enter the HostName and Port where Data Collector is
running. The default value of the port is 9580.
b. If you clicked No, the Configure Embedded Audit page will be displayed.
9. On the Configure Embedded Audit page, click Use Default to use the default
ports to run Apache Kafka, 2181 and 9092.
Note: If you choose Configure, enter the ports to run Apache Kafka and
Apache Zookeeper.
10. On the Adaptive Media Configuration page enter the following configuration
information:
a. Http Port - This is the port where the Adaptive Media Delivery server will
listen.
b. Rendition Repository Location - This is the location where generated
renditions of assets will be stored.
Note: In an HA environment, if all of the Adaptive Media Delivery

nodes have their own repositories, you must specify the Rendition
Repository Location on each node.
c. Adaptive Media Username - Enter the name of the user who you want to
use to sign in to the Adaptive Media Delivery Server Administration page.
Note: This document refers to this user as the Adaptive Media Delivery
administrator.
d. Adaptive Media Admin Password - Enter the password you want the
Adaptive Media Delivery administrator to use to sign in to the Adaptive

Media Delivery Server Administration page. The user name and password
provided will be stored in the Adaptive Media Delivery database.
e. OTMM Host Name - Enter the host name where the OTMM server is
running.
f. OTMM User Name - Enter the OTMM user name to connect to the OTMM
server fromAdaptive Media Delivery.
g. OTMM Password - Enter the password for the OTMM user.
11. On the Pre-Installation Summary page, review the installation details, and click
Install.
9.2.2 Installing Adaptive Media Delivery using the console

using the console.
installation parameters in the adaptivemedia_config.txt configuration file.
9.2.2.1 To install Adaptive Media Delivery using the console

To install Adaptive Media Delivery using the console:
WINDOWS
LINUX
2. Extract the adaptivemedia_config.txt from the ISO to a location. Provide the

installation parameters required for your installation.
3. At a command prompt, navigate to the Adaptive Media Delivery directory,

\AMD, that is available in the mounted location, and then enter one of the
following commands:
WINDOWS
<Mounted location>\AMD\Disk1\InstData\VM\install.exe -i console
-f <PATH_TO_adaptivemedia_config.txt>
LINUX
<Mounted location>/AMD/Disk1/InstData/VM/install.bin -i console
where
-i specifies the mode of installation to be launched.


during the install procedure. The configuration file is mandatory in this
installation mode.
file. For example:
G:\AMD\Disk1\InstData\VM\install.exe -i console -f c:
9.2.3 Installing Adaptive Media Delivery silently

silently.
Prior to launching the installer, you must specify the values of the installation
parameters in the adaptivemedia_config.txt.
9.2.3.1 To install Adaptive Media Delivery silently
To install Adaptive Media Delivery silently:
WINDOWS
LINUX
2. Extract the adaptivemedia_config.txt from the ISO to a location. Provide the

3. At a command prompt, navigate to the Adaptive Media Delivery directory,

\AMD, that is available in the mounted location, and then enter one of the
following commands:
WINDOWS
<Mounted location>\AMD\Disk1\InstData\VM\install.exe -i silent
LINUX
<Mounted location>/AMD/Disk1/InstData/VM/install.bin -i silent
where


installation mode.
file. For example:
G:\AMD\Disk1\InstData\VM\install.exe -i silent -f c:
9.2.4 Performing post-installation tasks

9.2.4.1 Installing ImageMagick
For Windows, ImageMagick is installed as part of the Adaptive Media Delivery
installation. For Linux, you need to install it manually. The steps are similar to
installing ImageMagick on OTMM server. You can get the RPMs required for
installation from the <ADAPTIVE_MEDIA_HOME>/install/ImageMagick folder. For
more information, see “Installing ImageMagick on Linux” on page 62.
Note: If you installed Adaptive Media Delivery on the OTMM server, rename
Windows only the ffmpeg.exe file under <ADAPTIVE_MEDIA_HOME>/ImageMagick to
_ffmpeg.exe.
9.2.4.2 Configuring notification settings

You must configure the following entries in the system configuration settings to
notify the Adaptive Media Delivery user of asset level changes in OTMM to
Adaptive Media Delivery.
To configure notification settings:
1. Sign in to the OpenText Media Management Web Administration tool.
2. On the top-level menu, click Settings, and search for

ADAPTIVE_MEDIA_ENABLED.
3. Navigate to the row, and click the Edit link to edit the property.
4. Set the ADAPTIVE_MEDIA_ENABLED property to Y.
5. On the OTMM server, at the command prompt, change to the <TEAMS_HOME>/

install/ant directory, and run the following command:
ant configure-adaptive-media
The Ant command prompts you for the following inputs:

a. Adaptive Media Identifier - OTMM includes a pre-configured delivery

server configured with the identifier OTMM.NOTIFIER.ADAPTIVE.
MEDIA.DELIVERY. This will be shown as the default value. If your
configuration has more than one delivery server with their own rendition
repository, you can enter the identifier configured in the amd.
delivery.server.id property in amd.properties file of the Adaptive
Media Delivery server.
Notes
• While performing the configuration, you need to specify the amd.
delivery.server.id that is provided above, while running the
target Ant configure-adaptive-media command in the following
instances:
• If all the Adaptive Media Delivery nodes are using shared
repository, run this target only once and point to any of the
Adaptive Media Delivery node URLs or Proxy URLs.
• If the Adaptive Media Delivery nodes are using individual
repositories, run this target for each node and point to each of the
Adaptive Media Delivery server IDs and Adaptive Media
Delivery URLs.
b. Adaptive Media Delivery URL - Enter the URL for Adaptive Media
Delivery server using the format:
http(s)://<hostname>:<port>
c. User name for Adaptive Media - Enter the user name that you want to use
to connect to the Adaptive Media Delivery server. This is the same user
name that you entered during the installation.
d. Password for Adaptive Media User - Enter the password of the user
mentioned in the above. This is the same user password you have entered
during the installation.
6. Restart OTMM.
Tip: If Adaptive Media Delivery needs to be updated, you can use the
same Ant target to re-configure the connection details.
9.2.4.3 Configuring the amd.properties file

To configure the amd.properties file:
• In a text editor, open the <ADAPTIVE_MEDIA_HOME>/data/config/amd.

properties file and update the following entries based on the appropriate
application server:
JBOSS
otmm.provider_host=remote://ip address or host name of the OTMM
server:11099

9.3. Starting and stopping the Adaptive Media Delivery server
otmm.initial_context_factory=org.jboss.naming.remote.client.
InitialContextFactory
otmm.factory_url_packages=org.jboss.naming
TOMEE
otmm.provider_host=ejbd://ip address or host name of the OTMM
server:11099
otmm.initial_context_factory= org.apache.openejb.client.
RemoteInitialContextFactory
9.2.4.4 Configuring application server libraries
To configure application server libraries:
1. If the application server that you are using for OTMM is JBoss EAP 6.4 or
Wildfly-9.0.2.Final, copy the following JAR files from the <JBOSS_HOME>\bin\
client folder to the <ADAPTIVE_MEDIA_HOME>\lib folder.
• jboss-cli-client.jar
• jboss-client.jar
2. If the application server that you are using used for OTMM is TomEE, copy the
following JAR from the <TOMEE_HOME>\lib folder to <ADAPTIVE_MEDIA_HOME>
\lib folder:
javaee-api-7.0-1.jar
Note: Perform this step only if Adaptive Media Delivery uses the SDK
implementation.
9.3 Starting and stopping the Adaptive Media

Delivery server
To start and stop the Adaptive Media Delivery server on Windows:
1. Start the OpenTextAdaptiveMediaDelivery under Services.
2. Stop the OpenTextAdaptiveMediaDelivery under Services.
To start and stop the Adaptive Media Delivery server on Linux:
1. To start the server, enter the following at the command prompt :

adaptivemediaservice start
2. To stop the server, enter the following command at the command prompt:
adaptivemediaservice stop

9.4 Upgrading Adaptive Media Delivery

This section describes the steps that you perform during the Adaptive Media
Delivery upgrade.
The upgrade program is delivered on the Media Management ISO and guides you
through the upgrade of the schema and application.
Important
This section is not applicable to SAP® HANA.
9.4.1 Before you upgrade

Prior to upgrading, you must perform backup procedures.
9.4.1.1 To back up Adaptive Media Delivery
To back up Adaptive Media Delivery:
1. Shut down Adaptive Media Delivery by doing one of the following:
Windows
Stop the OpenTextAdaptiveMediaService.
Linux
Run the following command:
adaptivemediaservice stop
2. Back up Adaptive Media Delivery as follows:
Note: Adaptive Media Delivery provides an in-place upgrade, these

components are modified during the upgrade.
• <ADAPTIVE_MEDIA_HOME>
• Your database.
• Any customizations and configurations that you deployed in Adaptive

Media Delivery.
3. Linux - Uninstall the previous version of ImageMagick. For example, 6.8.0-5 or

6.9.2-7.
Note: Windows - The updated version of ImageMagick is installed

automatically during the upgrade installation. For more information about
versions, see OpenText Media Management Technical Specifications (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/69371555).

9.4. Upgrading Adaptive Media Delivery
9.4.2 To upgrade Adaptive Media Delivery using the setup

screens
To upgrade Adaptive Media Delivery using the setup screens:
1. Mount the appropriate platform-specific Media Management ISO in the system

where Adaptive Media Delivery is installed.
WINDOWS
LINUX
Note: You must mount the Linux OTMM ISO as the Linux root user.
2. Verify that the Adaptive Media Delivery server is not running.
3. At a command prompt or on a terminal, start the Adaptive Media Delivery

installer by entering one of the following command:
WINDOWS
<ISOPATH>/AMD\Disk1\InstData\VM\install.exe
LINUX
<ISOPATH>/AMD/Disk1/InstData/VM/install.bin
4. On the License Agreement page, click I accept the terms of the License
Agreement > Agree.
5. On the Select Execution Type page, click Upgrade > Next.
6. On the Choose Product Features page, for a typical upgrade, select the
Database Schema and Application check boxes to upgrade the database
schema and application, thus providing the minimal software to start Adaptive
Media Delivery.
Note: In an HA (Cluster) environment, select the Database Schema and

Application check boxes for the first node that you upgrade. To upgrade
subsequent nodes, select the Application check box only.
7. On the Pre-Installation Summary page, verify your selections, and click Install
to begin the upgrade process.
Notes
• If any errors occur during the upgrade, see “Troubleshooting the upgrade”
on page 116.

• After a successful upgrade, the Complete page appears. You must restart the
system.
9.4.3 To upgrade Adaptive Media Delivery using the console

You can upgrade Adaptive Media Delivery using the console on Windows and
Linux platforms. All messages are displayed as text in the console window.
Note: You must use the <ISOPATH>/AMD/adaptivemedia_config.txt file to

upgrade Adaptive Media Delivery using the console.
To upgrade Adaptive Media Delivery using the console:
1. Copy the adaptivemedia_config.txt file to a local folder and edit the file to
match the 16.3 installation values.
Tip: You can find the current values in the following file
<ADAPTIVE_MEDIA_HOME>/install/ant/build.cfg
WINDOWS
LINUX

WINDOWS
<ISOPATH>/AMD\Disk1\InstData\VM\install.exe -i console -f
<FULL_PATH_TO>/adaptivemedia_config.txt
LINUX
<ISOPATH>/AMD/Disk1/InstData/VM/install.bin -i console -f
4. Follow the prompts to complete the upgrade.
Notes
on page 116.
system.

9.4.4 To upgrade Adaptive Media Delivery silently

You can upgrade Adaptive Media Delivery silently on Windows and Linux
platforms. All messages are displayed as text in the console window.
Note: You must use the <ISOPATH>/AMD/adaptivemedia_config.txt file to

upgrade Adaptive Media Delivery silently.
To upgrade Adaptive Media Delivery silently:
1. Copy the adaptivemedia_config.txt file to a local folder and edit the file to
Tip: You can find the current values in the following file:
<ADAPTIVE_MEDIA_HOME>/install/ant/build.cfg
WINDOWS
LINUX

WINDOWS
<ISOPATH>/AMD\Disk1\InstData\VM\install.exe -i silent -f
LINUX
<ISOPATH>/AMD/Disk1/InstData/VM/install.bin -i silent -f
Notes
on page 116.
system.

9.4.5 Troubleshooting the upgrade

This section outlines the steps to take if your upgrade fails. After the upgrade fails,
you must undo all the upgrade changes prior to running the upgrade process again.
During the upgrade, the schema is validated to find any schema conflicts between
the two instances. If conflicts are found during the schema validation, the upgrade
process will report an error and stop. There are other reasons that the upgrade
process may fail.
9.4.5.1 To continue after an upgrade error

To continue after an upgrade error:
1. Determine the upgrade error. If any errors occur during the upgrade, review the
following files to determine the reason for the failure:
• <ADAPTIVE_MEDIA_HOME>/logs/install/upgradeValidation.log
• <ADAPTIVE_MEDIA_HOME>/Adaptive_Media_Delivery_Install_*.log
• <ADAPTIVE_MEDIA_HOME>/logs/install/upgradeValidator.log
• <ADAPTIVE_MEDIA_HOME>/logs/install/upgrade-amd.log
2. If any errors occur while upgrading the schema, refer to the

<ADAPTIVE_MEDIA_HOME>/logs/install/upgrade-amd.log file for a list of
issues.
3. Run the following SQL script to revert any changes that you performed during
the upgrade on the Adaptive Media Delivery database:
<ADAPTIVE_MEDIA_HOME>/data/upgrade/drop_sql.sql
Note: While running the <ADAPTIVE_MEDIA_HOME>/data/upgrade/

drop_sql.sql file, ignore any errors indicating that objects, such as a
table, trigger, or index do not exist in the database or schema.
4. Resolve the upgrade issues identified prior to rerunning the upgrade.
9.4.6 Performing post upgrade tasks

This section provides information about tasks that you perform after upgrading.

9.4.6.1 Upgrading ImageMagick

For Windows, the latest version of ImageMagick is installed as part of the Adaptive
Media Delivery upgrade. For Linux, you need to upgrade ImageMagick manually.
You can obtain the RPM for installation from the OTMM server. For more
information about versions, see OpenText Media Management Technical Specifications
9.4.6.2 Verifying and configuring the communication type

For upgrade installations, Adaptive Media Delivery uses the OTMM SDK or REST-
based communication to communicate with OTMM.
9.4.6.2.1 To verify the communication type is REST-based or OTMM SDK
To verify the communication type is REST-based or OTMM SDK:
1. In a text editor, open the <ADAPTIVE_MEDIA_HOME>/data/config/

DeliveryServiceConfiguration.xml and locate the following:
<Service name="DefaultContentService" type="com.
opentext.adaptivemedia.interfaces.ContentService">
2. Verify the communication type:
• For REST-based communication, the entry appears as follows:

<ServiceImpl className="com.opentext.adaptivemedia.
services.impl.DefaultRESTContentServiceImpl" seqNum="0"/>
Note: To work with multiple tenants, use only REST-based

communication. To change the communication type to REST-based,
you must update the DefaultContentService ServiceImpl class
name to DefaultRESTContentServiceImpl in the
DeliveryServiceConfiguration.xml file.
• For SDK based communication the entry appears as follows:

<ServiceImpl className="com.opentext.adaptivemedia.
services.impl.DefaultContentServiceImpl" seqNum="0"/>
3. If Adaptive Media Delivery is using OTMM SDK, update the

APPLICATION_SERVER type in the <ADAPTIVE_MEDIA_HOME>/deploy/
resources/appedition.properties file.
4. Restart the Adaptive Media Delivery service.

9.5 Performing additional advanced configurations

for Adaptive Media Delivery
The following are configuration files that you might need update after installing
Adaptive Media Delivery to perform advanced configurations. These files are
located in <ADAPTIVE_MEDIA_HOME>/data/config:
• amd.properties
• ImageProfiles.xml
• ProfileCollections.xml
• DeliveryServiceConfiguration.xml
• credential_SEC.cfg and db_SEC-cfg
9.5.1 Configuring ImageProfiles.xml

The ImageProfiles.xml file stores the image profiles that are run to generate
renditions. The profile that runs is determined based on the input parameter prid to
adaptivemedia. If no prid is passed, the default profile is used.
You can configure image attributes in the ImageProfiles.xml file. The

ImageProfiles.xml contains a list of profiles.
Each profiles contains one or more image option. Individual image options can have
a command with dynamic values that use the format $IMAGE_OPTIONVALUE. For
example, the ImageMagick command to resize image is -resize widthxheight.
To generate an image with a dynamic height and width, create an image option
element with the value -resize ${wd}x${ht}. To generate images of varying height
and width pass the query parameter wd=<width> and ht=<height> in the rendition
URL.
If none of the dynamic attributes in the image options are specified in the request
query parameter, the image option will not be added to the rendition generation
command.
The file contains a list of image profiles with one default profile with name DEFAULT.
You can choose the profile you want by passing the "prid=<profile_name>"
request parameter. In this case, Adaptive Media Delivery chooses the image options
given in the profile and generates a rendition.
The output format of ImageMagick depends on the extension of the output file. To
generate different image formats, pass the "op=<extension>" request parameter.
For example, use "op=png" to generate a PNG file.
Note: Some image attributes with special characters needs to be enclosed in

double quotes for the Windows server and single quotes for the Linux server.
For example, while specifying image geometry, special characters such as >,

9.5. Performing additional advanced configurations for Adaptive Media Delivery
<, ! and ^ can be used. In such cases, you must enclose the parameters in
double/single quotes. For example, -resize "100x100>".
9.5.2 Configuring ProfileCollections.xml

The ProfileCollections.xml file stores image profiles as a collection. This file
contains a list of profile collections. If you need to generate a set of renditions
upfront, you can pass the request "prclid=<PROFILE_COLLECTION_ID>" query
parameter. If the prclid parameter is passed along with the profile ID parameter,
prid, then the Profile rendition response will have rendered.
9.5.3 Configuring amd.properties

This properties file configures various settings for Adaptive Media Delivery. The
following are configured in the amd.properties file:
Note: While updating the amd.properties file, set amd.delivery.server.id

to a unique value for each of the Adaptive Media Delivery server nodes.
9.5.3.1 Database
Use the parameters in this section to configure the database.
db.jdbc.url Stores the JDBC URL of the database to

connect to this database.
db.jdbc.driver Stores the JDBC driver to use this database.
9.5.3.2 DataCollector
Update this section only if you are using Data Collector with Adaptive Media
Delivery.
dc.application.type The application type. By default, this is

Media Management. This property is used
by the analytics services to categorize the
events.
dc.application.type The name of the host where Media
Management is running. This property is
used by analytics services.
dc.application.type This is the name of the host where the
OpenText Data Collector service is running.
The value should use the following format:
<hostname>:<port>

9.5.3.3 HTTP Response Headers

Use the parameters in this section to configure the response headers that are added
to the generated renditions.
headers.Cache This controls the cache settings for the

rendition images.
headers.Expires The cache expiry date for the rendition
images.
9.5.3.4 OTMM Properties

Use the following properties to connect the Adaptive Media Delivery server to
Media Management.
otmm.provider_host The JNDI provider host name which looks

up OTMM services.
otmm.initial_context_factory, These properties are used to configure the
otmm.factory_url_packages, naming context.
otmm.use_remote_interfaces,
otmm.use_internal_context_factory_builder
otmm.restservices.url This property is used when staging the assets
from OTMM should use REST API calls. The
URL should be: http://otmmhost:
11090/otmmapi/v3
9.5.3.5 Zookeeper Properties

Use the Zookeeper properties only when you are using the Embedded Audit
feature.
tpccnsmr.zookeeper.connect The hostname:port where Zookeeper is

running, Zookeeper running in embedded
audit will always listen to localhost:
2181. If you intend to use a different
instance of Zookeeper, configure it here.
tpccnsmr.group.id The consumer group name to consume
messages from Kafka topic.
tpccnsmr.zookeeper.session.timeout.ms The session time out for the Zookeeper
instance.
tpccnsmr.zookeeper.sync.time.ms The synchronize interval for the Zookeeper
instance.
tpccnsmr.auto.commit.interval.ms The auto commit interval for the Zookeeper
instance.
tpccnsmr.consumer.timeout.ms The consumer connection timeout.

9.6. Integrating Adaptive Media Delivery with Content Delivery Network
9.5.3.6 Adaptive Media

If you want to use more than one node of the Adaptive Media Delivery server with
their own rendition repository, then set amd.delivery.server.id to a unique value
on each of the Adaptive Media Delivery server nodes. Use this node ID to register
with the OTMM. For more information, see Step 5 in “Configuring notification
settings” on page 109. OTMM registers nodes with these ID and uses it to track the
assets consumed by the nodes. Based on this, OTMM will notify registered Adaptive
Media Delivery nodes of any changes to the assets.
9.5.4 Configuring credential _SEC.cfg and db_SEC.cfg

The credential_SEC.cfg and db_SEC.cfg are security files. They store encrypted
user name and password for OTMM and the database respectively. If you need to
change the user name and password details, you must decrypt the files first, make
modifications, and then encrypt the files again.
To configure credential _SEC.cfg and db_SEC.cfg:
1. To decrypt the database credentials, run the following Ant target:

ant amd-decrypt-db-login
2. To encrypt the database credentials, run the following Ant target:

ant amd-encrypt-db-login
3. To decrypt the OTMM credentials, run the following Ant target:

ant amd-decrypt-otmm-login
4. To encrypt the OTMM credentials, run the following Ant target:

ant amd-encrypt-otmm-login
9.6 Integrating Adaptive Media Delivery with Content

Delivery Network
You can integrate Adaptive Media Delivery with a Content Delivery Network
(CDN), such as Amazon CloudFront, Microsoft® Azure® (Azure ), Akamai and so
on. When integrated with CDN, external applications use URLs that reference the
CDN host name.
When an external application requests a rendition, the CDN checks if the rendition is
available in the CDN cache. If the requested rendition is not available in the CDN
cache, the CDN will be configured to call Adaptive Media Delivery to retrieve the
requested rendition. The CDN will cache this rendition so that subsequent requests
can be serviced without making calls to Adaptive Media Delivery.

Notes
• If a registered asset or a particular version is purged from OTMM, Adaptive
Media Delivery will notify the integrated CDN to purge the asset or
rendition from the CDN cache.
• This integration is optional.
9.6.1 Notifying CDN to purge an asset or rendition

A standard Java interface, com.opentext.adaptivemedia.
interfaces.CDNCacheService, is defined to notify CDN to purge the asset or
rendition from the CDN cache.
Adaptive Media Delivery provides default implementation classes for the Amazon
CloudFront and Azure CDNs. To configure Adaptive Media Delivery to use the
implementation of the Amazon CloudFront or Azure CDNCache service, see the
following:
• “Configuring Adaptive Media Delivery to use the default implementation of
Amazon CloudFront CDNCache Service” on page 123
• “Configuring Adaptive Media Delivery to use the default implementation of
AzureCDNCacheService” on page 124
9.6.1.1 Writing a custom implementation class

If you are not using Amazon CloudFront or Azure as your CDN provider, you must
write a custom implementation class that will purge the asset or rendition from the
CDN cache by implementing the CDNCacheService interface and extending the
com.opentext.adaptivemedia.common.Tenant.BaseTenantService class.
9.6.1.1.1 To write a custom implementation class
To write a custom implementation class:
1. Create a class that will purge the asset or rendition from the CDN cache by
a. Implement the com.opentext.adaptivemedia.

interfaces.CDNCacheService interface.
b. Extend the com.opentext.adaptivemedia.common.Tenant.
BaseTenantService class.
Notes
• This interface has one method as follows:
Public void purgeContent (String assetId)
• The implementation class must contain constructor that takes the
com.opentext.adaptivemedia.common.Tenant class as an

9.6. Integrating Adaptive Media Delivery with Content Delivery Network
argument and the constructor must invoke the super(Tenant

tenant) method. For example:
Public implementationClassName (Tenant tenant)

{
super(tenant);
}
2. Add the class file that you created in Step 1 to the following location:
%JETTY_HOME%\adaptivemedia-base\webapps\deliveryservices.war\WEB-
INF\classes\com\opentext\adaptivemedia\services\impl\
3. Update the className attribute of the ServiceImpl node of the

CDNCacheService interface in the <ADAPTIVE_MEDIA_HOME>/data/config/
DeliveryServiceConfiguration.xml file with the implementation className
that you created in Step 1. For example:
<Service name="CDNCacheService"
type="com.opentext.adaptivemedia.interfaces.CDNCacheService">
<ServiceImpl
className="com.opentext.adaptivemedia.services.impl.CloudFrontCac
heServiceImpl" seqNum="0"/>
</Service>

implementation of Amazon CloudFront CDNCache Service
The following table lists and describes the settings used in Amazon CloudFront the
implementation class.
Cloud_front_ The alphanumeric text string that uniquely identifies the user who owns
access_key_i the AWS account.
d
Cloud_front_ The secret access key, a 40-character string, used to communicate with the
secret_acces AWS account.
s_key
Cloud_front_ The Web distribution ID.
distribution
_id

9.6.1.2.1 To configure the default Amazon CloudFront CDNCacheService
To configure the default Amazon CloudFront CDNCacheService:
1. Create the following tenant settings using the Adaptive Media Delivery Web
Administration tool:
• Cloud_front_access_key_id
• Cloud_front_secret_access_key
• Cloud_front_distribution_id
2. Update the className attribute of ServiceImpl node of the CDNCacheService

interface in the <ADAPTIVE_MEDIA_HOME>/data/config/
DeliveryServiceConfiguration.xml file. For example:
<ServiceImpl
className="com.opentext.adaptivemedia.services.impl.CloudFrontCac
heServiceImpl" seqNum="0"/>
</Service>

implementation of AzureCDNCacheService
The following lists and describes the settings used in the Azure implementation
class:
azure_client The Azure active directory application ID.

_id
azure_ad_pas The authentication key for the application ID.
sword
azure_tenant The Azure tenant ID.
_id
azure_subscr The Azure subscription ID.
iption_od
azure_resour The name of the resource group within the Azure subscription.
ce_group_nam
e
azure_profil The name of the CDN profile which is unique within the resource group.
e_name
azure_endpoi The name of the endpoint under the profile which is unique globally.
nt_name

9.6.1.3.1 To configure the default Azure CDNCacheService
To configure the default Azure CDNCacheService:
1. Create the following tenant settings using the Adaptive Media Delivery Web
Administration tool:
azure_client_id
azure_AD_password
azure_tenant_id
azure_subscription_id
azure_resource_group_name
azure_profile_name
azure_endpoint_name
2. Update the className attribute of ServiceImpl node of the CDNCacheService

interface in <ADAPTIVE_MEDIA_HOME>/data/config/
DeliveryServiceConfiguration.xml file. For example:
<ServiceImpl
className="com.opentext.adaptivemedia.services.impl.AzureCDNCache
ServiceImpl" seqNum="0"/>
</Service>
9.7 Troubleshooting
The following are tips to troubleshoot issues that you might encounter:
9.7.1 Troubleshooting installation issues

• If there are any errors during installation, check the <ADAPTIVE_MEDIA_HOME>/
logs/install/Adaptive_Media_Delivery_Install*.log file for any
installation errors. The installer performs the following actions:
• Configures Adaptive Media Delivery.

• Installs the schema, provided you chose to the install schema option.
• Creates the administrator user for the Adaptive Media Delivery
Administration Web page.
• The install schema outputs are logged in the ddl.log file, which is located in the
<ADAPTIVE_MEDIA_HOME>/logs/install folder. Check if any errors occurred
when the database scripts ran, and resolve any errors.
• The create admin user task creates a log file, <ADAPTIVE_MEDIA_HOME>/logs/
install/createadminuser.log. Review this file to see if any errors occurred
when the admin user was created.

9.7.2 Seeing outdated content

If outdated asset content is seen in the external applications on purged or new
versions of assets, do the following:
• Verify that the Event Listeners are configured properly and that Adaptive
Media Delivery is enabled in OTMM. For more information, see “Configuring
notification settings” on page 109.
9.7.3 Not receiving notification for asset level changes

If your users are not receiving notifications for asset level changes in OTMM, do the
following:
• Verify the following settings from the Settings page in the OpenText Media
Management Web Administration tool by doing the following:
a. On the Settings page, and search for ADAPTIVE_MEDIA_ENABLED,

click the property name, and verify that the
ADAPTIVE_MEDIA_ENABLED property is set to Y.
b. On the Settings page, search for EVENT_LISTENERS, click the property

name, and verify that it includes the following value:
com.artesia.server.event.listener.EventNotificationListener
c. On the Settings page, search for EXTERNAL_NOTIFICATION_SERVICES,

verify that it includes the following value:
com.artesia.server.asset.notification.
DeliveryServiceNotification
For more information about how to change the properties of a component, see
section 2.13.2.3 “Editing a component and properties” in OpenText Media
9.8 Uninstalling Adaptive Media Delivery

To uninstall Adaptive Media Delivery:
• Launch the uninstall application, which is located in the following directory:

<Adaptive_Media_Install_location>/UninstallAdaptive Media Delivery.
WINDOWS
Double-click Uninstall Adaptive Media Delivery.exe.
LINUX
Double-click Uninstall Adaptive Media Delivery.

9.8. Uninstalling Adaptive Media Delivery
Notes
• This uninstaller deletes all the components that were installed during
the Adaptive Media Delivery installation.
• The database schema is not deleted as part of uninstallation process.

Chapter 10
Integrating Media Management and Data Collector
To integrate Media Management with Data Collector and enable Analytics, you
must configure a single sign-on (SSO) to OpenText™ Information Hub (iHub). This
section explains how to integrate iHub with OTDS to configure SSO and enable
Analytics in Media Management.
Important
• For previous versions of Media Management, it was necessary to
integrate iHub with OTDS using the OTDS Report Security Server
Extension (RSSE) service. The current version of iHub no longer requires
the RSSE service. If you are upgrading to the current version of Media
Management, you must remove the RSSE service and follow separate
instructions to upgrade iHub and integrate it with OTDS. For more
information, see “Upgrading OpenText Information Hub” on page 207.
• For more information about versions, see:
• OpenText Media Management Release Notes (https://
knowledge.opentext.com/knowledge/llisapi.dll/open/69371555)
• OpenText Media Management Technical Specifications (https://
Note: Prior to integrating, you must have Data Collector and the OpenText
Analytics products installed.
To integrate, you must do the following in sequence:
1. Integrate iHub with OTDS user management. This will provide a seamless SSO
integration with Media Management.
2. Configure a dedicated iHub user for Media Management in OTDS.
3. Grant the new user read-execute permission to the iHub dashboards and reports
that Media Management uses.
4. Configure the sign-in credentials for the new user. For more information, see
section 2.11.1 “Configuring the iHub user sign-in credentials” in OpenText Media

Chapter 10 Integrating Media Management and Data Collector
10.1 To integrate iHub for with OTDS user

management
To configure iHub for SSO:
• Follow the instructions in the “Configuring OpenText Directory Services”

section of OpenText™ Information Hub Installation, Configuration, and
Administration Guide (https://knowledge.opentext.com/knowledge/llisapi.dll/
open/68745200) to configure iHub for SSO. Ensure you do the following as you
perform the configuration:
• Note whether you configure the authentication principal attribute for the
iHub OTDS resource as oTExternalID1 or oTExternalID3.
• Remember to create an Admin group in your OTDS user partition. You will
configure this as the administrator’s group in iHub.
• Remember to assign the iHub Default Volume Organization ID as the OTDS
user partition.
Important
Use the OTDSTicket authentication mechanism for users instead of
OAuth2. The OTMM user interface only supports the OTDSTicket
integration.
10.2 To configure a dedicated iHub user for OTMM

To configure a dedicated iHub user for OTMM in OTDS:
• Create a product-specific iHub user account in an OTDS user partition, such as

mmihubuser. For more information, see OpenText Directory Services - Installation
and Administration Guide (OTDS160204-IWC) .
10.3 To grant the new user read-execute permission

to the iHub dashboards and reports
Note: Make sure that you have configured the iHub reports and dashboards in
the /Applications/OTMM16 folder before you perform this task. The reports
and dashboards are delivered with the Data Collector installer.
To grant the new user read-execute permission to the iHub dashboards and
reports in OTMM:
1. In a web browser, navigate to the OpenText Information Hub. For example:

http://<ihub_host>:8700/iportal
2. Sign in to an administrator user account.

10.4. Creating iHub credentials
3. On the left side, under Default Volume, navigate to Documents >

Applications.
4. To grant the dedicated iHub user, mmihubuser, read-execute permissions on

the /Applications/OTMM16 folder, subfolders, and contained files, do the
following:
a. In the panel on the right, navigate to the OTMM16 folder, click , then
click Share.
b. Click the Users radio button.
c. In the Available list, choose the dedicated iHub user, mmihubuser, and
then click the right arrow to move it to the Selected list.
d. Select the following check boxes:
• Visible
• Execute
• Read
• Apply these privilege settings to the contents of the folder
• Recursively include subfolders and their contents
10.4 Creating iHub credentials

You must create iHub credentials for OTMM. For more information, see section
2.11.1 “Configuring the iHub user sign-in credentials” in OpenText Media

Chapter 11
Configuring video and audio
This chapter describes the steps necessary to configure your Media Management
installation for video and audio. This includes installing and configuring the
FlipFactory or Vantage server from Telestream, or Harmonic ProMedia Carbon (also
referred to in this guide as Rhozet) server, or FFmpeg server. It also includes steps
necessary to set up the Media Streaming and download servers, such as Adobe
Media Server , IIS, Wowza Streaming Engine, or Apache. If you are not planning to
process and store audio or video content, you may skip this chapter.
Note: If you do plan to process audio or video using Rhozet Carbon Coder,
you must request the software and license from OpenText Customer Support if
you have not received it yet.
11.1 Configuring the Transcode server

Media Management supports transcoding video and audio assets by using one of
the following supported Transcode servers:
• Rhozet
• Telestream FlipFactory
• Telestream Vantage
• FFmpeg
11.1.1 Transcoding terminology

The following list describes the terminologies used with various Transcode servers:
Preset
This is specific to Rhozet. A preset saves the settings that define a specific
output. For example, you could have a preset called QuickTime MP4 with H.264
for Streaming, which saves the H.264 and QuickTime parameters used for
streaming output from your web server. It also specifies the path for output
files. Rhozet includes 100+ presets.
Media Management defines presets for various output types (for import or
export of videos). A preset is identified by a hexadecimal string of 32 characters.
GUID
The Globally Unique Identifier (GUID) of a Preset is specific to Rhozet. This is
how a Preset is referred to in the APIs when called from the Media Management
server.
Profile
This is specific to Rhozet.

Chapter 11 Configuring video and audio
A profile is a collection of presets in Rhozet server. The profile is processed as a

single job in the server.
Factory
This is specific to FlipFactory.
The factory can be created in FlipFactory with a single or group of products.
Each product generates different output format video.
Example:
Create a factory named otmm_export_mpeg4 with H.264 product. It creates
output video in MP4 format. FlipFactory comes with various output products.
Media Management creates various factories for video import and export.
Workflow
This is specific to Vantage.
Media Management creates various workflows for video and audio imports and
exports. A workflow can be created in Vantage with a group of actions that must
be performed on the asset.
11.1.2 Media Management configuration parameters

The following list describes the Media Management configuration parameters
required for integrating the Transcode server with Media Management. Most of
these parameters are common to all Transcode servers.
VIDEO_TRANSCODE_CLASS
• For the FlipFactory server - 'com.artesia.video.transcode.services.
FlipFactoryTranscodeServices'
• For the Rhozet server - 'com.artesia.video.transcode.services.
RhozetTranscodeServices'
• For the Vantage server - ‘com.artesia.video.transcode.services.
VantageTranscodeServices'
• For the FFMPEG server - 'com.artesia.video.transcode.services.
FFMpegTranscodeServices'
Default class name of the Media Management Video adapter class. It is used to
submit and manage video transcode jobs on the Transcode server.
You can configure this setting through the VIDEO\TRANSCODE component,
which belongs to the Video configuration group. You can access this group from
the Settings page in the Web Administration tool. For more information, see
TRANSCODE_HOST
Details of the server where the Transcode server is installed.

11.1. Configuring the Transcode server
FlipFactory only
If FlipFactory is configured in LoadBalance/FactoryArray, provide all
hostnames in an array like the following example:
"SERVER1:PORT,SERVER2:PORT"
If the port is not configured, the default value from TRANSCODE_PORT will
be used.
Vantage only
If Vantage is used as the Transcode server, then the value of this entry
should be specified as http://server:port.
If Vantage is configured in LoadBalance/Array, then you must provide
details of all nodes in an array like the following example:
http://server1:port1,http://server2:port2
Note: The default port for Vantage is 8676.
Rhozet only
Specify the host name of server where Rhozet is installed. For example:
"SERVER1"
FFmpeg only
Specify the host name of server where FFmpeg is installed.
Notes
• If you are using FFmpeg as the Transcode server and FFmpeg is running
on the same server as OTMM, set the value of this entry to localhost.
• If the FFmpeg server is running remotely, use the one of the following
formats for the host name:
• hostname:port
• ip addresss:port
TRANSCODE_PORT
Use one of the following values:
• 9000, which is the default port to invoke FlipFactory HTTP APIs from Media
Management.
• 1120, which is the default port to invoke Rhozet APIs from Media
Management.
Note: When using Vantage, this entry is ignored because the port is
specified in the above entry.


TRANSCODE_USER
The user name or account name for the FlipFactory server. All factories used in
Media Management must be created with this user name only, for example,
'otmm'.
Note: This is specific to FlipFactory.

TRANSCODE_CATEGORY
On a Vantage server, this is the name of the category containing the default
Media Management workflows. For example, MediaMgmt.
TARGET_PATH
A shared network path for the Transcode server where the transcode output
files will be written to. The user who executes OTMM must have read access to
this path and the Transcode server must have write access to this path. This
entry value is added from the installer. For example:
\\<transcode server host>\<transcode_working_folder>
Notes
• Linux - This shared folder must be mounted to a Linux folder. The

OTMM user must have read access to it. For example:
/usr/local/mount_point_directory
• You can configure this setting through the VIDEO\TRANSCODE
component, which belongs to the Video configuration group. You can
access this group from the Settings page in the Web Administration tool.
For more information, see section 2.13.2.3 “Editing a component and
properties” in OpenText Media Management - Administration Guide
(MEDMGT-AGD).
• This setting is applicable to Rhozet, Vantage, and FFmpeg only.

VIDEO_FILE_STAGING_AREA
Folder where Media Management stages video content for transcoding. The user
executing OTMM must have read and write access to this folder. The Transcode
server will read the content from this location. This entry value gets added from
the installer. For example:
\\<transcode server host>\<staging area directory>
Note: Linux - This shared folder must be mounted to a Linux folder. The
Media Management user must have write access to it. For example:
/usr/local/<mount_point_directory>
You can configure this setting through the CONTENT\CONFIG component,

which belongs to the General configuration group. You can access this group
from the Settings page in the Web Administration tool. For more information,
see section 2.13.2.3 “Editing a component and properties” in OpenText Media
VIDEO_BASE_URL
Set the base URL to the video server for playing video proxies. The base URL is
of the form:
For IIS Server or Apache HTTP Server:

http://<web-server>/<application name for http progressive
download>
For Adobe Media Server :

rtmp://<AMS server>/<AMS app>/_definst_/mp4:
When streaming proxy video, Media Management dynamically constructs the

URL for streaming using the base URL, which identifies the server location
where the video files can be streamed from. The full URL is of the form:
<baseURL>/<filepath>
where filepath is the relative file path from the repository where the proxies
are usually placed after the import is complete. Media Management moves the
files from the Transcode server to the repository. The baseURL may refer to the
Adobe Media Server (uses rtmp:// protocol by default) or HTTP download
servers such as Apache or IIS. For more information about AMS configuration,
see “Configuring Adobe Media Server ” on page 186.
Note: The streaming server may be installed on the same host as Media
Management or on a different host.


AUDIO_BASE_URL
Set the base URL to the server for playing audio proxies. The base URL is of the
form:
For IIS Server or Apache HTTP Server:

http://<web-server>/<application name for http progressive
download>
For Adobe Media Server :

rtmp://<AMS server>/<AMS app>/_definst_/mp3:
VIDEO_PROGRESSIVE_DOWNLOAD_URL
If the VIDEO_BASE_URL is set to a streaming server for clients that do not
support configured streaming server to play proxies, set this to the base URL of
the progressive download server for playing video proxies. The base URL is of
the form:
http://<web-server>/<application name for http progressive download>
AUDIO_PROGRESSIVE_DOWNLOAD_URL
If the AUDIO_BASE_URL is set to a streaming server for clients that do not support
configured streaming server to play proxies, set this to the base URL of the
progressive download server for playing audio proxies. The base URL is of the
form:
http://<web-server>/<application name for http progressive download>
Note: For integrators - The video/audio absolute streaming and

progressive URLs can be read from the asset object.
WORKING_PATH
This path must have the same value as the VIDEO_FILE_STAGING_AREA entry.
Note: This is for Linux only.

Example 11-1: Linux

/usr/local/<mount_point_directory>
Note: This entry must be configured on Linux.

UNC_REPOSITORY
This is for Linux only.
UNC path or absolute path of the staging area where the Transcode server will
pick up media assets for transcoding. This value must be a Windows path or a
UNC path. For example:
"C:\TranscodeArea\<staging_area_directory>"
or
"\\<transcode server host>\<staging area directory>"
Notes
• For FlipFactory, this path must be always in the UNC path format. For
example,
"\\<transcode server host>\<staging area directory>"
• This value must be configured on Linux.

UNIX_VIDEO_WORKING_AREA_UNC
The UNC path of the location where the Transcode server writes the transcoded
files. For example:
Note: This Linux-only entry must have a back slash ("\") at the end. For
example:
"\\<transcode server host>\<transcode working file directory>\"


Note: This output working area can be the same staging area used for
transcoding input (VIDEO_FILE_STAGING_AREA, UNC_REPOSITORY).
UNIX_RELATIVE_VIDEO_WORKING_AREA
Linux mount path to the Transcode server output working folder
(UNIX_VIDEO_WORKING_AREA_UNC).
Note: This Linux-only entry must have a forward slash ("/") at the end. For
example:
"/usr/local/<mount_point_directory>/"

Note: This path can be the same local directory path used to stage
transcode input files.
PRIMARY_KEYFRAME
The key-frame index used to create the thumbnail. By default this is 2, which
means the third keyframe in the video is set as the thumbnail.
If this key-frame index number is greater than the highest frame index number
of the video asset, the highest frame index number (the last key frame) will be
used to generate the thumbnail. If this number is a negative number, the lowest
frame index number (the first key frame) will be used to generate the thumbnail.
Note: The thumbnail can be changed within the OTMM UX application for
each individual video.

VIDEO_TRANSCODE_JOB
Factory name/ Profile GUID/Workflow name which is used by Media
Management to generate a proxy video and key-frames during import. This
Factory/ Profile/Workflow is configured to generate MP4 proxies and
Keyframes.
A proxy video is a low-bandwidth version of the imported video asset (also
known as the Master asset) for a quick preview.


PROXY_VIDEO_TRANSCODE_JOB
Factory name/ Preset GUID/Workflow name which is used by Media
Management to generate a proxy video during the transcode process and is
primarily used when upgrading to a version 7 Media Management system. This
Factory/ Preset/Workflow is configured for generating a new proxy to replace a
pre-7.0 proxy. In new OTMM systems, it is not used.
AUDIO_TRANSCODE_JOB
Management to generate an audio proxy during import.
EXPORT_VIDEO_TRANSCODE_JOB
Management to queue an export job with the Transcode server.
The format for export may be selected during the Factory/Preset/Workflow
creation process.
Also, additional EXPORT_VIDEO_TRANSCODE_JOBs for various formats can
be added. See examples below.
DEFAULT_FRAME_RATE
This specific to FlipFactory and Vantage.
This is used to provide the default frame rate value for input video files. This
framerate will be used when FlipFactory orVantage is unable to identify the
frame rate value from the input video file metadata (for example '29.97').


<FILE_EXTENSION>_EXPORT_CLIP_TRANSCODE_JOB
When the export of a video clip is processed without giving any conversion, this
entry determines the output format of the video clip. The output factory/preset/
workflow is considered based upon the extension of its parent (Master) video
file. For example, while exporting a MP4 video clip asset, it uses the factory/
preset/workflow that is configured using the following entry for the output
video clip.
"MP4_EXPORT_CLIP_TRANSCODE_JOB"="<factory name of mp4> or <mp4 preset
GUID>"
Note: This is specific to video clip assets only.

DEFAULT_EXPORT_CLIP_TRANSCODE_JOB
This is the default output factory/preset/workflow considered if the extension of
its parent (Master) video file is not configured.
Note: This is specific to video clip assets only. The default value is
configured as MP4, but can be changed to any format.

11.1.3 Setting up a shared transcoding user account

Typically, it is helpful to create a common user in a Windows environment to
facilitate sharing of content.
To configure a common Windows user on both systems to enable the Transcode

server to sign in to the Media Management server. At the command prompt, enter
lusrmgr.msc to add the common Windows user. You may add the user to the
Administrator's group. Make sure the user IDs are configured with the same
password on both systems unless you are using a Windows domain ID.
Note: Creating the user is only required for Windows systems. Linux systems
will mount the shared video staging area. When mounting the shared folder,
read/write access to the mounted file system must be provided to the local
Media Management user ID.

Rhozet Carbon Coder

Configure the “Nexus Service” to sign in using this common Windows user ID.
(For example, rhozet; Services Nexus Server Log on.) Restart Nexus Server.
Verify that it starts using the new sign in.
Telestream FlipFactory server
Configure the Flip Engine to sign in using this common Windows user ID. (For
example, flip; Services ‘Flip Engine’ Logon). Restart Flip Engine. Verify that it
starts using the new sign in.
Telestream Vantage server
Configure all the Vantage services to sign in using this common Windows user
ID. All Vantage Windows service names are preceded by “Vantage”.
FFmpeg
Configure all the FFmpeg services to sign in using this common Windows user
ID.
Media Management server
Verify that the same user account exists on the Media Management server.
11.1.4 Setting up shared folders for transcoding

The Media Management server and audio/video Transcode servers share files
through a shared directory. This allows the transcoder to know where to read the
files to transcode and where to deliver the output files. Therefore, the OpenText
Media Manager service and Video transcode service must be configured to run as
user accounts. The shared folders are then configured to allow appropriate access
rights to these users. You can set up the user accounts in the following ways:
• Create a domain user account, for example otmmuser, and start the video
transcode service, streaming video service, and the OTMM service under that
user’s account.
• Create a local user account, for example otmmuser, on both the video server
machine and the OTMM server machine. Again, start the video transcode
service, streaming video service, and the OTMM service under that user’s
account.
For simplicity, OpenText recommends that you set up only one share and use it for
reading the input file and writing the output files. The shared storage can reside on
any of the following:
• The Media Management server.
• The Transcode server.
• A separate storage, such as a NAS.
WINDOWS
The key requirement is that both OTMM and the transcoder are executing with a
user ID that has both read and write capabilities and that both servers can
access the shared storage.

LINUX
The key requirement is the OTMM user has both read and write access to the
local mounted transcode folders and the transcode user has read and write
capabilities to the Windows shared folders.
11.1.4.1 Windows shared storage example

A Windows example for shared storage might look like the following figure where
the storage is on the Transcode server.
Figure 11-1: Transcode storage
Notes
• \\TranscodeSrv\staging_area - On the Transcode server machine, create a

folder such as D:\staging_area and enable this folder for access by the
Windows common user by clicking the folder properties, share, and then
add the user and grant permissions.
• On the Windows Media Management server, edit the Media Management
setting to include this shared staging area path. You should specify the
following value as a network UNC path in the VIDEO_FILE_STAGING_AREA
setting in the CONTENT\CONFIG component, which belongs to the
General configuration group. You can access this group from the Settings
page in the Web Administration tool. For more information, see section
2.13.2.3 “Editing a component and properties” in OpenText Media
\\TranscodeSrv\staging_area
• \\TranscodeSrv\transcode_wf - It is recommended that this be the same as
the staging_area. If this folder needs to be in a different location, then
create this folder on the Transcode server machine and enable it for read
access for the common user. Click the folder properties, share, and then add
user and grant permissions.

11.1.4.2 Central shared storage example

A central storage example might look like the following:
Figure 11-2: Central storage
In this example, the shared transcode folders are located on an independent File
Server.
• In this example, the shared transcode folders are located on an independent File
Server.
• On the File Server, create the transcode_wf (output) folder and the
staging_area (input) folder.
• Share both folders giving the common user read and write access to both
folders.
• Set the VIDEO_FILE_STAGING_AREA setting value as follows:
Note: VIDEO_FILE_STAGING_AREA is located under the CONTENT

\CONFIG component, which belongs to the General configuration group.
You can access this group from the Settings page in the Web
component and properties” in OpenText Media Management - Administration
Guide (MEDMGT-AGD).

WINDOWS
"VIDEO_FILE_STAGING_AREA"="\\TranscodeSrv\staging_area"
UNIX
VIDEO_FILE_STAGING_AREA" = "/<mount_point>/staging_area
11.1.4.3 Media Management on Linux shared storage example

On a Linux installation, a storage example might look like the following:
Figure 11-3: Linux Storage Example
Note: OpenText recommends that you use a single share for simplicity.
1. On Linux Media Management systems mount the shared folders as local

directories using the CIFS protocol.
Note: Ensure that the Media Management user has read and write
privileges to the mounted directories.
2. Edit the settings on Linux as follows:
Note: You can edit these settings through the Settings page in the Web
component and properties” in OpenText Media Management -
a. Specify the VIDEO_FILE_STAGING_AREA setting value as the local mount

path for the folder mounted from the Transcode server. For example:
"VIDEO_FILE_STAGING_AREA" = "/<mount_point>/staging_area"
Note: This setting is accessible through the CONTENT\CONFIG

component, which belongs to the General configuration group. You

can access this group from the Settings page in the Web
Administration tool. For more information, see section 2.13.2.3
“Editing a component and properties” in OpenText Media Management
- Administration Guide (MEDMGT-AGD).
b. Specify the WORKING_PATH as the same value as the
VIDEO_FILE_STAGING_AREA.
"WORKING_PATH"="/<mount_point>/staging_area"
Note: This is available under the VIDEO\TRANSCODE component,

which belongs to the Video configuration group. You can access this
group from the Settings page in the Web Administration tool. For
more information, see section 2.13.2.3 “Editing a component and
(MEDMGT-AGD).
c. Specify the UNC_REPOSITORY UNC path to the shared storage, such as \
\transcode Srv\staging_area. For example:
"UNC_REPOSITORY"="\\transcode Srv\staging_area"

(MEDMGT-AGD).
d. Specify the UNIX_RELATIVE_VIDEO_WORKING_AREA value as the local mount
path for the transcode output files. For example:
"UNIX_RELATIVE_VIDEO_WORKING_AREA"="/<mount_point>/
transcode_wf/"

(MEDMGT-AGD).
e. Specify the UNIX_VIDEO_WORKING_AREA_UNC value as the network path of
the transcode_store folder. For example:
"UNIX_VIDEO_WORKING_AREA_UNC"="\\transcode Srv\transcode_wf\"

(MEDMGT-AGD).

11.2 Configuring video with Rhozet Carbon Coder

Media Management delivers video and audio transcoding by default by integrating
Rhozet Carbon Coder, which powers video metadata, import, and export.
Carbon Coder is a stand-alone application which runs on a single system that can be
used for production purposes. Because video and audio transcoding requires more
CPU cycles than typical applications, OpenText recommends installing Carbon
Coder on a separate Windows server. For a list of supported operating systems for
Rhozet, see the Rhozet documentation.
Notes
• The supported operating systems for Rhozet may differ from those
supported for Media Management.
• Rhozet may need all the available CPU cycles, depending on the volume of
media.
• For more information about dependencies, installation instructions, and
other related information, see the Rhozet Carbon Coder documentation.
Prior to installing Rhozet Carbon Coder, make sure you have the license
dongle available.
11.2.1 Installing Rhozet Carbon Coder

For more information about installing Rhozet Carbon Coder, see the Rhozet Carbon
Coder user documentation at:
https://www.harmonicinc.com/media/2016/06/ProMediaCarbon_3_20_UGuide.pdf.
11.2.2 Setting up video transformations in Rhozet Carbon

Coder
This section describes deploying the default video transcode jobs. These are called
profiles in Rhozet Carbon Coder.
Prior to setting up video transformations, you must install Rhozet Carbon Coder.
For more information about dependencies, installation instructions, and other
related information, see the Rhozet documentation.
To set up video transformations in Rhozet:
1. Sign in to the server where you installed OTMM.
2. Locate the Rhozet transcode presets in <TEAMS_HOME>\data\

videotransformer_profiles.zip.

11.2. Configuring video with Rhozet Carbon Coder
3. Copy this ZIP file to the Rhozet server machine.
4. Sign in to the Rhozet Carbon Coder host.
5. Close the Rhozet Carbon Admin.
6. Extract the videotransformer_profiles.zip file (located in <TEAMS_HOME>

\data) and copy the extracted .cpf files to the C:\Documents and Settings\
All Users\Application Data\Rhozet\Carbon Coder\User Presets folder.
7. Restart the Nexus Server by running the services.msc command, and then
select Nexus Server > restart.
8. Open the Rhozet Carbon Admin. It may need a couple minutes to import
presets and build the updated preset list.
9. Open the Preset Editor.
10. Verify the presets and profile which are imported by selecting the following
items from the left navigation panel of the Preset Editor:
a. Web → Flash → Flash download and F4V export preset.

b. Web → Windows Media → Windows Media streaming preset.
c. Handheld → iPhone → iPhone Video preset.
d. Handheld → 3GPP → Blackberry/3GPP preset.
e. Audio → MP3 → Audio import.
f. System → AVI export, Quicktime Movie Trailer.
g. H.264 → MP4 import.
h. OTMM → otmm_default_import_profile.
11. Restart Rhozet Carbon Coder by running the services.msc command, and
then select Nexus Server > restart.
12. Verify the GUIDs for each of the presets on the Media Management server as
follows:
Note: The following are available under the VIDEO\TRANSCODE

component, which belongs to the Video configuration group. You can
access this group from the Settings page in the Web Administration tool.
For more information about viewing components, see section 2.13.2.2
“Viewing a component and properties” in OpenText Media Management -
• VIDEO_TRANSCODE_JOB → otmm_default_import_profile.
• PROXY_VIDEO_TRANSCODE_JOB → MP4 import.
• EXPORT_VIDEO_TRANSCODE_JOB → AVI export preset.
• AUDIO_TRANSCODE_JOB → Audio import.
• EXPORT_VIDEO_TRANSCODE_JOB_WMV → Windows media streaming.

• EXPORT_VIDEO_TRANSCODE_JOB_IPHONE → iPhone Video preset.

• EXPORT_VIDEO_TRANSCODE_JOB_MOBILE → Blackberry/3GPP preset.
• EXPORT_VIDEO_TRANSCODE_JOB_MOV → Quicktime Movie Trailer.
• EXPORT_VIDEO_TRANSCODE_JOB_F4V → F4V export preset.
• EXPORT_VIDEO_TRANSCODE_JOB_MP4 → MP4 import.
• EXPORT_VIDEO_TRANSCODE_JOB_AVI → AVI export preset.
11.2.3 Configuring Rhozet Carbon Coder

This section describes how to set up Rhozet Carbon Coder and integrate it with
Media Management.
Media Management provides preconfigured presets that work with Rhozet by

default. The presets, which are configured under the following transcode job entries,
are ready to use after the configurations described in this section are complete.
Note: The following settings are located under the VIDEO\TRANSCODE

component, which belongs to the Video configuration group. You can access
this group from the Settings page in the Web Administration tool. For more
information about editing settings, see section 2.13.2.3 “Editing a component
and properties” in OpenText Media Management - Administration Guide
(MEDMGT-AGD).
• VIDEO_TRANSCODE_JOB
• PROXY_VIDEO_TRANSCODE_JOB
• EXPORT_VIDEO_TRANSCODE_JOB
• AUDIO_TRANSCODE_JOB
• DEFAULT_EXPORT_CLIP_TRANSCODE_JOB
• MOV_EXPORT_CLIP_TRANSCODE_JOB
• F4V_EXPORT_CLIP_TRANSCODE_JOB
• FLV_EXPORT_CLIP_TRANSCODE_JOB
• AVI_EXPORT_CLIP_TRANSCODE_JOB
• WMV_EXPORT_CLIP_TRANSCODE_JOB
• MP4_EXPORT_CLIP_TRANSCODE_JOB
• MPG_EXPORT_CLIP_TRANSCODE_JOB
• MXF_EXPORT_CLIP_TRANSCODE_JOB
• 3GP_EXPORT_CLIP_TRANSCODE_JOB
The following are additional GUIDs which are preconfigured, but are part of the
optional export transformers, which are installed separately:

• EXPORT_VIDEO_TRANSCODE_JOB_WMV
• EXPORT_VIDEO_TRANSCODE_JOB_IPHONE
• EXPORT_VIDEO_TRANSCODE_JOB_MOBILE
• EXPORT_VIDEO_TRANSCODE_JOB_MOV
• EXPORT_VIDEO_TRANSCODE_JOB_F4V
• EXPORT_VIDEO_TRANSCODE_JOB_MP4
• EXPORT_VIDEO_TRANSCODE_JOB_AVI
For both these sets, the values are pre-configured as seen through the Settings page
in the Web Administration tool. Do not modify them unless you need to create your
own custom presets and profile. For more information about how to modify custom
presets and profiles, see Rhozet Carbon Coder User Guide.
Notes
• You should verify that the GUIDs defined through the Settings page exist
using the Rhozet Carbon Admin preset editor. If they do not exist, you can
configure your own presets following the instructions below.
• Media Management uses Profiles to interact with Rhozet while importing
assets and uses Presets for exporting assets. To conform to Media
Management specifications for keyframes of 320x240, you must configure a
custom Video Keyframe GUID.
To customize a video keyframe proxy:
1. To setup Rhozet to capture thumbnails from videos, open the Preset editor by
clicking Start > Programs > Rhozet > Carbon Coder > Carbon Coder Admin.
2. Select the JPEG Thumbnail Preset from Web/Thumbnails, which is required, or

close your required thumbnail.
3. If the Thumbnail selected is not exactly as required, then Copy this Preset and
edit it by clicking Edit Preset for the copied thumbnail. A sample is given
below.
• Optional: Set the Pathto the destination folder to be the same as the folder
where the Proxy Videos are picked up, for example, \\TranscodeSrv\
transcode_wf.
• Optional: Change Interval to 10 seconds.

• Optional: Change Thumbnail size to 320x240.
• Change any other entries, if required.
4. Save the file.
5. Restart the Nexus Server service.

6. Update this new JPEG Thumbnail preset in the otmm_default_import profile

using Promedia Carbon. The JPEG Thumbnail preset should be the second line
in the otmm_default_import profile.
Important
Make sure that the Write First Frame (checkbox) attribute is set to
TRUE. This is required for generating all the keyframes and making sure
that the Media Management features, including Media Catalog, will
function correctly.
11.2.4 Integrating Media Management and Rhozet

Media Management interfaces with Rhozet Carbon Coder through Carbon APIs.
Import jobs are submitted to Rhozet by the Media Management server using the
Carbon APIs to queue jobs to Rhozet for transcoding using the Profile represented
by VIDEO_TRANSCODE_JOB. These files are staged to a Media Management pick up
folder using the Media Management APIs.
The following steps are needed for Media Management APIs to interact with Rhozet
Carbon Coder APIs:
Note: Make sure the Transcode server can access the Media Management host
via a browser. The Media Management URL is configured using the
WEB_APPS_BASE_URL setting that is configured through the Settings page in the
Web Administration tool. For more information, see section 2.13.2.3 “Editing a
Guide (MEDMGT-AGD).
• Configure the VIDEO\TRANSCODE component, which belongs to the Video

configuration group, with the host, port and GUIDs (identifiers inside Rhozet for
a specific format/codec to transcode). You can access the Video group from the
Settings page in the Web Administration tool. For more information about
editing component, see section 2.13.2.3 “Editing a component and properties” in
OpenText Media Management - Administration Guide (MEDMGT-AGD).
Set the file sharing variables as described in “Setting up shared folders for
transcoding” on page 143.
A sample configuration is included with the installation.
Example 11-2: Rhozet configuration

"VIDEO_TRANSCODE_CLASS"="com.artesia.video.
transcode.services.RhozetTranscodeServices"
"TRANSCODE_HOST"="Rhozetserver"
If Rhozet server is installed with multiple agents, provide only the
Rhozet server hostname. The agent hostname details are not required.
"TRANSCODE_PORT"="1120"

"TARGET_PATH"="\\<transcode server host>

\<transcode_working_folder>"
"PRIMARY_KEYFRAME"="3"
"VIDEO_TRANSCODE_JOB"="{7DD4221A-750B-4014-
A990-05B13F7C3C1D}"
"PROXY_VIDEO_TRANSCODE_JOB"="{AFD2718A-
ECB6-4B21-8652-2F5DABD04856}"
"EXPORT_VIDEO_TRANSCODE_JOB"="{C16C55A3-9010-45CE-AD6C-
E60846C3FB05}"
"AUDIO_TRANSCODE_JOB"="{06E30773-64DD-4C81-84A0-83005B6C06DD
}"
"EXPORT_VIDEO_TRANSCODE_JOB_WMV"="{AB646E14-3E71-4750-8A64-
EA38CD126AF5}"
"EXPORT_VIDEO_TRANSCODE_JOB_IPHONE"="{9432FE23-CB4C-452C-
B87A-D54E5957DD98}"
"EXPORT_VIDEO_TRANSCODE_JOB_MOBILE"="{D6E6040B-21D1-426B-
BF69-7971B6A46B90}"
"EXPORT_VIDEO_TRANSCODE_JOB_MOV"="{BC452EA1-0B1D-4996-95EE-
EB9A46CA7726}"
"EXPORT_VIDEO_TRANSCODE_JOB_F4V"="{AFD2718A-
ECB6-4B21-8652-2F5DABD04856}"
"EXPORT_VIDEO_TRANSCODE_JOB_MP4"="{6C40AD39-8F54-4020-914E-0
F3FCC980042}"
"EXPORT_VIDEO_TRANSCODE_JOB_AVI"="{C16C55A3-9010-45CE-AD6C-
E60846C3FB05}"
"DEFAULT_EXPORT_CLIP_TRANSCODE_JOB"="{6C40AD39-8F54-4020-914
E-0F3FCC980042}"
"MOV_EXPORT_CLIP_TRANSCODE_JOB"="{BC452EA1-0B1D-4996-95EE-
EB9A46CA7726}"
"F4V_EXPORT_CLIP_TRANSCODE_JOB"="{AFD2718A-
ECB6-4B21-8652-2F5DABD04856}"
"FLV_EXPORT_CLIP_TRANSCODE_JOB"="{F26FB530-
A0BA-4EA7-9AC1-701C8E7B196D}"
"AVI_EXPORT_CLIP_TRANSCODE_JOB"="{C16C55A3-9010-45CE-AD6C-
E60846C3FB05}"
"WMV_EXPORT_CLIP_TRANSCODE_JOB"="{AB646E14-3E71-4750-8A64-
EA38CD126AF5}"
"MP4_EXPORT_CLIP_TRANSCODE_JOB"="{6C40AD39-8F54-4020-914E-0F
3FCC980042}"
"MPG_EXPORT_CLIP_TRANSCODE_JOB"="{CB8B763A-269B-4680-9DAC-50
C783A563EC}"

"MXF_EXPORT_CLIP_TRANSCODE_JOB"="{C5CECA39-
C3E4-4A72-9468-28F325C894CF}"
"3GP_EXPORT_CLIP_TRANSCODE_JOB"="{D6E6040B-21D1-426B-
BF69-7971B6A46B90}"
Additional Configuration for Linux only:
Add the following settings Linux under the VIDEO\TRANSCODE
component, which belongs to the Video configuration group. The path
must end with / or \ as follows.
"UNIX_VIDEO_WORKING_AREA_UNC"="\\<Working area server>
\<Shared Folder>\"
"UNIX_RELATIVE_VIDEO_WORKING_AREA"="<local path to the shared
folder>/"
Also, add the following settings for Windows and Linux, under the
VIDEO\TRANSCODE section:
"AUDIO_BASE_URL"="http://IIS_Server/IIS_App"
"VIDEO_BASE_URL"="http://IIS_Server/IIS_App"
• Through the Settings page, which is accessible from the Web Administration
tool, configure the RHOZET\PROFILE component, which belongs to the Video
configuration group, as follows:
Note: For more information about editing settings, see section 2.13.2.3
“Editing a component and properties” in OpenText Media Management -
The following section is used for importing video assets into Media
Management. This example configuration shows the index values of the default
profile 'VIDEO_TRANSCODE_JOB'.
[RHOZET\PROFILE]
"PROXY_INDEX"="0"
"KEYFRAME_INDEX"="1"
"CLOSEDCAPTION_INDEX"="2"
PROXY_INDEX, KEYFRAME_INDEX and CLOSEDCAPTION_INDEX indicate the
respective positions of the presets present in the profile.
If you want to create a new profile, you can use the Carbon Coder interface to
create a new profile. The profile must include a preset for proxy and a preset for
keyframes.
PROXY_INDEX should specify all the indices where Presets related to proxy
creation are present in the Rhozet profile. If multiple indices are provided, only
the first proxy will be considered.
KEYFRAME_INDEX should specify all the indices where Presets related to keyframe
generation are present in the Rhozet profile.

CLOSEDCAPTION_INDEX should specify all the indices where Presets related to

closed captions (Text tracks) creation are present in the Rhozet profile.
Note: The indices should be specified as comma separated values and the
first index should start from zero.
The following video configuration samples (for Windows and for Linux) have the
following assumptions:
• The shared transcode folders are located on the Transcode server machine.
• The staging area folder name is staging area. This is where the videos are input
to the Transcode server.
• The transcode working file area is transcode_wf. This is where the video
Transcode server writes out transcoded files.
• The Rhozet Carbon Coder host name is rhozetSrv in which the “H:” drive has
the staging area and Transcode working file area.
Example 11-3: Windows sample video staging configurations
You must update the staging area setting. Update the

VIDEO_FILE_STAGING_AREA setting CONTENT\CONFIG component,
which belongs to the General configuration group, as follows:
"VIDEO_FILE_STAGING_AREA"="\\rhozetSrv\staging_area"
Notes
• The General configuration group is accessible from the Settings page in the
Web Administration tool. For more information about editing the
configurations settings, see section 2.13.2.3 “Editing a component and
(MEDMGT-AGD).
The following are not used for the Windows configuration:

• UNC_REPOSITORY
• WORKING_PATH
• UNIX_RELATIVE_VIDEO_WORKING_AREA
• UNIX_VIDEO_WORKING_AREA
Example 11-4: Linux sample video staging configurations
On Linux, Windows shared directories cannot be accessed by using a UNC

path. These need to be mounted to a Linux local directory. Assume that
staging_area and transcode_wf are mounted to a Linux directory, as
shown in the following example:

"\\rhozetSrv\staging_area" mount to "/usr/local/share/

staging_area"
"\\rhozetSrv\transcode_wf" mount to "/usr/local/share/

transcode_wf"
You must update the staging area setting. Update the

VIDEO_FILE_STAGING_AREA setting located under the CONTENT
\CONFIG component, which belong to the General configuration group, as
follows:
"VIDEO_FILE_STAGING_AREA"="/usr/local/share/staging_area"
"WORKING_PATH"="/usr/local/share/staging_area"
"UNC_REPOSITORY"="\\rhozetSrv\staging_area"
"UNIX_VIDEO_WORKING_AREA_UNC"="\\rhozetSrv\transcode_wf\"
"UNIX_RELATIVE_VIDEO_WORKING_AREA"="/usr/local/share/
transcode_wf/"
Notes
• The Video configuration group is accessible from the Settings page in the
Web Administration tool. For more information about how to edit settings,
• The trailing slashes at the end of UNIX_VIDEO_WORKING_AREA_UNC and
UNIX_RELATIVE_VIDEO_WORKING_AREA are required.
• Make sure the Media Management server is accessible from the Rhozet
server because HTTP notifications are sent to from the Rhozet server to the
Media Management server.
11.3 Configuring video with Telestream FlipFactory

Media Management delivers video and audio transcoding with the integration of
Telestream FlipFactory, which powers video metadata, import, and export. This
section describes the steps necessary to configure your Media Management
installation for video with the Telestream FlipFactory server.
Note: For more information about versions, see OpenText Media Management
open/69371555).

11.3. Configuring video with Telestream FlipFactory
11.3.1 Installing Telestream FlipFactory

To install Telestream FlipFactory:
1. Access the FlipFactory User guide, which is available at:

http://www.telestream.net/download-files/flipfactory/7-3/
FlipFactory_UserGuide.pdf
2. Refer to the FlipFactory User Guide for installation instructions.
11.3.2 Setting up video transformations in FlipFactory

This section describes deploying the default video transcode jobs. These are called
factories in FlipFactory.
To set up video transformations in FlipFactory:
1. Sign in to the Media Management server machine.
2. Locate the FlipFactory transcode configuration file in <TEAMS_HOME>\data\

videotransformer_factories.zip.
3. Copy this ZIP file to the FlipFactory server machine.
4. Sign in to the FlipFactory server.
5. Close all FlipFactory consoles.
6. Stop the FlipFactory Engine service in Windows services.
7. Unzip the videotransformer_factories.zip file and copy the otmm.xml file

from the videotransformer_factories folder of the extracted ZIP to the
$flipfactory$\Xml\accounts\import folder (for example, C:\Program
Files (x86)\Telestream\FlipFactory\Xml\accounts\import), to create a
user account in FlipFactory with the name otmm or create a new user account in
FlipFactory.
8. Copy the otmm.xsl file from the style sheets folder of the extracted ZIP to the
$flipfactory$\http\metadata\stylesheets folder. For example:
C:\Program Files (x86)\Telestream\FlipFactory\http\metadata
\stylesheets
9. Edit otmm.xml and do the following.
a. Replace all occurrences of the $CONFIGUREME$ string with your destination

folder directory for the Transcode server. The destination folder should be
in the UNC path and it should have read privileges for the Media
Management server.
b. Replace all occurrences of the string $OTMM_HOST_NAME$ with the Media

FlipFactory server.
c. Replace all the occurrences of $OTMM_HTTP_PORT$ with the http port where
the OTMM server was configured. In case of single node, the default value
is 11090. If a load balancer or proxy is configured, specify the port as http
port on which the load balancer or proxy is running. The OTMM host name
and HTTP port configured in the above steps are used to send a http
notification after a transcode job is done on the FlipFactory server.
d. Change the values of the attributes personal and username to <username>
for the account tag where <username> is the new user account name in
FlipFactory.
e. Rename otmm.xml to <username>.xml and copy the file to the
$flipfactory$\Xml\accounts\import folder. For example, C:\Program
Files (x86)\Telestream\FlipFactory\Xml\accounts\import.
f. Restart the FlipFactory service to import the new user into FlipFactory.
g. Update the TRANSCODE_USER setting with the new user created above. This
property is located under the VIDEO\TRANSCODE component, which
belongs to the Video configuration group. This group is accessible from the
Settings page in the Web Administration tool. For more information about
editing a component, see section 2.13.2.3 “Editing a component and
(MEDMGT-AGD).
10. Perform steps Step 4 to Step 6 on all nodes of the FactoryArray.
Note: Since HTTP notification configuration stores the details of the

OTMM server, each user account can be used by a single OTMM server
only. If the same FlipFactory server has to be shared by various OTMM
servers, create a new user account for each OTMM instance.
11. Start the FlipFactory Engine Windows service.
12. If you have already configured your factory with a FlipFactory user account, for
example “demo”, and you want to use the same account name for Media
Management, then you must delete the “demo” account first (deleting an
account removes all the old configurations) and rename otmm.xml to demo.xml.
13. Start the FlipFactory console.
14. Sign in to FlipFactory with the OTMM account, which will be created
automatically by the XML file.
15. Verify the factory settings under the OTMM account.
Note: You must enable the Media Trimming setting for all factories configured
through the Settings page in the Web Administration tool for export video
transformations.

11.3.3 Configuring Telestream FlipFactory

This section describes how to set up FlipFactory and integrate it with Media
Management.
Media Management includes preconfigured factories that work with FlipFactory by

importing the otmm.xml user account.
The factories, which are configured under following transcode job settings, are ready
to use after the configurations described in this section are complete. The following
settings are located under the VIDEO\TRANSCODE component, which belongs to
the VIDEO configuration group. This group is accessible from the Settings page in
the Web Administration tool. For more information, see section 2.13.2.3 “Editing a
component and properties” in OpenText Media Management - Administration Guide
(MEDMGT-AGD).
The following additional factories, which are pre-configured, are part of optional
export transformers installed separately:

The values of both of these sets are pre-configured. The settings are located under
the VIDEO\TRANSCODE component, which belongs to the VIDEO configuration
group. This group is accessible from the Settings page in the Web Administration
tool. For more information, see section 2.13.2 “Configuring components” in
OpenText Media Management - Administration Guide (MEDMGT-AGD). Do not modify
these settings unless you need to create your own custom factories. For more
information about creating custom factories, see http://www.telestream.net/
download-files/flipfactory/7-3/FlipFactory_UserGuide.pdf.
Note: You should verify that the factories defined in through the Settings page
in the Web Administration tool exist using the FlipFactory console. If not, you
can configure your own factories by using the following instructions.
To customize video keyframe proxies:
1. To set up FlipFactory to capture thumbnails from videos, open Manage

Factories by clicking Start > Programs > Telestream > FlipFactory > FlipFactory
Console > Login.
2. Select the otmm_import_default factory.
3. Open the codec section of Keyframe product under otmm_import_default

factory.
4. Set Capture Interval to 10 seconds.
5. Adjust the Thumbnail size.
6. Save the factory settings.
7. Verify that otmm_import_default is set as the value of the

VIDEO_TRANSCODE_JOB setting, as follows:
"VIDEO_TRANSCODE_JOB"="otmm_import_default"
Note: The VIDEO_TRANSCODE_JOB setting is located under the VIDEO

\TRANSCODE component, which belongs to the VIDEO configuration
group. This group is accessible from the Settings page in the Web
Administration tool. For more information about viewing settings, see
section 2.13.2.2 “Viewing a component and properties” in OpenText Media

11.3.4 Integrating Media Management and FlipFactory

This section describes how to setup and configure FlipFactory to integrate it with
Media Management.
Note: Factories can be built on the FlipFactory server to configure different

transcode jobs. Build each factory to transcode and deliver media based on
your workflow and production requirements.
For Media Management APIs to interact with FlipFactory APIs, configure the
settings using the VIDEO\TRANSCODE component, which belongs to the Video
configuration group. You need to update the host, port, and factory names of the
factories required for Media Management to transcode audio and video assets. The
Video group is accessible from the Settings page in the Web Administration tool.
For more information about editing components, see section 2.13.2.3 “Editing a
component and properties” in OpenText Media Management - Administration Guide
(MEDMGT-AGD). The following is a sample configuration.
FlipFactory configuration example
"UNC_REPOSITORY"="\\TranscodeSrv\video_staging"
"VIDEO_TRANSCODE_CLASS"="com.artesia.video.transcode.services.FlipFac
toryTranscodeServices"
"TRANSCODE_HOST"="FLIPFACTORY_SERVER"
Note: If FlipFactory is configured in the FactoryArray/Load Balance Group,

provide all FlipFactory server details by providing the primary node first
followed by secondary nodes, like in the following example:
TRANSCODE_HOST="SERVER1:9000,SERVER2:9000"
When you submit jobs to the FlipFactory server, the FlipFactory server tries to
submit the job to the primary node first. If the primary node fails to respond,
the FlipFactory server falls back to the next node in the list. If the port number
is the default for all FlipFactory servers in FactoryArray, then enter the port
details in the TRANSCODE_PORT setting. If any port details are missed in the
above entry, the FlipFactory server uses the TRANSCODE_PORT value of the
setting as the default. The TRANSCODE_PORT setting is located under the VIDEO
\TRANSCODE component, which belongs to the Video configuration group.
For more information, see section 2.13.2.3 “Editing a component and
properties” in OpenText Media Management - Administration Guide (MEDMGT-
AGD).
"TRANSCODE_PORT"="9000"
"PROXY_VIDEO_TRANSCODE_JOB"="otmm_import_proxy"
"EXPORT_VIDEO_TRANSCODE_JOB"="otmm_export_avi"
"AUDIO_TRANSCODE_JOB"="otmm_import_audio"
"EXPORT_VIDEO_TRANSCODE_JOB_WMV"="otmm_export_wmv"
"EXPORT_VIDEO_TRANSCODE_JOB_IPHONE"="otmm_export_iphone"
"EXPORT_VIDEO_TRANSCODE_JOB_MOBILE"="otmm_export_mobile"

"EXPORT_VIDEO_TRANSCODE_JOB_MOV"="otmm_export_quicktime"
"EXPORT_VIDEO_TRANSCODE_JOB_F4V"="otmm_export_f4v"
"EXPORT_VIDEO_TRANSCODE_JOB_MP4"="otmm_export_mpeg4"
"EXPORT_VIDEO_TRANSCODE_JOB_AVI"="otmm_export_avi"
"DEFAULT_FRAMERATE"="29.97"
"TRANSCODE_USER"="otmm"
"DEFAULT_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mpeg4"
"MOV_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_quicktime"
"F4V_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_f4v"
"FLV_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_flash"
"AVI_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_avi"
"WMV_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_wmv"
"MP4_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mpeg4"
"MPG_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mpg"
"MXF_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mxf"
"3GP_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mobile"
Also, for both Windows and Linux, note the following under the VIDEO
\TRANSCODE component, which belongs to the VIDEO configuration group:
"VIDEO_BASE_URL"="http://IIS_Server/ IIS_App"
WINDOWS
Navigate to the VIDEO_FILE_STAGING_AREA property, and enter \
\TranscodeSrv\video_staging in the Value column.
LINUX
Navigate to the VIDEO_FILE_STAGING_AREA property, and enter /usr/local/
mount_point/video_staging in the Value column.
Note: The Video group is accessible from the Settings page in the Web
Administration tool. For more information about editing components, see
The following video configuration samples have the following assumptions:

• The staging area folder name is staging area.
• The transcode output working file area is transcode_wf.
• The FlipFactory server host name is flipFactorySrv in which the H: drive has
the staging area and transcode working file area.
Example 11-5: Windows sample video staging configurations
The staging area, VIDEO_FILE_STAGING_AREA, needs to be updated under

the CONTENT\CONFIG component, which belongs to the General
configuration group, as follows:
"VIDEO_FILE_STAGING_AREA"="\\flipFactorySrv\staging_area"

For FlipFactory, the transcode working file directory has to be configured in

the FlipFactory server factory product destination and must be a network
UNC path.
Note: The General group is accessible from the Settings page in the Web
Administration tool. For more information about editing components, see
Example 11-6: Linux sample video staging configurations
On Linux, Windows shared directories cannot be accessed by using the UNC

staging_area and transcode_wf are mounted to a Linux directory as
\\flipFactorySrv\staging_area mount to /usr/local/share/

staging_area
\\flipFactorySrv\transcode_wf mount to /usr/local/share/

transcode_wf
You must update component settings as shown in the following example:
"UNC_REPOSITORY"="\\flipFactorySrv\staging_area"
Notes
• The VIDEO_FILE_STAGING_AREA setting is located under the CONTENT
• The UNC_REPOSITORY and WORKING_PATH settings are located under the
VIDEO\TRANSCODE component, which belongs to the Video
configuration group.
• The General and Video group are accessible from the Settings page in the
Web Administration tool. For more information about editing components,
For FlipFactory, the transcode working file directory has to be configured in the
factory product destination of FlipFactory server and must be in the network UNC
path.
"UNIX_VIDEO_WORKING_AREA_UNC" = "\\flipFactorySrv\transcode_wf\"

"UNIX_RELATIVE_VIDEO_WORKING_AREA" = "/usr/local/share/transcode_wf/"
Note: The UNIX_VIDEO_WORKING_AREA_UNC and

UNIX_RELATIVE_VIDEO_WORKING_AREA settings are located under the VIDEO
\TRANSCODE component, which belongs to the Video configuration group.
This group is accessible from the Settings page in the Web Administration
tool. For more information about editing components, see section 2.13.2.3
11.4 Configuring video with Telestream Vantage

Media Management includes video and audio transcoding with the integration of
Telestream Vantage, which powers video metadata, import, and export. This section
describes the steps necessary to configure your Media Management installation for
video with the Telestream Vantage server.
open/69371555).
To install Telestream Vantage:
Follow the instructions in the Vantage Domain Management Guide (http://

www.telestream.net/pdfs/user-guides/
Vantage_Domain_Management_Guide_6.3.pdf).
To set up workflows in Vantage:
1. Sign in to the server where Media Management is installed.
2. Locate the Vantage transcode configuration file in <TEAMS_HOME>\data\

videotransformer_workflows.zip.
3. Copy <TEAMS_HOME>\data\videotransformer_workflows.zip to the Vantage

server.
4. Verify that the Vantage services are running.
5. Extract the videotransformer_workflows.zip file into a folder.
6. Navigate to the videotransformer_workflows\vantage\Workflows\

MediaMgmt folder in the extracted location and make the following changes in
each file:
a. Replace all occurrences of the string $OTMM_HOST_NAME$ with the Media

Vantage server.

11.4. Configuring video with Telestream Vantage
b. Replace all the occurrences of $OTMM_HTTP_PORT$ with the HTTP port

where the OTMM server was configured. In the case of a single node, the
default value is 11090. If a load balancer or proxy is configured, specify the
port as the HTTP port on which the load balancer or proxy is running. The
OTMM host name and HTTP port configured in the above steps are used to
make web service notifications after a transcode job is executed on the
Vantage server. So make sure the OTMM host configured in the above step
is accessible from the Vantage server over the HTTP port configured above.
7. Open the Vantage Management Console, sign in as a user with the Vantage
administrator role, and perform the following steps:
a. Navigate to Workflow Design Items > Media Nicknames and import all
the media nicknames in the videotransformer_workflows\vantage
\MediaNicknames folder in the extracted location.
b. Navigate to Workflow Design Items > Metadata Labels and import all the
metadata labels in the videotransformer_workflows\vantage
\MetadataLabels folder in the extracted location.
c. Navigate to Workflow Design Items > Attachment Nicknames and import
all the attachment nicknames in the videotransformer_workflows\
vantage\AttachmentNicknames folder in the extracted location.
8. Open Vantage Workflow Designer and sign in as a Vantage user and perform
the following steps to import all the default Vantage Workflows into a category.
a. Select File > Create New Category and create a new category, for example,
MediaMgmt.
b. Import all the workflows in the videotransformer_workflows\vantage
\Workflows\MediaMgmt folder in the extracted location by right-clicking
the newly created category in the left-hand side pane and selecting Import
Workflows.
c. Click File > Batch Workflow Operations and select all the workflows
associated with the above category and click Activate.
Media Management includes pre-configured workflows that work with Vantage by

importing them into a category. The workflows, which are configured through the
following transcode job settings, are ready to use after the configurations described
in this section are complete:
Note: The following transcode job settings are located under the VIDEO
\TRANSCODE component, which belongs to the VIDEO group. For more
information, see section 2.13.2.3 “Editing a component and properties” in

The following additional pre-configured factories are part of the optional export
transformers which are installed separately.
Note: The above workflows and factories are pre-configured. Do not modify
them unless you need to create your own custom workflows. The settings are
located under the VIDEO\TRANSCODE component, which belongs to the
VIDEO configuration group. This group is accessible from the Settings page in
the Web Administration tool. For more information, see section 2.13.2
“Configuring components” in OpenText Media Management - Administration
Guide (MEDMGT-AGD).
11.4.1 Integrating Media Management with Vantage

Workflows can be built on the Vantage server to configure different transcode jobs.
Build each workflow to transcode and deliver media based on your workflow and
production requirements.
For Media Management APIs to interact with Vantage APIs, configure the VIDEO
\TRANSCODE component, which belongs to the Video configuration group. You
need to update the host and workflow names of the workflows required for Media
Management to transcode audio and video assets.
The following is a sample configuration.

11.4. Configuring video with Telestream Vantage
Example 11-7: Vantage configuration
"VIDEO_TRANSCODE_CLASS"="com.artesia.video.transcode.services.
VantageTranscodeServices"
"TRANSCODE_HOST"="http://Vantage_SERVER:8676"
TARGET_PATH - \\<transcode server host>
\<transcode_working_folder>
Notes
• If Vantage is configured in the Array/Load Balance group, include all

Vantage server details by providing the primary node first followed by
secondary nodes like in the following example: TRANSCODE_HOST="http://
SERVER1:8676,http://SERVER2:8676"
• The Video group is accessible from the Settings page in the Web
Guide (MEDMGT-AGD).
"PROXY_VIDEO_TRANSCODE_JOB"="otmm_import_proxy"
"EXPORT_VIDEO_TRANSCODE_JOB"="otmm_export_avi"
"AUDIO_TRANSCODE_JOB"="otmm_import_audio"
"EXPORT_VIDEO_TRANSCODE_JOB_WMV"="otmm_export_wmv"
"EXPORT_VIDEO_TRANSCODE_JOB_IPHONE"="otmm_export_iphone"
"EXPORT_VIDEO_TRANSCODE_JOB_MOBILE"="otmm_export_mobile"
"EXPORT_VIDEO_TRANSCODE_JOB_MOV"="otmm_export_quicktime"
"EXPORT_VIDEO_TRANSCODE_JOB_F4V"="otmm_export_f4v"
"EXPORT_VIDEO_TRANSCODE_JOB_MP4"="otmm_export_mpeg4"
"EXPORT_VIDEO_TRANSCODE_JOB_AVI"="otmm_export_avi"
"TRANSCODE_CATEGORY"="MediaMgmt"
"DEFAULT_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mpeg4"
"MOV_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_quicktime"
"F4V_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_f4v"
"FLV_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_flash"
"AVI_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_avi"
"WMV_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_wmv"
"MP4_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mpeg4"
"MPG_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mpg"
"MXF_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mxf"
"3GP_EXPORT_CLIP_TRANSCODE_JOB"="otmm_export_mobile"
Also, for both Windows and Linux, note the following under the VIDEO
\TRANSCODE component, which belongs to the VIDEO configuration group:

Administration tool. For more information about editing component settings,
WINDOWS
"VIDEO_FILE_STAGING_AREA"="\\TranscodeSrv\video_staging"
LINUX
"VIDEO_FILE_STAGING_AREA"="/usr/local/mount_point/video_staging"
Sample video staging configurations
The following video configuration samples have the following assumptions:

• The staging area folder name is staging area.
• The transcode output working file area is transcode_wf.
• The Vantage server host name is VantageSrv in which the H: drive has the
staging area and transcode working file area.
Example 11-8: Windows
You must update the staging area setting as follows:
"VIDEO_FILE_STAGING_AREA"="\\VantageSrv\staging_area"
Notes
tool. For more information about how to edit settings, see section 2.13.2.3
• In Vantage, the transcode working file directory has to be configured in the
Vantage server factory product destination and must be a network UNC
path.
Example 11-9: Linux
On Linux, Windows shared directories cannot be accessed by using the UNC

staging_areaand transcode_wf are mounted to a Linux directory as
"\\VantageSrv\staging_area" mount to /usr/local/share/

staging_area

11.5. Configuring video using FFmpeg
"\\VantageSrv\transcode_wf" mount to /usr/local/share/

transcode_wf
You must update the settings as shown in the following example:
"UNC_REPOSITORY"="\\VantageSrv\staging_area"
Notes
tool. For more information about how to edit settings, see section 2.13.2.3
• The UNC_REPOSITORY and WORKING_PATH settings are located under the
VIDEO\TRANSCODE component, which belongs to the Video
configuration group. For more information about how to edit settings, see
• In Vantage, the transcode working file directory has to be configured in the
factory product destination of the Vantage server and must be in the
network UNC path:
"UNIX_VIDEO_WORKING_AREA_UNC" = "\\VantageSrv\transcode_wf\"
11.5 Configuring video using FFmpeg

FFmpeg supports video imports, exports, and metadata extraction in OTMM. Prior
to using FFmpeg to convert files, you need to do the following:
1. Install FFmpeg.
2. Integrate Media Management with FFmpeg.
3. Run the FFmpeg transcoder.

11.5.1 Installing FFmpeg

For more information about supported codecs and formats, see https://
www.ffmpeg.org/
To install FFmpeg:
1. Download FFmpeg from https://www.ffmpeg.org/.
Tip: OpenText recommends that Media Management and FFmpeg run on

the same operating system.
For more information about versions, see OpenText Media Management
2. Extract the downloaded static builds to the server where you want FFmpeg to
run.
3. Include the folder’s path that contains executable files from the extracted
location in operating system user’s PATH environment variable.
WINDOWS
An old version of ffmpeg.exe is available in the ImageMagick
installation directory. Rename ffmpeg.exe to _ffmpeg.exe in the
ImageMagick installation directory to use the latest version of the file.
LINUX
Edit the ${TEAMS_HOME}/bin/artesia-process-manager-wrapper-
unix.conf service configuration file to append the location of FFmpeg
in PATH_TO_CUSTOM_EXECUTABLES. You must do this as a separate task
in addition to editing the PATH environment variable to append the
FFmpeg location.
4. To ensure that FFmpeg is properly updated in PATH, do one of the following:
WINDOWS
Open a new command prompt, and run the following:
ffmpeg.exe
UNIX
On a terminal, run the following:
ffmpeg

11.5.2 Integrating Media Management with FFmpeg

The Media Management installation includes pre-configured settings that work with
FFmpeg by default. These settings are configured under the VIDEO\TRANSCODE
component, which belongs to the Video configuration group. This group is
accessible from the Settings page in the Web Administration tool. For more
information, see section 2.13.2.3 “Editing a component and properties” in OpenText
Media Management - Administration Guide (MEDMGT-AGD).
You can use these settings after performing the configurations described in this
section.
For Media Management APIs to interact with FFmpeg, configure the settings under
the VIDEO\TRANSCODE component. This component belongs to the Video
configuration group, which is accessible from the Settings page in the Web
Administration tool. For more information about components, see section 2.13.2.3
A sample configuration is included with the installation.
Example 11-10: FFmpeg configuration

"VIDEO_TRANSCODE_CLASS"="com.artesia.video.transcode.services.
FFMpegTranscodeServices"
# Specify the TRANSCODE_HOST details where FFmpeg server as
configured. Transcode host should be configured as
‘localhost’ only if FFmpeg is running in same server as OTMM.
"TARGET_PATH"="<transcode server host>
\<transcode_working_folder>"
Note: When you use the same FFMPEG server for multiple OTMM
servers, you must use different target paths for each OTMM
server.
Specify list of servers along with port where FFmpeg is
running externally.
# "TRANSCODE_HOST"="SERVER1:port1, SERVER2:port2"
"VIDEO_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -r 1/10 -s 500x376 -f image2
OTMM__OUTPUT__FILE%4d.jpg -s 640x352 -aspect 16:9 -r 29.97 -
b:v 8000000 -b:a 96000 -ar 48000 MEDIA_TRIM_SETTINGS
OTMM__OUTPUT__FILE.mp4"
"PROXY_VIDEO_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 640x352 -aspect 16:9 -r 29.97 -b:v
8000000 -b:a 96000 -ar 48000 -ac 2 MEDIA_TRIM_SETTINGS
#The following additional settings are part of the optional
export
transformers which are installed separately
"EXPORT_VIDEO_TRANSCODE_JOB"="-loglevel warning -y -i


"AUDIO_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -b:a 128000 -ar 48000 -ac 2
MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.mp3"
"EXPORT_VIDEO_TRANSCODE_JOB_WMV"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 640x480 -aspect 1 -r 30 -b:v 1000000 -
b:a 5000 -ar 8000 -ac 1 MEDIA_TRIM_SETTINGS
OTMM__OUTPUT__FILE.wmv"
"EXPORT_VIDEO_TRANSCODE_JOB_IPHONE"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 480x360 -r 30 -b:v 9000000 -b:a 48000 -
ar 44100 -ac 1 MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.mp4"
"EXPORT_VIDEO_TRANSCODE_JOB_MOBILE"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 320x240 -r 15 -b:v 64000 -b:a 128000 -ar
44100 -ac 2 MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.3gp"
"EXPORT_VIDEO_TRANSCODE_JOB_MOV"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 720x480 -r 29.97 -b:a 64000 -ar 44100 -
ac 2 MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.mov"
"EXPORT_VIDEO_TRANSCODE_JOB_F4V"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 640x352 -aspect 4:3 -r 29.97 -b:v 128000
-b:a 96000 -ar 48000 -ac 1 MEDIA_TRIM_SETTINGS
OTMM__OUTPUT__FILE.f4v"
"EXPORT_VIDEO_TRANSCODE_JOB_MP4"="-loglevel warning -y -i
"EXPORT_VIDEO_TRANSCODE_JOB_AVI"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 320x240 -r 15 -ar 48000 -ac 1
MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.avi"
"DEFAULT_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
"MOV_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 720x480 -r 29.97 -b:a 64000 -ar 44100 -
ac 2 MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.mov"
"F4V_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 640x352 -aspect 4:3 -r 29.97 -b:v 128000
-b:a 96000 -ar 48000 -ac 1 MEDIA_TRIM_SETTINGS
OTMM__OUTPUT__FILE.f4v"
"FLV_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 640x480 -aspect 16:9 -r 30 -b:v 3000000 -
b:a 96000 -ar 44100 MEDIA_TRIM_SETTINGS
OTMM__OUTPUT__FILE.flv"
"AVI_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 320x240 -r 15 -ar 48000 -ac 1
MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.avi"
"WMV_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 640x480 -aspect 1 -r 30 -b:v 1000000 -
b:a 5000 -ar 8000 -ac 1 MEDIA_TRIM_SETTINGS
OTMM__OUTPUT__FILE.wmv"
"MP4_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i


"MPG_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__OUTPUT__FILE.mpg"
"MXF_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
50000000 -ar 48000 -ac 8 MEDIA_TRIM_SETTINGS
OTMM__OUTPUT__FILE.mxf"
"3GP_EXPORT_CLIP_TRANSCODE_JOB"="-loglevel warning -y -i
OTMM__INPUT__FILE -s 320x240 -r 15 -b:v 64000 -b:a 128000 -ar
44100 -ac 2 MEDIA_TRIM_SETTINGS OTMM__OUTPUT__FILE.3gp"
Notes
• For both Windows and Linux, note the following settings under the
CONTENT\CONFIG component, which belongs to the General
configuration group:
WINDOWS
LINUX
"VIDEO_FILE_STAGING_AREA"="/usr/local/mount_point/
video_staging"
• The FFmpeg settings use templates, such as OTMM__OUTPUT__FILE%4d,
OTMM__OUTPUT__FILE, OTMM__INPUT__FILE, and MEDIA_TRIM_SETTINGS,
that will be replaced at runtime before submitting a job to FFmpeg.
OpenText recommends that you do not edit these templates, as it will result
in errors.
• For the value of the VIDEO_TRANSCODE_JOB setting, do not change the order
of keyframe generation and proxy generation. Also, for keyframe generation,
do not add any FFmpeg command line options after the -f option. That is,
'-f image2 OTMM__OUTPUT__FILE%4d.jpg' must always be together.
The following video configuration samples assume the following:

• The staging area folder name is "video_staging".
• The transcode output working file area is "transcode_wf".
• The server host name is "TranscodeSrv", which has configured folder called,
video_staging.

• You must update the staging area using the VIDEO_FILE_STAGING_AREA setting.
For more information, see Example 11-11, “Windows video staging
configuration” on page 174 and Example 11-12, “Linux video staging
configuration” on page 174. This setting is located under the CONTENT
\CONFIG component, which belongs to the General configuration group. This
group is accessible from the Settings page in the Web Administration tool. For
more information, see section 2.13.2.3 “Editing a component and properties” in
The following are sample video staging configurations for Windows and Linux.
Example 11-11: Windows video staging configuration

Example 11-12: Linux video staging configuration

"VIDEO_FILE_STAGING_AREA"="/usr/local/share/video_staging"
11.5.3 Configuring the FFmpeg transcoder to run locally

To configure the FFmpeg transcoder to run locally, you must change the value of the
TRANSCODE_HOST setting to localhost. The TRANSCODE_HOST setting is located
under the VIDEO\TRANSCODE component, which belongs to the Video
configuration group. This group is accessible from the Settings page in the Web
Administration tool. For more information about editing settings, see section 2.13.2.3
11.5.4 Installing and configuring the FFmpeg Transcode

service to run in a multi-tenant environment or
externally
This section provides information about the prerequisites you need, as well as how
to install and configure the FFmpeg Transcode service to run in a multi-tenant
environment or externally.
The FFmpeg installer is available in the Media Management, mediamgmt_16.

3_windows.iso or mediamgmt_16.3_linux.iso. The ffmpeg_config.txt
configuration file is available in ISO in the following location:
/FFMPEG/ffmpeg_config.txt
You can install the FFmpeg Transcode service using the following methods:
Setup screens (GUI mode)

An installer presents you with setup screens where you fill in your install
values.

Note: To pre-populate the installation screens with default responses, you

can specify values of the installation parameters in the ffmpeg_config.
txt configuration file. You can edit these values during the install.
For more information, see “Installing FFmpeg Transcoder service using the
setup screens” on page 176.
Console
ffmpeg_config.txt. You cannot change these values during the installation
process. This mode requires your intervention to proceed to subsequent steps.
installation parameters in the ffmpeg_config.txt file. This file is
mandatory if you are installing using console mode.
For more information, see “Installing FFmpeg Transcoder service using the
console” on page 178.
Silent
ffmpeg_config.txt. You cannot modify values during the installation process.
This mode requires no user interaction.
installation parameters in the ffmpeg_config.txt configuration file. The
configuration file is mandatory if you are installing using silent mode.
For more information, see “Installing FFmpeg Transcoder service silently”
on page 179.
11.5.4.1 Preparing to install the FFmpeg Transcode service

FFmpeg Transcode service is supported on the following platforms:
Operating Systems
• Windows Server
• Linux
• CentOs
Databases
• Oracle
• SQL Server
• PostgreSQL
• SAP HANA

Notes
• If you are using SQL Server you must map the pre-configured user to
the schema.
• For more information, see OpenText Media Management Technical
Specifications (https://knowledge.opentext.com/knowledge/llisapi.dll/
open/69371555).
The following prerequisites are required:
Database
The FFmpeg Transcode service installation requires a separate database and a
pre-configured database user. This user must have permissions to create tables,
triggers and views. Ensure that you are able to sign in using this database user.
Notes
• If you are using Oracle 12C, in addition to the permissions mentioned
above, the database user must have permissions to use the tablespace
quota on the default tablespace and create a sequence.
• If you are using SQL Server, you must select the collation as
SQL_Latin1_General_CP1_CI_AS during the install process.
Java
You must install the JRE on the remote server and set the Java executable in the
path of the user who is running the utility. For more information, see OpenText
11.5.4.2 Installing FFmpeg Transcoder service using the setup screens
Note: To use GUI mode on Linux, you need an X-Windows interface. You need
to set DISPLAY in your environment and have an X-Windows server running
on your local computer. For example, if you have connected to the Linux server
from your Windows computer, you need to have software such as OpenText™
Exceed™ TurboX (ETX) installed and running. Be sure to set your DISPLAY in
your Linux environment prior to running the installation. For example:
where
To install the FFmpeg Transcode service using the setup screen:
1. Mount the appropriate platform specific Media Management ISO on the system
where you want to install the FFmpeg Transcode service.
Windows

Linux
2. Optional Extract the ffmpeg_config.txt from the ISO to a working location.

Provide the installation parameters required for your installation.
3. At the command prompt or on a terminal, navigate to the FFmpeg directory

that is available in the mounted location, and then enter one of the following
commands:
WINDOWS
<Mounted location>\FFMPEG>Disk1\InstData\VM\install.exe -i gui
-f <PATH_TO_ffmpeg_config.txt>
LINUX
<Mounted location>/FFMPEG>/Disk1/InstData/VM/install.bin -i gui
-f <PATH_TO_ffmpeg_config.txt>
where
-i specifies the mode of installation to be launched. The default mode is GUI, if
no mode is passed. The GUI mode launches the setup screens.
installation mode.
qualified path name for the configuration file. For example:
G:\FFMPEG\Disk1\InstData\VM\install.exe -i gui -f c:
\ffmpeg_config.txt
4. On the License Agreement page, click I accept the terms of the License
Agreement, and then click Agree.
5. On the Choose Install Folder page, provide the location were you want to
install the FFmpeg Transcode service.
6. On the Choose Install set page, for a typical install, select the Schema and
Install FFmpeg Transcode Service check boxes to install the database schema
and the FFmpeg Transcode service, which provides the minimal software to
start the FFmpeg Transcode service.
Note: In an HA (Cluster) environment, select the Database Schema and

FFmpeg Transcode service check boxes for the first node that you install.
When you are installing subsequent nodes, select only the Install FFmpeg
Transcode Service check box.
7. On the Database Configuration page, provide the required configuration

information.

8. On the FFmpeg configuration page, specify the port and shutdown mode for
the FFmpeg Transcode service. The following are the shutdown modes:
• Immediate
Terminates the FFmpeg Transcode service process when you stop the
FFmpeg Transcode service.
• Complete
Waits for all the running Transcode jobs to complete and then shuts down
when you stop the FFmpeg Transcode service.
9. On the Pre-Installation Summary page, review your selections before

continuing, and click Install.
Notes
• If any errors occur during the install, see the logs files in <FFMPEG_HOME>
\logs\installation location.
• After a successful installation, the Complete page appears. Click Done,
and then restart the system manually.
11.5.4.3 Installing FFmpeg Transcoder service using the console
installation parameters in the ffmpeg_config.txt configuration file.
To install the FFmpeg Transcoder service using the console:
WINDOWS
LINUX
2. Extract the ffmpeg_config.txt from the ISO to a location. Provide the

3. At the command prompt, navigate to the FFmpeg directory that is available in

the mounted location, and then enter one of the following commands:
WINDOWS
<Mounted location>\FFMPEG>Disk1\InstData\VM\install.exe -i
console -f <PATH_TO_ffmpeg_config.txt>

LINUX
<Mounted location>/FFMPEG>Disk1/InstData/VM/install.bin -i
console -f <PATH_TO_ffmpeg_config.txt>
where
installation mode.
file. For example:
G:\FFMPEG\Disk1\InstData\VM\install.exe -i console -f c:
\ffmpeg_config.txt
Notes
• Restart the system manually.
11.5.4.4 Installing FFmpeg Transcoder service silently
installation parameters in the ffmpeg_config.txt configuration file.
To install the FFmpeg Transcoder service silently:
WINDOWS
LINUX
2. Extract the ffmpeg_config.txt from the ISO to a location. Provide the

3. At the command prompt, navigate to the FFmpeg directory that is available in

the mounted location, and then enter one of the following commands:
WINDOWS
<Mounted location>\FFMEG>Disk1\InstData\VM\install.exe -i
silent -f <PATH_TO_ffmpeg_config.txt>

LINUX
<Mounted location>/FFMPEG>Disk1/InstData/VM/install.bin -i
silent -f <PATH_TO_ffmpeg_config.txt>
where
installation mode.
file. For example:
G:\FFMPEG\Disk1\InstData\VM\install.exe -i silent -f c:
\ffmpeg_config.txt
Notes
• Restart the system manually.
11.5.4.5 Starting the FFmpeg Transcode service

To start the FFmpeg Transcode service:
WINDOWS
Start the FFmpegTranscodeService.
LINUX
ffmpegService start
Note: You can find the generated log file in the <FFMPEG_HOME> directory.

11.6. Video configuration for clip assets
11.5.5 Uninstalling the FFmpeg Transcode service

To uninstall the FFmpeg Transcode service:
1. To launch the uninstaller, do one of the following:
WINDOWS
• Navigate to <FFMPEG_HOME>\UninstallFFmpegTranscoder folder, and

click Uninstall FFmpegTranscoder.exe.
Tip: You can also use the Control Panel to uninstall the
FFmpegTranscoder from the list of applications installed on the
server.
LINUX
Sign in as the FFmpeg installed user, navigate to $FFMPEG_HOME/
UninstallFFmpegTranscoder, and the run the following command:
./Uninstall\ FFmpegTranscoder
Note: There is a space in the name of the uninstall executable.
2. Click Uninstall.
3. Click Done.
11.6 Video configuration for clip assets

When a clip export is processed without giving any conversion, this entry
determines the output format of the video clip. The output factory/preset is
considered based upon the extension of its parent (Master) video file.
<FILE_EXTENSION>_EXPORT_CLIP_TRANSCODE_JOB
For example, while exporting a MP4 (FILE_EXTENSION) video clip asset, it uses the
factory/preset that is configured under following entry for output video clip:
"MP4_EXPORT_CLIP_TRANSCODE_JOB"="<factory name of mp4> or <mp4 preset

GUID>"
Example 11-13: Various extensions

"MOV_EXPORT_CLIP_TRANSCODE_JOB"
"F4V_EXPORT_CLIP_TRANSCODE_JOB"
"FLV_EXPORT_CLIP_TRANSCODE_JOB"
"AVI_EXPORT_CLIP_TRANSCODE_JOB"
"WMV_EXPORT_CLIP_TRANSCODE_JOB"
"MP4_EXPORT_CLIP_TRANSCODE_JOB"
"MPG_EXPORT_CLIP_TRANSCODE_JOB"
"MXF_EXPORT_CLIP_TRANSCODE_JOB"
"3GP_EXPORT_CLIP_TRANSCODE_JOB"

If any clip asset parent extension is not configured under the VIDEO\TRANSCODE
component which belongs to the VIDEO configuration group, then the following
default setting is used to submit a video transcode job, which generates output
based on the default factory/preset under it.
"DEFAULT_EXPORT_CLIP_TRANSCODE_JOB"
Notes
• The DEFAULT_EXPORT_CLIP_TRANSCODE_JOB setting is located under the
VIDEO\TRANSCODE component, which belongs to the VIDEO
configuration group. This group is accessible from the Settings page in the
Web Administration tool. For more information about how to edit settings,
• This is specific to video clip assets only. The default value is configured for
MP4, but can be changed to any format.
11.7 Configuring the Streaming server

This section includes configurations for the following Streaming servers:
• “Configuring IIS for video” on page 182
• “Configuring the Wowza Streaming Engine” on page 183
• “Configuring Apache on Linux” on page 184
• “Installing Adobe Media Server (AMS )” on page 185
11.7.1 Configuring IIS for video

open/69371555).
To setup IIS to progressively download AMS video proxies:
1. Install IIS.
2. Go to Administrative Tools / IIS.
3. Under default website, create an application.
4. Set the Alias as Video.
5. Set the Physical path to <TEAMS_REPOSITORY_HOME>.
6. Select Video and click Mime Types.

11.7. Configuring the Streaming server
7. Click Add and enter the MIME types for the various list of file name extensions
and associated content types that are served as static files by the web server.
8. Click OK and import a new video.
9. Update the following VIDEO\TRANSCODE component settings, which are

located under the Video configuration group:
"VIDEO_BASE_URL"="http://<IIS server>/<IIS app>"
"AUDIO_BASE_URL"="http://<IIS server>/<IIS app>"
Administration tool. For more information about how to edit the settings
of a component, see section 2.13.2.3 “Editing a component and properties”
in OpenText Media Management - Administration Guide (MEDMGT-AGD).
11.7.2 Configuring the Wowza Streaming Engine

Follow the instructions in this section if you want to use the Wowza Streaming
Engine to stream your video and audio assets.
open/69371555).
To configure the Wowza Streaming Engine:
1. Install Wowza using the default setting Wowza Streaming Engine.
2. On the Wowza server create a new empty folder in C:\Program Files

(x86)\Wowza Media Systems\Wowza Streaming Engine 4.0.1\
applications to add a new application. For example:
C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.
0.1\applications\otmm
3. Navigate to C:\Program Files (x86)\Wowza Media Systems\Wowza

Streaming Engine 4.0.1\conf\ and make a copy of the vod folder and rename
it to otmm16. For example:
C:\Program Files (x86)\Wowza Media Systems\Wowza Streaming Engine 4.
0.1\conf\otmm
4. Edit the Application.xml file, located in C:\Program Files (x86)\Wowza

Media Systems\Wowza Streaming Engine 4.0.1\conf\otmm16, and on line 32,
enter the otmm repository shared folder. For example:
<Storage Dir>\\otmm_server\repository</Storage Dir>
Note: The shared folder should be accessible from the Wowza Server. The
User Account Log on options of the Wowza services can be updated with
details of a user who has access to the otmm repository shared folder.

5. Restart the Wowza Streaming Engine 4.0.1 and Wowza Streaming Engine
Manager 4.0.1 services.
6. On the Media Management server, edit the following settings which are located
under the VIDEO\TRANSCODE component, which belongs to the Video
configuration group:
"VIDEO_BASE_URL"="rtmp://<Wowza server name>:<port number>/
<application>/_definst_/mp4:"
"AUDIO_BASE_URL"="rtmp://<Wowza server name>:<port number>/
<application>/_definst_/mp3:"
Notes
Administration tool. For more information about how to edit the
settings of a component, see section 2.13.2.3 “Editing a component and
(MEDMGT-AGD).
• The default port number for Wowza is 1935.
7. Restart the OpenText Media Manager service.
11.7.3 Configuring Apache on Linux

The Apache HTTP server is the default web server provided for Linux.
To enable Apache:
1. Check if Apache is installed by issuing the following command as the root user:
rpm –qa | grep -i http
If necessary, install the Apache httpd service.
2. Run the following to check if the Apache httpd service is running:

service –-status-all | grep http
3. Map URL to the OTMM Repository.

To access the video files, the OTMM repository should be available in the
DocumentRoot of the Apache server. The simplest way to map the URL is to
create a symbolic link to <TEAMS_REPOSITORY_HOME> in the DocumentRoot
folder.
Notes
• The link name is required because it should be used to configure the
BaseURL in the component settings. Update the following settings
which are located under the VIDEO\TRANSCODE component, which
belongs to the Video configuration group:
"VIDEO_BASE_URL"=" http://servername/linkname"

"AUDIO_BASE_URL"=" http://servername/linkname"
Administration tool. For more information about how to edit the
settings of a component, see section 2.13.2.3 “Editing a component and
(MEDMGT-AGD).
4. Enable FollowSymlinks Options. Search for FollowSymlinks in httpd.conf and

add the + prefix. The default location for the httpd configuration file is /etc/
httpd/conf/httpd.conf.
5. Restart the Apache server.
11.7.4 Installing Adobe Media Server (AMS )

Media Management software creates AMS proxies of imported video. These videos,
especially long form videos, need a streaming server to view the proxies. This is an
optional step, which is needed for streaming of proxy videos, especially if they are
long-form content. This section explains the steps needed to configure AMS server in
a Windows environment.
You may use an existing installation or download the Adobe Media Server from:
http://www.adobe.com/products/adobe-media-server-standard.html
A suitable license is needed depending on your needs. The options are explained on
the website.
You may install AMS on the same host as Media Management or on a separate host.
AMS hosted on the application server enables a dedicated AMS with faster access to
the media.
To install AMS:
1. Follow the instructions for the appropriate Installer and set up AMS.
2. Select the default ports for Adobe Media Server , 1935, and HTTP Proxy, 8134.
Accept the Apache install option to enable HTTP delivery.
Notes
• The HTTP Proxy feature enables Adobe Media Server to redirect

requests for HTTP delivery to the Apache server.
• Ports 1935 and 8134 must be accessible to the clients. Make sure the
firewall settings are configured to allow traffic to and from these ports
on the host running Adobe Media Server .

11.7.4.1 Configuring Adobe Media Server

The following is a summary of the AMS configuration process:
• If AMS is running on a separate host, create a common Windows user called

fmsuser on both OTMM server and AMS with permissions to play files from the
repository folder (command line: lusrmgr.msc > Add User).
• Create a new application on AMS named video.
Tip: For more information, see “Setting up AMS application video”

on page 186.
• Map the Repository to the AMS video virtual directory.
• Enable the firewall to stream RTMP protocol.
Figure 11-4: AMS Configuration
Note: To avoid port conflicts, do not run AMS on the same server as IIS or
Apache unless AMS runs on a separate port.
11.7.4.2 Setting up AMS application video
Note: These instructions represent the simplest configurations for a quick start.
For more complex configurations, see the Adobe Media Server documentation.
1. Change directories to {AMS-Root}/Application/. You should see the LIVE and

VOD folders.
2. Create a new folder called VIDEO. This is the AMS application.
3. Copy the contents of the VOD folder to the VIDEO folder.
4. In the VIDEO folder, update Application.XML in the StreamsManagement

section as follows:

<StreamManager>
<VirtualDirectory>
<!-- Specifies application specific virtual directory mapping for
recorded streams. -
->
<Streams>/;<path to repository> </Streams>
</VirtualDirectory>
Where <path to repository> refers to the TEAMS_REPOSITORY folder,

which may take the form of a UNC path \\<Repository server>\<shared
repository>. You can also use a local path to the repository if they
are on the same server or are network mounted. For example, C:
\repository (for a locally installed Media Management server)or N:
\repository for a remotely installed AMS, where N: is a locally mapped
drive. You may map the drive with the Windows user ID with sign in at
startup enabled using Windows Explorer->map.
5. If HTTP streaming is included, make sure to set webroot Apache2.2/conf/

httpd.conf folder to the TEAMS_REPOSITORY_HOME.
Note: The Apache HTTP service should be started with a user who has
administrative privileges and has access to TEAMS_REPOSITORY_HOME.
6. Restart AMS to apply the changes made to application.xml.
11.7.4.3 Setting up Windows users

When AMS is installed on a server separate from Media Management, it needs to
access the repository where the video proxies are stored. This section assumes that
AMS and Media Management are on Windows. Additional changes are needed if
Media Management is installed on Linux.
You must create a common Windows user, fmsuser on both Media Management
server and AMS with permissions to play files from the repository folder.
Note: Both the AMS service and the AMS administrative service must be set
up with the shared user as the “Log on” user.
To set up Windows users:
1. Run lusrmgr.msc to create fmsuser with the name of the AMS user on AMS
server.
2. Click Server Manager > Configuration > Services > Adobe Media Server >
properties. Change the log on user ID to fmsuser.
3. Run lusrmgr.msc to create fmsuser with the name AMS user on the Media
Management server. Make sure the passwords match and are correctly set.

4. Click Repository > properties and then add fmsuser as a user and in the Share
and Security tabs and grant at least read permissions.
5. Restart Adobe Media Server. You can also restart Adobe Media Administration
Server with the same user credentials.
11.7.4.4 Setting up the base URL for the AMS streaming server
To set up the base URL for AMS streaming server, you must edit the values of the
following settings:
"VIDEO_BASE_URL"="rtmp://<AMS server>/<AMS app>/_definst_/mp4:"
"AUDIO_BASE_URL"="rtmp://<AMS server>/<AMS app>/_definst_/mp3:"
Note: These settings are located under the VIDEO\TRANSCODE component,

which belongs to the Video configuration group. This group is accessible from
the Settings page in the Web Administration tool. For more information about
editing settings, see section 2.13.2.3 “Editing a component and properties” in
11.7.4.5 Network configuration for streaming and Apache downloads

Adobe Media Server (AMS) uses the RTMP protocol for streaming video and has an
optional integrated HTTP server, which allows a single hosted solution for all
interactive and streaming applications with progressive delivery when needed. If
you have your own web server (either locally or remotely hosted), then you may opt
not to install the integrated HTTP server. In these cases, you can configure AMS to
send HTTP requests to external web servers using HTTP proxying.
HTTP proxying is enabled by default and is configured to local port 8134. AMS
normally listens for RTMPT connections on port 80, which is the default port for
HTTP connections. If a RTMPT request is blocked (for example, by firewall rules) or
AMS receives an unknown request through the tunneling port, AMS will forward
the request across the configured proxy port. For more information about HTTP
Proxy configuration parameters, see the Adobe online documentation:
http://kb2.adobe.com/cps/408/kb408205.html
For more information about administering and configuring Adobe Media Server ,
see https://helpx.adobe.com/adobe-media-server/config-admin/topics.html.

11.8. Optional video configurations
11.7.4.6 Securing AMS playback in Media Management

Adobe Media Server has several configuration options for securing video URLs to
prevent someone from accessing video content without an authentication session. By
using the AMS mechanism to check the domain of the SWF requesting the file, the
playback of the URLs can be locked to allow only the SWF files that have initiated
from the Media Management domain. The end result is that URLs will only be
accessible through the Media Management application—any other application
trying to play back the file will be rejected.
For more information about configuration security features, see the Adobe Media
Server Configuration and Administration documentation on the Adobe website.
11.8 Optional video configurations

To install the optional video transformers:
1. Run the following command from <TEAMS_HOME>\install\ant:

ant install-video-export-transformers
2. To remove any of the installed transformers, using the transformer

TRANSFORMER_ID ARTESIA.TRANSFORMER.STAGING.VIDEO, delete the entries for
the installed transformers from the following tables:
TRANSFORMER_INSTANCES
TRANSFORMER_INSTANCE_VALUES
Note: If you already executed this command in your environment in

releases prior to 7.0.4, then you should execute the following ant target to
overwrite the default target GUID entries in the database with the new
transcode job entries:
ant update-video-export-transformers

Chapter 12
Completing optional installation activities
12.1 Disabling use of Global Unique Identifiers

(GUIDs) for asset identifier
When a new asset is created, Media Management generates by default a 40-byte
universally unique UOI (Asset) ID. Universally-unique UOI IDs facilitate sharing
assets across multiple databases. However, they are also cryptic and can be
cumbersome.
After Media Management is installed, it is possible to disable generation of

universally-unique UOI IDs, causing Media Management to instead use sequential
numbers when generating UOI IDs.
To disable the generation of universally-unique UOI IDs:
• Locate the USE_SHAGEN setting, and change the value to N.
Note: The USE_SHAGEN setting is located under the IMPORT\SERVER

component, which is belongs to the Import configuration group. You can
access configuration groups through the Settings page. For more
information about configuration groups and components, see section
2.13.2 “Configuring components” in OpenText Media Management -
12.2 Installing additional image transformers

The Media Management installation package is delivered with optional transformers
that can be installed and configured for the following:
Image Conversions
These conversions may be used when exporting images to convert them to
specific formats and sizes. For more information about image transformer
settings, see OpenText Media Management - Integration Guide (MEDMGT-AIN).
Video Conversions
These conversions may be used when exporting videos to convert them to
specific formats. For more information about video conversion settings, see
OpenText Media Management - Integration Guide (MEDMGT-AIN). For
information on optional video configurations, see “Optional video
configurations” on page 189.

Chapter 12 Completing optional installation activities
12.2.1 Image conversions

To convert images:
1. You can install the optional image transformers by running this command from
the <TEAMS_HOME>/install/ant directory:
ant install-image-transformers
2. If you need to remove any of the installed transformers, delete the entries for
the installed transformers from the following tables in the order specified:
a. EXPORT_TRANS_CONTENT_TYPE_MAP
b. TRANSFORMER_INSTANCES
c. TRANSFORMER_ATTRIBUTES
d. TRANSFORMERS
12.2.2 Installing additional transformers

To install additional image transformers:
1. Run the following command from the <TEAMS_HOME>/install/ant directory:

ant install-additional-transformers
2. If you need to remove any of the installed transformers, delete the entries for
the installed transformers from the following tables in the order specified:
1. EXPORT_TRANS_CONTENT_TYPE_MAP
2. TRANSFORMER_INSTANCES
3. TRANSFORMER_ATTRIBUTES
4. TRANSFORMERS

Chapter 13
Starting OTMM
Note: In the current release of OTMM, the OpenText Indexer service is not
automatically started, stopped, or restarted with the Media Management
service. You must manage the Indexer service independently. Start, stop or
restart the OpenText Indexer service only after the corresponding operation is
successful for the Media Management service. This is applicable to all the
modes of managing the Media Management application.
13.1 Starting Media Management as a Windows

service
To start Media Management as a Windows service:
1. Click Windows Start Menu > All Programs > Administrative Tools > Services.
2. Select the OpenText Media Manager Service.
Note: The OpenText Media Manager service must be running successfully

before you can start any of the other Media Management services, such as
the OpenText Indexer service.
3. Click Start. If Media Management and the database are on different servers, you
can configure Media Management to start automatically.
13.2 Starting Media Management on Linux

To start Media Management on Linux:
1. Sign out of Media Management to allow your environment to set up properly.
2. Sign in to Media Management.
3. To start the Media Management server, run the following command:

mediamanagement-process-manager start
Note: The OpenText Media Manager service must be running successfully

before you start any of the other Media Management services, such as the
OpenText Indexer service.
Tips
• To stop the Media Management server, run the following command:
mediamanagement-process-manager stop

Chapter 13 Starting OTMM
• To restart the Media Management server, run the following command:

mediamanagement-process-manager restart
• These commands stop and restart the Media Management server only.
You must stop and restart the other Media Management services, such
as the OpenText Indexer service, separately.
13.3 Starting the OpenText Indexer as a service

The OpenText Media Manager service must be running successfully before you start
the OpenText Indexer service.
To start the OpenText Indexer service as a service on Windows:
1. Select Windows Start Menu > Programs > Administrative Tools > Services.
2. Select the OpenText Indexer service entry.
3. Start or stop the service by clicking Start or Stop.
To start the OpenText Indexer service on Linux:
• On a terminal, run the following command:

indexer-process-manager start
Tips
• To stop the service, run the following command:
indexer-process-manager stop
• To restart the OpenText Indexer service, run the following command:
indexer-process-manager restart

Chapter 14
Upgrading Media Management
The Media Management 16.3 upgrade supports upgrade installations from Media
Management version 16.2. This includes Creative Review; the 16.3 upgrade supports
upgrade installations from version 16.2.
This chapter provides upgrade instructions for Windows and Linux upgrades.
The Media Management upgrade is a suite of automated routines to migrate the

application configuration and database from a 16.2 instance to a 16.3 instance. It is
an in-place upgrade that overwrites the existing application installation and makes
updates to the database and installation directories. Because this process involves
overwriting, all the extensions and customizations will be lost. After the upgrade is
complete, you need to re-apply the customizations and extensions.
Important
To provide the ability to analyze image assets and apply the results in the
metadata of assets, you must install Rich Media Analysis Service. After
installing this service, you must perform tasks to activate the service and to
make image assets eligible for analysis. For more information, see the
following:
• “Prerequisites” on page 83
• Section 2.10 “Media Analysis” in OpenText Media Management -
Administration Guide (MEDMGT-AGD)
14.1 Upgrading OTMM

This section describes the steps that you need to do before upgrading to Media
Management 16.3 as well as during the upgrade.
The upgrade program is delivered on the Media Management ISO and guides you
through the upgrade of the schema and application.

Chapter 14 Upgrading Media Management
14.1.1 Planning the OTMM upgrade

Before you begin the OTMM upgrade process, you must do the following:
1. Shut down Media Management as follows:
WINDOWS
Stop the OpenText Media Manager service.
LINUX
mediamanagement-process-manager stop
Note: Verify that the OpenText Indexer service is not running.
2. Back up Media Management. Because OTMM provides an in-place upgrade, the

following components are modified during the upgrade:
• <TEAMS_HOME>
Important
Take special care to back up the servers folder where the OTDS
sign-in information is stored. The license files are also stored in this
location.
• Your database.
• Any customizations and configurations you have deployed in OTMM.
3. Back up all your customization configurations performed in OTMM. You may

need to reapply the configurations and redeploy the customizations when the
upgrade is completed.
a. Changes to the HTML5 UI in war/otmmux.war.

b. In general, customizations and configuration changes within JBOSS_HOME,
TOMEE_HOME and TEAMS_HOME/ear will need to be redeployed.
4. Linux - Uninstall the previous version of ImageMagick. For example, 7.0.3-8.
5. Upgrade OTDS to latest version before beginning the Media Management

upgrade. For more information, see OpenText Media Management Technical
69371555).
Notes
• OTDS is supported on the Solaris platform. It is not a requirement to

migrate these products to the Linux platform.

14.1. Upgrading OTMM
14.1.2 Upgrading using the setup screens on Windows

To upgrade using the setup screens on Windows:
1. Mount the Windows Media Management ISO image, mediamgmt_16.

3_windows.iso, on the Media Management application server, and then sign in
as the Media Management Windows user.
• At the command prompt, start the Media Management installer by entering

the following:
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.bat
• Double-click the install.bat file.
Next:

• Click WildFly and enter the location of the Wildfly home directory.
• Click TomEE and enter the location of the TomEE home directory.
5. On the Execution Type page, click Upgrade, and then click Next.
6. On the Choose Product Features page, for a typical upgrade, select the Schema
and Application check boxes to upgrade the schema and application, providing
the minimal software to start the Media Management application after
installation.
Note: In an HA (Cluster) environment, select the Schema and Application

check boxes for the first node you upgrade, and select only the
Application check box when upgrading the subsequent nodes.
7. On the Database Schema Configuration page, enter any missing database

schema configuration information, and then click Next.
Important
If the selected database is SQL Server, then you must provide the correct
port number. For example, the port number of the default instance or
named instance on which the Media Management database will be
created.

Notes
• Make sure to supply the same Media Management database user

credentials that are set for the current installation. These values will not
be uploaded to the user interface during the upgrade. You must
manually provide the SQL Server credentials.
test the connectivity to the database with the configured parameters. If
upgrading, only the database admin user details are validated, not the
Media Management database user details.
• Oracle users - Clear the Create Tablespace check box.
• Oracle users - If values were not automatically populated for the data
file directory and index file directory, you do not need to enter values
for these fields.
8. On the Execution Summary page, review your selections.
9. Click Install to begin the upgrade process.
Notes
• If any errors occur during the upgrade, see “Continuing after upgrade
errors” on page 202.
• After a successful upgrade, the Complete page appears. When the
upgrade is complete, you are prompted to restart the system. If you do
not restart the system, the application may not work or behave as
expected.
14.1.3 Upgrading using the setup screens on Linux

you through the upgrade of the schema and application.
Note: To use GUI mode on Linux, you need an X-Windows interface. You need
to set DISPLAY in your environment and have an X-Windows server running
on your local computer. For example, if you have connected to the Linux server
from your Windows computer, you need to have software such as OpenText™
Exceed™ TurboX (ETX) installed and running. Be sure to set your DISPLAY in
your Linux environment prior to running the installation. For example:
where

To upgrade using the setup screens on Linux:
1. Mount the Linux Media Management ISO, mediamgmt_16.3_linux.iso, on the

Media Management application server and sign in as the Media Management
user.
2. On a terminal, start the OTMM installer by entering the following:

<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.sh
Next:

• Click WildFly and enter the location of the Wildfly home directory.
• Click TomEE and enter the location of the TomEE home directory.
5. On the Execution Type page, click Upgrade, and then click Next.
6. On the Choose Product Features page, for a typical upgrade, select the Schema
and Application check boxes to upgrade the schema and application, providing
the minimal software to start the Media Management application after
installation.
Note: In an HA (Cluster) environment, select the Schema and Application

check boxes for the first node you upgrade, and select only the
Application check box when upgrading the subsequent nodes.
7. On the Database Schema Configuration page, enter any missing database

schema configuration information, and then click Next.
Notes
• Make sure to supply the same Media Management database user

credentials that are set for the current installation. These values will not
be uploaded to the user interface during the upgrade.
test the connectivity to the database with the configured parameters. If
you are upgrading, only the database admin user details are validated,
not the Media Management database user details.
• Oracle users - Clear the Create Tablespace check box.

• Oracle users - If values were not automatically populated for the data
file directory and index file directory, you do not need to enter values
for these fields.
8. On the Execution Summary page, review your selections before continuing.
9. Click Install to begin the upgrade process.
Notes
• If any errors occur during the upgrade, see “Continuing after upgrade
errors” on page 202.
• After a successful upgrade, sign out, and then sign in using the Linux
user account that was used to install Media Management.
14.1.4 Upgrading using the console

You can upgrade Media Management using the console on both Windows and
Linux platforms. This requires no X-Windows support and runs with no interface
windows. All messages are displayed as text in the console window.
You require the <ISOPATH>/OTMM/mediamanagement_config.txt file for the

console upgrade.
To upgrade using the console:
1. Copy the mediamanagment_config.txt file to a local folder and edit the file to
match the version 16.3 installation values.
Tip: You can find the current values can be found in the following
locations:
• <TEAMS_HOME>/install/ant/build.cfg file
Notes
• Because you are upgrading, you are not required to update the OTDS
configuration and video configuration settings in the
mediamanagement_config.txt file.
In the DATABASE SELECTION settings, set the values of the following
settings to 0 or leave them empty:
• Oracle - CREATE_TABLE_SPACE
• Postgres - CREATE_POSTGRESQL_TABLE_SPACE
2. Mount the appropriate platform specific Media Management ISO,

mediamgmt_16.3_windows.iso or mediamgmt_16.3_linux.iso.
3. At the command prompt or on a terminal, enter one of the following

commands:

WINDOWS
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.bat -i console -f
<FULL_PATH_TO>/mediamanagement_config.txt
LINUX
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.sh -i console -f
4. Follow the prompts to complete the upgrade.
5. Restart the system after a successful upgrade.
14.1.5 Upgrading using silent mode

You can upgrade Media Management using the silent on both Windows and Linux
platforms. This does not require an X-Windows support.
You require the <ISOPATH>/OTMM/mediamanagement_config.txt file for the silent

upgrade.
To upgrade using silent mode:
1. Copy the mediamanagment_config.txt file to a local folder and edit the file to
Tip: You can find the current values in the <TEAMS_HOME>/install/ant/

build.cfg file.
Notes
• Because you are upgrading, you are not required to update the OTDS
configuration and video configuration settings in the
mediamanagement_config.txt file.
In the DATABASE SELECTION settings, set the values of the following
settings to 0 or leave them empty:
• Oracle - CREATE_TABLE_SPACE
• Postgres - CREATE_POSTGRESQL_TABLE_SPACE
2. Mount the appropriate platform specific Media Management ISO,

mediamgmt_16.3_windows.iso or mediamgmt_16.3_linux.iso.
3. At the command prompt or on a terminal, enter one of the following

commands:
WINDOWS
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.bat -i silent -f

LINUX
<ISOPATH>/OTMM/Disk1/InstData/NoVM/install.sh -i silent -f
4. After a successful upgrade, do the following:
WINDOWS
Restart the system.
LINUX
Sign out, and then sign in using the Linux user account that was used to
install Media Management.
14.1.6 Continuing after upgrade errors

This section outlines the steps to take if your upgrade fails. After the upgrade fails,
you need to undo all the upgrade changes before you run the upgrade process
again.
During the upgrade, the schema is validated to find any schema conflicts between
the two instances. If conflicts are found during the schema validation, the upgrade
process will report an error and stop. There are other reasons that the upgrade
process may fail.
To continue after an upgrade error:
1. Determine the upgrade error. If any errors occur during the upgrade, review the
following files to determine the reason for the failure:
• <TEAMS_HOME>/logs/installation/upgradeValidation.log
• <TEAMS_HOME>/MediaManagement_InstallLog.log
• <TEAMS_HOME>/logs/installation/upgradeValidator.log
• <TEAMS_HOME>/ddl_install/log/upgrade_schema.log
2. If any errors occur while upgrading the schema, see the <TEAMS_HOME>/
ddl_install/log/upgrade_schema.log file for a list of problems.
3. Revert the upgrade changes.

Run the following SQL script to revert any changes performed during the
upgrade on the Media Management database:
<TEAMS_HOME>/data/upgrade/drop_sql.sql
Note: While running the <TEAMS_HOME>/data/upgrade/drop_sql.sql

file, ignore any errors indicating that objects such as a table, trigger, or
index do not exist in the database or schema.
4. Resolve any upgrade issues that were identified before running the upgrade
again.

14.2. Post-upgrade configurations
Note: Linux - Prior to running the upgrade again, you must uninstall
ImageMagick.
14.2 Post-upgrade configurations

This section provides information about post upgrade configurations.
14.2.1 Updating license files

After upgrading Media Management, existing customer-specific license files are
overwritten with default license files. You will need to copy your customer-specific
license files over the default license files. The license consists the license.dat and
license files. You should have backed up these files as part of backing up the
<TEAMS_HOME> directory because they are in the /servers subdirectory. Copy your
original license files into the new <TEAMS_HOME>/servers, overwriting the two files
placed there during the upgrade.
14.2.2 Clearing the JBoss cache

To clear the JBoss cache:
• Delete the tmp and data folders from the %JBOSS_HOME%\standalone location
before you start the OpenText Media Manager service.
14.2.3 Migrating Categories to Folders

Note: This section is only applicable if you were using Categories and you are
upgrading to the current version of OTMM from a version that is earlier than
10.5 Patch 2.
Categories were replaced by Folders. You can use a utility to perform a one-time
migration of all Categories to the Folder hierarchy of OTMM and migrate the assets
to the specific folders. This utility that performs the migration is an Ant target,
migrate-category-to-folder.
Notes
• The Category description is added to the Folder metadata description.
• Synonyms are added as Folder metadata description.
• Related terms are not migrated.
Before running the utility, you must configure the teams.properties file.
To configure the teams.properties file:
1. In a text editor, open the <TEAMS_HOME>\support\teams.properties file.

2. Configure the teams.properties file as follows:
teams.user=tsuper

teams.folder_name=MigratedCategory
teams.folder_type=ARTESIA.BASIC.FOLDER
teams.security_policy=1
teams.batch_size=500
where
teams.user is the OTMM user with administrator privileges who is running
the utility.
teams.folder_name is the Folder created under Public Folders where all the
category hierarchies will be migrated. When left blank, the top-level Categories
will be migrated as top-level folders within Public Folders.
teams.folder_type is the Folder Type for all newly created folders.
teams.security_policy is the security policy ID, which you must apply to the
newly created containers.
teams.batch_size is the number of assets within a Category that will be added
to the container at one time. If the Categories contain a large number of assets,
use teams.batch_size to control the number of assets that are included in a
transaction.
Note: The migration utility prompts you for the teams.password. Use the
password of the OTMM user with administrator privileges who is running the
utility.
To run the migration utility:
• Navigate to the <TEAMS_HOME>\support folder and run the following Ant

target:
ant migrate-category-to-folder
Note: The %TEAMS_HOME%/logs/installation/migrate-category-to-

folder.log is created. Use this LOG file to verify that the Categories
migrated successfully. If it was successful, run the cleanup Ant target.
To clean up migrated Categories:
• Navigate to the <TEAMS_HOME>\support folder, and run the following Ant

target:
ant cleanup-categories
Note: The %TEAMS_HOME%/logs/installation/cleanup-categories.

log is created. Use this LOG file to verify that the process ran successfully.

14.2. Post-upgrade configurations
14.2.4 Updating the transcode content target location

Note: You must apply this update if you are using any of the following:
• Rhozet
• Telestream Vantage
• FFmpeg
To update the transcode content target location:
• In the Web Administration tool, set the TARGET_PATH system setting to a shared
network path for the video or audio Transcode server where the Transcode
output file will be written. For example:
TARGET_PATH="\\<transcode server host>\<transcode_working_folder>"
Note: This setting is located under the VIDEO\TRANSCODE component,

which belongs to the Video configuration group. This group is accessible
from the Settings page in the Web Administration tool. For more
information about how to edit the settings of a component, see Section
2.13.2.3 “Editing a component and properties” in OpenText Media
14.2.5 Updating the video configuration

To update the video configuration on the Vantage server:
• Update the workflows in Vantage. For more information, see “Updating

workflows in Vantage” on page 75.
To update FFmpeg to latest version:
1. Uninstall the previous version of FFmpeg.

2. Install the current version of FFmpeg. For more information, see “Installing
FFmpeg” on page 170.
14.2.6 Upgrading ImageMagick

Notes
Windows ImageMagick is automatically installed as part of OTMM 16.2 and higher.

To upgrade ImageMagick on Linux:
• Install the current version of ImageMagick. For more information, see

“Installing ImageMagick on Linux” on page 62.

14.2.7 Configuring FFmpeg

You must configure FFmpeg if you upgraded to the current version of OTMM and
you are running on a Linux platform.
If you are installing a new version of FFmpeg, see “Configuring video using
FFmpeg” on page 169.
To configure FFmpeg on Linux:
• Edit the ${TEAMS_HOME}/bin/artesia-process-manager-wrapper-unix.

conf service configuration file to append the location of FFmpeg in
PATH_TO_CUSTOM_EXECUTABLES.
14.2.8 Regenerating the Tasset.dtd file

After successfully upgrading Media Management, you must regenerate the Tasset.
dtd file to update it with new or update metadata attributes.
To regenerate the Tasset.dtd file:
1. Verify that the OpenText Media Manager service is running.
2. Sign in to the Media Management Web Administration tool.
3. On the top-level menu, click Utilities > Regenerate tasset file.
4. Click Regenerate tasset file.
14.2.9 Rectifying corrupt mime type data for asset previews

and thumbnails
Note: This section is applicable only if asset previews and thumbnails are
generated with a PNG extension by changing the value of the
DEFAULT_IMAGE_THUMBNAIL_FORMAT setting under the IMAGE\CONFIG
component to PNG and you are upgrading to the current version of OTMM
from a version earlier than 16.2.2.
To rectify corrupt mime type data for asset previews and thumbnails:
• In a command prompt or terminal, navigate to the <TEAMS_HOME>/install/ant

folder and run the following Ant target:
ant rectify-content-mimetype
Notes
• If you do not run this Ant target, the asset previews and thumbnails
generated with PNG extension might not render in the browser.

14.3. Integrating Media Management and Secure MFT
• The <TEAMS_HOME>/logs/installation/rectify-content-
mimetype.log is created. Use this LOG file to verify that the corrupted
mime type information updated successfully.
14.3 Integrating Media Management and Secure MFT

This step is optional and is required only if you are planning to use Secure MFT. For
more information, see OpenText Secure MFT for Media Management - Enablement Guide
(MEDMGTPO-IMF).
14.4 Upgrading OpenText Information Hub

Note: This section is only applicable if you are using the Analytics feature in
OTMM.
The current version of iHub no longer requires the OTDS RSSE service to integrate
with OTDS and OTMM.
If you integrated iHub with OTDS using the OTDS Report Security Server Extension
(RSSE) driver and enabled Analytics in OTMM, you must upgrade to the current
version of iHub and remove the OTDS RSSE service. To do this, perform the
following tasks, which are further detailed later in this section, in sequence :
1. Optional If you made custom dashboards or reports, back up the OTMM16

applications folder.
2. Upgrade iHub to the current version.
3. Integrate iHub with OTDS user management.
4. Remove the OTDS RSSE service from iHub.
5. If you selected oTExternalID1 as the authentication principal attribute when

you configured the iHub OTDS resources in Step 3, reset the iHub configuration
file in OTMM.
Note: For more information about versions, see:

• OpenText Media Management Release Notes (https://knowledge.opentext.com/
knowledge/llisapi.dll/open/69371555)
• OpenText Media Management Technical Specifications (https://

14.4.1 To back up the OTMM16 applications folder

To back up the OTMM16 applications folder:
1. In the iHub portal, navigate to the Applications folder in the left pane.
2. In the panel on the right, navigate to the OTMM16 folder and click the ellipses
.
3. Select Download to export the existing OTMM16 folder dashboards, reports,

and configurations.
14.4.2 To upgrade iHub

To upgrade iHub:
• Upgrade iHub to the current version by following the instructions in the section
“Upgrading to iHub 16.2” of OpenText™ Information Hub Installation,
Configuration, and Administration Guide (https://knowledge.opentext.com/
14.4.3 To integrate iHub with OTDS user management

To integrate iHub with OTDS user management:
1. Follow the instructions in the “Configuring OpenText Directory Services”

section of OpenText™ Information Hub Installation, Configuration, and
Administration Guide (https://knowledge.opentext.com/knowledge/llisapi.dll/
open/68745200) to configure iHub for SSO. Ensure you do the following as you
perform the configuration:
• Note whether you configure the authentication principal attribute for the
iHub OTDS resource as oTExternalID1 or oTExternalID3.
• Remember to create an Admin group in your OTDS user partition. You will
configure this as the administrator’s group in iHub.
• Remember to assign the iHub Default Volume Organization ID as the OTDS
user partition.
Important
Use the OTDSTicket authentication mechanism for users instead of
OAuth2. The OTMM user interface only supports the OTDSTicket
integration.
2. In a web browser, open the iHub Information Console and do the following:
a. Verify that the /Applications/OTMM16 folder exists.
• If it does not, upload the OTMM16 folder that you backed up in “To back
up the OTMM16 applications folder” on page 208.

14.4. Upgrading OpenText Information Hub
b. Navigate to the /Applications/OTMM16 folder and set the folder

permissions. For more information on setting folder permissions, see “To
grant the new user read-execute permission to the iHub dashboards and
reports” on page 130.
c. Sign in to the iHub Information Console as the dedicated OTDS user and
verify access to the /Applications/OTMM16 folder.
14.4.4 To remove the OTDS RSSE service from iHub

To remove the OTDS RSSE service from iHub:
1. In a web browser, open the iHub System Console.

2. Navigate to the Clusters page.
3. On the Clusters page, select the Default Volume cluster.
4. Click the Web button and select Stop Service to shut down the web service.
5. When the web service is shut down, locate the IHUB_WEBAPPS_DIR folder.
Example: IHUB_WEBAPPS_DIR = C:\OpenText\InformationHub\modules\

BIRTiHub\iHub\web\webapps
6. Remove the axis2 folder from the webapps folder.

7. Restart the Default Volume cluster web service.
14.4.5 To reset the iHub credentials file

To reset the iHub credentials file:
• If you selected oTExternalID1 as the authentication principal attribute for the

new iHub OTDS resource, you must do the following to reset your iHub
configuration file:
a. On the OTMM machine, open the Command Prompt window and navigate
to the <TEAMS_HOME>/servers folder.
b. Use a text editor to edit the iHub_SEC.cfg configuration file as follows:
• On the first line, remove the @<otds_partition_name> extension from

the OTDS user name for the dedicated iHub user.
Example: Remove @MediaMgmt from mmihubuser@MediaMgmt.

• On the second line, edit the iHub user password.
Note: If you are using oTExternalID3 as the authentication principal

attribute, verify the configured iHub credentials are still valid and
continue to use the format <username>@<otds_partition_name> for
the user name.
Example: mmihubuser@MediaMgmt

c. Navigate to the <TEAMS_HOME>/install/ant folder and run the following

command in the Command Prompt window:
ant encrypt-ihub-login
14.5 Upgrading the FFmpeg Transcode service

Note: This section is only applicable if you are upgrading from FFmpeg
version 16.0.1 or higher to FFmpeg version 16.2.
The section provides information about upgrading the FFmpeg Transcoder service
in multi-tenanat environment or externally.
To upgrade the FFmpeg Transcode service:
1. Shut down FFmpeg Transcoder service by doing one of the following:
WINDOWS
Stop the FFmpeg Transcoder service.
LINUX
ffmpegService stop
2. Do one of the following to create the ffmpeg-transcoder.zip file in the

OTMM installation <TEAMS_HOME>/ffmpeg folder:
WINDOWS
At the command prompt, change to the <TEAMS_HOME>/install/ant
folder, and then run the following command:
ant build-ffmpeg-external-transcoder
LINUX
On a terminal on an OTMM server, navigate to <TEAMS_HOME>/install/
ant, and then run the following Ant target:
ant build-ffmpeg-external-transcoder
Example 14-1: Ant target

C:\MediaManagement\install\ant>ant build-ffmpeg-external-
transcoder
Note: This target creates the ffmpeg-transcoder.zip file in the OTMM

installation <TEAMS_HOME>/ffmpeg directory.
3. Copy the ffmpeg-transcoder.zip file that was created in Step 2 to an arbitrary

location on the FFmpeg server.

14.6. Verifying the upgrade
4. Extract the ffmpeg-transcoder.zip file to a temporary folder, copy all the

content available in the extracted folder/lib to the <FFMPEG_HOME>/lib
folder.
5. Start FFmpeg the Transcoder service by doing one of the following:
WINDOWS
Start the FFmpeg Transcoder service.
LINUX
ffmpegService start
14.6 Verifying the upgrade

After performing the upgrade, verify the upgrade by following the instructions in
“Verifying the OTMM installation“ on page 213.
Note: If you performed a reindex of Solr, you need to wait until the reindex is
complete before verifying that search is working.
14.7 Upgrading Creative Review

If you installed Creative Review, you need to follow the upgrade procedure. For
more information about upgrading, see Section 9.1 “Upgrading Creative Review” in
OpenText Media Management Creative Review - Installation Guide and Release Notes
(MEDMGTPO-ACR).
Note: The Creative Review 16.3 upgrade supports upgrade installations from
version 16.2.

Chapter 15
Verifying the OTMM installation
After you installed the application and optional components, and you stared the
application, you need to verify the installation.
To verify the OTMM installation:
1. Open the web browser and enter the URL of the OTMM Web Client. For
example:
http://otmm-host:11090/otmm
2. Sign in to the Media Management client using the accounts set up.
3. Test the install by performing some basic tasks, such as the following
• Import assets
• Export assets
• Search for assets
• Add a folder
Note: If any of these tasks fail, see “Troubleshooting the OTMM

installation” on page 213.
15.1 Troubleshooting the OTMM installation

15.1.1 Command Prompt window disappears during install
Windows Capture the content of the Command Prompt window during the execution of the
installer by pressing CTRL and executing the installer. This Command Prompt
window will be available until you release CTRL.
Linux To get addition debug information during the execution of the installer, enter the
following property:
export LAX_DEBUG=true

Chapter 15 Verifying the OTMM installation
15.1.2 Application deployment issues

The Media Management server has been configured to use marker files for
deployment. The following are the important markers:
• .dodeploy
• .isdeploying
• .deployed
• .failed
For a complete list of marker files, see the following JBoss documentation: https://
access.redhat.com/site/documentation/en-US/
Administration_and_Configuration_Guide/index.html
Each of the marker files are prefixed with the deployment package name. For Media
Management, it is artesia.ear. The .dodeploy marker is an instruction to the
application server to deploy the application package. The rest indicate the
deployment states for the application package.
If for some reason, the deployment fails, you will find the <TEAMS_HOME>/ear/
artesia.ear.failed marker file.
To re-deploy the package after undertaking any corrections, rename the artesia.
ear.failed marker file to artesia.ear.dodeploy. To verify if the deployment was
successful, ensure that you have the artesia.ear.deployed marker file in the
<TEAMS_HOME>/ear directory.
15.1.3 OTMM Sign-in issues

1. Using the OTDS web sign-in page, try to sign in to OTDS directly using the
following format:
<protocol>://<otds server name>:<port>/otdsws/login
2. Sign in to the OTDS Web Client as otadmin@otds.admin.

3. Locate the OTMM resource and verify that it is activated.
4. Using the OTDS Web Client, edit the OTMM resource and verify that the Push
Connector is configured.
Tip: Use the Test button to verify the connection.
5. Verify the date on the OTMM and OTDS server are synchronized.
Tip: Use a time service to verify they are always synchronized.
6. On the OTMM server, verify the OTDS sign-in information by doing the
following:

15.1. Troubleshooting the OTMM installation
a. At the command prompt, change to the <TEAMS_HOME>\install\ant

directory.
b. Run the following command:
ant decrypt-otds-login
c. In a text editor, open the <TEAMS_HOME>/servers/OTDS_SEC_Srv.txt file
and verify that the OTDS sign-in information is correct.
15.1.4 Import issues

Cannot import assets
1. Verify that the property template was created. For more information, see
“Creating Property Templates” on page 79.
2. Verify OTMM user has sufficient permissions to access the OTMM
repository.
15.1.5 Indexer and Search issues

Indexer issues and Search does not work
1. Verify that the Solr server is running by entering its URL in a web browser.
The format is: http://<solr_hostname>:port/solr.
a. If the Solr server not available, start Solr.

b. Using the Core Selector list in the left pane, choose otmm to navigate
to the otmm core.
c. In the left pane, select Query.
d. Click Execute Query.
Note: If any of the above steps fail, Solr is not configured correctly.
Check you configuration.
2. Verify that the Indexer is running:
a. Verify that the Indexer credentials by changing to the <TEAMS_HOME>/

install/ant directory and running the following Ant task:
ant decrypt-indexer-login
In a text editor, open the <TEAMS_HOME>/servers/index_SEC.txt file,
and verify the user credentials are valid.
b. Single instance - Verify that the SOLR_URL is valid by opening the
<TEAMS_HOME>/data/cs/global/Tresource file, located the value of
the SOLR_URL entry, and testing that URL in a web browser.
c. HA configuration
Verify that the Master URL is configured by running the following SQL
statement:
SELECT URL FROM SOLR_MONITOR_TABLE WHERE IS_MASTER='Y'

Copy the value in the URL column, and test it in a web browser.
d. Verify that the OpenText Media Manager service is running without
error.
e. HA configuration - If the service is not running, verify that the
PROVIDER_HOST is properly configured. For more information, see
“Enabling failover of the client API (optional)” on page 238.
3. Solr and the Indexer are running, but Search fails.

SQLServer installations only - Verify that the SQL Server Agent service is
running.
Change your Indexer credentials
1. Stop the Indexer.
2. Change directory to the <TEAMS_HOME>/servers folder.
3. Rename the index_SEC.cfg file to index_SEC.cfg.bak.
4. Create a sign-in file named index_SEC.cfg.
5. Edit the file with the new user name and password information. Enter the
user name on the first line and the password on the second line.
6. Change directory to the <TEAMS_HOME>/install/ant folder.
7. Encrypt the new password file using the following Ant task:
ant encrypt-indexer-login
8. Restart the Indexer and verify that the sign-in works.
Indexing fails. The Indexer log reports that it is unable to communicate with
OTMM.
1. Verify that credentials in the <TEAMS_HOME>/servers/index_SEC.cfg file

are correct.
2. Verify that the OTMM server is running without errors.
3. HA configuration - If the service is not running, verify that the

PROVIDER_HOST is properly configured. For more information, see
“Enabling failover of the client API (optional)” on page 238.
4. To test this, use the Solr URL to query the Solr index directly. The format of
the Solr URL is: http://<solr_hostname>:port/solr.
Indexing fails. The Indexer log reports that it is unable to communicate with Solr.
1. Check the Solr configuration to verify that location of the index is correct.
2. Verify that the port number is available.
3. Verify that the Solr URL is responsive.

4. To test this, use the Solr URL to query the Solr index directly.
15.1.6 Transcoding of video and audio assets fails

Rhozet or Flip Factory
If you are using Rhozet or Flip Factory, do the following:
1. Verify that the transcode host is configured properly and that the port is not
blocked by a firewall.
2. Verify that all shared folders are configured as required for OTMM.
Notes
• OTMM and the Transcode server must share files. If the permissions
are not set correctly on the shared folders, transcode fails.
• If the shared folders are not configured correctly, transcode fails.
Vantage
If you are using Vantage, do the following:
1. Verify that the transcode host and transcode category are configured
properly.
2. Verify that the MediaInfo executable is available in a user path.
Notes
FFmpeg
If you are using FFmpeg, do the following:
1. Verify that the transcode host is configured properly.
2. Verify that the FFmpeg and/or MediaInfo executables are available in a user
path.
Notes

15.1.7 Analytics
Analytics reports and dashboards are not working. com.artesia.analytics
errors in the application server log.
Analytics reports and dashboards are not working. Data is not being imported
to the Data Collector CSV files for the tenant ID.
1. Verify the Data Agent configuration through the Analytics page in the Web
Administration tool.
2. Verify that the Data Collector server is running on the configured host and
port location.
3. Verify that the iHub console URL is valid. Test this by signing in directly to
the iHub console using a web browser.
4. Verify that the OTMM report and dashboard paths are valid in iHub.
15.1.8 Adaptive Media Delivery

OTMM is not able to contact the Adaptive Media Delivery server.
1. Check the URL using the following format:

<protocol>://<deliveryserver_host>:<port> /adaptivemedia/
<ping_from_OTMM_server>.
2. If the above does not return an image with 1x1 pixel response (200 status),
then server is not running or the Adaptive Media Delivery server host is not
reachable.
Adaptive Media Delivery server is not showing images.
• Verify that the Adaptive Media Delivery server is running. Check the URL
using the following format:
<protocol>://<deliveryserver_host>:<port> /adaptivemedia/
<ping_from_OTMM_server>.
15.1.9 Thumbnails do not appear in Mobile or Web Desktop

Client
Thumbnails do not appear for assets. There is an exception in the OTMM
application log.
• Verify that the ImageMagick executable is available in the user path.
PDFs and Microsoft Office documents do not generate previews/thumbnails.

There is an exception in the OTMM application server log related to
transformation failures.
• Verify that the Spicer executable is available in a user path. Complete the
Spicer transformer install step.

15.1.10 PDF preview is not generated for assets

PDF previews are not generated for some assets, such as PDFs and Microsoft Office
documents. In addition, there is an exception in the OTMM application server log
related to transformation failures and non-availability of required DLL files.
For Windows, verify that the Spicer executable file is available in the user path. If it
is already available in the user path, verify that Microsoft Visual C++ Redistributable
for Visual Studio 2012 is installed. This should be automatically installed as part of
installation. If it is not installed, you can install it from the <TEAMS_HOME>\install\
vcredist folder. When you double-click the EXE installation file, you are presented
with the repair and uninstall options, if it is already installed.
For Linux, see “Installing X Virtual Framebuffer on Linux” on page 63.
15.1.11 Videos do not play

Adobe Media Server
1. Verify that the application is set up properly in Adobe Media Server.
2. Verify that the OTMM repository is accessible to the Adobe Media Server.
Wowza Streaming Engine
1. Verify that the application is set up properly in the Wowza Streaming

server.
2. Verify that the OTMM repository is accessible to the Wowza Streaming

server.

Chapter 16
Configuring for High Availability
This chapter defines High Availability (HA) and how the Media Management
application can be configured to best support highly available needs. It does not
define a service level agreement between Media Management and the customer.
Instead, it helps the customer understand the architecture of Media Management
solutions in relation to a highly available environment.
Note: Instructions are provided for both Windows and Linux. When specific
examples are given, if you are on Linux and the Windows syntax is used, you
need to replace the <TEAMS_HOME> in the Windows syntax with your value,
$TEAMS_HOME, and replace the backward slashes with forward slashes. If you
are on Windows and the Linux syntax is used, you need to replace the
TEAMS_HOME in the Linux syntax with your value, $TEAMS_HOME, and replace
the forward slashes with backward slashes.
16.1 What is HA?

It is important to first understand what is meant by the term high availability. While
the term is generally used in a consistent manner, the degree by which HA support
is provided has wide variations. The following paragraphs provide a useful
distinction between HA and Fault Tolerance:
• One way to understand HA is to contrast it with fault tolerance. These terms
describe two different benchmarks measuring availability. Fault tolerance is
defined as 100 percent availability 100 percent of the time, regardless of the
circumstances. A fault tolerant system is designed to guarantee resource
availability.
• In contrast, an HA system is concerned with maximizing resource availability. A
highly available resource is available a very high percentage of the time and may
even approach 100 percent availability, but a small percentage of down time is
acceptable and expected.
• HA can be defined as follows:
• A highly available resource is almost always operational and accessible to
clients.
• The following article describes the concept of HA:
http://technet.microsoft.com/en-us/library/cc750543.aspx
As described by Microsoft, HA does not provide for 100 percent availability 100
percent of the time. The goal of HA is to ensure the application is available as much
as possible within the means of the application, hardware, and hosting systems
capabilities.

Chapter 16 Configuring for High Availability
16.1.1 References and other reading

The following information may prove valuable to configure Media Management and
supporting technologies:
• Oracle Maximum Availability Architecture (MAA).
• Oracle Maximum Availability Architecture (MAA) is Oracle's best practices
blueprint based on proven Oracle HA technologies and recommendations. The
goal of MAA is to remove the complexity in designing the optimal HA
architecture.
16.2 Providing HA support

The Media Management application can be installed and configured in a manner
which provides HA capabilities. While this configuration does involve some manual
steps, it can be automated and integrated with a monitoring system to enable full
hands-off HA support.
Providing application HA support requires a complete analysis of the solution to

identify “Failure Points” along with a system impact and process protection options.
The following sections detail the various components within each system and
subsystem of the Media Management application, the impact when unavailable, and
options for providing HA support.
16.2.1 General HA best practices

There are a number of important best practices which should be followed to support
HA requirements. These include the following:
• Regular system backups to include application data and configuration.
• Implementation of system monitoring tools capable of monitoring system
resources (such as disk), processes, and networks.
• Clear definition of standard operating procedures (SOPs) with respect to system
administration and management.

16.2. Providing HA support
16.2.2 Overview of Media Management processes

The following figure depicts the processes which make up the Media Management
solution. This diagram includes optional custom processes and the DMZ web server
as well as the file storage.
Figure 16-1: Media Management Processes
The following sections detail each of the processes along with an explanation of
which HA options are available if the system becomes unresponsive.
16.2.3 Media Management application server

The Media Management JVM executes the J2EE application server hosting the Media
Management web client and business services.
Impact When Unavailable

When the Media Management application server process is down, users cannot
access the application or managed assets through this node.
HA Capability
OpenText recommends that you set up the application server in an application
server cluster. When configured with a load balancer or when using the client
API clustering (through JBoss or TomEE), future requests will automatically be
re-routed to other nodes in the application server cluster if an application server
node fails to respond. You can optionally configure the application server to
replicate HTTP session information so that a users browser session is not lost if
an application server node fails. For more information about how to perform
this configuration, see “Enabling Session Replication” on page 224.

16.2.3.1 Enabling Session Replication

You can optionally enable HTTP session replication so that a users’ data stored in an
HTTP session is maintained across all the nodes in the cluster.
Note: There are significant performance impacts when you enable this
behavior because HTTP session information must be replicated on all nodes.
The HTTP session replication is enabled only for the following web applications in
Media Management:
• HTML5 user interface (otmmux.war)
• Web Administration user interface (teams.war)
• REST API (restapi.war)
This means that HTTP session information pertaining to these WARs is replicated
among all the nodes.
By enabling session replication, if one of the instances is not reachable, the Web
Administration, HTML5 user interface application and REST API web application
users who were on that instance, are automatically redirected to the other instance in
the cluster.
Note: Even if you enable this mode, OTMM requires that you enable Sticky
Sessions in the Load balancer. If a node fails in any application other than the
web applications where the session replication is enabled, users must sign in
again.
To enable HTTP session replication:
1. Uncomment the <distributable/> tag in the $TEAMS_HOME/ear/artesia.

ear/teams.war/WEB-INF/web.xml, $TEAMS_HOME/ear/artesia.ear/
restapi.war/WEB-INF/web.xml, and $TEAMS_HOME/ear/artesia.ear/
otmmux.war/WEB-INF/web.xml files
Note: In the web.xml file, you must add the tags as per the deployment
descriptor tags order. The order is: icon, display-name, description,
distributable, context-param, filter, filter-mapping,listener,
servlet, servlet-mapping, and so on.
For example:
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://
java.sun.com/xml/ns/javaee/web-app_3_0.xsd"
version="3.0">

<description>
....
<distributable/>
...
<filter>
...
<listener>
...
</web-app>
2. JBoss EAP only - Uncomment the replication-config section in the

$TEAMS_HOME/ear/artesia.ear/restapi.war/WEB-INF/jboss-web.xml,
$TEAMS_HOME/ear/artesia.ear/otmmux.war/WEB-INF/jboss-web.xml and
$TEAMS_HOME/ear/artesia.ear/teams.war/WEB-INF/jboss-web.xml files.
Note: You must perform this procedure on all nodes in the cluster.
16.2.4 Apache Solr (search engine)

The Apache Solr server process provides the main index search capabilities. This
module is designed to be installed and configured on the Media Management
application server or its own server.

Search and indexing capabilities are unavailable. You will have access to the
Media Management applications, but will be unable to use search to locate
specific assets. In addition, new or modified assets will not be updated in the
Solr search index.
HA Capability
Search is provided by one or more Solr/slave instances. Indexing can be
redirected using Media Management Ant tasks.

16.2.5 Indexer
The Indexer component is responsible for extracting change records from the Media
Management database and updating the search index.

Updates to the search index do not occur. Searching in the UI can continue, with
the understanding that new assets will not be returned in search results.
HA Capability
The Indexer Monitor is an automated process that makes sure an Indexer
process is always available to process data. In an HA environment, only one
Indexer is active at any one time even though Indexers are installed on each
Media Management host. If the active Indexer becomes inactive, one of the other
available Indexers automatically becomes the active Indexer and takes over the
indexing tasks.
16.2.6 Database
The database maintains the system data and metadata for the Media Management
application. The Media Management business services leverages JDBC drivers to
communicate with the database.

If the database is unavailable, the entire Media Management application will be
unavailable and unusable.
HA Capability
To provide HA support for the Media Management application, OpenText
recommends that you configure your Oracle database in a cluster with at least
two nodes. The Media Management application server can then be configured to
leverage the transparent application failover (TAF) capabilities.
The JDBC and ODBC drivers are designed to leverage the TAF capabilities of the
Oracle database, providing connect-time failover.


16.2.7 Solr index files

The Solr search index files are stored with the Solr instance.

Searching and indexing are not possible.
HA Capability
In a Media Management HA environment, Solr is set up as a master/slave
configuration. One Solr server is configured as the master and is responsible for
indexing. Other installed Solr servers are configured as slaves. Slaves replicate
the Solr index files on their local host. All Solr servers can be used for searching.
16.2.8 Database data files

The database data files contain the data which is managed within the database
process.

The Media Management application will be unavailable.
HA Requirements
The database data files must be placed on an HA capable shared SAN device.
16.2.9 Asset repository

Media Management requires a content storage device for the management of the
asset content files. Currently supported options include file system, EMC Centera®,
HSM, and SANs.
The storage device selected for the HA configuration must be capable of providing
clustering to ensure that all application nodes can access content (read and write)
files at any time.

All content related features will fail. This includes import, export, and thumbnail
access.
HA Options
The Media Management repository must be placed on an HA capable shared
SAN device.

16.3 Recommended HA configuration

This section details the specifics of the suggested architecture along with key
configuration changes which must be made to enable this architecture.
Note: You must use the same network user ID when installing Media
Management on all nodes. Using the same user ID facilitates resource sharing
in the HA cluster.
The following figure outlines the various components in the suggested HA

configuration.
Figure 16-2: HA Configuration Components
Note: OpenText Secure MFT (Secure MFT) Enterprise Server, consisting of

Secure MFT Web Services and Secure MFT Transfer Server, is an optional
component. Although Secure MFT supports a multi-server topology of one
Enterprise Server and one or more Location Servers, Media Management only
supports an Secure MFT setup consisting of one Secure MFT Enterprise Server.

16.3. Recommended HA configuration
Therefore, Media Management has a single point of failure in Secure MFT. The
impact of an Secure MFT failure is limited. If any component of the Enterprise
Server, the web services or the Transfer Server, fails after the Secure MFT-
based file transfer starts, the import or export activity would also fail.
However, if either of these components becomes inaccessible before the Secure
MFT-based file transfer is committed to, Media Management reverts to native
HTTP-based transfer.
16.3.1 Shared storage requirements

The following file system storage locations must reside on shared storage accessible
by all nodes in an application server cluster:
• TEAMS_REPOSITORY_HOME
• IMPORT_WORKING_AREA
• DEFAULT_EXPORT_AREA
• VIDEO_FILE_STAGING_AREA
• BULKEDIT_WORKING_AREA
• Linux only - UNIX_RELATIVE_VIDEO_WORKING_AREA
Note: When choosing these shared storage areas, you should consider other
component disk needs. For example, the DEFAULT_EXPORT_AREA and the
EXPORT_WORKING_AREA directories should be separate. Make sure these
temporary work areas do not conflict with the disk requirements for Solr
indexing.
16.3.2 Setting up HA
open/69371555).
To prepare to set up HA:
Note: On Linux, you must mount the Media Management ISO as the Linux
root user.
1. Set the OTDS HA cluster by following the instructions in OpenText Directory

Services - Installation and Administration Guide (OTDS160204-IWC). For more
information about installing OTDS, see “Phase 1 - OTDS” on page 19.
2. Set up the OTMM cluster as described in “OTMM cluster” on page 230.
3. Perform a simple import, export, and search in Media Management to verify

that they work correctly.

Note: After a successful installation, set the ownership of the install folder to
Linux only the product user. For example:
chown –R otmmuser /usr/local/share/OTMM
16.4 OTMM cluster

This section provides instructions for performing clustering of the Media
Management system. The installation and configuration sequence is as follows. The
details for each step are given in the subsections that follow.
1. Configure the OTMM resource in OTDS server as described in “Configuring

OTMM resources in OTDS” on page 35.
2. Set up the database as described in “Database setup” on page 26.
3. Install Media Management on the first node as described in “Installing Media
Management on the first cluster node” on page 231.
4. Install Media Management on the other nodes as described in “Installing Media
Management on other cluster nodes” on page 231.
5. Perform any optional installation activities as described in “Completing optional
installation activities“ on page 191. Where updates to the configuration settings
are required, the updates must be applied to all nodes of the Media Management
cluster.
Note: For more information about editing configuration settings and

components, see Section 2.13.2.3 “Editing a component and properties” in
6. Configure Media Management for clustering on all nodes as described in
“Configuring Media Management on all cluster nodes” on page 232.
7. Configure the Media Management Indexers for HA as described in “Media
Management Indexer configuration on the cluster nodes” on page 240.
8. Configure the Solr master on the primary OTMM node. The primary OTMM
node is where the Schema was installed. The primary OTMM node will have the
TEAMS_HOME/ddl_install folder with logs and the SQL scripts used to install
the database schema. On all other OTMM nodes, configure the Solr slave. For
more information, see “Solr configuration on cluster nodes” on page 249.

16.4. OTMM cluster
16.4.1 Installing Media Management on the first cluster node

To install Media Management on the first cluster node:
1. Perform one of the following, based on your operating system:

2. Perform the steps from “Post installation tasks“ on page 71.
3. Configure the video transcoding as described in “Configuring video and audio“
on page 133.
4. Perform the OTDS configuration steps in “Verifying and Configuring Push
Connector for Media Management“ on page 81.
a. Perform the instructions To update the OTDS Push Connector for all
OTDS cluster nodes.
b. Perform the instructions To configure the OTDS Push Connector for
Media Management only once.
16.4.2 Installing Media Management on other cluster nodes

To install OTMM on other cluster nodes:
1. When installing Media Management on the other cluster nodes, install only the
OTMM Application, deselect the Schema option, and then point to the existing
database which was created as part of the first cluster node installation.
Tip: You can use the same mediamanagment_config.txt settings that you
used when you set up the first OTMM cluster node. Copy this
configuration file to the current OTMM cluster node before running the
installer on the current node.
2. Install OTMM.
a. Perform the steps in one of the following:

b. Choose the one of following options during the installation process:
• On the Choose Product Features page, select only the Application

option.
• On the Database Schema Configuration page, provide the existing
database details.
Note: Oracle users - Do not select the Create table space option.

3. Copy the files in the <TEAMS_HOME>/servers folder from the first node to the
<TEAMS_HOME>/servers folder on the remaining nodes of the cluster.
4. Copy the <TEAMS_HOME>/servers/index_SEC.cfg file from the first node to

the <TEAMS_HOME>/servers folder on the remaining cluster nodes.
5. Linux - Perform the steps in “Installing ImageMagick on Linux” on page 62.
6. Linux - Perform the steps in “Installing X Virtual Framebuffer on Linux”

on page 63.
7. Create the Solr index.
• On Windows - Perform the steps in “Installing and configuring Solr on

Windows” on page 47.
• Linux - Perform the steps in “Installing and configuring Solr on Linux”
on page 64.
8. Edit the VIDEO and AUDIO component settings to match those configured on
the first cluster node. For more information and for sample configurations, see
“Configuring video and audio“ on page 133.
16.4.3 Configuring Media Management on all cluster nodes

The Media Management instance is enabled for clustering by default.
Communication defaults have been provided for JBoss or TomEE nodes on different
machines to discover each other and form a cluster, these defaults can be
customized.
16.4.3.1 Configuring OTMM with JBoss on all cluster nodes

To configure OTMM with JBoss on all cluster nodes:
1. Configure and share TEAMS_REPOSITORY_HOME on a location shared by all hosts.
Note: For a Windows cluster, you might need to use a UNC path, such as
\\sharedhost\repository, if the application server cannot access a
mounted drive when it is run as a Windows service. You must ensure that
the user running the OpenText Media Manager service has read and write
access to the shared repository.
2. Configure the JBoss settings for the first cluster node in one of the following:
WINDOWS
<JBOSS_HOME>/bin/ otmm-standalone.bat
LINUX
<JBOSS_HOME>/bin/otmmstandalone.sh
For more information, see “Configuring JBoss” on page 72.

16.4. OTMM cluster
3. In a text editor, open the <JBOSS_HOME>/standalone/configuration/otmm.

xml file, and change default-interface to public. For example:
<socket-binding-group name="standard-sockets" defaultinterface="
public" port-offset="${jboss.socket.binding.portoffset: 10000}">
4. Search for web subsystem and add an attribute called instance-id. Record the
value of the attribute because you must specify the same name in the Load
Balancer configuration of the cluster setup. You must provide a unique name on
each node. Preferably, provide the same value as OTMM_JBOSS_NODE_NAME,
which is configured in the otmm-standalone.conf.bat file on Windows or the
otmm-standalone.conf file on Linux. For example:
JBoss EAP
<subsystem xmlns="urn:jboss:domain:web:2.2" default-
virtualserver="default-host" native="false" instance-id="otmm-
node2">
Wildfly
<subsystem xmlns="urn:jboss:domain:undertow:2.0" instance-
id="otmm-node2">
Note: This step is required only if you are using an AJP protocol-based
software load balancer, such as Apache Web Server configured with
mod_JK or mod_proxy_ajp.
5. Verify that the configuration group component settings are consistent with the
first OTMM cluster node through the Settings page. Verify the settings for any
optional installation configuration items that are installed. For more information
about the Settings page, see OpenText Media Management - Administration Guide
(MEDMGT-AGD).
6. Configure the OTMM node in the load balancer by mapping requests for the
following URLs from the load balancer to the OTMM server:
• /artesia-ws
• /artesia-ws/*
• /artesia-ux-ws
• /artesia-ux-ws/*
• /content
• /content/*
• /otmm
• /otmm/*
• /otmmapi
• /otmmapi/*
• /swagger-ui

• /swagger-ui/*
• /teams
• /teams/*
• /hostedhelp/*
7. Enable Sticky Sessions in the Load balancer.
Note: OTMM requires that you enable Sticky Sessions.
16.4.3.2 Configuring OTMM with TomEE on all cluster nodes

To configure OTMM with TomEE on all cluster nodes:
1. Configure and share TEAMS_REPOSITORY_HOME on a location shared by all hosts.
Note: For a Windows cluster, you might need to use a UNC path, such as
\\sharedhost\repository, if the application server cannot access a
mounted drive when it is run as a Windows service. You must ensure that
the user running the OpenText Media Manager service has read and write
access to the shared repository.
2. Adapt JmsResourceAdapter in the tomee.xml file on all cluster nodes by

changing ServerUrl to use the hostname of the respective node instead of the
localhost.
a. In a text editor, open the %TOMEE_HOME%/conf/tomee.xml file.

b. Navigate to ServerUrl.
c. Change ServerUrl to use the hostname of the respective node, instead of
the localhost.
Example 16-1: ServerUrl using localhost
<Resource id="JmsResourceAdapter"
type="ActiveMQResourceAdapter">
BrokerXmlConfig = xbean:file:../conf/
activemq.xml
ServerUrl = nio://localhost:54545?
soTimeout=60000&daemon=true&keepAlive=true&
connectionTimeout=120000&wireFormat.tcpNoDelayEnabl
ed=true&wireFormat.maxInactivityDuration=240000&amp
;wireFormat.maxInactivityDurationInitalDelay=120000
</Resource>
Example 16-2: ServerUrl hostname
<Resource id="JmsResourceAdapter"
type="ActiveMQResourceAdapter">
BrokerXmlConfig = xbean:file:../conf/

16.4. OTMM cluster
activemq.xml
ServerUrl = nio://hostname:54545?
;wireFormat.maxInactivityDurationInitalDelay=120000
</Resource>
3. Adapt the transportConnector in the activemq.xml file on all nodes by doing

the following:
a. In a text editor, open the %TOMEE_HOME%/conf/activemq.xml file.
b. Navigate to transportConnector.
c. Change transportConnector to use the hostname of the respective node,

instead of the localhost
Example 16-3: transportConnector using localhost
<transportConnectors>
<transportConnector name="nio"
enableStatusMonitor="true" uri="nio://localhost:54545?
;wireFormat.maxInactivityDurationInitalDelay=120000"/>
</transportConnectors>
Example 16-4: transportConnector using hostname
<transportConnectors>
<transportConnector name="nio"
enableStatusMonitor="true" uri="nio://hostname:54545?
;wireFormat.maxInactivityDurationInitalDelay=120000"/>
</transportConnectors>
4. Adapt the network networkConnector in the activemq.xml file on all nodes by

a. In a text editor, open the %TOMEE_HOME%/conf/activemq.xml file.
b. Navigate to networkConnector.
c. Enter the list all of the nodes in the networkConnector name URL.

Example 16-5: networkConnector using localhost
<networkConnector name="connector1" uri="static:(nio://

localhost:54545)">
Example 16-6: networkConnector using hostname
<networkConnector name="connector1" uri="static:(nio://

server1:54545,nio://server2:54545,nio//
server3:54545.....)">
5. Adapt the server.xml files on all cluster nodes.
a. Add or adapt the following line in the %TOMEE_HOME%/conf/server.xml

file.
<Engine name="Catalina" defaultHost="localhost"
jvmRoute="node1">
Note: The load balancer will use the same unique identifier.
OpenText recommends that you use the same identifier per TomEE
node.
b. Configure the cluster communication using Apache Tribes
SimpleTcpCluster by adding or adapting the following XML element in the
%TOMEE_HOME%/conf/server.xml file.
Note: Ensure that the multicast address is not used within the
targeted network environment and is not same as the one that you
provided in the TomEE_Home/conf/multicast.properties file.
<Cluster
className="org.apache.catalina.ha.tcp.SimpleTcpCluster"
channelSendOptions="8">
<Manager
className="org.apache.catalina.ha.session.DeltaManager"
expireSessionsOnShutdown="false"
notifyListenersOnReplication="true"/>
<Channel
className="org.apache.catalina.tribes.group.GroupChannel">
<Membership
className="org.apache.catalina.tribes.membership.McastService
"
address="228.0.0.4"
port="45564"
frequency="500"
dropTime="3000"/>
<Receiver
className="org.apache.catalina.tribes.transport.nio.NioReceiv

16.4. OTMM cluster
er"
address="auto"
port="4000"
autoBind="100"
selectorTimeout="5000"
maxThreads="6"/>
<Sender
className="org.apache.catalina.tribes.transport.ReplicationTr
ansmitter">
<Transport
className="org.apache.catalina.tribes.transport.nio.PooledPar
allelSender"/>
</Sender>
<Interceptor
className="org.apache.catalina.tribes.group.interceptors.TcpF
ailureDetector"/>
<Interceptor
className="org.apache.catalina.tribes.group.interceptors.Mess
ageDispatchInterceptor"/>
</Channel>
<Valve
className="org.apache.catalina.ha.tcp.ReplicationValve"
filter=""/>
<Deployer
className="org.apache.catalina.ha.deploy.FarmWarDeployer"
tempDir="/tmp/war-temp/"
deployDir="/tmp/war-deploy/"
watchDir="/tmp/war-listen/"
watchEnabled="false"/>
<ClusterListener
className="org.apache.catalina.ha.session.ClusterSessionListe
ner"/>
</Cluster>
6. Verify that the configuration group component settings are consistent with the
first OTMM cluster node through the Settings page. Check the settings for any
optional installation configuration items that you installed. For more
information about the Settings page, see OpenText Media Management -
7. Configure the OTMM node in the load balancer by mapping requests for the
following URLs from the load balancer to the OTMM server:
• /artesia-ws
• /artesia-ws/*
• /artesia-ux-ws
• /artesia-ux-ws/*
• /content

• /content/*
• /otmm
• /otmm/*
• /otmmapi
• /otmmapi/*
• /swagger-ui
• /swagger-ui/*
• /teams
• /teams/*
• /hostedhelp/*
8. Enable Sticky Sessions in the Load balancer.
Note: OTMM requires that you enable Sticky Sessions.
16.4.3.3 Enabling failover of the client API (optional)

For client applications that use the Media Management API, you may optionally
configure the API calls made to the application server to switch to another node in
the cluster if an application server node fails.
Note: In-flight transaction failover is not supported.
To enable API failover in JBoss:
1. Provide a comma-delimited list of hosts and port numbers for each of the
application server nodes.
2. Provide the port number to the remote port of the application server. Typically,
the port used is 11099 and it is defined in the <JBOSS_HOME>\standalone\
configuration\otmm.xml file.
3. Edit the PROVIDER_HOST setting in the [JNDI\CONFIG] section of the TResource

file.
Example 16-7: PROVIDER_HOST configuration for JBoss
"PROVIDER_HOST"="remote://OTMM-Node1:11099,remote://
OTMMNode2:11099"
where
OTMM-Node1 and OTMMNode2 are Media Management instances in a two-
node cluster.

16.4. OTMM cluster
For more information about the TResource file, see OpenText Media Management
To enable API failover in TomEE:
1. In a text editor, open the %TOMEE_HOME%\conf\multicast.properties file.
2. Update value of the disabled parameter to false. For example:
org.apache.openejb.server.discovery.MulticastDiscoveryAgent
bind = 235.25.20.3
port = 6142
disabled = false
group = default
3. Edit the PROVIDER_HOST setting in the [JNDI\CONFIG] section of the Tresource

file.
Example 16-8: PROVIDER_HOST configuration for TomEE

PROVIDER_HOST configuration
"PROVIDER_HOST"="multicast://multicastaddress:port"
where
multicastaddress is the bind parameter value in the %TOMEE_HOME%
\conf\multicast.properties file
port is the port parameter value in the %TOMEE_HOME%\conf\
multicast.properties file
For more information about the TResource file, see OpenText Media Management
16.4.4 Testing Media Management on the first node

Before continuing with the configuration, test that OTMM is set up correctly on the
first cluster node by performing the instructions in “Verifying the OTMM
installation“ on page 213.

16.4.5 Media Management Indexer configuration on the cluster

nodes
Each Media Management installation contains an Indexer component. The Indexer is
responsible for keeping the search index synchronized with the Media Management
repository. In an HA environment, one of the Indexers will be the active Indexer,
fetches and indexes assets from the Media Management database. The other
installed Indexers will be waiting (inactive, on-call) to take over if the active Indexer
fails. The Indexer Monitor keeps track of the available Indexers and makes sure one
Indexer is always active to process data. The Indexer Monitor performs the
following administrative tasks:
• Maintains a list of active and inactive Indexers. Indexers running in an HA
environment check in periodically to verify that they are still running or still
active.
• Monitors if the active Indexer is still active. If not, it will activate another Indexer.
• Logs all the administrative tasks it has performed.
To set up the Indexer monitor:
1. Stop the Indexer on all the nodes by running one of the following commands:
WINDOWS
Stop the OpenText Indexer service from the Services menu.
LINUX
At the command prompt, run the following command:
<TEAMS_HOME>/bin/stopIndexer.sh
2. PostgreSQL only - Set up a job scheduler in the database to support the HA

configuration for Solr-based searching and indexing.
Note: An HA configuration for Solr-based searching and indexing

requires a pgAgent, which is a job scheduler for PostgreSQL. The pgAgent
is not installed by default on PostgreSQL. You must download and install
it.
a. Install pgAgent.
Note: Identify the appropriate installation package for your operating

system and PostgreSQL database. For Red Hat Linux, RPM packages
are available. For Windows, if you installed the PostgreSQL database
from EnterpriseDB, you can install pgAgent through the Application
Stack Builder where it will be listed in the add-ons, tools and utilities
category.
b. To set up the pgAgent schema on the Media Management database, do one
of the following:

16.4. OTMM cluster
• If your OTMM database is on Windows and you installed pgAgent

through the Application Stack Builder from EnterpriseDB, run the
following scripts on the OTMM database using the database credentials
that you configured during installation:
<pgagent installation directory>/pgagent.sql
<pgagent installation directory>>/pgagent_update.sql (if
present)
Note: To run these SQL scripts, use PSQL or pgAdmin.
• If your OTMM database is on Linux, connect to the OTMM database

using the database credentials that you configured during installation,
and then run the following:
create extension pgagent;
Note: To run this SQL command, use PSQL or pgAdmin.
c. To set up the password file for the pgAgent service or daemon, do one of
the following:
Important
Do not enter the password in the pgAgent connection string as it
might be visible to all users in the Task Manager output or ps
command.
WINDOWS
• In a text editor, create the following file using the log-in account for
the pgAgent service:
%APPDATA%\postgresql\pgpass.conf
• Add a row for the OTMM user and database using the following
format:
hostname:port:database:username:password
LINUX
• In a text editor, create the following file, with (0600) permission,

using the log-in account for the pgAgent daemon:
~/.pgpass
• Add a row for the OTMM user and database using the following
format:
hostname:port:database:username:password
Note: For more information about creating the password file, see
https://www.postgresql.org/docs/current/static/libpq-pgpass.html.
d. To set up the pgAgent service or daemon, do one of the following:

WINDOWS
Install the pgAgent service for the OTMM database by running the
following:
"<pgAgent Install Directory>/pgAgent" INSTALL OTMM_pgAgent
-u <Domain Username> -p <DomainPassword> hostaddr=<dbserver
address> dbname=<OTMM dbname> user=<OTMM dbusername>
where
Domain Username is name of the user who is running the pgAgent
service
DomainPassword is password of the user who is running the pgAgent
service
dbserver address is the host name of the database that you used in
the password file
OTMM dbname is the name of the OTMM database
OTMM dbusername is the name of the OTMM schema owner
LINUX
Install the pgAgent daemon for the OTMM database by running the
following:
/path/to/pgagent hostaddr=<dbserver address> dbname=<OTMM
dbname> user=<OTMM dbusername>
where
dbserver address is the host name of the database that you used in
the password file
OTMM dbname is the name of the OTMM database
OTMM dbusername is the name of the OTMM schema owner
For more information about setting up pgAgent as a service or daemon on

your operating system, see http://www.pgadmin.org/docs/dev/
pgagent.html.
3. Register the Indexer on the first cluster node with the Indexer Monitor by
entering the following command, at the command prompt, from the
TEAMS_HOME>\install\ant directory:
ant configure-indexer-ha
4. On the first cluster node, start the Indexer Monitor by entering the following
command, at the command prompt, from the <TEAMS_HOME>\install\ant
directory:
ant create-indexer-monitor-job

16.4. OTMM cluster
Important
This section is not applicable to SAP HANA. For more information
indexing for SAP HANA, see “Creating and starting the scheduler
indexer monitor job” on page 245.
Tip: To stop the Indexer Monitor at any time, enter the following
command:
ant drop-indexer-monitor-job
5. On all other nodes, register their the Indexers with the Index Monitor by
entering the following command from the <TEAMS_HOME>\install\ant
directory:
ant configure-indexer-ha
6. Start the Indexer on all the nodes by doing on of the following:
WINDOWS
Start the OpenText Indexer service from the Services menu.
LINUX
At the command prompt, enter the following command:
<TEAMS_HOME>/bin/startIndexer.sh
Indexer Monitor Configuration
The Indexer Monitor can be configured to do the following:

• Set the amount of inactive time it will wait before trying to switch the active
Indexer. The default is five minutes.
• Set the frequency for how often to perform its checks. The default is two minutes.
• Set the debug log level, which controls how much information is logged in the
INDEXER_MONITOR_LOG table. The default is 0, the minimum amount.
The Indexer Monitor consists of several tables, functions, procedures, and triggers in
the Media Management database which can be installed and configured using
several Ant scripts.
• Indexer activation sequence:
The Indexer Monitor assigns the active status in sequence. As each Indexer
registers, it is assigned a sequence number. The first Indexer started will be
assigned sequence = 1. You can use the default sequence numbers or assign your
own.
It is possible to assign sequence numbers to registered indexers to control the
order in which backup Indexers are activated after a failure.
To assign a sequence number to an Indexer:
• ant –Dix.sequence=3 change-indexer-sequence

To assign a sequence number to a remote Indexer:
• ant Dix.hostname=remotehost Dix.sequence=6 change-indexer-sequence
Note: All the ant scripts mentioned in the following sections should all be
run on the first node from the <TEAMS_HOME>/install/ant directory.
Indexer Monitor Job frequency

The Indexer Monitor job is scheduled by default to run every two minutes. At
this time, the monitor checks the Indexer table to verify the active Indexer has
checked in. To modify the value of the job frequency for SQL Server, Oracle, or
PostgreSQL, use the Ant task. For SAP HANA, use the XS Job console.
To modify the job frequency for SQL Server, Oracle, or PostgreSQL:
• At a command line, enter the following Ant task:

ant -Dfrequency=<#> change-indexer-monitor-job-frequency
where
<#> is the frequency desired (in minutes)
To modify the job frequency for SAP HANA:
• Navigate to XS Job console and update the frequency value.
Max Indexer inactivity

By default, if the active Indexer does not check in every five minutes, it is
considered failed and given an INACTIVE status. At this time, a new Indexer is
promoted to the ACTIVE status. To modify the maximum inactivity time for
SQL Server, Oracle, or PostgreSQL, use the Ant task. For SAP HANA, use the XS
Job console.
To modify the maximum inactivity time for SQL Server, Oracle, or

PostgreSQL:
• At a command line, enter the following Ant task:

ant -Dtimeout=<#> change-indexer-monitor-timeout
where
<#> is the timeout desired (in minutes)
To modify the maximum inactivity time for SAP HANA:
• Navigate to XS Job console and update the scheduler timeout value.
Indexer Monitor debug log level

The Indexer Monitor logs its activity in the INDEXER_MONITOR_LOG table.
By default, the log level is set to zero (0). Use the following Ant task to adjust the
Indexer Monitor logging level:
ant -Dlevel=<#> change-indexer-monitor-debug-level

16.4. OTMM cluster
where
<#> is one of the following values:
Dlevel When it logs information

0 • When the monitor process starts.
• When the monitor process is
terminated.
• When the frequency of the monitor
process is changed.
• When a new Indexer record is added to
the INDEXER_MONITOR_TABLE.
• When the record for an Indexer is
deleted from the
INDEXER_MONITOR_TABLE.
• When the IS_ACTIVE value changes
for an Indexer record in the
INDEXER_MONITOR_TABLE.
1 • Every time the monitor process runs.
2 • Every time the Indexer calls the
“checkin” procedure.
• When the monitor process determines
that there are no inactive and valid
Indexers available to be made active.
• When the monitor process determines
that the current active Indexer is still
valid.
Note: The debug log level controls the amount of logging information
added to the INDEXER_MONITOR_LOG table.
16.4.6 Creating and starting the scheduler indexer monitor job

Note: This section is only applicable to SAP HANA.
Prior to creating a scheduler, you must have SAP HANA Studio installed.
To create and starting the scheduler indexer monitor job:
1. Grant the following XS privileges to the user who you want to schedule the job.
• sap.hana.xs.admin.roles::JobAdministrator
• sap.hana.xs.admin.roles::HTTPDestAdministrator
2. Verify that XS engine is installed and running by accessing the following URL:
http://<ipaddress/hostname>:8000/
3. Change the SAP HANA Studio Perspective to SAP HANA Development.

4. Click the Window menu > Perspective > Open Perspective > Other.
5. In Open Perspective click SAP HANA Development.
6. Click File > XS Project.
7. Create an XS Project and name it, for example OTMM, and click Next.
8. Add the workspace and click Next.
9. Choose the XS JavaScript file name, for example, OTMM.xsjs, and click Finish.
Note: This creates a project with the following files:
OTMM
JavaScript Resources
SAP HANA System Library
.xsaccess
.xsapp
OTMM.xsjs
10. To create an XS Job scheduler file in the project that you created in Step 9, OTMM,
do the following:
a. Right-click the project, for example OTMM, and click New > Other.
b. Choose XS Job Scheduler File and click Next.
c. Enter the name of the parent folder. For example, OTMM.
d. Enter a name for the file, for example OTMM.xsjob, and click Finish.
11. Double-click the OTMM.xsjs file and do the following:
a. Remove the content of the file.

b. Add the following to the empty file:
Note: Replace <teams_owner> with the Media Management schema

owner.
function OTMM_MONITOR()
var query = "{CALL <teams_owner>.MONITOR_INDEXERS}";
$.trace.debug(query);
var conn = $.db.getConnection();
var pcall = conn.prepareCall(query);
pcall.execute();
pcall.close();

16.4. OTMM cluster
conn.commit();
conn.close();
}
Notes
• The above schedule runs every 59 seconds.
• The following describes the content of the OTMM.xsjob file:
Description
The description you give for this Job
Action
The stored procedure or XSJS function name that you want run.
The name must be complete with the package path prefixed to
it.
Schedules
This block contains the properties of the schedule frequency.
Description
The description of the job frequency.
xscron
The frequency of the job. For more information, see the
following:
XSCron syntax Meaning and permitted value

Year Four digits. For example, 2017.
Month 1 to 12
Day -31 to 31
DayofWeek mon,tue,wed,thu,fri,sat,sun
Hour 0 to 23
Minute 0 to 59
Second 0 to 59
12. Double-click the OTMM.xsjob file and do the following:
a. Remove the content of the file.

b. Add the following to the empty file:
{
"description": "Call the procedure MONITOR_INDEXERS",
"action": "OTMM:OTMM.xsjs::OTMM_MONITOR",
"schedules": [
{
"description": " Call the procedure
MONITOR_INDEXERS ",

"xscron": "* * * * * * 59"

}
]
}
13. To activate all the objects do the following:
a. Right-click the name of the project.

b. Click TEAM > Activate All.
c. Choose all the objects in OTMM to activate them, and click OK.
14. To navigate to the XS Job dashboard, do the following:
a. Click the following link to open the XS Job console.

http://<DB HOST NAME>:8000/sap/hana/xs/admin/#/package/
XS_Job_learning
b. Sign in and click > XS Job Dashboard.
15. In the XS Job dashboard, navigate to Scheduler Enabled and set it to Yes.
16. Click the scheduler called OTMM.
17. To activate the schedule job, do the following:
a. Click the name of the schedule, for example OTMM.

b. Click the Configuration tab.
c. Select the following check boxes:
• Activate
• Schedules
d. Click Save Job.
18. To enable the job log clean-up do the following:
a. Click the Log Cleanup tab.

b. Select Yes for Job Log Cleanup Enabled.
c. Provide values for XSCron and Day.
d. Click Save Job.
Note: The syntax for XSCron is as follows:

• Year Month Day DayofWeek Hour Minute Second
where
Year Is four digits. For example, 2017.

Month is 1 to 12
Day is -31 to 31

16.4. OTMM cluster
DayofWeek mon,tue,wed,thu,fri,sat,sun
Hour 0 to 23
Minute 0 to 59
Second 0 to 59
• The asterisk (*) indicates that the cron expression matches for all
values of that segment.
19. To verify the status of the job, click the Job Details tab and verify that the status
is active.
20. To verify the status of the job schedule, click View Logs.
16.4.7 Solr configuration on cluster nodes

The Solr HA configuration assumes that Media Management is installed on the node
or on a remote Solr node, and that the Indexer configuration has been successfully
completed.
The default Media Management installation assumes one Solr server per OTMM
application install node.
Note: If you are experiencing search performance issues in an HA

environment, you can adjust optional settings through the Settings page in the
Web Administration tool. For more information, see the following:
• Section 2.13.2.3 “Editing a component and properties” in OpenText Media
Management - Administration Guide (MEDMGT-AGD)
• Section 13.1.11 “COMMON\SOLR” in OpenText Media Management -
Administration Guide (MEDMGT-AGD)
16.4.7.1 Solr master configuration

To configure a Solr master server:
1. Choose any node in the OTMM cluster to be the master Solr server.
2. Sign in to this machine as the OTMM user.
3. At the command prompt, change the directory to <TEAMS_HOME>/install/ant

and enter the following command:
4. Restart the Solr server.

16.4.7.2 Solr slave configuration

To configure Solr as a slave on all other Media Management nodes:
1. Run the following Ant task to set up the slave Solr configuration:
2. Restart the Solr server.
16.4.7.3 Configuring Solr on a remote host for HA

To configure Solr on a remote host for HA:
• On Windows, perform the steps in “ Converting a remote Solr instance to

HA” on page 52.
• On Linux, perform the steps in “To convert a remote Solr instance to HA:“
on page 69.
16.4.7.4 Solr master failover

The Solr master server is responsible for all indexing tasks. If there is a failure and
the Solr master becomes unavailable, the Indexer will not be able to successfully
update assets for searching. When the Indexer detects a Solr failure that persists for
more than the value specified in the MAX_DOWNTIME setting, it will send an email to
the ADMIN_EMAIL_ADDRESS.
The Indexer only detects the Solr master failure while it is actively indexing assets.
For example, the Solr master server fails at 1:00 AM. At 10:00 AM users sign in to
OTMM and update assets. As the Indexer attempts to update the assets, it discovers
that the Solr master server failed. If MAX_DOWNTIME is set to five minutes, the Indexer
sends an email to ADMIN_EMAIL_ADDRESS at 10:05 AM, five minutes after it discovers
the failure. An email is not sent if the Solr master connection becomes available
before the MAX_DOWNTIME limit.
Notes
• You can configure the ADMIN_EMAIL_ADDRESS and MAX_DOWNTIME through
the Settings page. For more information, see Section 2.13.2 “Configuring
components” in OpenText Media Management - Administration Guide
(MEDMGT-AGD).
• By default, the MAX_DOWNTIME is set to five minutes.
To configure a new Solr master:
1. Sign in to the OTMM instance where the Solr server is the server that you want
to become the new master.
2. At the command prompt, enter the following command from the
<TEAMS_HOME>/install/ant directory:

16.4. OTMM cluster
ant disable-solr-master
Note: Running this command disables the current Solr master in the
SOLR_MONITOR_TABLE.
3. At the command prompt, enter the following command from the

Notes
• Running this command causes the current host's Solr server to become
the new master server.
• If this OTMM node’s Solr server is remote, copy the configuration from
the local <TEAMS_HOME>/solr5_otmm/otmm/conf to the remote server’s
index, and then restart the Solr server.
• For Linux systems, after copying the conf directory to the remote
server, but prior to restarting the Solr server, change the permissions of
the directory to be owned by the Solr user by executing the chown -R
<solr username> conf command from the solr5_otmm/otmmcore
directory.
• There is a chance that some indexed assets might not have been
replicated to the slave before the failure. In that case, the administrator
may want to repopulate the INDEX_WORKQUEUE following the
instructions Section 6.3.1 “Reverting to a backup copy of the Solr index
files” in OpenText Media Management - Administration Guide (MEDMGT-
AGD), skipping the index restoration in step 3.
• For this task, the start.date will be the time of the Solr failure.
Important
On all other HA nodes, issue the following command from the
<TEAMS_HOME>/install/ant directory to configure the slaves to point to the
new Solr master:
ant update-solr-slave
If this OTMM node's Solr server is remote, copy the configuration from the
local <TEAMS_HOME>/solr_otmm/otmmcore/conf to the remote server's
index, and then restart the Solr server.
Notes
• For Linux systems, after copying the conf directory to the remote server, but
prior to restarting the Solr server, change the permissions of the directory to
be owned by the Solr user by executing the chown -R <solr username>
conf command from the solr5_otmm/otmmcore directory.

• Searching will continue after a Solr master failure. New assets will not be
reflected in the search results until all the slave nodes have successfully
replicated from the new master.
To re-configure a failed Solr Master node as a Solr slave:
1. Stop Solr server.
Note: There should be only one Solr master running.
2. To configure the node as a slave, run the following Ant task from the
Notes
• If this OTMM node's Solr server is remote, copy the configuration from
the local <TEAMS_HOME>/solr5_otmm/otmmcore/conf folder to the
remote server's index, and then restart the Solr server.
• If you are running on Linux, after copying the conf directory to the
remote server, change the permissions of the directory to be owned by
the Solr user by executing the chown -R <solr username> conf
command from the solr5_otmm/otmmcore directory.
The Solr server will reload the new slave configuration and the machine will now
work as a Solr slave node.
16.5 Risks
The following risks exist with this configuration and must be managed. They
include the following:
• Any custom background processes must be designed and built to appropriately
provide HA support.
• Support for in-flight session failover is not provided.

Chapter 17
Appendix A ‒ Uninstalling the Media Management
application
This appendix provides instructions for how to uninstall and clean your
environment. These instructions are helpful if you are performing multiple
installations or test installations.
17.1 Uninstalling Media Management

To uninstall Media Management:
1. Windows - Navigate to Programs and Features and select it. For example, in
the classic view of Control Panel, select Start > Settings > Control Panel >
Programs and Features.
2. Windows - Select OpenText Media Management from the list of applications

installed on the server and click Change/Uninstall.
Note: There is a known issue where the uninstall will sometimes fail with
an exception that says ...iawin32.dll not found. iawin32.dll is not
available in %TEAMS_HOME%\UninstallMediaManagement\resource.
The cause of this is the uninstaller is running using 32–bit Java instead of
64–bit. If you are getting this exception, run the following at the command
prompt from the %teams_home%\UninstallMediaManagement\ directory:
"Uninstall MediaManagement" LAX_VM "%java_home%\java.exe"
3. Linux - Sign in to the Linux machine as the root user and perform the following:
• Change directory to $TEAMS_HOME/UninstallMediaManagement and run

./Uninstall\ MediaManagement
Note: There is a space in the name of the uninstall executable.
4. Click Next.
5. Select Complete Uninstall (recommended) or Uninstall Specific Features (for

Expert users), and then click Next.
6. Select the OTDS Resource for OTMM check box to delete the OTDS Resource
that was created during the OTMM installation.
7. Select Yes, restart my system and click Done. The system will restart and the
Media Management application will be removed from the system.

Chapter 17 Appendix A ‒ Uninstalling the Media Management application
8. After Media Management has been removed and the system has been restarted,
verify that the OpenText Media Manager and OpenText Indexer services have
been removed. If they have not been removed, then use the following
commands to delete them:
sc delete OpenTextMediaManagementService
sc delete OpenTextIndexer
Note: The files and folders under the <TEAMS_HOME> and

<TEAMS_REPOSITORY_HOME> directories may still be available. If so,
manually delete them.
9. Linux - Delete the following manually, if required:
a. Delete the folder with name otmm from /etc/opentext.

b. Delete the following files from /etc/init.d:
• indexer-process-manager
• All the files with the prefix mediamanagement-process-manager
Note: You can perform this task using the root user or the user who
configure OpenText Media Management on Linux as part of the post-
installation tasks.
10. Proceed to “Uninstalling the Media Management database” on page 255to

remove Media Management database from the database server.
11. Proceed to “Uninstalling Solr” on page 256 to remove Solr.
Notes
• It is possible to uninstall Media Management as the OTMM user on Linux.
When a non-root user has uninstalled Media Management on Linux, the /
var/.com.zerog.registry.xml file must be manually edited to remove the
Media Management products and components information. When editing
this file, take care to only remove the Media Management related entries.
• For more information about how to uninstall OTDS, see OpenText Directory
Services - Installation and Administration Guide (OTDS160204-IWC).

17.1. Uninstalling Media Management
17.1.1 Uninstalling the Media Management database

To uninstall the Media Management database on Windows:
1. Oracle database - To delete the Oracle schema, run the following command
while logged in as the “system” user:
Drop user <teams_owner> cascade;
Note: <teams_owner> should be the schema owner.
2. SQL Server database - To delete the SQL Server database, do the following:
a. Log on to the database instance through the SQL Server Management

Studio using the 'sa' admin account.
b. Expand the SQL Server Agent and open the Job Activity Monitor. Delete
the Indexer Update job related to your database.
c. Expand the databases and right-click your database to delete it. Select the
Close all connections check box.
d. Expand Databases'sysdb'Security'Users and delete your related database
user. This is not applicable if you have uninstalled SSMA.
e. Expand Security'Logins and delete your related database login.
f. If any of these deletions fail, some of the processes you are trying to delete
may still be running. If so, expand Management and open the Activity
Monitor to determine if there are processes that need to be stopped and
then deleted.
3. PostgreSQL database - To delete the PostgreSQL database, do the following:
a. If you set up the HA Indexer and if pgAgent was configured as a service,

stop and delete the service. If pgAgent is running from a shell, stop the
process.
b. Connect to the PostgreSQL database using the pgAdmin client as database
super user, and do the following:
i. Drop the Media Management database.

ii. Drop the Media Management tablespaces. For more information, see
Step 6 on page 33.
iii. Drop the login role configured for Media Management.
4. SAP HANA - To delete the SAP HANA schema, do the following:
a. Sign in as the system user.

b. Run the following command:
DROP USER <teams_owner> CASCADE;
Note: The schema owner must be <teams_owner>.

17.1.2 Uninstalling Solr

To uninstall Solr on Windows:
1. Locate and record the location of the following:
• The nssm-2.24 folder installed to configure the Solr Windows service
Tip: If you are not sure where this was installed, you can be inspect the
properties of the Solr service in the Windows Services panel. The
nssm-2.24 folder will be listed as part of the Path to executable
property.
• The solr-5.3.1 folder where the Solr distribution was installed.
Tip: If you are not sure where this was installed, you can be inspect the
properties the HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\
services\Solr5.3.1\Parameters registry entry.
• If Solr was installed on a separate server from Media Management, the
\solr5_otmm folder containing the OTMM specific Solr indexes and
configuration.
Tip: If you are not sure where this was installed, you determine this
from the coreRootDirectory entry in the solr5.3.1\server\solr\
solr.xml file below the solr5.3.1 folder.
2. Stop the Solr Windows service.

3. Execute the \nssm-2.24\uninstallSolrService.bat script, which is located
in the nssm-2.24 folder.
4. Delete the following folders:
nssm-2.24
solr-5.3.1
Note: If Solr was installed on a different machine than Media

Management, delete the solr5_otmm folder.
To uninstall Solr on Linux:
1. Locate and record the location of the following:
• The directory underneath which the Solr distribution was installed. This will
be referred to as the SOLR_INSTALL_ROOT in the following instructions. The
Solr installer defaults to /opt, but you can override this during installation.
Tip: If you are not sure where this was installed, you determine it from
the SOLR_INSTALL_DIR entry in the /etc/init.d/solr script. If this
entry is set to /opt/solr, then /opt would be the
SOLR_INSTALL_ROOT.

17.1. Uninstalling Media Management
• The directory used by Solr to store writable files. This will be referred to as
the SOLR_FILES_DIR in the following instructions. The Solr installer defaults
to /var/solr, but you can override this during installation.
Tip: If you are not sure where this was installed, you can determine it
from the SOLR_ENV entry in the /etc/init.d/solr script. If this entry
is set to /var/solr/solr.in.sh, then /var/solr would be
SOLR_FILES_DIR.
• If Solr was installed on a separate machine from Media Management, the

solr5_otmm directory containing the OTMM indexes specific to Solr specific
and configuration.
Tip: If you are not sure where this was installed, you can determine it
from the coreRootDirectory entry in the <SOLR_FILES_DIR>/data/
solr.xml file.
2. Stop the Solr service by running the following command:

sudo service solr stop
3. Remove the Solr service by running the following command:

sudo chkconfig --del solr
4. Delete the Solr installation directory and the symbolic link below the
SOLR_INSTALL_ROOT by running the following commands:
sudo rm <SOLR_INSTALL_ROOT>/solr
sudo rm -r <SOLR_INSTALL_ROOT>/solr-5.3.1
5. Delete the Solr installation directory, SOLR_FILES_DIR, by running the

following command:
sudo rm -r <SOLR_FILES_DIR>
For example:
sudo rm -r /var/solr
6. Remove the Solr service boot script by running the following command:
sudo rm /etc/init.d/solr
Note: If Solr was installed on a different machine than Media

Management, delete the solr5_otmm directory:
For example:
sudo rm -r /var/solr5_otmm

17.2 Reinstalling Media Management

To reinstall Media Management:
1. Uninstall Media Management. For more information, see “Appendix A ‒

Uninstalling the Media Management application“ on page 253.
2. If you saved the mediamanagement_config.txt file, you can re-use it now.
3. If you did not select the OTDS Resource for OTMM check box when you
uninstalled Media Management, and you want to use the same resource for
OTMM that you used previously, then deactivate it or configure a new OTMM
resource on the OTDS server. For more information, see “Configuring OTMM
resources in OTDS” on page 35.
4. Install Media Management.

Chapter 18
Appendix B ‒ Validation checks
Before installing, the user-entered parameters for installation are validated. This list
contains the validation checks that are performed.
Database • Verify that only one database type, Oracle, SQL Server, PostgreSQL, or
Validation SAP HANA has been selected.
• Verify that a database connection can be established.
Application Verify that the base installation directory does not contain the terms
Validation 'teams' or 'data'.

Chapter 19
Appendix C – Deploying the OpenText Private Help
Server
This section discusses how to download a copy of the OpenText Media

Managementonline help files and host them on a local server by deploying the
OpenText Private Help Server.
19.1 Implementing the OpenText Private Help Server

for OpenText Media Management
The OpenText Media Management online help is delivered using the OpenText
Global Help Server system, which provides users with live access to the latest
version of the online help. If you do not want to use the OpenText Global Help
Server system, you can choose to download a copy of the online help files and host
them on a local server by deploying OpenText Private Help Server.
Note: The Private Help Server can support multiple OpenText products. If the
Private Help Server has already been installed within your organization to
support another OpenText product, you can add the OpenText Media
Management online help to that installation.
Setting up the Private Help Server requires you to complete the following general
tasks:
1. Prepare a server with the following:

• Apache Tomcat 7 or 8 application server.
• Java 1.6 or later.
2. Download and extract a copy of the product help files from OpenText My
Support.
3. Deploy the Private Help Server, which includes a web application that can locate
and return the locally deployed help files.
4. Configure the product to direct help requests to the Private Help Server.

Chapter 19 Appendix C – Deploying the OpenText Private Help Server
19.1.1 Downloading the OpenText Private Help Server Kit and

product online help files
The first step in setting up the OpenText Private Help Server Kit is gathering the
required files. These include the following:
• The OpenText Private Help Server Kit is available on OpenText My Support:
https://knowledge.opentext.com/go/62360624
• A copy of the product online help files that the Private Help Server will host. The
ZIP files for the OpenText™ Media Management Administration private help
system, and the OpenText™ Media Management Mobile Client and OpenText™
Media Management Web Desktop Client private user help systems are located
on OpenText My Support (https://knowledge.opentext.com/knowledge/cs.dll/
open/71520139).
19.1.2 Deploying the Private Help Server

You can install the Private Help Server application by completing the tasks
described below.
Extracting the files

Extract the Private Help Server Kit to a temporary directory. You will modify the
files in this working directory and then deploy them to your site in later steps.
Notes
• The Private Help Server Kit contains two similarly named files, one
compatible with Apache Tomcat 7.x and the other with Apache Tomcat 8.x.
During the setup process, you will need to rename these files by removing
the version information for the file that is compatible with your version of
Apache Tomcat.
• The Private Help Server Kit supports two help file branches, help and
pi_hosted, and contains support files for each branch. OpenText Media
Management uses the pi_hosted branch.
After you extract the files, you should see an Private Help Server Kit directory
that includes the following:
• application directory: Contains docsapimapper.war, the Private Help Server
Web application file.
• help_support directory: Contains support files for the help branch:
• docsapimapper.xml.tomcat<version>: The Web application descriptor file.

• docsapimapper.properties: The configuration properties file declaring the
installed product help under the help branch and the installation path.
• pi_hosted_support directory: Contains support files for the pi_hosted branch:

19.1. Implementing the OpenText Private Help Server for OpenText Media Management
• docsapimapper.xml.tomcat<version>: The Web application descriptor file.

• pidocsapimapper.properties: The configuration properties file declaring
the installed product help under the pi_hosted branch and the installation
path.
• Sample directory: Contains sample descriptor and configuration files taken from
a working sample deployment for each branch. Do not use these files in your
deployment.
• _readme.txt: A summary description of the files intended for users without
access to the information in this guide.
• docs.zip: Sample help files used to verify your Private Help Server deployment.
• Test Help Page - OT Private Help Server.zip: A sample page you can use to
connect to your Private Help Server deployment.
Creating the local help directory

You must create the <help_root> directory, which is the directory where you will
deploy the help files you want to make available through the Private Help Server
and then add the test files used to verify your deployment.
To create the <help_root> directory:
1. Create the directory where you will extract the online help files, for example C:
\ot_docs.
The <help_root> directory can exist on any local drive, but its path must not
contain any names with spaces.
2. Extract the sample help files in the docs.zip file into the <help_root> directory.
Note: Always use the Extract all option when you extract OpenText online
help files.
3. After you extract the files, open the <help_root>/docs/pi_hosted/test/
v160200/test-h-ugd/en/ofh directory and verify that the following files were
extracted:
• context.properties
• index.html
Creating a help folder alias

You need to define an alias that the Private Help Server application can use to locate
the online help files.
To create the help folder alias:
1. In the pi_hosted_support folder where you extracted the zip file, rename the
docsmapperapi.xml.tomcat<version> file for your version of Tomcat to
docsmapperapi.xml.

2. Open the docsmapperapi.xml file in a text editor, and then locate the
<Context> element.
3. Replace the <help_root> with the full path to the help file directory you created
in “To create the <help_root> directory:“.
For example, using the folder created above, the setting for Apache Tomcat 7.x
on Windows is:
<?xml version="1.0" encoding="UTF-8"?>

<Context aliases="/docs/pi_hosted=C:\ot_docs\docs
\pi_hosted
</Context>
Note: On non-Windows operating systems, use appropriate slashes,

double quotes, and brackets, for example:
<Context aliases="/docs/pi_hosted=C:/ot_docs/docs/pi_hosted">
The same example for Apache Tomcat 8.x is:
<?xml version="1.0" encoding="UTF-8"?>

<Context>
<Resources
className="org.apache.catalina.webresources.StandardRoot" >
<PreResources webAppMount="/docs/pi_hosted" base="C:/
ot_docs"
className="org.apache.catalina.webresources.DirResourceSet" />
</Resources>
</Context>
Creating a configuration properties directory

You must create a properties file that contains the setting required to locate your
help files.
To create a configuration properties directory and file:
1. Create a folder where the configuration properties file will be stored, known as
the properties root directory. For example C:\ot_docsconfig\properties
\docsmapper.
Note: You can create the properties root directory on any local drive, but
the directory path must:
• Not contain any spaces or special characters.
• Contain the subdirectories \properties\docsmapper. For example, if
the properties root directory is C:\ot_docsconfig, the full path is C:
\ot_docsconfig\properties\docsmapper.
2. In the pi_hosted_support folder, copy the pidocsapimapper.properties file

from the extracted files to the <properties_root>\properties\docsmapper
directory.

3. Open the pidocsapimapper.properties file in a text editor and define the

webserverHelpRoot and techDocs Root settings as follows:
webserverHelpRoot
The Tomcat root URL for the local help. The URL contains the following
information:
http://<host>:<port>/docsapimapper/docs/pi_hosted
where <host> is the server where Tomcat is deployed and <port> is the port
on which Tomcat listens. For example, on a server named host.
mycompany.com listening on port 8080, the setting is:
http://host.mycompany.com:8080/docsapimapper/docs/pi_hosted
Note: Specify the full server name or IP address as the <host> value.
Do not use localhost. Also, the value you use must be used in all
<host> settings, including URLs. IP address will not resolve to host
names and host names will not resolve to IP address.
techDocs Root
The path to the directory where the help files are stored. For example C:/
ot_docs/docs/pi_hosted.
<product_code>
Each OpenText product online help is identified by a specific product code.
In the <PRODUCT CODE> section of the file, create a new line and specify
your product code as <product_code>=<product_code>.
The product code setting for OpenText Media Management is: medmgtmod
medmgt
Example 19-1: Sample pidocsapimapper.properties file
# All values marked by < > must be updated.

# This file should be on the app server class path.
# URL and directory mappings

# helproot server MUST match JS setting
webserverHelpRoot=http://host.mycompany.com:8080/
docsapimapper/docs/pi_hosted
#Path to the help folder root

techDocsRoot=C:/ot_docs/docs/pi_hosted
# <PRODUCT CODE>
# Product directory mapping - will be the same as the
OpenText product name setting in the live Private Help Server
implementation.
# See your product documentation for the specific value for
your product.
# Some OpenText product codes are:
# Media Management: medmgt=medmgt

# InfoFusion: inf=inf
# Web Experience Management: wcmgt=wcmgt
# NOTE: test=test is required to verify the initial set up.
test=test
medmgtmod
medmgt
# Default locale to use

defaultLocale=en
# Parameter names - DO NOT MODIFY UNLESS INSTRUCTED

product=product
version=version
locale=locale
context=context
module=module
type=type
securityKey=security
Installing the descriptor and application files

The final step before testing the Private Help Server is deploying the application
files.
To install the files and start the application:
Important
Verify that Tomcat services are not running when you complete these tasks.
1. Copy the docsapimapper.war file into the <Tomcat_home>\webapps directory.

If there is an existing docsapimapper directory or docsapimapper.war file in
the folder, delete them.
2. Copy the docsapimapper.xml file from the working directory into the
<Tomcat_home>\conf\Catalina\localhost directory. If the Catalina\
localhost directory does not exist, create it.
3. Add the <properties_root> you created in “To create a configuration properties

directory and file:“ on page 264 (for example C:\ot_docsconfig) to the Tomcat
Java classpath.
For example, on Windows run the tomcat<x>w.exe file in the <Tomcat_home>
\bin folder, click the Java tab, and then append the properties root path to the
Java Classpath field. On non-Windows, set the path using the setenv.sh
command.
4. Start Tomcat.

Testing the Private Help Server

After Tomcat starts, you can test the deployment by submitting URL requests to it
through the Private Help Server Test Page. The Test Page contains a simple
JavaScript function that simulates an online help button that can call the test help
pages that are included with the Private Help Server.
Note: The Test Page is intended to verify that your Private Help Server is
installed and configured correctly. The page uses a simple method to request
the help files that may not work with all online help formats. Do not attempt to
modify the page to access other online help files or beyond the tasks described
in the procedure below.
To test the Private Help Server:
1. Extract the Test Help Page - Private Help Server.zip file to a working
directory.
help files.
2. In the extracted Test Help Page - OT Private Help Server folder, locate the
pi_hosted\TestPage.html file, and then open it in a text editor.
3. Locate the urlRoot: setting, and then replace the <host> and <port> values with
your Tomcat server name and the port on which it listens.
4. Save the file and then open it in a browser.
Note: We recommend that you use a recent release of the Firefox or

Chrome browsers.
5. Click Test Your Local Server to test your deployment.

The page displays the URL it will attempt to open based on the settings you
made to the HTML file.
If the Private Help Server is deployed correctly, the URL will be processed and
return a help page that confirms that the deployment is working.
Deploying additional help files

Once you have successfully set up the Private Help Server, you can deploy other
product help files in addition to the test file.
To deploy additional help files:
1. Stop Tomcat.
2. Extract the additional help files to the help root folder you created in “To create
the <help_root> directory:“.

help files.
3. Update the Private Help Server help registry by executing the following
command at a command line prompt:
java -jar <tomcat_home>\webapps\OTHelpServer\WEB-INF\lib
\HelpServer-<version>.jar -d <help_dir> -s
where <tomcat_home> is the path to your Tomcat installation, <version> is an
optional version number in the jar file name and <help_dir> is the help root
folder. For example, the following command updates the help registry for a
help root folder C:\ot_docs\docs\pi_hosted:
java -jar C:\PROGRA~1\APACHE~1\TOMCAT~1.0\webapps\OTHelpServer
\WEB-INF\lib\HelpServer-16.0.0.jar -d C:\ot_docs\docs\pi_hosted -s
4. Edit the pidocsapimapper.properties file and add the product code for your
help on the line below the test setting test=test. For more information, see
“Creating a configuration properties directory” on page 264.
5. Restart Tomcat.
To access the help files, you can use the TestPage.html file as long as you modify
the settings to reflect the values for your help. You can gather these settings from the
file path after you extract the help files to the help folder.
The help file path uses the following convention:
<helproot>/docs/pi_hosted/<product>/<version>/<module>/<language>/
<type>
For example, the OpenText Web Experience Management - Content Workspaces Help
(WCMGT-H-UGD) version 16.4 online help extracts to the following path:
<helproot>/docs/pi_hosted/wcmgt/v160400/wcmgt-h-ugd/en/ofh
So, to use the TestPage.html file, the JavaScript settings must be updated as
follows:
product: 'wcmgt',
version: 'v160400',
type: 'ofh',
module: 'wcmgt-h-ugd'
Modify your installed product to use the Private Help Server

After you have successfully deployed and tested the Private Help Server and added
your copy of the product online help to it, you are ready to modify your installation
of OpenText Media Management to redirect help requests from the OpenText Global
Help Server to your Private Help Server. For more information, see “Configuring
Media Management to use the OpenText Private Help Server” on page 269.

19.1.2.1 Troubleshooting the Private Help Server

If you get an error when you attempt to set up the Private Help Server, check the
following common issues:
• Verify that you are using the correct slashes in any folder paths you must specify
in settings. The direction of slashes in folder paths can matter for some operating
systems.
• Verify that the Tomcat classpath is set correctly. The path you specify should not
include the properties\docsmapper folders; it should specify the path to the
folder where you created those subfolders. For more information about setting
the Tomcat classpath, see “Installing the descriptor and application files”
on page 266.
• Analyze the log files in the <Tomcat_home>\logs folder, including the
hosteddocslog.<date> file for more information.
19.1.3 Configuring Media Management to use the OpenText

Private Help Server
You can configure Media Management to use an OpenText Private Help Server for
the Administration help, Mobile Client and Web Desktop Client user help. To do
this, you need to edit the settings located under the HELP\CONFIG component,
which belongs to the General configuration group. For more information about how
to edit the settings see, Section 2.13.2.3 “Editing a component and properties” in
Note: Do not change these unless you are setting up a Private Help Server or
as instructed by OpenText.
To configure OpenText Media Management to use the Private Help Server:
• Configuring the following settings by enter the appropriate value under the
Value column:
• BASE_URL – Enter the URL of your OpenText Private Help Server private
server.
• TENANT_ID – An optional, customer identifier assigned to you by

OpenText. Do not specify a setting in this field unless instructed by
OpenText
• TYPE – Do not change the default setting unless OpenText instructs you to
do so.
• VERSION – Do not change the default setting unless OpenText instructs

you to do so.

OpenText Media Management 16.3 - Installation Guide English (MEDMGT160300-IGD-EN-07) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenText Media Management 16.3 - Installation Guide English (MEDMGT160300-IGD-EN-07) PDF

Uploaded by

Copyright:

Available Formats

OpenText™ Media Management

This document provides instructions for installing OpenText

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Copyright © 2018 Open Text. All Rights Reserved.

No Warranties and Limitation of Liability

2 Installation Overview ............................................................... 17

3 Core Media Management Installation Preparation ............... 23

4 Installing on Windows ............................................................. 39

OpenText Media Management – Installation Guide iii

4.2.2 Installing Solr on the Media Management host .................................. 50

5 Installing on RedHat Enterprise Linux .................................. 53

6 Post installation tasks ............................................................. 71

7 Verifying and Configuring Push Connector for Media

8 Installing OpenText Media Management Rich Media

iv OpenText Media Management – Installation Guide

8.1 Preparing to install .......................................................................... 83

9 Installing OpenText Media Management Adaptive Media

OpenText Media Management – Installation Guide v

vi OpenText Media Management – Installation Guide

9.6.1.3 Configuring Adaptive Media Delivery to use the default

10 Integrating Media Management and Data Collector ........... 129

11 Configuring video and audio ................................................ 133

OpenText Media Management – Installation Guide vii

11.5.4.1 Preparing to install the FFmpeg Transcode service ......................... 175

12 Completing optional installation activities ......................... 191

13 Starting OTMM ....................................................................... 193

14 Upgrading Media Management ............................................ 195

viii OpenText Media Management – Installation Guide

14.2.3 Migrating Categories to Folders ..................................................... 203

15 Verifying the OTMM installation ........................................... 213

16 Configuring for High Availability ......................................... 221

OpenText Media Management – Installation Guide ix

16.2.7 Solr index files .............................................................................. 227

17 Appendix A ‒ Uninstalling the Media Management

18 Appendix B ‒ Validation checks .......................................... 259

19 Appendix C – Deploying the OpenText Private Help

x OpenText Media Management – Installation Guide

1.1 Media Management system and its components

Figure 1-1: Media Management architecture

Note: Secure MFT works only with MS SQL Server.

OpenText Media Management – Installation Guide 11

In these instructions, <TEAMS_REPOSITORY_HOME> should be replaced with the

1.1.2.1 OTDS terminology

12 OpenText Media Management – Installation Guide

provider when the user partition is created. A synchronized user partition

OTDS Web Client

1.2 Recommended configuration

The server roles are as follows:

Media Management server

OpenText Media Management – Installation Guide 13

Media Management contains the Media Management Indexer component,

OpenText™ Media Management Rich Media Analysis Service

Note: You can optionally install Rich Media Analysis Service.

OpenText™ Media Management Adaptive Media Delivery

14 OpenText Media Management – Installation Guide

OpenText Directory Services server

Audio/Video Transcode server

Apache Solr™ Search Server

The following are OTMM product options:

OpenText™ Secure MFT for Media Management

OpenText Media Management – Installation Guide 15

OpenText™ Media Management Creative Review