EMC Documentum MediaTransformationServices · EMC™ Documentum™ MediaTransformationServices...

EMC™ Documentum™

Media Transformation ServicesVersion 6.5 SP2

Installation Guide

P/N 300009504 A01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748‑91031‑508‑435‑1000www.EMC.com

Copyright© 1994 ‑ 2009 EMC Corporation. All rights reserved.

Published June 2009

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONSOR WARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLYDISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up‑to‑date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Table of Contents

Preface ................................................................................................................................. 7

Chapter 1 Media Transformation Services Overview .................................................... 9What is Content Transformation Services?........................................................... 9Content Transformation Services scalability ................................................... 10

What is Media Transformation Services? ............................................................ 10Media Transformation Services environment...................................................... 11Media Transformation Services plug‑ins ........................................................ 11Audio/Video Transformation Services............................................................ 12Documentum Foundation Classes ................................................................. 12

Features of Media Transformation Services ........................................................ 13Media Transformation Services capabilities ........................................................ 14Supported transformations by source and target formats .................................... 17CTS Activity Template ..................................................................................... 18

Chapter 2 Getting Started ............................................................................................ 19Selecting the server host .................................................................................... 19Setting up a global registry................................................................................ 20Installation prerequisites ................................................................................... 20Software prerequisites .................................................................................. 21Uninstalling older versions of Media Transformation Server............................ 21Setup verifications ........................................................................................ 21Identifying a Connection Broker in dfc.properties....................................... 21Checking Connection Broker and repository services .................................. 22

Chapter 3 Installing Media Transformation Services ................................................... 23Pre‑Installation steps ........................................................................................ 23Remove old DFC .......................................................................................... 23Backing up profiles ....................................................................................... 24Downloading the installers ........................................................................... 24Installing rendering applications and other software....................................... 24

Media Transformation Server installation overview ............................................ 25Required Media Transformation Server installation information .......................... 25Installing Media Transformation Server ............................................................. 28Installing CTS DAR files.................................................................................... 30Deleting version 6.0 DocApps ....................................................................... 30Configuring headless Composer .................................................................... 31Installing a DAR file with DAR Installer Plugin .............................................. 31

Configuring an instance of Media Transformation Server .................................... 33Configuring a repository for both Document Transformation Servicesand Media Transformation Services ................................................................... 35Enabling a DFC installation to access a global registry ........................................ 37

EMC Documentum Media Transformation Services Version 6.5 SP2 Installation Guide 3

Table of Contents

Configuring a CTS product to the global registry ............................................ 37Installing Branch Office Caching Services ........................................................... 37Post‑installation tasks ....................................................................................... 40

Chapter 4 Installing and Configuring the CTS Activity Template ................................. 41Pre‑installation requirements ............................................................................ 42Installing CTS Activity Template ....................................................................... 42Installing CTSActivity DAR file on a Windows/Unix repository withDAR Installer Plugin......................................................................................... 44Validating and installing CTS Activity Template ................................................. 46Making the CTS Activity Template available to users .......................................... 46Making transformation profiles available for use with CTS ActivityTemplate .......................................................................................................... 47Transformation profiles with no parameters ................................................... 48

Chapter 5 Verifying, Expanding, Removing, and Uninstalling MediaTransformation Services ............................................................................. 49Verifying the Media Transformation Services installation .................................... 49Verifying startup of Media Transformation Services........................................ 50Verifying installation using DAM .................................................................. 50Verifying installation using Web Publisher ..................................................... 50

Expanding Media Transformation Services......................................................... 51Configuring Media Transformation Server for another repository .................... 51

Removing the Media Transformation Server instance from a repository ............... 52Uninstalling Media Transformation Server ......................................................... 53Uninstalling Content Transformation Services .................................................... 54Uninstalling the CTS Activity Template from a Windows host ............................. 54Uninstalling the CTS Activity Template from a UNIX host .................................. 55

Chapter 6 Installing and Configuring CTS WebServices .............................................. 57Installing CTS WebServices on Windows (JBoss)................................................. 57Configuring CTS WebServices on Windows (JBoss) ............................................ 59Verifying the Configuration on Windows (JBoss) ................................................ 60Configuring CTS WebServices instance using other application servers................ 61Installing CTS WebServices on UNIX ................................................................. 68

Chapter 7 Installation Troubleshooting ........................................................................ 69Cannot pass SuperUser and repository user information screen........................... 69If Media Transformation Server installation fails ................................................. 69COM errors on the Media Transformation Services host duringinstallation ....................................................................................................... 69Modifying the COM access permission settings .............................................. 70Setting the default impersonation level .......................................................... 71

If cts_instance_info is not created when the Configurator is executed ................... 71

4 EMC Documentum Media Transformation Services Version 6.5 SP2 Installation Guide

Table of Contents

List of Figures

Figure 1. Typical Media Transformation Services installation................................................. 11


Table of Contents

List of Tables

Table 1. Features of Media Transformation Services ............................................................ 13Table 2. Media Transformation Services supported capabilities ............................................ 15Table 3. Supported transformations with Media Transformation Services ............................. 17Table 4. Required Media Transformation Server installation information .............................. 26Table 5. Description of DAR Installer Fields (CTS DAR) ...................................................... 32Table 6. Description of DAR Installer Fields (CTS Activity DAR).......................................... 45


Preface

This guide describes how to install Documentum Media Transformation Services for Windows. Itlists installation prerequisites and provides step‑by‑step instructions for installing and uninstallingthe Media Transformation Server. In addition, this manual includes a brief overview of MediaTransformation Services architecture.

You can find additional information about Media Transformation Services in the followingdocuments:• Media Transformation Services Administration Guide, which describes the functionality of MediaTransformation Services and how to configure and troubleshoot Media Transformation Services.

• Media Transformation Services Release Notes, which includes important notes on installation andadministration issues, requirements, and limitations. This document also references some bugs.

• Audio/Video Transformation Services Installation and Release Notes, which includes installation andrelease note information for Audio/Video Transformation Services, an add‑on component toMedia Transformation Services, which includes audio and video plug‑ins. This document alsoincludes instructions on integrating a Streaming Server.

• Content Transformation Services Product Development Guide, which explains how to use the ContentTransformation Services plug‑in SDK to create and configure your own plug‑ins for MediaTransformation Services. Contact your account representative for availability of the ContentTransformation Services Product Development Guide.

• Thumbnail Server Installation, Configuration, and Release Notes, includes installation instructions,configuration information, and release notes for Thumbnail Server.

See the appropriate Documentum product documentation for information on related Documentumproducts.

Intended audienceThis guide is intended for the person who installs Media Transformation Services, often called thesystem administrator or system operator.

It is assumed that the system operator has a basic understanding of the Windows operating system.

This guide is not intended as a development guide for Transformation Services plug‑ins. See yourDocumentum account representative for availability of the Content Transformation Services ProductDevelopment Guide which includes more information and instructions on developing your ownplug‑ins. Also see theMedia Transformation Services Administration Guide for instructions on simplemodifications to plug‑ins, and more explanation on their function.


Preface

Revision historyThe following changes have been made to this document.

Revision history

Revision date Description

June 2009 Initial publication for version 6.5 SP2 product release.


Chapter 1Media Transformation ServicesOverview

This chapter contains a brief overview of Media Transformation Services and outlines a typical MediaTransformation Services installation. It gives a basic description of the Documentum environmentand relates the Media Transformation Services components within the installation.

This chapter contains the following sections:• What is Content Transformation Services?, page 9

• What is Media Transformation Services?, page 10

• Media Transformation Services environment, page 11

• Features of Media Transformation Services, page 13

• Media Transformation Services capabilities, page 14

• Supported transformations by source and target formats, page 17

• CTS Activity Template , page 18

What is Content Transformation Services?Content Transformation Services (CTS) is a suite of Documentum server products that performtransformations and analysis on repository content. CTS includes these main products:

• Advanced Document Transformation Services (ADTS)

• Document Transformation Services (DTS)

• Media Transformation Services (MTS)

• XML Transformation Services (XTS)

Additional components may be available for some of products. For example, Media TransformationServices may also include Audio/Video Transformation Services (AVTS).


Media Transformation Services Overview

Content Transformation Services scalability

Content Transformation Services (CTS) products allow for a high level of scalability. All CTS productsrun under the same Windows Service on the CTS host. This means that stopping or starting the CTSservice stops or starts all the CTS products on that host. For example, if your CTS host containsDocument Transformation Services and Media Transformation Services, stopping the CTS WindowsService stops both of those products.

Each CTS product can be configured for multiple repositories. If you have one installation of aproduct on a host, that installation can be configured against different repositories.

CTS scalability also allows for several instances of Content Transformation Services products ondifferent hosts to be configured for the same repository. This means that your installation can takeeither of two forms: one with identical plug‑in capabilities, or one with different plug‑in capabilities.

The ability for each instance of Media Transformation Server to handle different plug‑ins means thatyou can have each instance dedicated to a specific type of transformation. For example, you mighthave a dedicated Media Transformation Server for transforming images to JPEG images, and adedicated Media Transformation Server for all other tasks. In this case, each instance has differentplug‑ins, but all instances point to the same repository. Each server accepts only those items from theprocessing queue that it is capable of handling.

In addition, having multiple Media Transformation Services installations will not prevent queueitems from being processed in the event of a hardware failure in one instance.

To enable this functionality, Content Transformation Services has format awareness. Formatawareness is the ability for a Content Transformation Services product to recognize which file formatsit is capable of processing. Items that cannot be processed successfully will be removed from thequeue automatically. For example, if several transformation requests are made for JPEG files, but theproduct does not support JPEGs, the system will remove those items from the queue. A check forunprocessed items is performed periodically.

What is Media Transformation Services?Media Transformation Services (MTS) is server software that integrates with Content Server toperform analysis and transformation activities for media file formats. Thumbnail, storyboard, andlow‑resolution renditions are generated automatically. Media transformations can be triggeredautomatically by certain events, such as when an object is versioned, or as requested by users.

The Media Transformation Services software package includes the following major components:• Media Transformation Server

• Thumbnail Server

• Audio/Video Transformation Services (AVTS is an optional product that is not included withthe purchase of Media Transformation Services. AVTS also includes support for a streamingserver. The actual streaming server is a third party product that is not included with purchaseof Media Transformation Services)



Media Transformation Services environmentFigure 1, page 11 shows a typical Media Transformation Services installation on the Documentumplatform.

Figure 1. Typical Media Transformation Services installation

Media Transformation Services plugins

The Media Transformation Server plug‑ins identify and extract media‑specific properties, such asheight, width, color mode, and compression, and generate thumbnails and low‑resolution renditionsof objects. The plug‑ins also enable the transformation of media files from one format to another (forexample, from TIFF to JPEG) and provide users with the ability to perform transformations such asresizing, flipping, or rotating an image.

The standard Media Transformation Services plug‑ins are as follows:• PowerPoint — generates thumbnails, low‑resolution renditions, storyboards, and slide objectsfor PowerPoint files.

• Image 1 — processes images and other file formats. Generates thumbnails, generateslow‑resolution renditions, extracts properties, and performs transformations such as resize andtransformTo.

• Image 2 — processes images and other file formats. Generates thumbnails, generateslow‑resolution renditions, extracts properties, and performs transformations such as resize.

• Image 3 — processes images and other file formats. Generates thumbnails, generateslow‑resolution renditions, and extracts properties of large image files. This plug‑in also generatesthumbnails, generates low‑resolution renditions, extracts properties, and creates storyboards forPDF files.

• PDF Storyboard— generates thumbnails, low‑resolution renditions, and storyboards for PDF files.

• XMP — extracts metadata from image and document (PDF) formats.

• EXIF — extracts EXIF metadata from image files that have embedded EXIF metadata.



During an installation of Media Transformation Services, all standard plug‑ins are installed.

There may be prerequisite, third party applications required for some of the standard plug‑ins. Formore information applications see theMedia Transformation Services Installation Guide. For informationon specific versions supported with Media Transformation Services, see theMedia TransformationServices Release Notes.

Plug‑ins are extensible. You can configure plug‑in types and formats, and you can add new plug‑insto the system to support new file formats as required. For information about creating and addingnew plug‑ins, see theMedia Transformation Services Administration Guide, the Content TransformationServices Product Development Guide, or contact your Documentum account or support representative.

Audio/Video Transformation Services

Audio/Video Transformation Services is an optional product that must be purchased separately.

The add‑on Audio/Video Transformation Services component contains the following plug‑ins:• AVI Video plug‑in (AVI)

• Telestream plug‑in (TLS)

These plug‑ins include transformation profiles for audio and video files.

For more information on Audio/Video Transformation Services, contact your account representativeor see theAudio/Video Transformation Services Installation and Release Notes.

Documentum Foundation Classes

The Documentum Foundation Classes (DFC) are a set of Java classes that provide access to ContentServer functionality.

DFC must be installed on the Media Transformation Services host, and is included with the installer.During installation, the Media Transformation Services installer checks for an existing DFC on thehost. The following scenarios are possible:

• If DFC does not exist on the host, the installer installs the correct version.

• If an older version of DFC exists on the host, it is replaced by the version included with theinstaller. Refer to the relevant version of the Documentum System Migration Guide available on theDownload Center at https://emc.subscribenet.com/control/dctm/index for more information onmigration issues. Follow the Documentum Foundation > Documentation for Documentum 6.5link.

Any applications that were dependent upon the older version of the DFC will have to be upgradedas well. For more information on the DFC and its effect on other applications, refer to your specificDocumentum application documentation.

