Sunteți pe pagina 1din 270

OpenText™ Media Management

Installation Guide

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

This document provides instructions for installing OpenText Media Management.

MEDMGT160300-IGD-EN-07

OpenText™ Media Management Installation Guide

MEDMGT160300-IGD-EN-07

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

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

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

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

Table of Contents

9.6.1.3

Configuring Adaptive Media Delivery to use the default 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

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

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

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

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.

Availability, non- replicated) Media Management system. Figure 1-1: Media Management architecture Note: Secure MFT

Figure 1-1: Media Management architecture

Management system. Figure 1-1: Media Management architecture Note: Secure MFT works only with MS SQL Server.

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

Chapter 1

Overview

1.1.2

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.

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

For more information, see http://ant.apache.org/ . Note: References to the Media Management Web Client or OTMM

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

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.

a search index using Apache Solr™ as the search engine. Note: Media Management needs to share

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

Experience Analytics Data Collector Data Collector service. Notes • You can optionally install Adaptive Media

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

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/

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.

for long running audio and video assets in Media Management. Note: When using a Video Transcode

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

- Installation Guide and Release Notes (MEDMGTPO-ICC) . Important The time clock for all the servers

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.

you have installed up to that point before continuing on. Figure 2-1: Standard Installation order of

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

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

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.

see “Phase 3 - Post-installation software” on page 20 . Note: For more information, see OpenText

2.2. Phases of the installation process

2.2.1 Phase 1 - OTDS

OpenText My Support ( https://support.opentext.com ) . Notes • OTDS Web Client is included in the

Notes

OTDS Web Client is included in the installation.

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

Tomcat_port is the Tomcat port on which OTDS is running Note: Ensure that the web interface

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.

you complete the installation of the OpenText components. Note: For more information about versions, see OpenText

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

® “Installing ImageMagick on Linux” on page 62 Note: The Windows installer installs ImageMagick

Note: The Windows installer installs ImageMagick automatically.

Video Transcoder Might require a separate license.

Harmonic Rhozet™ Carbon Coder™ (Rhozet) and Carbon Server

Telestream FlipFactory ® (FlipFactory ) and Telestream FactoryArray ® (FactoryArray)

Telestream Vantage ® (Vantage)

FFmpeg

This is open source.

Streaming Server (optional video and audio streaming software) Might require a separate license.

Adobe Media Server, Wowza, IIS, Apache HTTPD

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

3.2 Install prerequisites

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

before beginning the Media Management system installation: Note: For more information, see OpenText Media Management

OTDS Download OTDS from OpenText My Support (https://support.opentext.com) and install it.

Java Development Kit (JDK) Download latest JDK from:

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.

platform Notes • Windows - Use the JBoss EAP Installer method, as

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:

You must install and configure Wildfly. For more information, see “Installing and configuring JBoss” on page 24.

Apache TomEE TomEE Download TomEE from:

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.

installation prompts and what the requirements are for OTMM. Notes • You must perform these configurations

Notes

You must perform these configurations on all Media Management nodes.

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

the JBoss installation folder. For example: C:\jboss-eap-6.4 Notes • Windows - Use the JBoss EAP Installer

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/

Check the following technical specifications to ensure that you have the minimum patch level, if not you must download and install it:

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

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

Chapter 3

Core Media Management Installation Preparation

Chapter 3 Core Media Management Installation Preparation Notes • You must perform these configurations on all

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.

See the following sections for your database type. Notes • For more information, see OpenText Media

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.

3. Verify the disk space requirements for your data files.

Note: The Media Management schema installation uses these credentials to create the database owner, database schema 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 . 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.

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 resources based on your requirements for the number of assets.

3. Install SQL Server and create a named/default SQL Server instance.

Chapter 3

Core Media Management Installation Preparation

For more information about the supported version of the database, see OpenText Media Management Technical Specifications (https://knowledge.opentext.com/

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.

for the Collation settings, SQL_Latin1_General_CP1_CI_AS. Note: Use the SQL Server configuration manager to change

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.

For more information about the supported version of the database, see OpenText Media Management Technical Specifications (https://knowledge.opentext.com/

Ensure that the following Oracle product components are installed on the Media Management database server:

Oracle 11g R2 Server/12c Server.

database server: • Oracle 11g R2 Server/12c Server. Note: If you plan to use a container

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.

during installation and upgrade). • Oracle Java Products. Note: For more information, see OpenText Media Management

2. Verify the disk space requirements for your tablespaces.

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

Chapter 3

Core Media Management Installation Preparation

Chapter 3 Core Media Management Installation Preparation Note: You can create a user or use an

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

the following command to apply the change: /sbin/sysctl -p Note: You must set the value of

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.

To prepare the PostgreSQL database: 1. Install PostgreSQL. Notes • For more information about the supported

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.

Chapter 3

Core Media Management Installation Preparation

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.

following configuration settings for your database instance. Note: Change the parameters based on your requirements. The

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 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 (*) 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 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

3.3. Database setup Note: The Media Management schema installation uses these credentials to create the database

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

prior to running the installer. Proceed to Step 7 . Note: The installer creates tablespaces based

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

• TEAMS_PM_IDX • TEAMS_UOIS_DATA • TEAMS_UOIS_IDX Note: You can use the

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:

Chapter 3

Core Media Management Installation Preparation

Chapter 3 Core Media Management Installation Preparation Notes • The installer expects this specific folder structure

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:

OTMM resources in OTDS. To integrate OTMM with OTDS: Notes • As part of the installation

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.

user partition with the default user tsuper . Note: OTMM provides support for multiple user partitions.

Note: OTMM provides support for multiple user partitions. The user partitions can be synchronized, non-synchronized, or a combination of both.

Chapter 3

Core Media Management Installation Preparation

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.

user partition, refer to the “All Synchronized” section. Notes • For more information, see OpenText Directory

Notes

For more information, see OpenText Directory Services - Installation and Administration Guide (OTDS160204-IWC).

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.

in the installation when you run the installation program. Note: Using this file is optional, but

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:

“Installing on Windows“ on page 39

“Installing on RedHat Enterprise Linux“ on page 53

• “Installing on RedHat Enterprise Linux“ on page 53 Note: In the current version of OTMM,

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

Management ISO> /OTMM/mediamanagement_config.txt Note: If you select a Unicode database during the

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.

Noteswith setup screens where you fill in your install values. • OpenText recommends that you use

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

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 no user interaction.

process. This mode requires no user interaction. Note: Prior to launching the installer, you must specify

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 silent mode.

4.1.1 Installing OTMM using the setup screens

silent mode. 4.1.1 Installing OTMM using the setup screens Note: OpenText recommends that you use this

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.

Optional
Optional

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

where you want to install the Media Management application. Important Do not use spaces in the

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.

Notespage, specify the database schema settings and click Next . • If the selected database is

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.

- Verify that the SQL Server Agent Service is running. Important For installations on SQL Server

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.

Chapter 4

Installing on Windows

11. On the Application Configuration page, specify the Application Configuration settings and click Next.