• If a version of DFC exists and it is newer than that which is included with the installer, it will berefreshed.


https://emc.subscribenet.com/control/dctm/index


Features of Media Transformation ServicesThe following are the features that Media Transformation Services offers. Additional features andcapabilities are available with optional add‑on transformation services.

Table 1. Features of Media Transformation Services

Feature Comments

Integrates with entire Documentum product suite andis backwards compatible.

Runs as a Windows Service and intelligently handlesexceptions raised by native applications.

Generates thumbnail, storyboard, and low‑resolutionrenditions of some imported files, and can regeneratethose renditions on command.

See Media Transformation Servicescapabilities, page 14 for details.

Offers image manipulation features.

Transforms common image formats into a variety ofother formats (including PDF).

Includes single and multi‑page TIFF toPDF. See Supported transformations bysource and target formats, page 17 fordetails.

Controls transformation parameters such as page size,layout, and security for PDF transformations.

Creates new renditions.

Transforms a document as part of a business workflowprocess using the CTS Activity Template.

CTS Activity Template is included.See the Media Transformation ServicesAdministration Guide for details.

Creates new related objects by transformation.

Allows for automated transformations. For example, perform a savedtransformation upon versioning anobject.

Enables the transformation UI through a DocumentumWDK client (for example, Digital Asset Manager).

Extracts file properties and maps them to Documentumattributes.

Embeds Documentum attributes into file properties.

Creates PDF storyboards.

Creates PowerPoint storyboards.

Performs PowerPoint assembly.

Integrates with Thumbnail Server. See Thumbnail Server Installation,Configuration, and Release Notes.

Provides XMP roundtrip support.



Feature Comments

Provides support for extracting EXIF metadata fromapplicable image file formats

Offers add‑on transformation services (optional). See Audio/Video Transformation ServicesInstallation and Release Notes.

Media Transformation Services capabilitiesMedia Transformation Services is able to generate a number of renditions for a file upon import. It isalso able to extract a variety of properties and perform other actions on files, either upon import orthrough user interaction. The following table details those out of the box capabilities.



Table 2. Media Transformation Services supported capabilities

Inputformat

Createthumbnailand low‑resolutionrendition

Createstoryboard

Extractproperties

Write XMPto content

ExtractXMP fromcontent

Extract EXIFmetadata

Resize Editproperties

Image formats

AI* √ √

BMP √ √ √

CR2 √ √ √

CRW √ √ √

DNG √ √

EPS* √ √ √ √ √ √

FPX √ √ √

GIF √ √ √ √ √

JPEG √ √ √ √ √ √ √

JPEG2000 √ √

PGM √ √ √

PNG √ √ √ √ √ √

PNM √ √ √

PPM √ √ √

PSD* √ √ √ √ √ √

SVG √ √ √ √ √

TIFF √ √ √ √ √ √ √



Inputformat

Createthumbnailand low‑resolutionrendition

Createstoryboard

Extractproperties

Write XMPto content

ExtractXMP fromcontent

Extract EXIFmetadata

Resize Editproperties

WBMP √ √ √

WMF √ √ √

Document formats

HTML √ √

PDF √ √ √

POT, POTX √ √ √

PPT, PPTX √ √ √



Supported transformations by source andtarget formatsDepending on your installation, Media Transformation Services can perform the followingtransformations.

Table 3. Supported transformations with Media Transformation Services

Source format Target formats

AI [1][2] BMP, GIF, JPEG, PNG, PNM, PPM, PSD, TIFF, WBMP

BMP BMP, GIF, JPEG, PGM, PNG, PNM, PPM, TIFF, WBMP

CR2 BMP, GIF, JPEG, JPEG2000, PBM, PCX, PDF, PICT, PGM, PNG, PNM,PPM, PSD(Photoshop7), SCT, SGI, TGA, TIFF, WBMP,

CRW BMP, GIF, JPEG, JPEG2000, PBM, PCX, PDF, PICT, PGM, PNG, PNM,PPM, PSD(Photoshop7), SCT, SGI, TGA, TIFF, WBMP,

DNG BMP, GIF, JPEG, JPEG2000, PCX, PICT, PNG, SCITEX, SGI, SVG, TGA,TIFF

EPS [1] [2] GIF, JPEG, PDF, PNG, PSD, TIFF

FPX BMP, GIF, JPEG, PGM, PNG, PNM, PPM, TIFF, WBMP

GIF BMP, GIF, JPEG, PDF, PGM, PNM, PNM, PPM, PSD, TIFF, WBMP

JPEG BMP, GIF, JPEG, PDF, PGM, PNG, PNM, PPM, PSD, TIFF, WBMP

JPEG2000 BMP, GIF, JPEG, JPEG2000, PCX, PICT, PNG, SCITEX, SGI, SVG, TGA,TIFF

PDF [2] EPS, GIF, JPEG, PNG, PSD, TIFF

PGM BMP, GIF, JPEG, PGM, PNG, PNM, PPM, TIFF, WBMP

PNG BMP, GIF, JPEG, PGM, PNG, PNM, PPM, PSD, TIFF, WBMP

PNM BMP, GIF, JPEG, PGM, PNG, PNM, PPM, TIFF, WBMP

PPM BMP, GIF, JPEG, PGM, PNG, PNM, PPM, TIFF, WBMP

PSD [1][3] GIF, JPEG, PDF, PNG, PSD, TIFF

SVG GIF, JPEG, PNG, PSD, SVG, TIFF

TIFF BMP, GIF, JPEG, PDF, PGM, PNG, PNM, PPM, PSD, TIFF, WBMP

WBMP BMP, GIF, JPEG, PGM, PNG, PNM, PPM, TIFF, WBMP

WMF BMP, GIF, JPEG, JPEG2000, PBM, PCX, PICT, PGM, PNG, PNM, PPM,SCT, SGI, TIFF, TGA, WBMP

Note: The following notes apply to Table 3, page 17:

[1] Media Transformation Services requires the latest version of GhostScript be installed in orderto perform transformations where the source format is AI, EPS, or PDF.[2] When performing a transformation where PSD (Photoshop) is both the source and targetformat (PSD to PSD), all of the layers will be flattened.[3] PPTX format requires Office 2007 or Office 2003 SP2 with compatibility pack installed.



CTS Activity TemplateThe CTS Activity Template allows users to add a content transformation as part of a workflow process.With this version of Media Transformation Services the CTS Activity Template is available for usewith Documentum Process Builder.

See Chapter 4, Installing and Configuring the CTS Activity Templatefor the procedures required toinstall the activity template and theMedia Transformation Services Administration Guide for instructionson how to make the template available to users.

Any user profile for Media Transformation Services can be used with the CTS Activity Template.However, keep in mind that if a profile contains user‑defined parameters, these parameters cannot beexposed within the workflow. See theMedia Transformation Services Administration Guide for detailsabout choosing profiles and making them available for use with the Activity Template.


Chapter 2Getting Started

This chapter explains how to prepare for installing Media Transformation Services on a Windowshost. It describes pre‑installation requirements. This chapter contains the following sections:• Selecting the server host, page 19 describes requirements for selecting the Media TransformationServer host.

• Setting up a global registry, page 20 describes requirements for selecting a global registry.

• Installation prerequisites, page 20 describes software and setup that is required before installingMedia Transformation Services.

Selecting the server hostThis section provides basic guidelines for selecting the host machine for your Media TransformationServices installation.

Caution: To ensure optimal system performance, Media Transformation Server should not be:• Installed on the same host as Content Server or the FAST (Full Text Index) Server.

This configuration is not supported by Documentum.

When selecting the Media Transformation Server host, consider the amount of memory on thecandidate server. Media Transformation Services requires an amount of memory equal to at leasttwice the size of the largest file you expect to process. For example, if you expect users to workwith 1 GB files, the Media Transformation Server host must have at least 2 GB of memory to ensureefficient media processing.

As well, all Content Transformation Services products installed on a host use the same Windowsservice. This means that any actions (such as starting or stopping an application) performed onthat Windows service affect all of the CTS products using it. The number of products installed ona single host, the expected usage of those products, and the host’s hardware capabilities are majorfactors in selecting the host. If you are planning to use the same host for more than one CTS product,ensure that it has sufficient hardware and processing capabilities for optimal performance. For moreinformation on CTS scalability, see Content Transformation Services scalability, page 10.

Refer to theMedia Transformation Services Release Notes for complete information on hardware andsoftware requirements.


Getting Started

Setting up a global registryWhen a global registry is enabled, you can deploy service‑based objects automatically from the centralrepository designated as the global registry, and network locations created in the global registry areavailable in distributed configurations. The global registry is enabled during repository configuration.There is no limit to how many repositories may be configured as global registries; however, you mayneed more than one global registry if you have applications that have very different user access levels.

If the global registry does not have the Content Transformation Services product configured againstit, then the transformation and rich_media_services DARs need to be manually run against the globalregistry. See Enabling a DFC installation to access a global registry , page 37 for further information.

To set up a global registry:

1. Determine which repository will function as the global registry.

2. During repository configuration, you will be prompted to provide the user login name andpassword for the global registry user. By default, the global registry user has the user nameof dm_bof_registry.The global registry user’s account is used by DFC clients to connect to the repository to accessrequired service‑based objects or network locations stored in the global registry. The globalregistry user has Read access to objects in the /System/Modules and /System/NetworkLocationsonly, and no other objects.

3. When you install DFC on client machines, provide those DFC installations with the global userlogin credentials.This applies to Desktop installations on end‑user computers, to WDK‑based clients such asWebtop on application server host, and to the DFC instance on Content Server and remoteContent Server hosts.

4. Ensure that the global registry repository projects to connection brokers known to the DFCinstances that must access the global registry. Identifying a Connection Broker in dfc.properties,page 21 provides instructions.

Installation prerequisitesThis section describes the prerequisites for a successful Media Transformation Services installation.

TheMedia Transformation Services Release Notes provide complete information on hardware, operatingsystem, and software version requirements.


Getting Started

Software prerequisites

The following software must be installed, configured, and running properly on your network beforeyou install Media Transformation Services:

• Documentum Content Server

The following software must be installed, configured, and running properly on the MediaTransformation Server host before you install Media Transformation Services:• Microsoft Windows as the operating system.

• Microsoft PowerPoint to use the PowerPoint plug‑in (optional)

• GPL Ghostscript to allow the Image 3 plug‑in to process PDF files (optional)

• headless Composer

Note: See theMedia Transformation Services Release Notes for the software versions certified to run withyour version of Media Transformation Services.

Uninstalling older versions of Media TransformationServer

If you are installing Media Transformation Server on a host that has a previous version of MediaTransformation Server (or Media Server, prior to version 5.3), you must properly uninstall it first. Ifyou do not uninstall the previous version, your new installation of Media Transformation Server mayfail. For information and instructions on uninstalling Media Transformation Server, see UninstallingMedia Transformation Server, page 53, or refer to the Installation Guide for your existing version.

Setup verifications

Prior to installation, verify the following:• WinZip or a similar file‑extraction utility is installed on the host machine.

• If you already have a dfc.properties file, it is pointing to the correct Connection Broker. Identifyinga Connection Broker in dfc.properties, page 21 provides instructions.

• The Connection Broker and repository services are running on your Content Server. CheckingConnection Broker and repository services, page 22 provides more information on this topic.

Identifying a Connection Broker in dfc.properties

If you already have Documentum Foundation Classes (DFC) installed on your Media TransformationServices host, you will have a dfc.properties file. Follow this procedure to ensure that the correctConnection Broker is specified If you are installingMedia Transformation Services on a clean host, youwill not have a dfc.properties prior to installation; in this case, the following procedure is not required.

For more information on the Connection Broker, see the Content Server Administration Guide.


Getting Started

To identify the correct Connection Broker in dfc.properties:

1. Search for the dfc.properties file on your Media Transformation Services host. The file is usuallylocated in the Windows (C:\Documentum\config.) folder.

2. Open dfc.properties in a text editor.

3. Find the line indicating the Connection Broker. Ensure that the specified Connection Broker is theone that contacts the repository. Change it if necessary.

4. Save and close the dfc.properties file.

Checking Connection Broker and repository services

The Connection Broker and repository services must be running properly on the Content Server hostbefore you install Media Transformation Services. The Content Server Administration Guide should bereferenced for information and instructions pertaining to Connection Broker and repository services.


Chapter 3Installing Media TransformationServices

This chapter explains how to install Media Transformation Server on a Windows host. It describesthe installation process, provides information needed to perform the installation, and containsstep‑by‑step instructions for installing the Media Transformation Server. Post‑installation tasks,configuration tasks, and troubleshooting information are also provided.

This chapter contains the following sections:• Pre‑Installation steps, page 23

• Media Transformation Server installation overview, page 25

• Required Media Transformation Server installation information, page 25

• Installing Media Transformation Server, page 28

• Installing CTS DAR files, page 30

• Configuring an instance of Media Transformation Server, page 33

• Configuring a repository for both Document Transformation Services and Media TransformationServices, page 35

• Enabling a DFC installation to access a global registry , page 37

• Installing Branch Office Caching Services, page 37

• Post‑installation tasks, page 40

PreInstallation stepsThis section explains what to do before you install the Media Transformation Server.

Remove old DFC

If a version of the DFC older than that which is installed with this version is detected during theinstallation, you will be prompted to uninstall it before resuming the Media Transformation Serverinstallation. Refer to the relevant version of the Documentum System Migration Guide available atPowerlink at www.powerlink.emc.com for more information on migration issues. Follow the


http://www.powerlink.emc.com

Installing Media Transformation Services

Technical Documentation and Advisories > Software ~ D ~ Documentation > Documentum System>link.

Backing up profiles

If you have customized or added any profiles on a repository that was previously configured withMedia Transformation Services, these profiles will be migrated automatically during installation andconfiguration of this version of Media Transformation Services. However, it is recommend that allprofiles be backed up manually prior to installing this version of Media Transformation Services.Export a copy of all profiles to a local disk before making any changes to your Media TransformationServices installation.

It is also recommended, but not mandatory, to remove old profiles from the repository beforeinstalling this version. This ensures that only the current profiles included with this version of MediaTransformation Services are contained within this folder.

To back up and remove profiles from a previous installation:

1. On the repository where Media Transformation Services is configured, navigate to /System/MediaServer.

2. Back up any customized profiles from the previous version by exporting the contents of theMedia Server folder to a local disk.

3. Delete the contents of the Media Server folder (including all versions and descendents).

Downloading the installers

Before beginning the installation process, it is best to have all installers ready and available on yourMedia Transformation Services host. Download the installers from the EMC Download Center (https://emc.subscribenet.com) to a temporary directory on your Media Transformation Services host.

Installers for Audio/Video Transformation Services are accessed through the AVTS link on theDownload Center site.

Unzip any zipped files before you proceed with the installation.

Installing rendering applications and other software

Before installing the Media Transformation Server, you must install several applications and othercomponents on the server host. TheMedia Transformation Services Release Notes provide informationon specific versions of software supported for this release.

The following applications should be installed:• Microsoft PowerPoint

• GPL Ghostscript


https://emc.subscribenet.com



Note: Ensure that all applications are installed to their default direction. Media TransformationServices looks to each application’s default installation directory when it needs to launch anapplication.

Make sure all installed programs have been launched and the registration dialog box no longerappears. The registration screen that appears in some newly installed programs may interferewith Media Transformation Services processing. Note that all applications must be closed prior toinstalling Media Transformation Services.

Media Transformation Server installationoverviewBefore installing Media Transformation Server for the first time, ensure that you have fulfilled all ofthe pre‑installation prerequisites detailed in this document.

If you are reinstalling Media Transformation Server, you must properly uninstall your previousversion of Media Transformation Server first. If you do not uninstall Media Transformation Serverfirst, your new installation may fail. Refer to Uninstalling Media Transformation Server, page 53.

Media Transformation Server installation is accomplished as a three‑part process:1. Install Media Transformation Server.

2. Install CTS DAR files. CTS DAR files need to be installed prior to running the ConfigurationUtility.

3. Configure Media Transformation Server to at least one repository.

The standard configuration procedure is found at Configuring an instance of MediaTransformation Server, page 33. Depending on your installation scenario, you may also need toperform the procedure for Configuring a repository for both Document Transformation Servicesand Media Transformation Services, page 35.

After installing Media Transformation Server, you can verify that your installation is runningcorrectly. Verifying the Media Transformation Services installation, page 49 explains this procedure.

If you have already installed Media Transformation Server, but would like to add a new instance to arepository, Expanding Media Transformation Services, page 51 provides instructions for doing so.

To remove Media Transformation Services from a repository, see Removing the Media TransformationServer instance from a repository, page 52).

Required Media Transformation Serverinstallation informationThis section provides a table for recording the information you need to install Media TransformationServer. Having this information ready and available prior to installation ensures the accuracy andefficiency of your installation.



Table 4. Required Media Transformation Server installation information

Installation information Description Your value

DFC Installation Directory This is the destination directoryfor DFC.

The default is directoryC:\Program Files\Documen‑tum\CTS.

DFC User Directory This is where exporteddocuments are stored, andwhere checked out documentsare stored. The defaultdirectory is C:\Documentum.

Connection Broker Host Name

(if not detected)

If the correct DFC has notyet been installed on thehost, you will be promptedfor the Primary ConnectionBroker host name servicingthe repository you wantto configure with MediaTransformation Server, duringinstallation.

Media Transformation Serverinstallation directory

The directory in which to installMedia Transformation Server.It is recommended that youinstall Media TransformationServer in the default installationdirectory.

Media Transformation Serverhost

(if not detected)

The name of the machine onwhich you are installing MediaTransformation Server.

You may need to enterthis information if it is notautomatically detected by theinstaller.

Repository SuperUser nameand password

The account the MediaTransformation Server uses tolog in to the repository. Askyour administrator to supplyyou with a SuperUser nameand password.

You cannot use thedm_mediaserver user accountas the repository SuperUser.



Installation information Description Your value

Repository user name The name of the user whowill receive notifications fromMedia Transformation Server.

Media Transformation Servicesnotifies the user of the resultsof processing. For example, ifMedia Transformation Serverfails to process a particularitem, it queues an eventto the Inbox of the MediaTransformation Server systemoperator user (sysOpUser).

This user should be differentfrom the dm_mediaserver user.

Domain name The name of the domain againstwhich the user is authenticated.Use the fully qualified domain.

Global registry Different DFC installations canuse different global registrieswhere required service‑basedobjects or network locationsare stored. A single DFCinstallation can have only oneglobal registry. You will beprompted during installationfor the primary registry.

dm_bof_registry By default, the global registryuser has the user name ofdm_bof_registry.Duringrepository configuration,provide the user login nameand password for the globalregistry user. The globalregistry user should besomeone other than theadministrator.



Installing Media Transformation ServerThe following procedure will install the Media Transformation Server service and supporting files.Complete the information in Table 4, page 26 prior to performing this procedure.

Note: Some screens mentioned below may not appear during your installation, depending on what isalready installed on the Media Transformation Server host.

To install Media Transformation Server:

1. Log in to the selected Media Transformation Server host as an administrator user.

2. Ensure that no programs or applications are running on the host.

3. Navigate to the folder containing the unzipped Media Transformation Server installation files.Downloading the installers, page 24 provides information about where the files should be located.

4. Double‑click mtsWinSuiteSetup.exe.The Media Transformation Services Installer splash screen is displayed, followed by the Welcomescreen, which lists the components being installed.

5. Click Next.The license agreement terms are displayed.

6. Select the option to accept the terms of the license agreement, then click Next.

7. The Installer checks for any versions of the DFC currently installed on the host.If a version of the DFC older than that which is installed is detected, you are prompted touninstall it before resuming the Media Transformation Server installation. See Remove oldDFC, page 23 for more information.If a newer version of DFC is already installed, the Installer will not replace it.

8. The DFC Runtime Environment Optional Features screen appears. If you want to install theDeveloper Documentation and/or the Primary Interop Assembly Installer, select these options.Click Next.

9. On the Directory for Documentum Software screen, change the destination folder for DFC (thedefault is C:\Program Files\Documentum\), if required, then click Next. To accept the default,click Next.

Note: If you already have the correct version of the DFC on your system, you will not see thisscreen; go to Step 12.

10. You are prompted to enter the User Directory for DFC Runtime Environment. This is whereexported documents, checked out documents, and DFC log files are stored. The default directoryis C:\Documentum.If required, change the user directory for DFC, then click Next. To accept the default directory,click Next.


11. You are prompted to enter a Connection Broker host name (or IP address) and port number.Type the name of the Connection Broker host name in the Connection Broker Host Name fieldand, optionally, type the port number in the Port Number field, and click Next.




12. Identify the Content Transformation Services installation directory (for core components that allCTS products use). The Installer creates a directory named CTS within the chosen directory.It is recommended that you accept the default directory (for example, C:\ProgramFiles\Documentum\CTS), which is where any other Documentum products are installed.• To accept the default directory, click Next.

• To choose another directory, click Browse, navigate to the directory, and click Next.

13. Identify the host name of the host machine. This may be detected automatically, if you areinstalling directly from the host. Otherwise, enter the network host name, and click Next.

14. Identify the port number to which the CTS Administration Agent will be configured. This portis used in conjunction with Documentum Administrator to communicate with CTS hosts. Thedefault port number is 9095. Enter a port number and click Next. The Admin user name andpassword screen appears.

15. Enter the Admin user name and password; if you are installing for a domain user, use the format<username>@<domain> in the Admin user name field. Click Next.

16. The Installer checks the host for the required and recommended rendering applications. If any ofthese is missing (or not available in the default installation directory), you are warned that MediaTransformation Server will not be able to support some file formats.If you have already installed the recommended application, but they are located in a directoryother than the default, cancel the Installer and reinstall the rendering application into the defaultdirectory.If you do not wish to transform the file formats supported by the missing application, click Next.

17. The Installation Summary screen appears, listing the applications that will be installed.

Note: If the correct version of DFC is already installed, the summary screen will show thatDFC will be refreshed.

• If you are satisfied with the installation confirmation, click Next.

• If you want to change a component of the installation, use the Back button to navigate backthrough the Installer and change the install information.

18. The installation proceeds.If a message appears advising you that the _jvm directory already exists, click Yes to overwritethe directory.

19. The installer now migrates all old profiles automatically. A dialog box appears confirmingthe following information:• Creation of a pre‑migration report of all profiles before they are upgraded.

• Confirmation of the beginning of the profile migration process.

• Reminder to backup all profiles first before continuing.

If you have backed up your old profiles. Select Next. The installation proceeds.

20. The DFC Global Registry designation screen appears. Identify the global registry repository.Click the Designate the global registry box. Enter the repository name and password. ClickTest Connect, if desired. Click Next.



21. Enter the default global registry user name (dm_bof_registry) and password. This should besomeone other than the administrator. Click Next.

22. A message notifies you that Media Transformation Server was installed successfully. Click Finish.

23. The Installation Wizard closes.

Note: It is strongly recommended that you restart your system after installation.

Installing CTS DAR filesYou need to install CTS DAR files before configuring CTS products to get all the latestchanges/enhancements. Install the DAR files in the global repository and each repository that isconfigured for Media Transformation Services.

There are two CTS DAR files:• Rich Media Services DAR file

• Transformation DAR file

• CTSAspects DAR file (do not install if you are using a 5.3x Content Server)

The DAR files can be installed from any machine with the latest version of headless Composerand the DAR Installer plug‑in on the local machine. Headless Composer is installed as part ofContent Server version 6.5. Headless Composer can be found on the Content Server host atC:\Documentum\<product>\6.5\install\composer\composer\ComposerHeadless.

If Content Server is of a version other than 6.5x, you will need to download and install headlessComposer before attempting to install the CTS DAR files. Headless Composer is available on the EMCdownload site as part of Documentum Developer Studio. Consult the Documentum Composer UserGuide for more information about Composer.

Note: You must have Superuser privileges for the repositories in which you are installing the DARfiles.

If you are upgrading fromMedia Transformation Services version 6.0, you must delete existing version6.0 DocApps before installing the DAR files.

Deleting version 6.0 DocApps

Follow this procedure only if you are upgrading from Media Transformation Services version 6.0:

To delete version 6.0 DocApps:

1. Log in to DAM as an administrator user.

2. Navigate to the \Cabinet\System\Applications folder.

3. Click the checkboxes for:• CTSTransformRequest

• MediaProfile





4. Select File>Delete.

5. For each folder, select Delete This folder and All Subfolders and Objects and Delete AllVersions.

6. Click Finish to apply to all three folders.

7. Click Continue to confirm the deletion.

8. Check the Applications folder to ensure the folders are deleted.

Configuring headless Composer

The headless Composer zip file has the format DCTM_Headless_Composer_<platform>_<version>.zip.

To configure headless Composer:

1. Extract the headless Composer .Zip file to a directory of your choice on your local machine. Thedirectory name must not contain any spaces.

2. Open the dfc.properties file at: ..\ComposerHeadless\plugins\com.emc.ide.external.dfc_1.00\documentum.config with a text editor.

3. Add the DFC and connection broker information, similar to the following:dfc.docbroker.host[0]=[DocBroker IP address or host name]

4. Save your changes and close dfc.properties.

Installing a DAR file with DAR Installer Plugin

You can use the DAR Installer Plugin to install a DAR file to a repository if you do not want to use theinterface within Composer. The DAR Installer plugin requires Composer or Headless Composer tobe installed, but does not launch the full Composer IDE. The DAR Installer Plugin is useful in caseswhere you want to de‑couple the development of DAR files from the installation of DAR files. It isalso useful in situations where installation of DAR files is required as part of a deployment process.

When you open the DAR Installer program, it creates three folders in your Composer installationdirectory:• darinstallerconfig ‑ contains configuration files for the DAR Installer program

• darinstallerlogs ‑ the default location of the log files

• darinstallerworkspaces ‑ workspaces that are created and used by the DAR Installer program.The DAR Installer program does not delete these workspaces automatically, so you occasionallyneed to cleanup this directory. The workspace directories are named in the following form:darinstaller_workspace_yyyy‑mm‑dd‑hh‑mm‑ss.

The DAR Installer requires you to fill in certain values that are marked with an asterisk (*). All otherfields are optional. For a description of the fields for the DAR Installer Utility, see Table 5, page 32.



To install a DAR file with DAR Installer Plugin:

DAR files are installed one at a time.

1. Download the DAR Installer zip file from the same place that you downloaded Composer. Youcan find the DAR Installer Plugin by going to https://emc.subscribenet.com/control/dctm/searchand searching for ʺComposer” to reach the Documentum Composer download site.

2. Unzip the DAR Installer zip file to the root of your Composer or headless Composer installationdirectory.

3. Run darinstaller.exe, which is located in the Composer root directory, to start the DAR InstallerPlugin.

4. In the DAR Details section, specify values for the fields.

5. In the Connection Broker Details section, specify values for Connection Broker Host andConnection Broker Port and click Connect.

6. In the Repository Details section, specify values for the fields and click Install to install theDAR file to the repository.Refer to the Description of DAR Installer Fields table to help guide you through the DAR fileinstall process.

7. Repeat steps 2–4 for the next DAR file.You can view the log for the DAR installation by selecting the log file from the Log File drop downmenu and clicking Open.

Table 5. Description of DAR Installer Fields (CTS DAR)

Parameter Required Description

DAR Yes The absolute file path to the.dar file that you want to install.The file path cannot containany I18N characters or theinstallation will fail.

Input File No The absolute file path to theinstall‑based parameter file

Local Folder No The absolute file path tolocalized .properties files.If you want to make yourapplication available in otherlanguages, you need to localizethe project data such as labels,tabs, and descriptions.

Log File No The file to save the log to. If thisis not specified, the file defaultsto <DAR>.log

Connection Broker Host Yes The address of the ConnectionBroker


https://emc.subscribenet.com/control/dctm/search



Connection Broker Port Yes The port of the ConnectionBroker Repository

Repository Yes The name of the repository thatyou want to install the DAR fileto. Click on the Connect buttonafter entering the Docbrokerhost and port to retrieve theavailable repositories.

User Name Yes The login name for therepository

Password Yes The password for logging intothe repository

Domain No The domain where therepository resides

Configuring an instance of MediaTransformation ServerTo complete the Media Transformation Server installation, you must configure an instance of MediaTransformation Server. If you are configuring Media Transformation Server to a repository that willalso be configured with Document Transformation Server or Document Transformation Server ‑Legacy, you will also need to perform the procedure for Configuring a repository for both DocumentTransformation Services and Media Transformation Services, page 35.

Caution: Make sure the appropriate Connection Broker and repositories are running beforecontinuing with the configuration.

To configure an instance of Media Transformation Server:

1. Navigate to the Media Transformation Services Configurator under Start > Programs >Documentum > MTS Instance Add or Remove.

2. The Media Transformation Services Configurator splash screen is displayed, followed by theWelcome screen.Click Next.

3. The license agreement terms are displayed.Select the option to accept the terms of the license agreement, then click Next.

4. Select Add a Media Transformation Services instance to a repository, and click Next.

5. Enter the name of the Media Transformation Server host. The installer may detect the host namefor you. This will be the name of the machine on which you have installed Media TransformationServer.Click Next.



6. A list of the repositories served by your Connection Broker appears. For instructions on selectinga Connection Broker, see Identifying a Connection Broker in dfc.properties, page 21. Select arepository to be served by the Media Transformation Server and click Next.

7. The User Information screen appears.

a. Enter the SuperUser name that Media Transformation Server will use to access the repository.(Do not use dm_mediaserver.)

Note: In a domain‑required repository, you must configure the product with a registereddomain user.

b. Enter the password for the SuperUser account.

c. Enter the domain name, if applicable.

d. Enter the name of the repository user who will receive notifications from MediaTransformation Server, otherwise known as the system operator. (Do not usedm_mediaserver.)

Note: If you are unsure of which users to specify, refer to Required Media TransformationServer installation information, page 25 for details regarding values for these fields.

e. If you are not configuring multiple domains, skip this step and proceed to Step 8.• Check the Add Additional Domain Users check box, if you are setting up to supportrequests from additional domains. If you have multiple domains in your environment andyou have users in different domains that will be transforming content, select this option.The installer will create an Admin user for each domain to support transformations byusers of each domains.

• Enter credentials for a new domain and its SuperUser in the required fields.

• Repeat this step to include additional domains, as required.

Click Next.If you cannot continue, check with the repository administrator to verify that the users existand that you entered the correct password.

8. If the repository you have chosen is in a distributed environment, a screen will appear with alist of Content Servers configured for the repository you have chosen to configure with MediaTransformation Server.Select a Content Server from the list and select Process local content only.For more information on Distributed Content Servers and the distributed environment, see theDocumentum Distributed Configuration Guide.

9. The User Authentication screen appears. Enter the system administrator name and password;if you are installing as a domain user, use the format <username>@<domain> in the systemadministrator name field.Click Next.

10. A dialog box indicates the success of the Media Transformation Server configuration.Click Finish. The Configurator closes.

If this repository will also be configured for Document Transformation Server or DocumentTransformation Server ‑ Legacy, you need to perform the configuration described in Configuring arepository for both Document Transformation Services and Media Transformation Services, page 35.



Configuring a repository for both DocumentTransformation Services and MediaTransformation ServicesWhen Media Transformation Services and Document Transformation Services are installed ondifferent servers but configured against the same repository, the following additional configuration isnecessary for the correct transformations to be handled by the correct product.

To configure the Document Transformation Server or Document TransformationServer Legacy:

1. Navigate to %CTS%\config.

2. Open the CTSServerService.xml file in a text editor.

3. Comment out the full <QueueProcessorContext> section, where queueItemName=ʺdm_mediaserverʺ for the appropriate repository.For example, this section may appear as follows:<QueueProcessorContext DocbaseName="Repository1"><CTSServer AttributeName="queueInterval" AttributeValue="10"/><CTSServer AttributeName="maxThreads" AttributeValue="10"/><CTSServer AttributeName="tempFileDir" AttributeValue="E:\PROGRA~1\DOCUME~1\CTS\docbases\Repository1\config\temp_sessions"/><CTSServer AttributeName="mediaServerName" AttributeValue="dts1_Repository1"/><CTSServer AttributeName="queueItemName" AttributeValue="dm_mediaserver"/><CTSServer AttributeName="sysOpUserName" AttributeValue="ctsadmin"/><CTSServer AttributeName="maxQueueItemsToSignOff" AttributeValue="10"/><CTSServer AttributeName="maxQueueItemAge" AttributeValue="1m"/><CTSServer AttributeName="processLocalContentOnly" AttributeValue=""/><CTSServer AttributeName="queueProcessor" AttributeValue="com.documentum.cts.impl.services.ctsserver.CTSLegacyQueueProcessor"/><CTSServer AttributeName="legacyTaskProcessor" AttributeValue="com.documentum.cts.impl.services.task.legacycalls.LegacyCallProcessor"/><CTSServer AttributeName="aaesProfilePath" AttributeValue="/System/Media Server/Command Line Files/aes_legacy_calls.xml"/><CTSServer AttributeName="bgProfilePath" AttributeValue="/System/Media Server/Command Line Files/background_legacy_calls.xml"/><CTSServer AttributeName="customProfilePath" AttributeValue="/System/Media Server/Command Line Files/custom_legacy_calls.xml"/><CTSServer AttributeName="notifySuccessMessage" AttributeValue=""/><CTSServer AttributeName="notifyFailureMessage" AttributeValue="Yes"/><CTSServer AttributeName="ctsRefreshQueueItemName" AttributeValue="cts_info_change"/><CTSServer AttributeName="ignoreKeywordName" AttributeValue="ignore_cts_processing"/><CTSServer AttributeValue="10" AttributeName="thresholdForQueueItemsToSignOff"/><CTSServer AttributeValue="YES" AttributeName="ignoreItemsToSignOffLimit"/></QueueProcessorContext>

4. Save and close the file.

5. Restart the Documentum Content Transformation Services service.



To configure the Media Transformation Server:

1. Navigate to %CTS%\config.

2. Open the CTSServerService.xml file in a text editor.

3. Comment out the full <QueueProcessorContext> section, where queueItemName=ʺdm_autorender_win31ʺ for the appropriate repository.For example, this section may appear as follows:<QueueProcessorContext DocbaseName="Repository1"><CTSServer AttributeName="queueInterval" AttributeValue="10"/><CTSServer AttributeName="maxThreads" AttributeValue="10"/><CTSServer AttributeName="tempFileDir" AttributeValue="E:\PROGRA~1\DOCUME~1\CTS\docbases\Repository1\config\temp_sessions"/><CTSServer AttributeName="mediaServerName" AttributeValue="mts1_Repository1"/><CTSServer AttributeName="queueItemName" AttributeValue="dm_autorender_win31"/><CTSServer AttributeName="sysOpUserName" AttributeValue="ctsadmin"/><CTSServer AttributeName="maxQueueItemsToSignOff" AttributeValue="10"/><CTSServer AttributeName="maxQueueItemAge" AttributeValue="1m"/><CTSServer AttributeName="processLocalContentOnly"AttributeValue=""/><CTSServer AttributeName="queueProcessor" AttributeValue="com.documentum.cts.impl.services.ctsserver.CTSLegacyQueueProcessor"/><CTSServer AttributeName="legacyTaskProcessor"AttributeValue="com.documentum.cts.impl.services.task.legacycalls.LegacyCallProcessor"/><CTSServer AttributeName="aaesProfilePath" AttributeValue="/System/Media Server/Command Line Files/aes_legacy_calls.xml"/><CTSServer AttributeName="bgProfilePath" AttributeValue="/System/Media Server/Command Line Files/background_legacy_calls.xml"/><CTSServer AttributeName="customProfilePath" AttributeValue="/System/Media Server/Command Line Files/custom_legacy_calls.xml"/><CTSServer AttributeName="notifySuccessMessage"AttributeValue=""/><CTSServer AttributeName="notifyFailureMessage"AttributeValue="Yes"/><CTSServer AttributeName="ctsRefreshQueueItemName"AttributeValue="cts_info_change"/><CTSServer AttributeName="ignoreKeywordName" AttributeValue="ignore_cts_processing"/><CTSServer AttributeValue="10" AttributeName="thresholdForQueueItemsToSignOff"/><CTSServer AttributeValue="YES" AttributeName="ignoreItemsToSignOffLimit"/></QueueProcessorContext>

4. Save and close the file.

5. Restart the Documentum Content Transformation Services service.The Document Transformation Server (or Document Transformation Server ‑ Legacy) and MediaTransformation Server will now handle the correct transformations in the repository.



Enabling a DFC installation to access a globalregistryThis step is only necessary if you did not select a global registry during the installation, or if thepassword for the global registry user has changed, or if you are updating the dfc.properties with adifferent global registry than initially configured.

The dfc.properties file contains properties that relate to accessing the global registry.

To enable a DFC installation to access a global registry repository:

1. On the DFC host, navigate to $DOCUMENTUM/config (UNIX or Linux) or%DOCUMENTUM%\config (Windows).

2. From a command prompt, execute the following command to generate the encrypted form ofthe global registry user’s password:java cp dfc.jar com.documentum.fc.tools.RegistryPasswordUtils password_of_user

where password_of_user is the global registry user’s clear‑text password. In step 4 below, you willneed to enter the encrypted form of this password in the dfc.properties file.

3. Open the dfc.properties file in a text editor.

4. Modify the following attributes:dfc.bof.registry.repository=global_registry_repository_namedfc.bof.registry.username=user_login_namedfc.bof.registry.password=encryped_password_of_user

where encryped_password_of_user is the encrypted password you generated in 2 above.

5. Save the dfc.properties file.

Configuring a CTS product to the global registry

Ensure the global registry has the Content Transformation Services product configured againstit; otherwise the transformation and rich_media_services DAR files will need to be manually runagainst the global registry.

Installing Branch Office Caching ServicesThe following section outlines the procedures required to install BOCS and configure to the globalregistry.

To install Branch Office Caching Services:

1. Download the compressed distribution file to a temporary location on the BOCS server host.

2. Extract the file.

a. On Windows, double‑click the file.

b. On UNIX and Linux, untar the file:



% tar xvf filename

3. Start the installation program.• On Windows, double‑click the file named bocsWinSuiteSetup.exe.

• On UNIX and Linux, type% bocsoperatingsystemSuiteSetup.bin

where operatingsystem is the operating system on which you are installing, and press Enter.

The Setup program starts and a Welcome dialog box is displayed.

4. Read the information on the dialog box and click Next.The installer verifies operating system requirements. The license agreement dialog box isdisplayed.

5. Accept the license terms, and click Next.The Enter JBoss Server Info dialog box appears.

6. Provide information for the JBoss servers.Two instances of the JBoss servers are created, Admin Server and one to which BOCS is deployed.

a. Type in a password for the user ’JBoss’.

b. To use a port for the Admin Server that is different from the default, type in a port numberfor the Admin Server port.The default is 7001.

c. To use an instance port number that is different from the default, type in a port number forthe instance port. (This is the JBoss server instance to which the BOCS server is deployed.)The default is 8086.

d. Click Next.On Windows hosts, the Enter Install Owner Password dialog box appears.

7. If you are installing on a Windows host, type the installation owner’s password, and click Next.The installation owner is the user who is conducting the installation procedure.The Specify BOCS options dialog box appears.

8. Specify the location and maximum sizes of the content caches:

a. To choose a directory for the Cache directory that is different from the default, use Browse.The Cache directory is the directory where cached content is held.

b. To choose a maximum size for the Cache directory that is different from the default, typethe new value.The value is interpreted as megabytes.

c. To choose a directory for the Prime Store directory that is different from the default, useBrowse.The Prime Store directory is the directory where parked content is held.

d. To choose a maximum size for the Prime Store directory that is different from the default,type the new value.The value is interpreted as megabytes.

e. Click Next.



A dialog box appears to allow you to enable pull mode for the connection to DMS.

9. If the BOCS server will operate in pull mode, enable pull mode:

a. Select Enable Pull Mode.More fields appear on the dialog box.

b. Type the URL that the BOCS server will use to connect to DMSIn pull mode, BOCS servers take messages from DMS. The URL must be in the followingformat:http://host:port

where host is the host of the DMS server and port is the port on which the DMS server islistening.

c. Type the name of the bocs config object.Record the name you select for later use when actually creating the bocs config object. Thename is recorded in the acs.properties file by the installation program. If you use a differentname when creating the bocs config object, you must edit the acs.properties file to changethe name.

d. Record the Path to Certificate value that is displayed.This directory path will be required later, when the bocs config object is created.

e. Click Next.The Proxy Settings dialog box appears.

10. Indicate whether a proxy server will be installed between BOCS and Content Server.

a. If no proxy server will be installed, select No.

b. If a proxy server will be installed:

i. Select Yes.

ii. Specify the proxy server’s host name.

iii. Specify the port used to contact the proxy server.

c. Click Next.The Administration dialog box appears.

11. If the BOCS server will operate in push mode, click Next without providing a URL.A Warning dialog box appears, telling you that pull mode is disabled for the BOCS server. ClickOK. The Administration dialog box appears.

12. Specify the password for the bocsAdmin user, and click Next.The URL displayed on the Administration dialog box is the URL needed to create the resourceagent in Documentum Administrator for BOCS. The URL is also displayed on the Summarydialog box and written to the install log file. Be sure to record that URL for use in DocumentumAdministrator when creating the BOCS resource agent.A Summary dialog box appears, listing the components that will be installed and where each willbe installed and the URL to for administration resource agent.

13. Click Next to start the installation.A status dialog box appears to track the progress of the installation process.



14. Click Finish.

15. Using Documentum Administrator, create a configuration object for the BOCS in the globalregistry.For more information see the Documentum Administrator User Guide.

Postinstallation tasksThe following tasks should be performed after installing the Media Transformation Server componentand configuring it for at least one repository.

1. Install the Thumbnail Server using the information in Thumbnail Server Installation, Configuration,and Release Notes.

2. Refer to Verifying the Media Transformation Services installation, page 49 to verify and test theinstallation of Media Transformation Services.

3. Install Audio/Video Transformation Services, if applicable using Audio/Video TransformationServices Installation and Release Notes.


Chapter 4Installing and Configuring the CTSActivity Template

This chapter contains tasks that must be performed to install and configure the CTS Activity Templatefor Documentum Process Builder.

The CTS Activity Template allows users to add a transformation as part of a workflow process.With this version of Media Transformation Services the CTS Activity Template is available for usewith Documentum Process Builder.

Any user profile for Media Transformation Services can be used with the CTS Activity Template.However, keep in mind that if a profile contains user‑defined parameters, these parameters cannotbe exposed within the workflow. See Making transformation profiles available for use with CTSActivity Template, page 47 for details about choosing profiles and making them available for usewith the activity template.

The following section outlines the procedures required to install and configure the activity templatefor Content Transformation Services. These procedures are meant to supplement — not replace — theinformation in the Documentum Process Builder documentation set. You should be familiar withthe Documentum Process Builder application and have access to the Documentum Process BuilderInstallation Guide, Documentum Process Builder User Guide, and Documentum Process Builder ReleaseNotes before proceeding with the tasks in this section.

See theMedia Transformation Services Administration Guide for instructions on how to use the activitytemplate.

This chapter contains the following topics:

• Pre‑installation requirements, page 42

• Installing CTS Activity Template, page 42

• Installing CTSActivity DAR file on a Windows/Unix repository with DAR Installer Plugin, page 44

• Validating and installing CTS Activity Template, page 46

• Making the CTS Activity Template available to users, page 46

• Making transformation profiles available for use with CTS Activity Template, page 47


Installing and Configuring the CTS Activity Template

Preinstallation requirementsIn earlier releases of Documentum, the software that comprises Process Engine was installed as partof the Content Server installation. Forms & BPM docapps (now known as DAR file) were installedmanually. In release 6.5, Documentum Process Engine is installed separately on the server wherethe Content Server is hosted. Process Engine installs all required DAR files like Forms DAR andBPM DAR. Upon successful installation of Process Engine, installer will deploy bpm.ear file toJBoss deploy directory.

Before installing the CTS Activity Template, these actions are required:1. Install Process_Engine according to Documentum Process Engine Installation Guide. The Process

Engine has to be installed on Content Server host. The Process Engine will install BPM and FormsDAR’s to the docbase. Process Engine (BPM & Forms DARs) is a prerequisite for ctsActivityDAR to successfully install. Process Engine is included with the purchase of DocumentumBusiness Process Manager.

2. Install BPM according to Documentum Business Process Manager Installation Guide.

3. Install and configure Media Transformation Services according to theMedia TransformationServices Installation Guide.

4. Install Documentum Administrator according to Documentum Administrator Installation Guide.

5. Install the Documentum Process Builder DAR file according to the Documentum Process BuilderInstallation Guide.

6. Install the Documentum Process Builder Java files according to the Documentum Process BuilderInstallation Guide.

Installing CTS Activity TemplateInstallation of the template involves these procedures. Procedures are provided for both Windowsand non‑Windows. Follow the appropriate instructions for your host.

These procedures are described below.

To install CTSActivity on Windows Content Server:

1. Download the CTS Activity Template for Documentum Process Builder for Windows Installerfrom the EMC Download Center to a temporary directory on your Content Server Host.

2. Expand the self‑extracting executable file to a temporary directory.

3. Ensure the JBoss application server (Java Method server) is not running.

4. Navigate to the temporary directory with the expanded installer files.

5. Double click on the ctsActivityServerWinSetup.exe file. The Welcome screen lists thecomponents that will be installed.

6. Click Next.The software license agreement appears.

7. Select the option to accept the terms of the license agreement, and click Next.




The installation proceeds. A confirmation screen appears when the installation process iscomplete.

8. The installation summary screen appears indicating the applications that will be installed. If youagree with them, click Next.

9. An information screen appears reminding you to install the DAR file and restart the Java MethodServer. Click Next.A summary screen appears when the installation process is complete.

10. Click Finish.The CTS Activity Template is now installed. Follow the procedure below to confirm that theCTSActivity Java Method was successfully installed.

To run the CTSActivity Java Method Installer on UNIX Content Server:

1. Download the CTS Activity Template for UNIX installer from the EMC Download Center to atemporary directory on your Content Server Host.

2. Expand the installer TAR file to a temporary directory.

3. Ensure the JBoss application server (Java Method server) is not running.

4. Use the tar utility to transfer the downloaded file to a temporary directory using the followingcommand applicable for your operating system:• For Solaris: % tar ‑xvf CTSActivity_<version>_solaris.tar

• For AIX: % tar ‑xvf CTSActivity_<version>_aix.tar

• For HP‑UX: % tar ‑xvf CTSActivity_<version>_hpux.tar

• For Linux: % tar ‑xvf CTSActivity_<version>_linux.tar

The file creates two files: ctsActivityServer<platform>Setup.bin and ctsActivityServerFileSetup.jar.You will need to add execute permission to the .bin file.

5. Run the installer by entering ./ctsActivityServer<platform>Setup.bin. Click Next.

6. The CTS Activity Template Installer splash screen is displayed, followed by the Welcome screen.Click Next.

7. The software license agreement appears. Click Next.

8. Select the option to accept the terms of the license agreement, and click Next.The installation summary screen appears indicating the applications that will be installed. If youagree with them, click Next.The installation process begins.

9. An information screen appears reminding you to install the DAR file and restart the Java MethodServer. Click Next.

10. A summary screen appears when the installation process is complete.

11. Click Finish.The CTS Activity is now installed. Follow the procedure below to confirm CTSActivity Java Methodis successfully installed.




To confirm CTSActivity Java Method is correctly installed on Windows and UNIX:

1. Ensure the CTSActivityTemplateMethod.class including foldercom\documentum\cts\servermethod have been copied to the following location:• For Windows:

C:\Documentum\dba\java_methods\com\documentum\cts

• For UNIX:

$Documentum/dba/java_methods/com/documentum/cts/servermethod

2. Ensure the ctsTransform.jar files have been copied to the following location:• For Windows: C:\Documentum\jboss4.2.0\server\DctmServer_MethodServer\deploy\bpm.ear\bpm.war\WEB‑INF\lib

• For UNIX: $DOCUMENTUM_SHARED/jboss4.2.0/server/DctmServer_MethodServer/deploy/bpm.ear/bpm.war/WEB‑INF/lib

3. Ensure, the CTSActivity DAR file is installed on the global registry repository. See InstallingCTSActivity DAR file on a Windows/Unix repository with DAR Installer Plugin, page 44.

Installing CTSActivity DAR file on aWindows/Unix repository with DAR InstallerPluginAfter you install the CTS Java Method and before you use the CTS Activity Template you must installthe CTSActivity DAR file on each repository.

The CTSActivity DAR file is installed in the same way as the CTS DAR files, using headless Composerand the DAR Installer Plugin. See Installing CTS DAR files, page 30 for the complete procedure.

The DAR Installer requires you to fill in certain values that are marked with an asterisk (*). Allother fields are optional. See Table 6, page 45.

To install CTSActivity DAR file on a Windows/Unix repository with DAR InstallerPlugin:

1. Log in to a Windows machine on which Documentum Headless Composer is installed.

2. Copy the CTSActivity.zip file from the distribution file to a temporary location on the computer.

3. Unzip the file to a temporary directory.A subdirectory called CTS Activity Template is created and the DAR file archive is unzipped tothe new subdirectory.

4. Open the DAR Installer Program, darinstaller.exe. It is located in your Composer installationdirectory.

5. In the DAR Details section, specify values for the fields for the DAR file you are installing.

6. In the Connection Broker Details section, specify Connection Broker Host and ConnectionBroker Port values that project to the Windows/UNIX repository. Click Connect.



7. In the Repository Details section, specify values for the fields and click Install to install theDAR file to the repository.

After installing the DAR file on all required repositories, you must validate and install the CTSActivity Template on Documentum Process Builder.

Table 6. Description of DAR Installer Fields (CTS Activity DAR)


DAR Yes The absolute file path to the.dar file that you want to install.The file path cannot containany I18N characters or theinstallation will fail.

Input File No The absolute file path to theinstall‑based parameter file

Local Folder No The absolute file path tolocalized .properties files.If you want to make yourapplication available in otherlanguages, you need to localizethe project data such as labels,tabs, and descriptions.

Log File No The file to save the log to. If thisis not specified, the file defaultsto <DAR>.log

Connection Broker Host Yes The address of the ConnectionBroker

Connection Broker Port Yes The port of the ConnectionBroker Repository

Repository Yes The name of the repository thatyou want to install the DAR fileto. Click on the Connect buttonafter entering the Docbrokerhost and port to retrieve theavailable repositories.

User Name Yes The login name for therepository

Password Yes The password for logging intothe repository

Domain No The domain where therepository resides



Validating and installing CTS Activity TemplateAs described in the Documentum Process Builder User Guide, activity templates have three possiblestates: draft, validated, and installed. An activity template in the draft state has not been validated sinceit was created or last modified. A template in the validated state has passed the server’s validationchecks, which ensure that the template is correctly defined. A template in the installed state is readyto use for creating activities. The current state of an activity template is indicated on the templateicon in the palette.

You can validate your open template only if it is in the draft state and you have Write permission.

An activity template must be installed before it is available for creating activities. You can only installan activity template if it is in the validated state, and you have Write permission.

To validate and install CTS Activity Template on Documentum Process Builder:

1. Launch Documentum Process Builder.

2. Log in to the repository to which you have installed the DAR file.

3. Select CTSActivity tab.

4. Select Tools > Activity Template > Validate. Confirm that the CTS Activity Template has beenvalidated:• If the Validate option is unavailable, it means the template is currently validated or installedor you do not have permission to validate.

• If the validation is successful, a red check mark appears next to the activity template icon inthe Activity Templates window.

• If validation fails, a dialog box appears telling you so. Click the Details button to see the errorthat prevented validation.

5. Select Tools > Activity Template > Install.• If the Install option is unavailable, it means the template is currently installed or you don’thave permission to install.

• If the installation is successful, the validation icon appears next to the activity template inthe Activity Templates window.

6. Repeat for each Documentum repository in which you plan to use the CTS Activity Template.

Making the CTS Activity Template available tousersUsers can begin using the CTS Activity Template after:• All installation procedures are complete.

• The system administrator has given CTS users access to Documentum Process Builder (consult theDocumentum Process Builder User Guide for details).

• The users have set their Preferences to display the CTS palette in Documentum Process Builder.See the following procedure:



To display the CTS palette in Documentum Process Builder:

1. Launch Documentum Process Builder.

2. Select File > Preferences.The Preferences dialog box appears. The list box on the left displays the available activity palettes,and the list box on the right displays the palettes currently being displayed in DocumentumProcess Builder.

Note: Preferences are saved separately for each user. The list of palettes may differ if you login as a different user.

3. To display the CTS palette in Documentum Process Builder, highlight its name in the left list boxand click Add.The name moves to the right list box.

The CTS palette and template are now available to use with a business process.

Note: The preferences you set apply to your user ID only; each user can set different preferences.

Making transformation profiles available foruse with CTS Activity TemplateAll CTS Profiles which you would like to use with CTS Activity Template must be linked. OnlySystem Profiles are available for CTS Activity Template.

To make transformation profiles available for use with CTS Activity Template

1. Login to the repository using Digital Asset Manager or Webtop.

2. Navigate to: /System/Media Server/Profiles.

3. Select Show All Object and Versions from the top right hand corner of the screen to view allprofiles.

4. Select the required profile from the list.

5. Select Edit>Add to Clipboard from the main menu.

6. Navigate to /System/CTSActvity from the tree menu. Click on the CTSActivity folder.

7. Select Edit>Link Here from the main menu.The profile is now linked.

8. Repeat steps 3‑7 as required.



Transformation profiles with no parameters

There are profiles that do not include user‑defined parameters that are suitable for linking, forexample, transform_to_html_dts. You will find them in the /System/Media Server/System Profilesfolder.


Chapter 5Verifying, Expanding, Removing, andUninstalling Media TransformationServices

This chapter explains how to verify an installation of Media Transformation Services. It also explainshow to expand your Media Transformation Services installation by adding instances of the MediaTransformation Server and Thumbnail Server. The process for removing a Media TransformationServer instance is also explained. Procedures for uninstalling Media Transformation Server and theContent Transformation Services component are provided in this chapter.

This chapter contains the following sections:• Verifying the Media Transformation Services installation, page 49 provides instructions for testingthe success of your Media Transformation Services installation.

• Expanding Media Transformation Services, page 51 explains why you would expand MediaTransformation Services, and provides instructions for adding new instances of MediaTransformation Server.

• Removing the Media Transformation Server instance from a repository, page 52 providesinstructions for removing an instance of Media Transformation Server from a repository.

• Uninstalling Media Transformation Server, page 53 provides the procedure to uninstall MediaTransformation Server.

• Uninstalling Content Transformation Services, page 54 gives instructions for uninstalling theContent Transformation Services component.

Verifying the Media Transformation ServicesinstallationThis section describes how to verify that you have successfully installed Media TransformationServices. There are two ways to verify a Media Transformation Services installation:

• Check that the Windows Content Transformation Services service and plug‑ins have started, andthat all plug‑ins are present on the repository.

• Import a test file to the repository using a Documentum client that uses Media TransformationServices, such as Digital Asset Manager (DAM) or Web Publisher.


Verifying, Expanding, Removing, and Uninstalling Media Transformation Services

Both tests are recommended. This will ensure your Media Transformation Services installationis working correctly.

Verifying startup of Media Transformation Services

Once Media Transformation Server is installed and configured for a repository, Media TransformationServices should start automatically.

To verify startup of Media Transformation Services:

1. Log in to the Media Transformation Server host as an administrator user.

2. SelectWindows > Administrative Tools > Services to access the Windows Services utility.

3. Ensure that Documentum Content Transformation Services is started.

Verifying installation using DAM

Once Media Transformation Server and Thumbnail Server are installed, you can use DigitalAsset Manager (DAM) to verify that Media Transformation Server is generating thumbnails andlow‑resolution renditions correctly.

To verify a Media Transformation Server installation using DAM:

1. Use DAM to import an image file.The import may take a few minutes. After the import has finished, you will receive notificationin your Inbox.

2. Navigate to the image file you just imported and select it.You should see a thumbnail of the image file you imported.

3. Select the file.

4. Select View > Renditions, or click the renditions icon for the object.If Media Transformation Server is installed and running successfully, DAM displays anyrenditions of the file, along with properties information.

Verifying installation using Web Publisher

Once Media Transformation Server and Thumbnail Server are installed, you can use Web Publisherto verify that Media Transformation Server is generating thumbnails and low‑resolution renditionscorrectly.

To verify a Media Transformation Server installation using Web Publisher:

1. Use Web Publisher to import an image file.



The import may take a few minutes. After the import has finished, you will receive notificationin your Inbox.

2. Navigate to the image file you just imported and select it.

3. Select View > Renditions.If Media Transformation Server is installed correctly, Web Publisher displays any renditions ofthe file, along with properties information.

4. Select View > Page View > Thumbnail.If Media Transformation Server is installed correctly, Web Publisher displays the thumbnailgenerated for the image file.

Expanding Media Transformation ServicesIf you wish, you can add more than one Media Transformation Server configuration to your system.For more information on scalability, see Content Transformation Services scalability, page 10.

Configuring Media Transformation Server for anotherrepository

This section describes how to configure a Media Transformation Server against another repository.You can run one installation of Media Transformation Server on a single host, and have it configuredagainst multiple repositories.

This procedure does not perform the base installation or install configuration files, which mustbe done only once. You do not need to rerun the entire installation procedure to apply MediaTransformation Services to an additional repository. It is only necessary to add an instance of theMedia Transformation Server and create a base URL for use by the Thumbnail Server.

Caution: Ensure the appropriate Connection Broker and repositories are running beforecontinuing with the configuration.

To configure an instance of Media Transformation Server:

1. Navigate to the Media Transformation Services Configurator under Start > Programs >Documentum > MTS Instance Add or Remove.The Media Transformation Services Configurator splash screen is displayed, followed by theWelcome screen.



4. Select Add a Media Transformation Services instance to a repository, and click Next.



5. Enter the name of the Media Transformation Services host. The Configurator may detect thehost name for you. This will be the name of the machine on which you have installed MediaTransformation Server.Click Next.

6. A list of the repositories served by your Connection Broker appears. For instructions on selectinga Connection Broker, see Identifying a Connection Broker in dfc.properties, page 21. Select arepository to be served by the Media Transformation Server and click Next.

7. The User Information screen appears.Enter the SuperUser name that Media Transformation Server will use to access the repository.(Do not use dm_mediaserver.)Enter the password for the SuperUser account, and re‑enter it to verify.Enter the name of the repository user who will receive notifications from Media TransformationServer, otherwise known as the system operator. (Do not use dm_mediaserver.)

Note: If you are unsure of which users to specify, refer to Required Media Transformation Serverinstallation information, page 25 for details regarding values for these fields.

Click Next.If you cannot continue, check with the repository administrator to verify that the users exist andthat you entered the correct password in both fields.

8. If the repository you have chosen is in a distributed environment, a screen will appear with alist of Content Servers configured for the repository you have chosen to configure with MediaTransformation Services.Select a Content Server from the list and select Process local content only.For more information on Distributed Content Servers and the distributed environment, see theDocumentum Distributed Configuration Guide.

9. A dialog box indicates the success of the Media Transformation Server configuration.Click Finish.

This additional repository is now configured for Media Transformation Services.

Removing the Media Transformation Serverinstance from a repositoryThis section describes how to remove an instance of Media Transformation Server from a repository.This procedure does not remove the configuration files and services associated with MediaTransformation Server. To remove the Media Transformation Server from a host, see UninstallingMedia Transformation Server, page 53.

To remove an instance of Media Transformation Server from a repository:

1. Navigate to the Media Transformation Server Configurator under Start > Programs >Documentum > MTS Instance Add or Remove.The Media Transformation Services Configurator splash screen is displayed, followed byWelcome screen.





4. Select Remove a Media Transformation Server instance from a repository and click Next.

5. Select the repository from which you want to remove the Media Transformation Server, andclick Next.The User Information screen appears.

6. Enter the SuperUser name that Media Transformation Server uses to access the repository.

7. Enter the password for the SuperUser account.

8. Click Next.If you cannot continue, check with the repository administrator to verify that the user existsand that you entered the correct password.

9. The instance of Media Transformation Server is removed.A dialog box indicates the success of the Media Transformation Server repository instanceremoval.

10. Click Finish.The instance of Media Transformation Server is now removed from the repository.

Uninstalling Media Transformation ServerThis section describes how to uninstall Media Transformation Server from a Windows host. Theuninstaller removes all folders and the files contained within those folders. Files that are in use aremarked for deletion and removed when the system is restarted.

To remove only an instance of Media Transformation Server, follow the instructions in Removing theMedia Transformation Server instance from a repository, page 52.

Caution: It is strongly recommended that you remove all instances of Media TransformationServices configured to repositories prior to uninstalling.

To uninstall Media Transformation Server:

1. Log in as an administrator user to the machine on which Media Transformation Server is installed.

2. Make sure that no programs or applications are running.

3. Click Start > Settings > Control Panel and double‑click Add/Remove Programs.

4. In the Change or Remove Programs window, select Documentum Media Transformation Servicesand click Change/Remove.The uninstaller for Media Transformation Server opens and displays the Welcome dialog box.





7. The location(s) from which Media Transformation Services will be removed is displayed. ClickNext.The Content Transformation Services service stops and Media Transformation Services willbe uninstalled.

8. If prompted to, restart the computer. This deletes any Media Transformation Server files that mayhave been in use. This is especially important if you are going to reinstall Media TransformationServer on the host.

Uninstalling Content Transformation ServicesIf you are uninstalling all Content Transformation Services products (Document TransformationServices, Advanced Document Transformation Services, XML Transformation Services, MediaTransformation Services) from your host, then you will also need to uninstall the common ContentTransformation Services component. This provides a clean host on which to install other products, orto reinstall a Content Transformation Services product.

To uninstall Content Transformation Services:

1. Log in as an administrator user to the machine on which Content Transformation Services isinstalled.

2. Ensure that no programs or applications are running.

3. Click Start > Settings > Control Panel and double‑click Add/Remove Programs.

4. In the Change or Remove Programs window, select Documentum Content TransformationServices and click Change/Remove.The Uninstaller for Content Transformation Services opens and displays the Welcome screen.

5. Click Next.

6. The location from which Content Transformation Services will be removed is displayed. ClickNext.The Content Transformation Services service stops and Content Transformation Services isuninstalled.

7. Restart the computer if prompted to do so. This deletes any files that may have been in use. Thisis especially important if you are going to reinstall a Content Transformation Services producton the host.

Uninstalling the CTS Activity Template from aWindows hostThis section describes how to uninstall the CTS Activity Template from a Windows host.

Caution: Do not uninstall DFC prior to uninstalling CTS Activity Template Services.



To uninstall CTS Activity Template from the Control Panel:

1. On the host machine, click Start > Settings > Control Panel and double‑click Add/RemovePrograms.

2. In the Change or Remove Programs window, locate the Documentum CTS Activity Template forBPM program, select it, and click Change/Remove.

3. In the Change/Remove dialog box, click Next.The UninstallShield Wizard welcome screen appears.

4. Click Next.

5. Click Next again.The uninstall proceeds.

6. When the uninstall is complete, you will receive notification from the uninstaller. click FinishThe CTSActivity Java Method is now uninstalled.

Uninstalling the CTS Activity Template from aUNIX hostThis section describes how to uninstall the CTS Activity Template from a UNIX host.

Caution: Do not uninstall DFC prior to uninstalling CTS Activity Template Services.

To uninstall CTS Activity Template from a UNIX host using the Uninstall Wizard:

1. On the host machine, navigate to the directory called _uninst in the root location of the install (forexample, $DOCUMENTUM/_uninst).

2. Open the ctsActivity folder.

3. In a command window, run the file ./uninstall.bin.The Uninstall Wizard launches and the Welcome screen appears.

4. Click Next.A dialog box appears detailing the DAR name and target repository.

5. Click Next.The installation process continues.

6. Follow the prompts to remove CTS Activity Template from the appropriate application server.

7. Click Finish to close the uninstaller.


Chapter 6Installing and Configuring CTSWebServices

CTS WebServices is based on Documentum Foundation Services platform. It provides synchronousrealtime transformation capabilities. Any client application based on CTS WebServices may requesttransformations that result in files that are available directly to the client, with minimal turn aroundtime.

CTS WebServices installers are available for Windows and UNIX operating systems.

The following topics are covered in this chapter:• Installing CTS WebServices on Windows (JBoss), page 57

• Configuring CTS WebServices on Windows (JBoss), page 59

• Verifying the Configuration on Windows (JBoss), page 60

• Configuring CTS WebServices instance using other application servers, page 61

• Installing CTS WebServices on UNIX, page 68

Installing CTS WebServices on Windows(JBoss)The following procedure details the process for installing CTS WebServices on a Windows host. TheCTS WebServices installer installs all the necessary files to run and configure the core components ofCTS web services including an installation of the JBoss application server.

To install CTS WebServices on Windows:

1. Log in to the selected CTS WebServices host as an administrator user.

2. Ensure that no programs or applications are running on the host.

3. Navigate to the folder containing the unzipped CTS WebServices installation files. Downloadingthe installers, page 24 provides information about where the files should be located.

4. Double click ctsWebServicesWinSuiteSetup.exe.The CTS WebServices Installer splash screen is displayed, followed by the Welcome screen,which lists the components being installed.

5. Click Next.


Installing and Configuring CTS WebServices

The license agreement terms are displayed.


7. The Installer checks for any versions of the DFC currently installed on the host.If a version of the DFC older than that which is installed is detected, you are prompted touninstall it before resuming the installation.If a newer version of DFC is already installed, the Installer will not replace it.

8. The DFC Runtime Environment Optional Features screen appears. If you want to install theDeveloper Documentation select it. Click Next.

9. On the Directory for Documentum Software screen, enter the destination folder for DFC, thenclick Next. To accept the default (C:\Program Files\Documentum\), click Next.


10. You are prompted to enter the User Directory for DFC Runtime Environment. This is whereexported documents, checked out documents, and DFC log files are stored. The default directoryis C:\Documentum.If required, change the user directory for DFC, then click Next. To accept the default directory,click Next.


11. You are prompted to enter a Connection Broker host name (or IP address) and port number. (Thisis the Content Server’s IP address.)Type the name of the Connection Broker host name in the Connection Broker Host Name fieldand, optionally, type the port number in the Port Number field, and click Next.


12. On the FS2 Services Settings screen, doNOT select Enable Federated Search Services. ClickNext.

13. You are prompted to select an installation mode. Choose Standalone installation and click Next.

14. Enter the password for the CTS WebServices Installation Owner username. The installationowner username (which is the admin user of the host machine) will be populated automatically.Click Next.

15. You are prompted to enter information for the application server (JBoss) which is bundled withCTS WebServices installer.Enter a password for the Admin User that will be created. This password is required to access theJBoss administrative console.Enter a listen port for JBoss. The default Listen Port is 8888. Keep the default or change itif desired.Click Next.

16. The Installation Summary screen appears, listing the applications that will be installed.



Note: If the correct version of DFC is already installed, the summary screen will show thatDFC will be refreshed.

• If you are satisfied with the installation confirmation, click Next.

• If you want to change a component of the installation, use the Back button to navigate backthrough the Installer and change the install information.

17. The installation proceeds.

18. After installation, you are prompted to designate a global registry repository. If you wish to usea global registry, select the option.Enter the repository name, the login name (that is, dm_bof_registry user), and password for theuser.Select the option to Test Connection. This test confirms that the provided global repository isaccessible.Click Next.

19. The JBoss application server is started. The installer also deploys dfs.ear and thetransformation.ear files.

20. Click Finish.

Configuring CTS WebServices on Windows(JBoss)The CTS WebServices Configurator adds the desired repository to the CTS WebServices instance,so that any client can request transformations on available profiles from the repository. You canconfigure the same CTS WebServices instance to multiple repositories.

Follow these steps to configure CTS WebServices instance to a JBoss application server. To configureCTS WebServices for other supported environments, go to Configuring CTS WebServices instanceusing other application servers, page 61.

To configure CTS WebServices on Windows:

1. Start the CTS WebServices Configurator using Start>All Programs>Documentum>CTSWebServices Configurator.

2. The CTS WebServices Configurator splash screen is displayed, followed by the Welcome screen.Click Next.

3. The license agreement terms are displayed.Select the option to accept the terms of the license agreement, then click Next.

4. Select Add a CTS WebServices instance to a repository, and click Next.

5. Enter the name of the CTS WebServices host. The installer may detect the host name for you.Click Next.

6. A list of the repositories served by your Connection Broker appears. For instructions on selectinga Connection Broker, see Identifying a Connection Broker in dfc.properties, page 21. Select arepository to be served by CTS WebServices and click Next.



7. The User Information screen appears.

a. Enter the SuperUser name that CTS WebServices will use to access the repository.

Note: In a domain‑required repository, you must configure the product with a registereddomain user.

b. Enter the password for the SuperUser account.

c. Enter the domain name, if applicable.

d. Enter the name of the repository user who will receive notifications from CTS WebServices,otherwise known as the system operator.

Click Next.If you cannot continue, check with the repository administrator to verify that the users existand that you entered the correct password.

8. Click Finish to complete the configuration.

Verifying the Configuration on Windows(JBoss)This procedure verifies that the standard CTS WebServices installation and configuration (asdescribed above) were successful.

To verify the CTS WebServices configuration on Windows:

1. Check whether preferences.xml is updated with configured docbase.Navigate to and open in an xml or text editor the file preferences.xml in the folderC:\Documentum\cts_ws\config. The configurator updates this file with the repository name,username, domain name & password file location.

<Repositories><AekFilePath>C:/Documentum/cts_ws/config/aek.key</AekFilePath><LoginContext DocbaseName="RCR_GR"><ServerProperty Key="domain" Value=""/><ServerProperty Key="userName" Value="documentum"/><ServerProperty Key="passwordFile" Value="C:/DOCUME~2/cts_ws/config/pfile/RCR_GR_password.txt"/><ServerProperty Key="maxConnectionRetries" Value="10"/></LoginContext></Repositories>

2. A password file with an encrypted password is located in the folder C:/Documentum/cts_ws/config/pfile.

3. Check that transformation.properties contains the correct information.Navigate to and open the file transformation.properties in the folder C:\Documentum\jboss4.2.0\server\DctmServer_DFS‑CTS\conf.Ensure that the following line item appears to specify the location of preferences.xml.#cts ws preferences config location CTSWSConfig=C:/Documentum/cts_ws/config/preferences.xml



4. Check that the files emc‑dfs.ear and transformation.ear were deployed to the locationC:\Documentum\jboss4.2.0\server\DctmServer_DFS‑CTS\deployThe ear files are exploded by the configurator and the folders are named dfs.ear andtransformation.ear.

5. Check that the Windows service EMC Documentum Content Transformation WebServicesis running.Navigate to the Windows Services panel (click Start > Control Panel > Administrative Tools >Services).Ensure the service has the status of Started and is set to start up automatically.

6. Check that the JBoss console has been installed correctly.By default the CTS WebServices instance (using JBoss app. Server) runs on port ʺ8888”. Open theURL http://localhost:8888 from the CTS WebServices host to check that the JBoss console opens.

7. Using a web browser, check whether all WSDL files are accessible from both the CTS WebServicesmachine and a client machine.Use the table below to enter and compose your URLs for each WSDL file.

File Name URL

From the CTSWS machine

ObjectService http://localhost:8888/services/core/ObjectService

ProfileService http://localhost:8888/services/transformation/ProfileService

TransformationService http://localhost:8888/services/transformation/Transformation‑Service

From a client machine

ObjectService http://<CTSWS_HOST IP>:8888/services/core/ObjectService

ProfileService http://<CTSWS_HOST IP>:8888/services/transformation/ProfileService

TransformationService http://<CTSWS_HOST IP>:8888/services/transformation/TransformationService

8. Check that the log file is created.The CTS WebServices log file is located in the folder C:\Documentum\cts_ws\logs. The log fileis created once the first request is serviced from the client.

Configuring CTS WebServices instance usingother application serversTo deploy CTS webservices on a supported application server other than JBoss, complete thefollowing steps for your supported application server. (SeeMedia Transformation Services Release Notesfor a list of supported application server environments.)



To prepare BEA WebLogic for CTS WebServices:

1. Create a new WebLogic domain (for example, ws) using the BEA Configuration Wizard.

2. Make sure to select Development Mode in the Configure Server Start Mode wizard page, tomake use of the auto deployment feature.Once the domain is created, all files related to the domain are available underC:\bea\user_projects\domains\ws (if WebLogic was installed in the default directory C:\bea).

To prepare IBM WebSphere for CTS WebServices:

1. Stop the WebSphere application server if it is already running. Make sure any required FixPacksare installed.

To configure CTS WebServices instance for other supported applications:

1. Deploy emc‑dfs.ear file by copying it to the deploy directory of your supported applicationserver instance. See the chapter on ʺManually deploying services on supported applicationservers,” in the applicable version of the Documentum Foundation Services Deployment Guide forcomplete instructions.

2. Deploy transformation.ear file by copying it to the deploy directory of your supported applicationserver instance. See the chapter on ʺManually deploying services on supported applicationservers,” in the applicable version of the Documentum Foundation Services Deployment Guide forcomplete instructions.

3. Start the Windows service for the server instance.Restart the application server for applications other than Windows.

4. Enter the following URLs to check the accessibility of WSDL files:From CTS webservice machine:• ObjectService:

http://localhost:port/services/core/ObjectService?wsdl

• ProfileService

http://host:port/services/transformation/ProfileService?wsdl

• TransformationService:

http://host:port/services/transformation/TransformationService?wsdl

5. On the CTS WebServices machine, create a ʺcts_ws” folder in your working directory, for exampleC:\Documentum\cts_ws.

6. Create the following subfolders in the ʺcts_ws” folder and a sub‑folder ʺpfile” within the configfolder:• \cache

• \config

• \logs

• \config\pfile

7. Using a text editor, create a preferences.xml file with the following content:The configurator job updates the elements of this file.



You will need the following information:• File path

• Repository (Docbase) name

• Domain name

• User name<?xml version="1.0" encoding="UTF8"?>

<ServiceConfiguration ID="CTS Web Services"><PropertyList><ServerProperty Key="Cache" Description="The Temperory

Cache Directory" Value="C:\Documentum\cts_ws\cache" /><ServerProperty Key="AllowDirectTransfer" Description=

"Allow Direct File Transfer From CTS Server to Client.Set it to false if there is a firewall restriction" Value="true" />

<ServerProperty Key="CTSWSPingInterval" Description="Interval(in seconds) used to specify how frequent the LB should ping itsCTS instances for heart rate." Value="180" />

<ServerProperty Key="FailoverRetries" Description="Allow anumber of retries if a request fails while waiting on the HTTPresponse from CTS" Value="1" />

<ServerProperty Key="InstanceSelector" Description="Specifyan implementation class for instance selection " Value="com.emc.documentum.cts.lb.workers.DefaultSelector"/>

<Repositories><AekFilePath>C:\Documentum\cts_ws\config\aek.key/

<AekFilePath><LoginContext DocbaseName="docbase_name_here"><ServerProperty Key="domain" Value="domain_name_here"/><ServerProperty Key="userName" Value="user_name_here"/><ServerProperty Key="passwordFile" Value="C:\Documentum\

cts_ws\config\pfile\mspassword.txt"/><ServerProperty Key="maxConnectionRetries" Value="10"/></LoginContext></Repositories>

</PropertyList></ServiceConfiguration>

8. Place the preferences.xml file in the config folder (%WorkingDir%\cts_ws\config).

9. Copy the aek.key file from %CTS_HOME%\config on the CTS Server (for example C:\ProgramFiles\Documentum\CTS\config) to %CTS_HOME%\cts_ws\config on the CTS WebServicesmachine (for example C:\Documentum\cts_ws\config).

10. Copy the file mspassword.txt from the CTS Server machine (for example C:\ProgramFiles\Documentum\CTS\docbases\docbase_name\config\pfile) to the pfile folder on the CTSWebServices machine (for example C:\Documentum\cts_ws\config\pfile)

11. Update/repackage transformation.ear file with following changes:

a. Update the dfc.properties file under APP‑INF\classes. Enter your docbroker machine, aswell as the Global Repository and a username and password. Typically it will look like:dfc.data.checkout_dir=${dfc.data.user_dir}/checkoutdfc.data.dir=C:\Documentum\datadfc.data.export_dir=${dfc.data.user_dir}/exportdfc.data.user_dir=${dfc.data.dir}dfc.exception.include_decoration=falsedfc.exception.include_id=falsedfc.globalregistry.password=YiYQgefRI63JTWDokb7HJQ==dfc.globalregistry.repository=CSFPI33_GR



dfc.globalregistry.username=dm_bof_registrydfc.search.ecis.enable=falsedfc.search.ecis.host=dfc.search.ecis.port=dfc.tokenstorage.dir=${dfc.data.user_dir}/apptokendfc.tokenstorage.enable=falsedfc.docbroker.host[0]=10.31.107.145dfc.docbroker.port[0]=1489

b. Edit the log4j.properties file located under \transformation.ear\APP‑INF\classes to createlogs under %CTS_HOME%\config\cts_ws\logs folder.Properties which should be modified are given in bold.

... FILE log4j.appender.F1=org.apache.log4j.RollingFileAppender

log4j.appender.F1.File=C\:/Documentum/cts_ws/logs/log4j.log

log4j.appender.F1.MaxFileSize=10MB

log4j.appender.F1.layout=org.apache.log4j.PatternLayout

log4j.appender.F1.layout.ConversionPattern=%d{ABSOLUTE} %5p[%t] %20c{1} %m%n

FILE_TRACE log4j.appender.FILE_TRACE=org.apache.log4j.RollingFileAppender

log4j.appender.FILE_TRACE.File=C\:/Documentum/cts_ws/logs/trace.log

log4j.appender.FILE_TRACE.MaxFileSize=100MB

log4j.appender.FILE_TRACE.layout=org.apache.log4j.PatternLayout

log4j.appender.FILE_TRACE.layout.ConversionPattern=%d{ABSOLUTE}[%t] %20c{1} %m%n

CTSWS log4j.category.com.emc.documentum.fs.services.transformation=DEBUG,CTSWSAppender

log4j.category.com.emc.documentum.cts=DEBUG, CTSWSAppender

log4j.appender.CTSWSAppender=org.apache.log4j.DailyRollingFileAppender

log4j.appender.CTSWSAppender.File=C\:/Documentum/cts_ws/logs/CTSWS_log.txt

log4j.appender.CTSWSAppender.Append=true

log4j.appender.CTSWSAppender.layout=org.apache.log4j.PatternLayout

log4j.appender.CTSWSAppender.layout.ConversionPattern=%d{HH\:mm\:ss,SSS} %5p %20c{1} %m%n

log4j.appender.CTSWSAppender.DatePattern='.'yyyyMMdd

DFSlog4j.category.com.emc.documentum.fs=INFO, DFSAppender



log4j.appender.DFSAppender=org.apache.log4j.DailyRollingFileAppender

log4j.appender.DFSAppender.File=C\:/Documentum/cts_ws/logs/DFS_log.txt

log4j.appender.DFSAppender.Append=true

log4j.appender.DFSAppender.layout=org.apache.log4j.PatternLayout

log4j.appender.DFSAppender.layout.ConversionPattern=%d{HH\:mm\:ss,SSS} %5p [%t] %20c{1} %5x %m%n

log4j.appender.DFSAppender.DatePattern='.'yyyyMMdd

12. Copy the transformation.properties file from \transformation.ear\APP‑INF\classes to theapplication server’s current working folder.The typical WebLogic workspace for the domain is C:\bea\user_projects\domains\ws.The typical WebSphere workspace is C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\AppSrv01.

13. Open the transformation.properties file at %CTS_HOME%\config folder and edit it to pointto the preferences.xml file:

CTSWSConfig=C:/Documentum/cts_ws/config/preferences.xml

To complete the CTS WebServices deployment on BEA WebLogic:

1. Deploy the transformation.ear. For auto deployment copy and paste the updatedtransformation.ear to the autodeploy folder at C:\bea\user_projects\domains\ws\. Start theAdmin Server from the domain ʺws”. This automatically deploys the transformation.ear file.You can also deploy the transformation.ear file using WebLogic’s admin console. To use theadmin console, perform the following steps:

a. Start the WebLogic server from the ws domain.

b. Login to the WebLogic Admin Console using the URL: http://localhost:7001/console.

c. Click Lock & Edit in the change center.

d. Click the Deployments node from the Domain Structure tree.

e. Click Install.

f. Navigate to the location where transformation.ear is available. Click Next.

g. Select the option to Install this deployment as an application option and click Next

h. Make sure the name is fetched as ʺtransformation” and click Finish.

i. Click Activate Changes to complete the deployment process.

j. The application will be in the ʺprepared” state. Select transformation.Select Servicing all requests from the Start button.

k. Click Yes to start the deployment.

l. After deployment ensure the state of the transformation application is Active and WebModules are deployed and shown.



2. Make sure TransformationService and ProfileService are accessible to the WebSphere machineand a client machine using the following URLs:

http://localhost:<port>/services/transformation/TransformationServiceWebLogic machine

http://localhost:<port>/services/transformation/ProfileService

http://<WebLogic machine/ip>:<port>/services/transformation/TransformationService

Remote clientmachine:

http://<WebLogic machine/ip>:<port>/services/transformation/ProfileService

The default port number for HTTP is 7001.

3. Restart the webservice application server.

To complete the CTS WebServices deployment on IBM WebSphere:

1. Start the IBMWebSphere Application Server service in the Windows Services tool.

2. Log in to the admin console using the URL: http://localhost:9060/ibm/console

3. Expand the Applications node and click Install New Application.

4. Enter the file path to transformation.ear on your local file system. Click Next

5. On the Select Installation Options screen, ensure the application name is fetched asʺtransformation” and click Next without making any changes.

6. On theMap modules to servers screen select both the modules and click Next.

7. On theMap virtual hosts for Web modules screen Select both the web modules and click Next.

8. On the Summary screen click Finish.

9. You are notified that the application transformation was installed successfully.Click Save to complete the installation of EAR file.

10. Select the Enterprise Applications node.

11. Select transformation from list of applications and click Start.Once transformation application started successfully, a green icon will be displayed inApplication status field.

12. Select the transformation link. This will open Enterprise Applications > transformationConfiguration page for the transformation application.

13. On the Configuration screen, click the Class loading and update detection link.

14. Select the option for Classes loaded with application class loader first and enter a pollinginterval value (should be in the range 0 through 2147483647). Click Apply.

15. Click Save to save the setting in master configuration.

16. Navigate to the Enterprise Applications > transformation page as done previously.

17. On the Configuration screen, selectManage modules to manage class loading options for webmodules of transformation EAR.

18. On theManage modules screen click the services‑transformation.war link.



19. On the Configuration screen select Classes loaded with application class loader first fromthe Class loader order list and click Apply.

20. Click Save to save the settings in master configuration.

21. Click the ucf.war link to change class loading options

22. On the Configuration screen select Classes loaded with application class loader first fromthe Class loader order list and click Apply.

23. Click Save to save the settings in master configuration.

24. Make sure TransformationService and ProfileService are accessible to the WebSphere machineand a client machine using the following URLs:

http://localhost:<port>/services/transformation/TransformationServiceWebSphere machine

http://localhost:<port>/services/transformation/ProfileService

http://<WebSphere machine/ip>:<port>/services/transformation/TransformationService

Remote clientmachine:

http://<WebSphere machine/ip>:<port>/services/transformation/ProfileService

The default port number for HTTP is 9080.

25. Send test transformation requests from client to WebServices.



Installing CTS WebServices on UNIXSee theMedia Transformation Services Release Notes for specific UNIX operating systems and versionsthat are supported for CTS WebServices.

To install CTS WebServices on UNIX:

1. Add the following environment variables before starting the CTS WebServices installation.Otherwise, Installation & configuration will fail.

2. Create two folders and use the command chmod 777 to provide full permissions to them.

3. Set the variables DOCUMENTUM and DOCUMENTUM_SHARED variables with above createdfolders respectively with following commands.export DOCUMENTUM=/ctsws45/dctmexport DOCUMENTUM_SHARED=/ctsws45/dctm/dctm_shared

4. Run Xmanager in passive mode in your workstation.

5. Set DISPLAY environment variable in CTSWS host to point to your workstation IP. For example:export DISPLAY=128.222.94.62:0.0

6. Start the Installer.


Chapter 7Installation Troubleshooting

This chapter provides information on troubleshooting a Media Transformation Services installation.In addition, consult the Media Transformation Services Release Notes for information regardingadditional items that can affect installation and configuration.

Cannot pass SuperUser and repository userinformation screenWhen you configure Media Transformation Server, you must provide the name and password for arepository SuperUser to allow Media Transformation Server to access the repository. You must alsoprovide the name of the repository user who will receive notifications from Media TransformationServer.

If the user information you provide is incorrect, you will not be able to configure MediaTransformation Server. Contact the repository administrator to verify that the SuperUser exists, thatyou are using the appropriate password, and that the notification user exists.

If Media Transformation Server installation failsIf you receive notification that the Media Transformation Server installation has failed, check theInstaller log file. By default, the log file (installer.log) is located in the Media Transformation Serverinstallation directory identified in Step 12 of the section Installing Media Transformation Server,page 28.

COM errors on the Media TransformationServices host during installationComponent Object Model (COM) is a Microsoft‑developed software architecture that allows for thecreation of component‑based applications. Component‑based applications allow other componentsand other applications to use their features.


Installation Troubleshooting

Some errors may occur on your Media Transformation Services host during installation because it hasinsufficient COM access permissions, or the COM default impersonation level is set improperly.

The most common errors received related to COM are:

• Setup failed to launch installation engine: Access is denied.

• Error installing Ikernel.exe, access is denied.

The following procedures address these errors.

Modifying the COM access permission settings

The following procedure modifies the COM access permission settings on your Media TransformationServices host.

To modify the COM access permission settings on Windows 2003 hosts:

1. Select Start > Run.

2. In the Run dialog, type dcomcnfg. If any warning screens appear, click No. The ComponentServices dialog box opens.

3. Double‑click Component Services.

4. Double‑click the Computers folder. My Computer will be listed in the right pane.

5. Right‑clickMy Computer and select Properties. TheMy Computer Properties dialog box opens.

6. Select the Default COM Security tab.

7. In the Access Permissions section, click Edit Default. The Access dialog box opens.

8. Ensure that either you (as the user) or System is listed and Access Permission is selected.

9. If neither you nor System have Allow Access, select the Access Permission option. Alternatively,to create a new profile with the necessary permissions:

a. Click Add. The Select Users or Groups dialog box opens.

b. In the Select this object type field, make sure that at least Users is entered. If it is not, clickLocations and select your computer.

c. In the Enter objects name to select field, type a new object. Click OK.

d. In the Access dialog box, select the new object.

e. Select Allow Access.

f. Click OK to close the dialog box.

g. Click OK to close the dialog box.

10. Close the Component Services dialog box.

11. Retry the Media Transformation Services installation.



Setting the default impersonation level

The following procedures set the default impersonation level to Identify.

To set the default impersonation level on Windows 2003 hosts:

1. Select Start > Run.

2. Type dcomcnfg. If any warning screens appear, click No. The Component Services dialogbox opens.

3. Double‑click Component Services.

4. Double‑click the Computers folder. My Computer will be listed in the right pane.

5. Right‑clickMy Computer and select Properties. The My Computer Properties dialog box opens.

6. Select the Default Properties tab.

7. Set the Default Impersonation Level field to Identify.

8. Click Apply, then click OK.

9. Retry the Media Transformation Services installation.

If cts_instance_info is not created when theConfigurator is executedIf the cts_instance_info type is not created when the Configurator is executed, there may be a problemwith locale settings. The following errors may appear:[dm_query2_e_data_dict_error_for_attr_a_c]error:"the following error(s) occurred processing an alter/createstatement for type cts_instance_info, attribute cts_version."

[dm_query2_e_invalid_locale_setting]error: "alter/create type:the session_locale setting of 'en_gb' in the sessionconfig objectis not a valid locale in the docbase. the alter/create isdisallowed because it contains locale sensitive information foran invalid locale. please either set the session_locale to avalid dd_locales value ('en'), or add a new locale entry todd_locales (dm_docbase_config)."

The locale setting for the server and for the repository should match. If, for example, the servermachine has a locale setting of UK (en_gb) and the repository has a locale setting of US (en_us), thects_instance_info type is not created.



The solution is to change the locale of the machine running the Configurator to match the locale ofthe repository, or add the Configurator machine’s locale to the repository. The locale setting can bechanged using DQL.


Index

Aadding

an MTS instance, 51repository to MTS, 25

architecture, 11audio plug‑ins, 12Audio/Video Transformation Services, 9

Ccapabilities of MTS, 14configuring, 37

CTS WebServices instance forWebLogic, 61

CTS WebServices instance forWebSphere, 61

Global registry, 20configuring an instance, 33configuring CTS WebService instance

JBoss, 59Connection Broker

checking services, 22host, 26identifying in dfc.properties, 21

Content Server, 19Connection Broker, 22installation prerequisite, 21repositories, 22

Content Transformation Servicesconfiguration, 37description, 9extending, 12format awareness, 10queue, 10scalability, 10uninstalling, 54

CTS Activity Templateand Documentum Process Builder, 41CTSActivity DAR, 44installing, 41

installing and validating, 46overview, 18uninstalling, 54 to 55users, 46

CTS DARinstalling, 30

CTS web servicesconfiguring CTS WebService

instance, 59CTS WebService instance

log file, 61CTS WebServices

configuring for WebLogic, 61configuring for WebSphere, 61installing on UNIX, 68installing on Windows, 57

cts_instance_info, 71

DDAM

using DFC, 12verifying MTS installation, 50

DARinstalling, 30

DFCabout, 12and dfc.properties, 21directories, 26installing, 12migrating, 12, 23removing, 23

dfc.propertiesidentifying a Connection Broker, 21

Documentum Foundation Classes. SeeDFCDocumentum Process Builder

installing and validating CTS ActivityTemplate, 46

domain name, 27


Index

Eexpanding MTS, 51

Ffailed installation, 69FAST Server, 19features of MTS, 13formats

input, 14, 17output, 17

Full Text Index Server, 19

Gglobal registry

DAR files, 37Global registry, 20, 27

about, 20enabling, 37set up, 20user name, 27

Hheadless Composer, configure, 31headless Composer, install, 21, 31host

preparing, 24selecting, 19

Iinput formats, 17installation

directory, 26failure, 69overview, 25prerequisites, 19 to 21procedure, 28troubleshooting, 69verifying with DAM, 50verifying with Web Publisher, 50

installation of plug‑ins, 12installers, 24installing, 30

CTS Activity Template, 41CTSActivity DAR, 44

installing and validating CTS ActivityTemplateDocumentum Process Builder, 46

installing CTS WebService instanceUNIX, 68Windows, 57

installing Media Transformation Server, 28instance

adding, 51configuring, 33removing, 52

Llocale setting, 71log file, 69

CTS WebService instance, 61

Mmedia plug‑ins, 49Media Transformation Server

adding an instance, 25, 51configuring, 33Connection Broker host, 26domain user, 27downloading installer, 24host, 26installation directory, 26installation information, 25installation log file, 69installation overview, 25post‑installation tasks, 40pre‑installation verifications, 21reinstalling, 21, 25removing from a repository, 25, 52repository user, 27software prerequisites, 21uninstalling, 21, 25, 53verifying installation, 49

Media Transformation Servicesarchitecture, 11components, 10environment, 11expanding, 51general description, 10integration with Streaming Servers, 10scalability, 51

migrating profiles, 24migration of DFC, 12, 23

Ooutput formats, 17


Index

Pplug‑ins

Audio/Video TransformationServices, 12

description, 11extending, 12installation of, 12prerequisites, 12, 21standard, 11

post‑installation tasks, 40PowerPoint plug‑in, 21pre‑installation tasks, 23prerequisites

Content Server, 21PowerPoint plug‑in, 21third party applications, 21

profilesremoving, 24

profiles, backing up, 24profiles, migrating, 24

Qqueue

removing unsupported formatsfrom, 10

Rreinstalling Media Transformation

Server, 21, 25removing an instance, 52repository

checking, 22removing an instance of Media Server

from, 25removing an instance of Thumbnail

Server from, 52required information, 26

repository user, 27, 69requirements

for Media Transformation Serverinstallation, 25

Media Transformation Serversoftware, 21

Sscalability

of Media Services, 51scalability of Content Transformation

Services, 10selecting host, 19software prerequisites, 21source formats, 17Streaming Server

integration, 10SuperUser information, 69system architecture, 11

Ttarget formats, 17Thumbnail Server

downloading installer, 24Transformation Services

Audio/Video, 12transformations

supported, 17troubleshooting, 69 to ?

Uuninstalling

Content Transformation Services, 54CTS Activity Template, 54 to 55Media Server, 25Media Transformation Server, 21, 53

Vverifications

Media Transformation Serverinstallation, 49

pre‑installation, 21video

plug‑ins, 12

WWeb Development Kit. SeeWDKWebPublisher

using to verify installation, 50Windows Services, 50


EMC Documentum MediaTransformationServices · EMC™ Documentum™ MediaTransformationServices...

Documents

Transcript of EMC Documentum MediaTransformationServices · EMC™ Documentum™ MediaTransformationServices...