EMC Documentum Content Transformation Services Transformation

EMC Documentum Content Transformation Services Transformation
EMC ® Documentum ®
Content Transformation Services
Transformation Suite
Version 7.1
Administration Guide
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Legal Notice
Copyright © 2002–2016 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS 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. Adobe and Adobe PDF
Library are trademarks or registered trademarks of Adobe Systems Inc. in the U.S. and other countries. All other trademarks
used herein are the property of their respective owners.
Documentation Feedback
Your opinion matters. We want to hear from you regarding our product documentation. If you have feedback
about how we can make our documentation better or easier to use, please send us your feedback directly at
[email protected]
Table of Contents
Preface
Chapter 1
Chapter 2
Chapter 3
.................................................................................................................................
Content Transformation Services Overview
9
................................................ 11
What is Content Transformation Services? ..........................................................
11
What is Advanced Document Transformation Services? ......................................
How Advanced Document Transformation Services works .............................
How Advanced Document Transformation Services creates PDF
renditions ................................................................................................
How Advanced Document Transformation Services creates
HTML renditions......................................................................................
Installed components ....................................................................................
Advanced Document Transformation Services plug-ins ..................................
12
12
What is Media Transformation Services? ............................................................
Installed components ....................................................................................
Media Transformation Services plug-ins ........................................................
16
16
16
What is Audio/Video Transformation Services ....................................................
Installed components ....................................................................................
Audio/Video Transformation Services plug-ins ...............................................
Content Transformation Services transformations ...............................................
Automated transformations ..........................................................................
Generating thumbnails .............................................................................
Generating storyboards.............................................................................
Generating low-resolution renditions .........................................................
Extracting media properties ......................................................................
Extracting XMP metadata..........................................................................
User transformations ....................................................................................
User transformation profiles ......................................................................
17
17
18
18
18
20
21
21
21
22
22
23
Administering and Configuring Content Transformation Services
through Documentum Administrator ...........................................................
25
Starting and stopping the Content Transformation Services
Administration Agent .......................................................................................
26
Configuration and Administration Tasks and Tips ......................................
General configuration and administration tasks ..................................................
Starting and stopping Content Transformation Services ..................................
Adding or removing repositories using Content Transformation
Services configurator ....................................................................................
Configuring separate Content Transformation Services instances to
handle real-time and asynchronous requests ..................................................
Integrating a Streaming Server with Content Transformation Services..............
Prerequisites ............................................................................................
Setting up a Streaming Server ....................................................................
Setting up streaming storage areas .............................................................
Setting default_storage for the format objects .............................................
Finding file format names .....................................................................
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
13
13
14
15
29
29
30
31
31
32
32
33
33
34
34
3
Table of Contents
Windows Media formats .......................................................................
Real Media formats...............................................................................
Darwin formats ....................................................................................
Flash formats .......................................................................................
Ensuring Streaming Server access to storage areas ......................................
Creating mount points or VirtualDirectory .................................................
Setting the storage area’s base_url attribute ................................................
Testing the Streaming Server .....................................................................
Real Helix on Windows.........................................................................
Defining file formats and DOS extensions ......................................................
Configuring Inbox notifications .....................................................................
Inbox notification behavior........................................................................
Changing the Content Transformation Services user .......................................
Configuring multiple domains for Content Transformation Services
products ......................................................................................................
Understanding the Register profile ................................................................
Changing the administrator password ...........................................................
Using the Content Transformation Services Reporting Tool .............................
Enabling and disabling the Content Transformation Services
Reporting Tool .........................................................................................
Viewing the Content Transformation Services Reporting Tool report ............
Managing the transformation queue ..............................................................
Viewing transformation requests in the queue ............................................
Changing a queue item’s priority ...............................................................
Viewing details of a queue item .................................................................
Deleting a pending queue item ..................................................................
Configuring additional queue management fields.......................................
Configuring the queue pre-processor mechanism ...........................................
Controlling how quickly programs time out ...................................................
Caching Content Transformation Services capabilities on startup .....................
Setting logging appenders .............................................................................
Enabling performance and throughput logging ..............................................
Processing requests for local content ..............................................................
Configuring Content Transformation Services for BOCS or ACS ......................
Configuring queue management for BOCS installations ..................................
Load balancing servers .................................................................................
Configuring Content Transformation Services Load Balancer ......................
Configuring the Server for SSL Mode .............................................................
Using a profile description bigger than 192 bytes ............................................
Automating thumbnail or proxy creation for custom formats ..........................
Performing bulk transformation requests for documents .................................
Improving the performance of Content Transformation Services ......................
Content Transformation Services clean up job.................................................
Job configuration options ..........................................................................
Content Transformation Services job Log4j configuration ............................
Changing the hostname of the Content Transformation Services
server machine .............................................................................................
Resolving issues with email content containing double byte characters ............
PDF compliance not working ........................................................................
Configuring WebServices in a single sign-on environment ..............................
Configuration tasks specific to Advanced Document Transformation
Services ...........................................................................................................
Creating thumbnails and storyboards for MSG assets .....................................
Configuring the Doc10 plug-in ......................................................................
Controlling the size of PDF renditions............................................................
PDF customization .......................................................................................
TRANSFORMATION ...............................................................................
SETTINGS ...............................................................................................
4
34
35
35
35
36
36
36
37
37
39
39
41
41
42
43
43
44
44
45
46
46
47
47
48
49
49
50
51
51
52
52
53
54
55
55
56
57
57
58
58
60
61
61
62
62
62
63
63
64
64
65
65
66
66
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Table of Contents
MSWORDSETTINGS ................................................................................
TOC ........................................................................................................
HEADER .................................................................................................
FOOTER ..................................................................................................
MARKUP.................................................................................................
HYPERLINKS ..........................................................................................
PDFSETTINGS .........................................................................................
PAGE.......................................................................................................
BOOKMARKS ..........................................................................................
FONTEMBEDDING .................................................................................
OPTIMIZE ...............................................................................................
PDFVERSION ..........................................................................................
JPEGIMAGECOMPRESS ..........................................................................
SECURITY ...............................................................................................
Generating a specific number of storyboard renditions....................................
Adding a signature page ...............................................................................
Creating PDF renditions and enabling thumbnail and storyboard
renditions on import .....................................................................................
Rich media enabling formats .....................................................................
Creating a PDF rendition on import ...........................................................
Registering formats to enable thumbnails and storyboards ..........................
Customizing printing and rendition output ....................................................
Saving PDF Text files ................................................................................
Storing PDF metadata ...............................................................................
Configuring for rendition replacement .......................................................
Configuring change tracking .........................................................................
Transferring document attributes...................................................................
Transferring document attributes to PDF and embedding metadata .............
Viewing the attributes in the PDF rendition ................................................
Configuration tasks specific to Media Transformation Services ............................
Configuring the PowerPoint2 plug-in .............................................................
Managing PowerPoint registration .................................................................
Configuring a primary Media Transformation Services instance ..................
Configuring a secondary Media Transformation Services instance ...............
Selecting a colorspace ...................................................................................
Generating the background color for thumbnails from transparent
PDF files ......................................................................................................
Improving the quality of JPEG image files converted from SVG format ............
Configuring the Image3 plug-in.....................................................................
ICC profiles ..............................................................................................
COM Server parameters ............................................................................
Pixel cache parameters ..............................................................................
Timeout configuration ..............................................................................
66
66
69
70
70
71
71
72
72
73
74
74
74
75
76
77
Configuration tasks specific to Audio/Video Transformation Services ..................
Configuring Content Server required for large video files ................................
Creating different default preview formats on import of video files .................
94
95
95
91
92
92
92
93
93
94
............ 97
Chapter 4
Creating a Content Transformation Services WebServices Activity
Chapter 5
Troubleshooting ........................................................................................
Troubleshooting tips for Content Transformation Services products ...................
Storing the intermediate output of chain profile to docbase ...........................
Preserving temporary or intermediate files to debug a problem .....................
Error events and log files .............................................................................
A transformation request fails .....................................................................
A profile error occurs ..................................................................................
Cannot add a rendition to a particular format ...............................................
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
78
78
79
80
81
81
82
83
84
84
84
86
86
87
88
90
90
90
101
101
102
102
103
104
104
105
5
Table of Contents
If Content Transformation Services server cannot communicate to
the repository .............................................................................................
Content Transformation Services fails to function .........................................
Content Transformation Services Administration Agent gives
AGENT_INACCESSIBLE message...............................................................
Content Transformation Services fails to transform any document
to PDF (using Tools->Transform) that is imported to a web cabinet
as WP admin user .......................................................................................
Content Transformation Services is not responsive after a set of
transformations ..........................................................................................
Manual re-configuration of Content Transformation Services
instance if the repository is deleted ..............................................................
Profile modifications ...................................................................................
Rendition failures due to expired login tickets ..............................................
Content Transformation Services Queue Item Cleanup —
Pre-Processing delay ...................................................................................
After restarting Content Server, Content Transformation Services
throws a "server communication failure” exception ......................................
Users with version permission get Inbox notification on legacy
transformations ..........................................................................................
Transparency in PNG renditions lost for Illustrator files ................................
Preserving ICC profiles during transformations ............................................
Text wrapping problems with large double byte characters ...........................
Embedding metadata for date datatype other than default ............................
Troubleshooting storyboard issues generated by the
PDFStoryboard plugin ................................................................................
Resolving issues with email content containing double byte
characters...................................................................................................
Performance degradation due to add_rendition_properties settings ...............
Appendix A
Formats supported by Advanced Document Transformation
Services ....................................................................................................
106
107
107
108
109
109
110
110
110
111
111
111
111
112
112
112
113
............................. 117
Appendix B
Formats supported by Media Transformation Services
Appendix C
Formats supported by Audio/Video Transformation Services
Appendix D
Audio and Video Codecs
6
105
106
................... 121
........................................................................... 125
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Table of Contents
List of Figures
Figure 1.
Processing a request for a PDF rendition in Advanced Document
Transformation Services ....................................................................................
13
Figure 2.
Processing a request for an HTML rendition in Advanced Document
Transformation Server ......................................................................................
14
Figure 3.
Typical Advanced Document Transformation Services installation ...........................
15
Figure 4.
Typical Media Transformation Services installation .................................................
16
Figure 5.
Typical Audio/Video Transformation Services installation .......................................
18
Figure 6.
The registration process ........................................................................................
20
Figure 7.
The transformation process ...................................................................................
23
Figure 8.
Throughput .........................................................................................................
59
Figure 9.
Content Transformation Services resource usage ....................................................
60
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
7
Table of Contents
List of Tables
Table 1.
Sample extracted media properties for Content Transformation Services ..................
22
Table 2.
Documentum format mapping ..............................................................................
39
Table 3.
Inbox notification settings .....................................................................................
40
Table 4.
Inbox notification behavior for admin and regular users .........................................
41
Table 5.
Documentum format mappings for Content Transformation Services ......................
78
Table 6.
Attribute mapping arguments ...............................................................................
85
Table 7.
Pixel cache parameters for Image3 plug-in .............................................................
93
Table 8.
Process Variables ..................................................................................................
98
Table 9.
Process Data Parameters .......................................................................................
99
Table 10.
Capabilities Supported for Document Formats .....................................................
113
Table 11.
Table 12.
Document Transformations Supported for Source and Target Formats ...................
Capabilities for Supported Media Image Formats .................................................
114
117
Table 13.
Media Transformations Supported for Source and Target Formats .........................
118
Table 14.
Capabilities Supported for Audio and Video Formats ...........................................
121
Table 15.
Audio and Video Transformations Supported for Source and Target
Formats .........................................................................................................
122
Audio and Video Codecs Supported for Input Formats .........................................
Audio and Video Codecs Supported for Output Formats ......................................
125
128
Table 16.
Table 17.
8
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Preface
This guide provides step-by-step procedures for configuring and administering Content
Transformation Services. This manual also includes some information about modifying plug-ins to
extend the functionality of Content Transformation Services.
This manual assumes that your Content Transformation Services is successfully installed. For
information on installing Content Transformation Services, refer to the EMC Documentum Content
Transformation Services Installation Guide.
Intended audience
This manual is intended for the person who is responsible for configuring and administering Content
Transformation Services, generally known as the system operator or system administrator.
It is assumed that the system operator has a basic understanding of the Windows operating system.
Revision history
The following changes have been made to this document.
Revision history
Revision date
Description
March 2016
Updated the sections Configuring the Doc10 plug-in, page 64 and
Registering formats to enable thumbnails and storyboards, page 80.
January 2015
Updated the section Storing the intermediate output of chain profile to
docbase, page 102.
October 2014
• Added the section Configuring WebServices in a single sign-on
environment, page 63.
• Modified the Note under the following sections:
— Configuring the Doc10 plug-in, page 64
— Configuring the PowerPoint2 plug-in, page 87
• Changed the term Microsoft Office PowerPoint to Microsoft
PowerPoint.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
9
Preface
Revision date
Description
September 2014
Modified the Note under the following sections:
• Advanced Document Transformation Services plug-ins, page 15
• Media Transformation Services plug-ins, page 16
December 2013
Added the section ’Storing the intermediate profile output to the
docbase’ in the ’Troubleshooting’ chapter.
November 2013
Initial publication.
10
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Chapter 1
Content Transformation Services
Overview
This chapter provides an overview of Content Transformation Services. It includes the following
sections:
• What is Content Transformation Services?, page 11
• What is Advanced Document Transformation Services?, page 12
• What is Media Transformation Services?, page 16
• What is Audio/Video Transformation Services, page 17
• Content Transformation Services transformations, page 18
What is Content Transformation Services?
Content Transformation Services (CTS) is a suite of Documentum server products that perform
transformations and analysis on repository content. The Content Transformation Services
functionality is available through Documentum client applications. Content Transformation Services
consists of these products:
• Advanced Document Transformation Services (ADTS)
• Media Transformation Services (MTS)
• Audio/Video Transformation Services (AVTS)
Content Transformation Services provides the following functionalities:
• Transformations
Content Transformation Services carries out a wide range of conversions of documents, media,
and audio/video content (for example, Microsoft Office documents into PDF and HTML formats).
You can also apply watermarks, PDF overlays, headers, and footers to the transformed PDFs.
Media files (images) can be transformed from one format into another with a wide range of options
(like changes in the resolution, orientation, and so on). Audio/video files can be transformed from
one format into another with options like updating frame-rate, bit-rate, resolution, encoding,
and so on, in the target files.
• Metadata Analysis and Attribution
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
11
Content Transformation Services Overview
Content Transformation Services extracts attributes from content. Examples of extracted attributes
are height and width of image files, and author and subject of documents. The extracted attributes
are stored as metadata or rendition attributes. Some rendition attributes can be mapped to
object-level attributes.
• Enhanced Content Previews
Content Transformation Services generates thumbnails and storyboards to enhance the
previewing experience of Microsoft Office documents, PDF, images and video files that are
present in the repository.
• Rendition Management
Content Transformation Services stores different formats of a repository file as renditions or
related objects. Renditions are alternate formats of content that share the same object attributes
and security. Related objects are complete objects on their own with independent metadata
and security.
What is Advanced Document Transformation
Services?
Advanced Document Transformation Services is a server software that generates copies of documents
in Portable Document Format (PDF), PDF text, PostScript, HyperText Markup Language (HTML),
and so on. You can use Documentum client applications to request such a copy (called a rendition)
of a document stored in a Documentum repository. The transformation capabilities of Advanced
Document Transformation Services include PDF assembly, header/footer creation, security, textual
watermarking, content overlays, and so on.
Advanced Document Transformation Services can also provide PDF transformations from other
file formats such as image and email formats.
Some Documentum client applications may not provide both PDF and HTML renditions; consult
the documentation for the client you are using.
This section contains information about the following topics:
• How Advanced Document Transformation Services works, page 12
• Installed components, page 14
• Advanced Document Transformation Services plug-ins, page 15
How Advanced Document Transformation Services
works
The following sections detail how Advanced Document Transformation Services creates PDF and
HTML renditions.
12
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Content Transformation Services Overview
How Advanced Document Transformation Services creates PDF
renditions
The following steps describe how Advanced Document Transformation Services produces PDF
renditions in response to client requests:
1.
In response to client requests (asynchronous transformation), a rendition request is sent to
Documentum Content Server.
2.
Content Server stores the request in a queue called dm_queue.
3.
Content Transformation Server polls dm_queue at predefined intervals, and retrieves any
pending requests.
4.
When Advanced Document Transformation Services finds a PDF rendition request in the queue,
it checks the format of the document and generates a PDF rendition based on the default profiles.
5.
Content Server adds the PDF rendition to the object in the repository.
An object represents a parent file, with all of its associated graphics, text, and renditions, in
the repository.
6.
Once a rendition has been added to the object, users can view the rendition.
Figure 1, page 13 illustrates this rendition process.
Figure 1. Processing a request for a PDF rendition in Advanced Document Transformation Services
How Advanced Document Transformation Services creates HTML
renditions
The following steps describe how a Advanced Document Transformation Server host produces
HTML renditions in response to client requests:
1.
A rendition request is sent to the Content Server.
2.
Content Server stores the request in a queue called dm_queue.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
13
Content Transformation Services Overview
3.
Content Transformation Server polls dm_queue at predefined intervals, and retrieves any
pending requests.
4.
When Advanced Document Transformation Services finds an HTML rendition request in the
queue, it checks the format of the document. Advanced Document Transformation Services
invokes the corresponding plug-in to process the file.
5.
The plug-in saves an HTML version of the document.
• If the result is a single HTML file, Advanced Document Transformation Services sends this
file to the Content Server.
• If the result consists of multiple files (for example, HTML, graphics, and XML files), Advanced
Document Transformation Services creates a Zip file containing these files, and sends the Zip
file to Content Server. The Zip file includes any folders the application creates to contain
these files.
6.
Content Server adds the HTML or Zip file to the repository as a rendition of the document object.
An object represents a parent file, with all of its associated graphics, text, and renditions, in the
repository.
7.
Once a rendition has been added to the object, users can view the rendition.
Figure 2, page 14 illustrates the rendition process.
Figure 2. Processing a request for an HTML rendition in Advanced Document Transformation Server
Installed components
Figure 3, page 15 shows a typical Advanced Document Transformation Services installation on
the Documentum platform.
14
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Content Transformation Services Overview
Figure 3. Typical Advanced Document Transformation Services installation
Advanced Document Transformation Services plug-ins
The Advanced Document Transformation Services plug-ins enable users to transform a variety of files
from one format to another (for example, from DOC to PDF or HTML).
The standard Advanced Document Transformation Services plug-ins are as follows:
• Doc2 — Transforms Adobe PDF files into the XML format. This transformation comes into use
while using the xCP Viewer Search feature.
• Doc3 — Transforms Adobe PostScript files into Adobe PDF files. It also supports the creation of
PDF-X, PDF-A flavours from a PDF source.
• Doc4 — Creates PDF from PDF source files with advanced options like overlay, header-footer,
signature, and so on.
• Doc5 — Supports page-reordering for PDF and multi-page TIFF files.
• Doc6 — Transforms Microsoft Word, Excel, and PowerPoint, text files and so on, to PDF format.
• Doc7 — Supports mail attachment extraction and storage as related objects.
• Doc8 — Transforms PDF files to PS format.
• Doc9 — Transforms PDF files to HTML format.
• Doc10 — Transforms PowerPoint files to PDF. It is an optional plug-in provided only to those
for customers who require high fidelity. It is not enabled out-of-the-box (OOTB) in Advanced
Document Transformation Services.
Note: To use this plug-in, install Microsoft PowerPoint 2007 SP3 (32-bit) on the Advanced
Document Transformation Services server that is installed on Windows Server 2008 R2 SP1
(64-bit) operating system.
• PDFStoryboard — Generates thumbnails, low-resolution renditions, and storyboards for PDF files.
• Image3 — Generates thumbnails, low-resolution renditions, and storyboards for PDF files.
• XMP — Extracts metadata from document (PDF) format.
During an installation of Advanced Document Transformation Services, all standard plug-ins are
installed.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
15
Content Transformation Services Overview
What is Media Transformation Services?
Media Transformation Services (MTS) is server software that integrates with Content Server to
perform analysis and transformation activities for media file formats. Thumbnail, storyboard,
and low-resolution renditions are generated automatically. Transformations can be triggered
automatically by certain events, such as when an object is versioned, or as requested by users.
This section contains information about the following topics:
• Installed components, page 16
• Media Transformation Services plug-ins, page 16
Installed components
Figure 4, page 16 shows a typical Media Transformation Services installation on the Documentum
platform.
Figure 4. Typical Media Transformation Services installation
Media Transformation Services plug-ins
The Media Transformation Services plug-ins identify and extract media-specific properties, such as
height, width, color mode, and compression, and generate thumbnails and low-resolution renditions
of objects. The plug-ins also enable the transformation of media files from one format to another (for
example, from TIFF to JPEG) and provide users with the ability to perform transformations such as
resizing, flipping, rotating an image, and so on.
The standard Media Transformation Services plug-ins are as follows:
• PowerPoint1 — Generates thumbnails, low-resolution renditions, storyboards, and slide objects
for PowerPoint files. This plug-in is available OOTB. It is also capable of the assembly feature.
• PowerPoint2 — Generates thumbnails, low-resolution renditions, storyboards, and slide objects
for PowerPoint files. It is an optional plug-in provided only to those for customers who require
high fidelity. It is also capable of the assembly feature.
16
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Content Transformation Services Overview
Note: To use this plug-in, install Microsoft PowerPoint 2007 SP3 (32-bit) on the Media
Transformation Services server that is installed on Windows Server 2008 R2 SP1 (64-bit) operating
system.
• Image1 — Processes images and other file formats. Generates thumbnails, generates
low-resolution renditions, extracts properties, and performs transformations such as resize and
transformTo.
• Image2 — Processes images and other file formats. Generates thumbnails, generates
low-resolution renditions, extracts properties, and performs transformations such as resize.
• Image3 — Processes images and other file formats. Generates thumbnails, generates
low-resolution renditions, and extracts properties of large image files. This plug-in also generates
thumbnails, generates low-resolution renditions, extracts properties, and creates storyboards for
PDF files.
• Image 4 — Processes images and other file formats.
• PDFStoryboard — Generates thumbnails, low-resolution renditions, and storyboards for PDF files.
• XMP — Extract metadata from image formats and PDF files.
• 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.
What is Audio/Video Transformation Services
Audio/Video Transformation Services provides transformation capability for audio and video file
formats.
This section contains information about the following topics:
• Installed components, page 17
• Audio/Video Transformation Services plug-ins, page 18
Installed components
Figure 5, page 18 shows a typical Audio/Video Transformation Services installation on the
Documentum platform.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
17
Content Transformation Services Overview
Figure 5. Typical Audio/Video Transformation Services installation
Audio/Video Transformation Services plug-ins
The Audio/Video Transformation Services plug-ins identify and extract media-specific properties and
generate thumbnails, storyboards, and low-resolution renditions of objects. The plug-ins also enable
the transformation of files from one format to another (for example, from AVI to MP4).
The standard Audio/Video Transformation Services plug-ins are as follows:
• Video1 — Identifies and extracts media-specific properties and generates thumbnails, storyboards,
and low-resolution renditions of objects. In addition, this plug-in facilitates the conversion of
one video format to another.
• Video2 — Performs closed caption extraction. Only MPEG videos and CEA-608 type captions are
supported currently.
During an installation of Audio/Video Transformation Services, all standard plug-ins are installed.
Content Transformation Services
transformations
Transforming is the act of changing a file in some way to create a new file.
Transformations take place either as part of the registration process (described in Automated
transformations, page 18) or as requested by users (described in User transformations, page 22).
The following examples illustrate how Content Transformation Services transforms files from one
format to another.
Automated transformations
The process of executing transformations automatically upon importing or versioning the repository
content is called Registration.
18
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Content Transformation Services Overview
The overall process of registering a file in Content Transformation Services (depicted in Figure 6,
page 20) is as follows:
1.
A user imports or checks in a file to the repository.
2.
Content Server creates a dmi_queue_item object of the event type dm_register_asset, which is
added to the queue. Only content that is rich media enabled is passed to the queue.
3.
The server checks the queue regularly; the default is every 10 seconds. When it finds queue items,
it signs off a certain number (the default is 10 items). Both of these parameters are configurable
through Documentum Administrator (see Chapter 2, Administering and Configuring Content
Transformation Services through Documentum Administrator for more information).
4.
The server starts processing the items using the register profile. It will not remove an item from
the queue until the transformation is complete or has failed.
5.
The server loads the transformation profile specified by the inner profile path in the register
profile.
6.
The server polls the plug-ins in the order specified by the transformation profile.
7.
The server finds a plug-in to accept the transformation. If more than one plug-in can handle the
transformation, the plug-ins are invoked in the order specified by the transformation profile.
8.
The server uses the command-line file to perform the transformation with the relevant plug-in.
9.
The server updates the object in the repository, storing the thumbnails and low-resolution
renditions (by using a DFC call) and storing media properties as attributes for each rendition
(in the attributes content_attr_name and content_attr_value of dmr_content objects). It removes
the dmi_queue item object from the queue.
10. The new object or renditions are available in the client application.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
19
Content Transformation Services Overview
Figure 6. The registration process
The automatic transformation processes performed by Content Transformation Services is described
in detail in the following sections:
• Generating thumbnails, page 20
• Generating storyboards, page 21
• Generating low-resolution renditions, page 21
• Extracting media properties, page 21
• Extracting XMP metadata, page 22
Generating thumbnails
A thumbnail is an image that is used to represent an object in client applications. Thumbnails provide
a visual cue for browsing media and enable users to identify objects quickly.
Content Transformation Services automatically generates a thumbnail for each object by passing the
object to the appropriate plug-in. The plug-in extracts the object’s properties and creates a new object
20
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Content Transformation Services Overview
by transforming the original object into a predefined thumbnail format (for example, a JPEG that is
100 x 100 pixels). Content Transformation Services sends the thumbnail back to Content Server as
a rendition of the original object. The thumbnail’s media properties are saved as attributes of that
rendition.
Content Server stores thumbnails in a special file store that is shared with the Thumbnail Server, a
dedicated server that delivers thumbnails directly to the browser.
Generating storyboards
Storyboards are low-resolution and low-bandwidth representations of video or multi-page objects
(for example, PDFs), displayed as a sequence of JPEG thumbnails. Storyboards are generated
automatically during registration (import or check in) of applicable file types.
For some video storyboards, each frame may include timecode information. The timecode is stored
as a property of each JPEG image content object in the storyboard.
For more information on which video formats are supported with a Streaming Server, see the EMC
Documentum Content Transformation Services Release Notes.
For multi-page documents such as PowerPoint presentations, the storyboard contains a thumbnail
of each slide in the presentation. Selecting one frame of an object’s storyboard will display that
frame in its related application as a JPEG image.
Storyboards are stored as renditions of the original dm_document object. Each JPEG image that
makes up a storyboard is stored in an administrator-specified location. For more information on
storage of objects, see the EMC Documentum Content Server Administration and Configuration Guide.
Generating low-resolution renditions
Low-resolution renditions are used to represent high-resolution objects. Low-resolution renditions
are used by the client applications when a user wants to preview a high-resolution media file. Due
to its smaller file size, a low-resolution rendition can be displayed more quickly than a file in its
original format.
Content Transformation Server automatically generates low-resolution renditions for supported files
upon registration. When the object is checked in, Content Transformation Server automatically
invokes the appropriate plug-in to generate the rendition according to a predefined profile. For
example, Content Transformation Server might generate a full-sized JPEG representation of the
image, reduce it to a predetermined width and height, and save it back to the repository as a
low-resolution rendition of the original object. Its media properties are stored as attributes of the
rendition. Low resolution renditions are stored in a location that is determined by the Content Server.
Extracting media properties
Content Transformation Services provides a range of plug-ins to support industry-standard file types.
Some plug-ins recognize files and automatically extract media-specific properties, such as image
height and width, bit rate, and audio sampling frequency.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
21
Content Transformation Services Overview
During registration, Content Transformation Services first generates media properties for the
high-resolution object. It then stores the properties for the object in two repeating attributes of
dmr_content objects: content_attr_name and content_attr_value.
Media properties are added to the object’s indexed metadata (as a string value) and saved back to
the repository. This provides the framework for client applications to expose media properties as
part of an object’s searchable metadata set. Content Transformation Services does the same for each
rendition (thumbnail, low-resolution, and transcoded renditions).
A sample of media properties extracted by Content Transformation Services for image, video, and
audio files can be found in Table 1, page 22.
Table 1. Sample extracted media properties for Content Transformation Services
Image
Video
Audio
Width
Frame width
Sample width
JPEG quality
Bit rate
Sample rate
Compression
Frame rate
Number of samples
Format
Format
Format
GIF interleave
Number of frames
Number of frames
Color mode
Frame height
Number of channels
Height
Duration
Duration
Extracting XMP metadata
Adobe’s Extensible Metadata Platform (XMP) embeds metadata (such as descriptions, titles,
keywords, author, and copyright information), into the file itself. In XMP-enabled applications,
metadata is captured during the creation process and embedded in the file.
Content Transformation Services has the ability to extract XMP metadata from supported formats
upon import. In addition, Content Transformation Services can write XMP metadata to those same
file formats.
User transformations
User requests are processed similarly to register requests. The main difference is that processing is
not automatic. A user must invoke a request for transformation.
The transformation process (depicted in Figure 7, page 23) is as follows:
1.
The Documentum client applications (WDK clients such as WebTop, Documentum Administrator,
Digital Asset manager, and so on) get a list of available profiles and their required parameters by
reading special system objects in the repository.
2.
The user requests a transformation for an object by selecting a profile and entering parameters
(if the profile requires parameters).
22
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Content Transformation Services Overview
3.
The application creates a transformation (TRANSCODE_CONTENT) request.
4.
Content Server creates a queue object that requests the transformation. The request contains the
profile ID, any parameter values required for a given operation (for example, height and width or
angle of rotation), and the source and target formats.
5.
The server polls the queue, finds objects for transformation, and matches the requested profile
and source format to a particular plug-in.
6.
The server locates the XML command-line file for the profile, substitutes parameters as required,
and invokes the plug-in to perform the transformation according to the selected profile and
parameters.
The transformation occurs in the background.
7.
When the transformation is complete, the server sends the transformed media back to Content
Server and updates the original object with the new rendition and its associated media properties,
which are stored as attributes of the rendition.
8.
The server removes the transformation request item from the queue.
Figure 7. The transformation process
User transformation profiles
Content Transformation Services provides a set of predefined profiles for most common operations
and allows administrators to extend or combine profiles and create new profiles to meet their specific
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
23
Content Transformation Services Overview
requirements. The following are examples of some profiles that a Content Transformation Services
administrator might create:
• Create small JPEG: Resizes an image to fit within 200 x 500 pixels and save it as a JPEG rendition.
• Resize H x W JPEG: Resizes an image to a specified height and width and save it as a JPEG rendition.
• Add text layer GIF: Adds a predefined text layer to an image and save it as a GIF rendition.
24
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Chapter 2
Administering and Configuring Content
Transformation Services through
Documentum Administrator
Many administration and configuration tasks for Content Transformation Services products can be
performed using the Content Transformation Services Administration component of Documentum
Administrator. You must have access to Documentum Administrator and the repositories to which
the Content Transformation Services product is configured.
The Content Transformation Services Administration component appears in Documentum
Administrator if at least one instance is installed and configured on a repository to which it is
connected. Perform this verification by executing the DQL/DFC call to find the presence of at least
one cts_instance_info object in the repository.
The following Content Transformation Services configuration and administration tasks can be
performed through Documentum Administrator client, in the Content Transformation Services
Administration Node:
• Change the user for repository login
• Change the polling interval— The polling interval is the amount of time in seconds that the
instance will wait between polls.
When document processing (transformation) is requested, Content Server creates queue items
and appends them to the dm_mediaserver queue or dm_autorender_win31 queue, depending
on the type of request. Content Transformation Services use a queue polling mechanism to look
for items in the queue to process. When Content Transformation Services finds items in any
of these queues, it proceeds with processing.
• Change the logging level — The logging level value controls how much information will be
recorded in the Content Transformation Services log files, which the product uses. Log files can
be used to troubleshoot the system.
• Change the system operator user — The system operator is the name of the user who receives
messages from an instance of Content Transformation Services .
If Content Transformation Services fails to process a particular item, it queues an event
(dm_mediaserver_error) to the Inbox of the repository user who is defined as the system operator
(sysOpUser). The event appears as an error message in the sysOpUser’s Inbox.
• Change the system notification setting — The notification setting controls whether success
notifications should be sent to each individual user requesting a transformation through Content
Transformation Services.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
25
Administering and Configuring Content Transformation Services through Documentum Administrator
• Change the maximum number of queue items — This value controls how many items the
Content Transformation Services instance adds for processing each time it polls the queue.
• Change the queue item expiry — This value controls the amount of time an item will be sitting on
a queue before being deleted from the queue.
• Change the Content Transformation Services user — This task can be done through
Documentum Administrator. Alternatively this task can be done using the setPassword utility.
Note that the system administrator must also change the password on the server. Changing the
administrator password, page 43 provides detailed information.
• View log files — Log files are created for each plug-in. The contents and detail level of each log file
depend on the log file setting you have chosen for the Content Transformation Services instance.
• View details of an instance — Details include the Content Transformation Services that is
configured for a repository, the version number of each product, the name of the host machine for
each product, its current status (running or stopped), the time it was last started, the number of
queued items for the instance, and the number of items processed by the instance.
• Control a Content Transformation Services instance — This includes starting, stopping,
and refreshing an instance. Note that performing any of these actions will apply to Content
Transformation Services running on the host. This is because Content Transformation Services on
a host uses the Content Transformation Services Windows service. Starting and stopping Content
Transformation Services Windows service can also be done manually, on the host machine. See
Starting and stopping Content Transformation Services, page 30.
The EMC Documentum Administrator User Guide provides more information about these
administration tasks.
Starting and stopping the Content
Transformation Services Administration
Agent
To use the Content Transformation Services Administration component in Documentum
Administrator, it is necessary to have the Content Transformation Services Admin Agent running on
the Content Transformation Services host machine. The Admin Agent can be controlled either from
the Windows Start menu or by running a batch file.
To start or stop the Content Transformation Services Admin Agent through the Start
menu:
1.
Log in to the Content Transformation Services host.
2.
Go to the Windows Services utility located at Start > Control Panel > Administrative Tools >
Services.
3.
Select Documentum CTS Admin Agent.
4.
To start the Admin Agent, click Start.
To stop the Admin Agent, click Stop.
26
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Administering and Configuring Content Transformation Services through Documentum Administrator
To start or stop the Content Transformation Services Admin Agent by running the
batch file:
1.
Log in to the Content Transformation Services host.
2.
Navigate to C:\Documentum\CTS\AdminAgent\bin.
3.
To start the Admin Agent, run the startup.bat file.
To stop the Admin Agent, run the shutdown.bat file.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
27
Administering and Configuring Content Transformation Services through Documentum Administrator
28
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Chapter 3
Configuration and Administration
Tasks and Tips
This chapter contains configuration and administration tasks for Content Transformation Services
products. Many configuration and administration tasks are performed through Documentum
Administrator.
The following sections are included in this chapter:
• General configuration and administration tasks, page 29
• Configuration tasks specific to Advanced Document Transformation Services, page 63
• Configuration tasks specific to Media Transformation Services, page 86
• Configuration tasks specific to Audio/Video Transformation Services, page 94
General configuration and administration tasks
This section contains procedures for the following general configuration and administration tasks
that are performed with Content Transformation Services products.
• Starting and stopping Content Transformation Services, page 30
• Adding or removing repositories using Content Transformation Services configurator, page 31
• Configuring separate Content Transformation Services instances to handle real-time and
asynchronous requests, page 31
• Integrating a Streaming Server with Content Transformation Services, page 32
• Defining file formats and DOS extensions, page 39
• Configuring Inbox notifications, page 39
• Changing the Content Transformation Services user, page 41
• Configuring multiple domains for Content Transformation Services products, page 42
• Understanding the Register profile, page 43
• Changing the administrator password, page 43
• Using the Content Transformation Services Reporting Tool, page 44
• Managing the transformation queue, page 46
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
29
Configuration and Administration Tasks and Tips
• Configuring the queue pre-processor mechanism, page 49
• Controlling how quickly programs time out, page 50
• Caching Content Transformation Services capabilities on startup, page 51
• Setting logging appenders, page 51
• Enabling performance and throughput logging, page 52
• Processing requests for local content, page 52
• Configuring Content Transformation Services for BOCS or ACS, page 53
• Configuring queue management for BOCS installations, page 54
• Load balancing servers, page 55
• Configuring the Server for SSL Mode, page 56
• Using a profile description bigger than 192 bytes, page 57
• Automating thumbnail or proxy creation for custom formats, page 57
• Performing bulk transformation requests for documents, page 58
• Improving the performance of Content Transformation Services, page 58
• Content Transformation Services clean up job, page 60
• Changing the hostname of the Content Transformation Services server machine, page 62
• Resolving issues with email content containing double byte characters, page 62
• PDF compliance not working, page 62
Starting and stopping Content Transformation Services
When you restart the Content Transformation Services host, the Content Transformation Services
server will start automatically. In addition, start and stop Content Transformation Services manually,
using the following procedure. This may be necessary after modifying a transformation profile,
for example.
To start or stop Content Transformation Services:
1.
Log in to the Content Transformation Services host.
2.
Go to the Windows services utility located at Start > Control Panel > Administrative Tools >
Services.
3.
Select Documentum Content Transformation Services.
4.
To start the product, click Start.
To stop the product, click Stop.
Note: A background service, called Documentum Content Transformation Monitor Services, restarts
Content Transformation Services if it stops unexpectedly. Since the monitor is set to run automatically
by default, you will not typically need to access it. It is located under Windows Services.
30
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Adding or removing repositories using Content
Transformation Services configurator
During installation, Content Transformation Services is configured to communicate with single or
multiple repositories. Add or remove a repository by running the Configurator (accessible through
the Windows Start menu). The EMC Documentum Content Transformation Services Installation Guide
provides information about the Configurator and how to run it.
Note: You must have SuperUser privileges for a repository to be able to add or remove support
for Content Transformation Services.
Configuring separate Content Transformation Services
instances to handle real-time and asynchronous
requests
For improving the performance of Content Transformation Services while handling both
asynchronous requests and real-time requests, you must have dedicated Content Transformation
Services instances for handling each kind of requests. If there are two Content Transformation
Services instances, for example,"CTS_Realtime” and "CTS_Async”, and you need to configure them
to handle real-time and asynchronous requests only, do the following:
1.
The "CTS_Realtime” instance should be tuned to not ping the queue and not pick up any of
the queue items.
a.
Login to the "CTS_Realtime” machine and navigate to the %CTS%\config folder.
b. Open the CTSServerService.xml file in a text editor.
c.
Comment out the full <QueueProcessorContext> sections, where queueItemName="dm_
mediaserver” for all of the repositories that are configured with "CTS_Realtime” instance.
There will be one <QueueProcessorContext> for one repository.
d. Update the other <QueueProcessorContext> and rename the queueItemName
"dm_autorender_win31" to "dm_autorender_win31_do_not_ping" for all of the repositories
that are configured with "CTS_Realtime” instance.
e.
2.
Save the file and restart Content Transformation Services.
The applications sending real-time requests to Content Transformation Services need to be
configured such that the requests do not go into "CTS_Async”.
a.
Login to the Application Server machine hosting your application.
b. Navigate to the Content Transformation Services preferences.xml and open it
in a text editor.
c.
Use this configuration element to specify a list of semicolon separated Content Transformation
Services instances.
ServerProperty Key="CTS_SkipList" Description="list of cts instances
(semicolon separated) to skip (scalability)" Value="CTS_Async;
<other-cts-instances>"/>
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
31
Configuration and Administration Tasks and Tips
Note: Use the hostname as it appears in cts_instance_info table. To retrieve the hostname,
run the "Select hostname from cts_instance_info” DQL.
With these changes, "CTS_Realtime” will not pick up any of the queue items and will be dedicated
only for the real-time requests. The "CTS_Async” will not receive any of the real-time requests and
will process only the queue items. This approach can be scaled up and applied to configure multiple
Content Transformation Services instances for handling either real-time or asynchronous requests.
Integrating a Streaming Server with Content
Transformation Services
This section describes how to integrate a Streaming Server with Content Transformation Services and
Content Server. It also provides an example of how to test the Streaming Server integration.
Supported streaming file format families depend upon the Streaming Server(s) that you integrate
with Content Transformation Services.
The following topics and tasks are included in this section:
• Prerequisites, page 32
• Setting up a Streaming Server, page 33
• Setting up streaming storage areas, page 33
• Setting default_storage for the format objects, page 34
• Ensuring Streaming Server access to storage areas, page 36
• Creating mount points or VirtualDirectory, page 36
• Setting the storage area’s base_url attribute, page 36
• Testing the Streaming Server, page 37
Prerequisites
Content Transformation Services does not include a Streaming Server. Streaming Server requirements
must be followed as per the documentation for those products. Content Transformation Services
is agnostic regarding streaming video servers and does not explicitly certify specific products or
versions. Streaming Servers must be purchased from their vendors.
Before integrating one or more Streaming Servers, they should be installed on their own host, where
possible. The Streaming Server should not be installed on the Content Server host. In many cases, the
intensive operations of the Streaming Server may degrade the performance of the Content Server.
There may be some exceptions to this, such as Windows Media Server. Refer to the documentation of
the streaming server product for further details.
32
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Setting up a Streaming Server
To integrate a Streaming Server with Content Server, complete the following steps.
To integrate a Streaming Server:
1.
Create a second dm_filestore object to store Windows Media streaming formats, if applicable.
Setting up streaming storage areas, page 33 provides detailed information.
2.
Set the default_storage attribute in the streaming format objects to the streaming storage area, as
described in Setting default_storage for the format objects, page 34.
3.
Ensure that the Streaming Server has access to the storage area. Follow the instructions in
Ensuring Streaming Server access to storage areas, page 36.
4.
Create a mount point (or a VirtualDirectory for Adobe Flash Media Server) on the Streaming
Server for the storage area, as described in Creating mount points or VirtualDirectory, page 36.
5.
Set the base_url attribute for the storage area. Setting the storage area’s base_url attribute, page
36 provides detailed information.
6.
Restart the Streaming Server.
7.
If using Windows Media Server, it should be initialized at least once prior to using with Content
Transformation Services.
Setting up streaming storage areas
Each Streaming Server may support different file formats. To use two Streaming Servers, you require
a second streaming storage area. The files handled by each server must be stored in separate areas.
This means that in addition to the default store (streaming_store_01), you must create another
streaming store (for example, streaming_store_02).
Note: It is important that you set the media_type to 2 in the dm_filestore object.
The Storage Management chapter in the EMC Documentum Content Server Administration and
Configuration Guide provides more information on creating storage areas.
To create a second streaming storage area:
1.
See the instructions provided in the EMC Documentum Content Server Administration and
Configuration Guide to create a dm_location object. Using DQL statements, your setup should
appear similar to the following:
create dm_location object
set object_name = ‘streaming_storage_02’,
set path_type = ‘directory’,
set file_system_path =
‘C:\DOCUMENTUM\data\<repository>\streaming_storage_02’,
set mount_point_name = ‘’
go
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
33
Configuration and Administration Tasks and Tips
2.
See the instructions provided in the EMC Documentum Content Server Administration and
Configuration Guide to create a dm_filestore object. Ensure that you set the media_type to 2. Using
DQL statements, your setup should appear similar to the following:
create dm_filestore object
set name = ‘streaming_store_02’,
set root = ‘streaming_storage_02’,
set is_public = true,
set require_ticket = false
set media_type = 2
go
Setting default_storage for the format objects
The default_storage attribute is used by the Documentum client to identify the storage location for
content. For streaming content, you must set the attribute to the object ID of the streaming content
storage area.
Only Digital Asset Manager and Web Publisher use the default_storage setting in format objects. If a
user saves a document with streaming content using any other Documentum client, the content is
saved to the default storage area for the object type.
Note: File formats supported by each server may change or differ from those listed below. Consult
your Streaming Server documentation for the current list of supported file formats.
Finding file format names
In the following DQL statements for setting the default_storage for format objects, file formats are
entered, not file extensions. File format names can be found by running the following DQL statement:
select * from dm_format where dos_extension = ’extension’
For example, the following DQL statement will find the name of the mov extension:
select * from dm_format where dos_extension = ’mov’
The result of the mov query will be one record, where quicktime is the proper format name for the
mov extension:
r_object_id
name
description
dos_extension
2701e306800001bf
quicktime
QuickTime Movie
mov
Windows Media formats
Even if you are using Real Helix Universal server exclusively, you must also identify a separate
storage area for Windows Media file formats. Use the following DQL statement to update the formats
recognized by the Windows Media storage area:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
where name =’<storage_area_name>’)
WHERE name in (‘<format_name>’, ‘<format_name>’)
34
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
For example, if the Windows Media file formats are to be stored in streaming_store_01, the statement
should appear as follows:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
WHERE name =’streaming_store_01’)
WHERE name in (‘wmv’, ‘wma’, ‘wmx’, ‘wax’, ‘asf’)
Real Media formats
Use the following DQL statement to update the formats recognized by the Real Media storage area:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
WHERE name =’<storage_area_name>’)
WHERE name in (‘<format_name>’, ‘<format_name>’)
For example, if the Real Helix server formats are to be stored in streaming_store_02:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
WHERE name =’streaming_store_02’)
WHERE name in (‘ra’, ‘ram’, ‘rm’, ‘rmm’, ‘rnx’, ‘rv’, ‘quicktime’)
Darwin formats
Use the following DQL statement to update the formats recognized by the Real Media storage area:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
WHERE name =’<storage_area_name>’)
WHERE name in (‘<format_name>’, ‘<format_name>’)
For example, if the Darwin formats are to be stored in streaming_store_03:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
WHERE name =’streaming_store_03’)
WHERE name in (‘quicktime’)
Flash formats
Use the following DQL statement to update the formats recognized by the Adobe Flash Media
Server storage area:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
WHERE name =’<storage_area_name>’)
WHERE name in (‘<format_name>’, ‘<format_name>’)
For example, if the Flash formats are to be stored in streaming_store_04:
UPDATE dm_format OBJECTS
SET default_storage=(SELECT r_object_id FROM dm_filestore
WHERE name =’streaming_store_04’)
WHERE name in (‘flv’, ‘f4v’)
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
35
Configuration and Administration Tasks and Tips
Ensuring Streaming Server access to storage areas
On a Windows host, the Streaming Server must run under the System account or as the Documentum
Content Server installation owner, to ensure access to the streaming content storage areas.
Creating mount points or VirtualDirectory
You must create a mount point (or a VirtualDirectory for Adobe Flash Media Server) on the Streaming
Server that points to the root of the streaming storage area. The root path is the value found in the
file_system_path attribute of the location object associated with the storage area. To obtain that
value, execute the following DQL statement:
SELECT file_system_path FROM dm_location a, dm_filestore f WHERE f.
name=’<storage_area_name>’ AND a.object_name=f.root
Substitute the storage area’s name for storage_area_name.
The returned value is a full root path specification for the storage area’s location.
Use your Streaming Server’s product documentation for instructions on how to create a mount
point or virtual directory.
Setting the storage area’s base_url attribute
For the Documentum client to retrieve a file from a streaming storage area, Content Server must
provide the URL for the content file. The Content Server then sends that URL to the Streaming Server.
The base of the URL returned by Content Server is defined in the base_url attribute of the streaming
storage area’s storage object. This attribute must be set manually for streaming content storage areas.
Refer to the documentation accompanying the Streaming Server to determine the base URL.
Note: For all base_url paths, you must include the ending forward slash (/).
For Windows Media Server:
• on its own, it is typically similar to:
mms://<host_name>/mountpoint1/
For Real Helix Universal Server, the base_url is typically similar to:
• Real file formats
rtsp://<host_name>:<port>/mountpoint1/
• Windows file formats (if you are not using Windows Media Server as well)
http://<host_name>:<port>/mountpoint2/
For Darwin Streaming Server:
• the base_url is typically similar to:
36
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
rtsp://<host_name>/
For Adobe Flash Media Server:
• the base_url is typically similar to:
rtmp://<host_name>/vod/mp4:<VirtualDirectory>/
To set the storage area’s base_url attribute:
For Windows Media Server:
• Use the following DQL statement to set the base_url attribute:
UPDATE dm_filestore object
set base_url=’mms://<machine name>/mountpoint1/’
where name = ’storage_area_name’
For Real Helix Universal Server:
• Use the following DQL statement to set the base_url attribute:
UPDATE dm_filestore object
set base_url=’rtsp://<machine name>:<port number>
/mount_point_name/’
where name = ’storage_area_name’
For Darwin:
• Use the following DQL statement to set the base_url attribute:
UPDATE dm_filestore object
set base_url=’rtsp://<machine name>/’
where name = ’storage_area_name’
For Adobe Flash Media Server:
• Use the following DQL statement to set the base_url attribute:
UPDATE dm_filestore object
set base_url=’rtmp://<host_name>/vod/mp4:<VirtualDirectory>/’
where name = ’storage_area_name’
Testing the Streaming Server
When you are finished integrating the Streaming Server with Content Server and Content
Transformation Services, it is important that you test the Streaming Server’s functionality.
You can test the configuration of your Streaming Server through IAPI calls.
Real Helix on Windows
The following example shows a test session for Real Helix Universal Server on Windows.
To test the Real Helix server on Windows:
1.
Enter the text in bold, when prompted:
/iapi32
Please enter a repository name (docubase) : dmtestdb
Please enter a user (Documentum): <user>
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
37
Configuration and Administration Tasks and Tips
Please enter password for Documentum :<password>
Documentum iapi - Interactive API interface
(c) Copyright Documentum, Inc., 1992-2001
All rights reserved.
Client Library Release 5.1.0.64 Win32
Connecting to Server using repository dmtestdb
[DM_SESSION_I_SESSION_START]info: "Session
011e9a8b80040107 started
for user Documentum."
Connected to Documentum Server running Release
5.1.0.64 Win32.Oracle
Session id is s0
API> create,c,dm_document
...
091e9a8b80037d00
API> set,c,l,object_name
SET> Streaming test
...
OK
API> set,c,l,a_storage_type
SET> streaming_store_01
...
OK
API> setfile,c,l,C:\Program Files\Real\RealServer\
Content\real8video.rm,rm
...
OK
API> save,c,l
...
OK
API> apply,c,l,GET_FILE_URL,FORMAT,S,rm
...
q0
API> next,c,q0
...
OK
API> dump,c,q0
...
USER ATTRIBUTES
result : T
base_url: rtsp://eng178:554/mountpoint1/
store : streaming_store_01
path : 001e9a8b\80\00\00\42.rm
ticket :
SYSTEM ATTRIBUTES
APPLICATION ATTRIBUTES
INTERNAL ATTRIBUTES
API> close,c,q0
...
OK
API>
2.
Concatenate the value for base_url and path (for example, rtsp://eng178:554/mountpoint1/
001e9a8b\80\00\00\42.rm) and paste the string into the Real Player.
The video represented by the URL will begin to stream.
38
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Defining file formats and DOS extensions
Define file formats and DOS file extension pairs in the repository for all source document types
that you want Content Transformation Services to recognize that are not standard, out of the box
pairs. In addition, if the DOS file extension differs from the Documentum format name, update the
FormatMapperService.xml config file on the Content Transformation Services host.
The EMC Documentum Administrator User Guide provides information and procedures to add file
formats to your system.
The following procedure is required only if the DOS file format differs from the Documentum
format name in Content Server. Table 2, page 39 lists some examples of the format mapping used in
Documentum systems. Use these format names in DQL.
Table 2. Documentum format mapping
Format
Documentum name
Bitmap image (BMP)
bmp
Encapsulated PostScript (EPS)
eps
GIF image
gif
JPEG image
jpg
TIFF image
tif
To update the FormatMapperService config file:
1.
Navigate to %CTS_HOME%\config.
2.
Open the FormatMapperService.xml file in a text editor.
3.
Add the format to the <CTSHandlerList> section, using the following syntax:
<FormatMapper CTSFormat="<dos extension>" DocumentumFormat="<format
name in Content Server>"/>
For example, the entry for JPEG files is:
<FormatMapper CTSFormat="jpeg" DocumentumFormat="jpg"/>
4.
Save and close the FormatMapperService.xml file.
Configuring Inbox notifications
When transformation requests fail, the Content Transformation Services server sends notifications to
the Inbox of the repository user. By default, success notifications are not sent. However, these default
behaviors can be configured using the procedures in this section.
The behavior of success and failure notifications differs slightly. While success notifications can be
suppressed for all users, failure notifications are sent to admin users regardless of the setting. Table
3, page 40 outlines these behaviors.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
39
Configuration and Administration Tasks and Tips
Table 3. Inbox notification settings
Notification
Setting
User(s) notified
Success
Yes
Regular user
No
none
Yes
Regular user and admin user
No
Admin user
Failure
The following is the level of Notification configuration option:
• Configuring the CTSServerService.xml file. See the procedures below for configuring the file.
To modify the configuration of success notifications:
1.
Navigate to %CTS_HOME%\config.
2.
Open the CTSServerService.xml file in a text editor.
3.
To turn on notifications for successful transformations, set the notifySuccessMessage parameter
to the following:
<CTSServer AttributeName="notifySuccessMessage" AttributeValue="YES"/>
To turn off notifications for successful transformations, set the notifySuccessMessage parameter
to the following:
<CTSServer AttributeName="notifySuccessMessage" AttributeValue="NO"/>
Note: There are two <QueueProcessorContext> tags for each repository that is configured.
Modify the notifySuccessMessage parameter within each <QueueProcessorContext> tag.
4.
Save and close the CTSServerService.xml file.
To modify the configuration of failure notifications:
1.
Navigate to %CTS_HOME%\config.
2.
Open the CTSServerService.xml file in a text editor.
3.
To turn on notifications for failure transformations, set the notifySuccessMessage parameter to
the following:
<CTSServer AttributeName="notifyFailureMessage" AttributeValue="YES"/>
To turn off notifications for failure transformations, set the notifySuccessMessage parameter to
the following:
<CTSServer AttributeName="notifyFailureMessage" AttributeValue="NO"/>
Note: There are two <QueueProcessorContext> tags for each repository that is configured.
Modify the notifySuccessMessage parameter within each <QueueProcessorContext> tag.
4.
40
Save and close the CTSServerService.xml file.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Inbox notification behavior
Content Transformation Services behaves differently for admin and regular queue items. The
following table details the behavior for administrative and regular users based on the type of queue
item and notification options selected.
Table 4. Inbox notification behavior for admin and regular users
Legacy calls (dm_autorender_win31 queue items)
Success Notification
Failure Notification
Admin user
Will not be notified.
Regular user
Will be notified
based on the entry in
CTSServerService.xml
for ‘notifySuccessMessage’.
Admin user
Both Admin user and
Regular user will be notified
based on the entry in
CTSServerService.xml
for ‘notifyFailureMessage’.
Regular user
Regular Queues (dm_mediaserver queue items)
Success Notification
Failure Notification
Admin user
Will be notified if
‘notifySuccessMessage’ is
set to ‘Yes’ and at the same
time if Regular user has not
requested it through the client
interface.
Regular user
Will be notified based on
the value given in the
client interface during the
transformation request.
Admin user
Will be notified based on the
entry in CTSServerService.xml
for ‘notifyFailureMessage’.
Regular user
Will be notified based on
the value given in the
client interface during the
transformation request.
Changing the Content Transformation Services user
In certain situations, it may be desirable to change the Content Transformation Services user account
after Content Transformation Services has been installed and configured. This may be necessary
for security reasons.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
41
Configuration and Administration Tasks and Tips
It is not necessary to uninstall and reinstall Content Transformation Services to make this change.
Simply ensure that the new user has the Admin priviledge or same access as the existing user for any
rendering software (for example, Ghostscript is being used by Content Transformation Services).
Configuring multiple domains for Content
Transformation Services products
The multiple domains feature processes user requests to multiple domains. This feature is enabled
only if the repository is already in domain-required mode. The following procedure is completed
using Documentum Administrator:
To configure users for multiple domains:
1.
Connect to the repository that is configured for the Content Transformation Services instance.
2.
Click the Administration node.
3.
Click the Content Transformation Services node.
4.
Click the CTS Instances node.
5.
Select the Content Transformation Services instance from the list of available instances.
6.
Click Tools > Content Transformation Services > Configure > Users.
7.
The CTS Administrative Users page displays a list with pre-configured administrative users and
their domains for the selected Content Transformation Services instance. Click Add.
The Content Transformations Services User Details page appears.
8.
Select the required super user from the list of options.
Note: The required dm_user should already be added to the repository.
9.
Enter the correct password.
10. Enter the correct domain.
11. Click OK to return to the CTS Administrative Users page.
12. Select OK to save the changes.
To change the password of an existing domain user configuration:
1.
From the CTS Administrative Users page, select the required domain user. Click Edit.
The Content Transformations Services User Details page appears with the Password fields
enabled.
2.
Enter the new password.
3.
Click OK to return to the CTS Administrative Users page.
4.
Select OK to save the changes.
To remove a domain user configuration:
1.
42
From the CTS Administrative Users page, select the domain user configuration you want to
remove. Click Delete.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
2.
Select OK to save the changes.
Understanding the Register profile
The Register Profile (register_xxxx.xml) is available in various flavors. A "forClient” attribute is
added to each InnerProfile element of the Register Profile. If this attribute is available for an inner
profile in the Register Profile, then Content Transformation Services will validate its value against the
value provided in the <forClients> element in the CTSProfileService.xml for each repository. If
the values match, the inner profile is executed.
For example, consider that the Register Profile has an inner profile register_xcp.xml for which the
"forClient” attribute is set to XCP.
<Transcodings>
<Transcode name="register" label="Register Profile"/>
</Transcodings>
<ProfileSequence>
<InnerProfile path="/System/Media Server/System Profiles/register_legacy"
waitOnCompletion="false" forClient="LEGACY">
</InnerProfile>
<InnerProfile path="/System/Media Server/System Profiles/register_mobile"
waitOnCompletion="false" forClient="MOBILE">
</InnerProfile>
<InnerProfile path="/System/Media Server/System Profiles/register_xcp"
waitOnCompletion="false" forClient="XCP">
</InnerProfile>
</ProfileSequence>
When Content Transformation Services is installed and configured to a certain repository, then the
<forClients> element in CTSProfileService.xml will reflect the following:
<ProfileManagerContext>
.....
<ForClients>XCP</ForClients>
.....
</ProfileManagerContext>
Since the value "XCP” matches the value in the <forClients> element, this inner profile is executed.
Hence, if you are required to add or change formats or profiles for xCP clients, then all changes
should be made to both the register_xcp.xml and register.xml.
Note: If an inner profile does not contain the "forClient” attribute, then it will be executed irrespective
of the "forClients” value(s) specified in the CTSProfileService.xml.
The EMC Documentum Content Transformation Services Profile Modification Guide provides detailed
information about the Register Profile.
Changing the administrator password
Change the Content Transformations Services administrator’s password by running the setPassword
utility. The password must be changed on Content Server also.
To change the administrator’s password:
1.
Stop Content Transformation Services.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
43
Configuration and Administration Tasks and Tips
2.
Change the password on the Content Server.
3.
Open a command prompt window.
4.
Enter the following command:
> cd %CTS%\docbases\<repository name>\CTSServerScript\bin
> setPassword <new_password>
5.
Restart Content Transformation Services.
Note: It is also possible to change the password in Documentum Administrator instead of running
the setPassword utility.
Using the Content Transformation Services Reporting
Tool
The Content Transformation Services Reporting Tool provides detailed information about
transformation type, volume, and error events. Data such as Content Transformation Services
performance, plug-in usage, and requests by users assists in monitoring and analyzing transformation
usage and can assist with load balancing strategies. Reporting can be logged for a configurable time
frame and then rolled over to be archived. The resulting information is retained in the repository
and is viewable as a CSV formatted file (a report format using comma-separated values) through
Digital Asset Manager. Users can view their own Content Transformation Services reporting data.
Administrators have access to all data.
Usage tracking is configured in Documentum Administrator. The Content Transformation Services
Reporting Tool reports on the number of requests in a given time frame according to the following
options:
• Number of successful transformations
• Number of requests that could not be handled
• Cumulative error report
• Number of errors per format and per specific transformation request
• Cumulative total file sizes of input and output per given time frame
• Total requests per specific user
Enabling and disabling the Content Transformation Services
Reporting Tool
The Content Transformation Services Reporting Tool is turned off by default. Usage tracking can
be switched on or off.
To enable or disable the Content Transformation Services Reporting Tool:
1.
Login to Documentum Administrator.
2.
In the tree pane, select Transformation Services > CTS Reporting Configuration.
44
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
3.
Select the following:
• Reporting Configuration (ON/OFF) check box, to select whether the data is collected or not.
• Purging Configuration (ON/OFF) option, to delete any data collected.
• Archiving Configuration (ON/OFF) option, to select whether data should be archived.
4.
If you have enabled Reporting Configuration and Archiving Configuration, provide the
information for the following fields.
• (Number of days) Archiving Interval to set how often the report should be archived —
everyday, every two days, and so on.
• (Size of transformation request table) Archiving DataSize, to set the number of transformations
that should be recorded at a time before the data is archived and for the compilation to start
again.
• (Archiving monitor interval in seconds) Archiving Monitor Interval, to set the length of time
in seconds the report should be updated.
5.
Click OK.
Viewing the Content Transformation Services Reporting Tool report
When the Content Transformation Services Reporting Tool is enabled, the following information is
recorded for each transformation request:
• The object ID of the source document
• The object ID of the queue item
• The user name who sends the requests
• The format of the source document SOURCE_FORMAT = "source_format"
• The format of target TARGET_FORMAT = "target_format"
• The transformation type, it could be either user created or auto/import
• The profile name used for the transformation request
• The target object type, it could be rendition or related object
• The parameters send in the request
• The queue item added time
• The queue item signed off time
• The transformation completed time
• The source file size
• The target file size
• The status, it could be SUCCESS, FAILED, or UNHANDLED
• The Content Transformation Services instance doing the transformation
• Any message resulting from a transformation execution.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
45
Configuration and Administration Tasks and Tips
To view the Content Transformation Services Reporting Tool report:
1.
2.
In Digital Asset Manager, go to Tools > Transformation report > View. The CTS Transformation
Report page appears.
Enter information for the following fields:
• Report name
• Start date
• End date
3.
Click OK. The Select Folder screen appears.
4.
Select the destination folder to save the retrieved report. Click OK. A CSV report opens with
the requested information.
Managing the transformation queue
The Queue Management feature provides a mechanism for monitoring and administering
transformation request queues. This feature allows users to view or delete their own pending
transformation requests. Administrators can manage the queues for all users and change the priority
of transformation requests when required.
The Queue Management feature is accessed through the Transformation node in Digital Asset
Manager.
Administrators can manage the queue by deleting items or changing the priority of items. Users can
view their own transformation requests and delete their own transformation requests, but cannot
change a queue item priority.
• Viewing transformation requests in the queue, page 46
• Changing a queue item’s priority, page 47
• Viewing details of a queue item, page 47
• Deleting a pending queue item, page 48
• Configuring additional queue management fields, page 49
Viewing transformation requests in the queue
Users can monitor the status of their transformation requests by viewing the queue. If a user is
dissatisfied with the priority level of their transformation request(s), they can ask their administrator
to change an item’s priority on their behalf.
To view transformation requests in the queue:
1.
Login to Digital Asset Manager.
2.
In the tree view on the left side of the screen, select the Transformations node. Click on the
Transformations link. A list of current queue items appears on the right pane.
46
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Transformation requests are displayed in the order of priority. The priority level of an item is
indicated as follows:
3.
•
denotes a high priority item
•
denotes a medium priority item.
•
denotes a low priority item.
For administrators only: Choose the items to view by selecting an option from the Show list
box in the top right corner:
• Show All displays all users transformation requests.
• Show Mine displays only your transformation requests.
4.
To sort transformation requests in ascending or descending order, click the header field on each
of the columns.
Changing a queue item’s priority
Administrators can change the priority of an item in the queue.
To change a queue item’s priority:
1.
Login to Digital Asset Manager.
2.
In the tree view in the left pane, select the Transformations node. The transformation queue
appears in the main pane.
3.
Find the target item in the queue.
4.
Select the item, and right-click with your mouse.
5.
Select View from the context menu.
The transformation details of this item are displayed.
6.
Change the numeric value in the Priority box. The highest priority is 10. The higher the numeric
value, the higher the priority level. When the priority level is changed, the queue position of
the object will change automatically.
7.
Click OK. The page returns to the list the transformation queue. Verify if the queue position has
changed. The color code of the priority item should change to a higher priority. See Viewing
transformation requests in the queue, page 46 for queue item priority level color codes.
Viewing details of a queue item
When a pending item is in the queue, the following transformation details are available depending on
which fields are configured:
• Description gives the name of the transformation being performed, such as Rotate.
• Parameters lists any user-defined parameters for this transformation, if applicable. For a
transformation such as Rotate, for example, the angle of rotation would be a parameter.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
47
Configuration and Administration Tasks and Tips
• From gives the name of the user who requested the transformation.
• Received is the date and time the transformation was requested.
• Source is the source (or input) file name being transformed.
• Priority is given to a queue item with the highest numeric value.
• Target is the target (or output) file name for the transformation. If the request is to create a
rendition, the Target field will show "None".
• Queue position gives the specific order number of this item in the queue.
To view details of a queue item:
1.
Login to Digital Asset Manager.
2.
In the tree view in the left pane, select the Transformations node. The transformation queue
appears in the main pane.
3.
Find the target item in the queue.
4.
Select the item, and right-click with your mouse.
5.
Choose View from the context menu.
The transformation details of this item are displayed.
Deleting a pending queue item
Administrators can delete any items in the queue. Users can only delete their own queue items. The
deletion is not immediate for users. Items are marked, then polled and then deleted.
Note: The queue item cannot be deleted if Content Transformation Services has already picked
up the queue for processing.
To delete a pending queue item:
1.
Go to the transformation queue by selecting the Transformations node.
The transformation queue appears in the main pane.
2.
Find the item(s) to delete from the queue.
To find items quickly, configure the display as follows:
• Sort alphabetically by document name by clicking the header on the Document column.
• Sort the requests alphabetically by user name by clicking the header on the Sent by column.
• Toggle between all users’ transformation requests or your own transformations using the
Show list box.
3.
Select the item(s), and right-click with your mouse.
Note: Select a range of items using the Shift key, or select multiple items using the Ctrl key.
4.
Select Delete from the context menu.
A delete confirmation page appears for each file you selected.
5.
48
Select OK to confirm a deletion, or click Cancel to abort a deletion request.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
If the queue item is pending, it will be deleted and removed from the transformation queue. If the
queue item is being processed, an error will show saying "Transformation request is being processed,
can’t delete."
Configuring additional queue management fields
Customize the queue management fields by adding additional columns.
To configure additional queue management fields:
1.
Login to Digital Asset Manager.
2.
Go to the Transformations node.
The right pane shows the default column fields.
3.
Click Column Preferences.
The screen displays the Preferences: Display Settings on the left and the default column setting
on the right.
4.
Select an additional item from the left list "Select attributes to display". Click the button to add to
the right list "Selected attributes to display as column". The right list shows the new attribute
added. Click OK.
The list view appears.
5.
Verify if the list view has the additional columns.
Configuring the queue pre-processor mechanism
This procedure mainly applies if you have different Content Transformation Services instances
polling the same repository but installed on separate hosts.
The queue pre-processor mechanism analyzes queue items and marks those that can be executed by
the Content Transformation Services instance, preventing items from being prematurely expired by a
Content Transformation Services instance that cannot handle them. This will also help the regular
queue processor thread not to perform the capability checking again during the execution. The
pre-processor tasks run with their own sessions.
This functionality is controlled by two elements in the CTSServerService config file:
• allowQueuePreProcessing
This element is used to pre-process queue items when Content Transformation Services starts up.
If the value is set to "YES", the pre-processor thread will be created. By default, the value is set to
"NO", and there is no pre-processing mechanism.
• markerInterval
This element sets the wait period between consecutive queue pre-processing jobs.
The expiration period and marking interval should be tuned based on each system configuration.
On a system with more than one Content Transformation Services instance polling the same queue,
the marker mechanism is not required and thus the default setting is appropriate. However, if there
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
49
Configuration and Administration Tasks and Tips
are different Content Transformation Services instances running against a repository, one Content
Transformation Services instance might expire items (because it cannot handle them) when the
instance that could handle them is busy. In this case, the pre-processing mechanism should be turned
on for those instances that could process the items.
Controlling how quickly programs time out
When Content Transformation Services is processing a request, it utilizes third party plug-ins as part
of the process. There may be occasions when one of these plug-ins fail, or simply runs longer than
you want it to run. To control the resources consumed by a plug-in, Content Transformation Services
includes an application timeout parameter. The value assigned to the parameter determines how
long the product waits for a plug-in to complete its process before moving on to the next request. The
timer starts when Content Transformation Services calls the plug-in.
For example, if Content Transformation Services calls a third party plug-in to print a PDF version of a
document and that process does not complete within 30 seconds, Content Transformation Services
abandons the request and checks the queue for the next request. When a rendition operation fails,
Content Transformation Services sends a message reporting the failure to the Content Transformation
Services log file and also to the requester’s Inbox.
The value for the application timeout parameter is controlled by the following related tags in the
plug-in configuration file:
<APPLICATION_WAIT_INTERVAL>1200</APPLICATION_WAIT_INTERVAL>
<APPLICATION_MONITOR>true</APPLICATION_MONITOR>
The default value for "APPLICATION_WAIT_INTERVAL” is 1200.
For example, if you want to configure "APPLICATION_WAIT_INTERVAL” to a higher value for any
PowerPoint transformation, modify the tags of the powerpoint1.xml file (available under the
folder %CTS_HOME%\CTS\config\powerpoint1\) as follows:
<APPLICATION_WAIT_INTERVAL>2400</APPLICATION_WAIT_INTERVAL>
APPLICATION_MONITOR>true</APPLICATION_MONITOR>
The wait interval represents the amount of time (in seconds) between retries. The max_retries value
multiplied by the wait_interval value gives the timeout parameter value.
<MAX_RETRIES>60</MAX_RETRIES>
<WAIT_INTERVAL>5</WAIT_INTERVAL>
For example, if you want to configure this value to 30 seconds, modify the values as follows:
<MAX_RETRIES>6</MAX_RETRIES>
<WAIT_INTERVAL>5</WAIT_INTERVAL>
Note: This task can also be performed through the Content Transformation Services Administration
component in Documentum Administrator. See Chapter 2, Administering and Configuring Content
Transformation Services through Documentum Administrator.
50
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Caching Content Transformation Services capabilities
on startup
An option is available to cache a Content Transformation Services instance’s execution capabilities.
Content Transformation Services can cache execution capability information of all the atomic profiles
in the repositories in which a Content Transformation Services instance is configured against.
This caching can be done either during the Content Transformation Services startup which can be
configured in the CTSProfileService.xml, or during the first load balancer call for getting the
capabilities. Refer to the following tags added to the service configuration file. The default value is
set to ’true’, which means Content Transformation Services will cache this capability information
during startup:
<ProfileConfig ProfileConfigName="cacheCapabilityOnStartup" ProfileConfigValue="true"/>
The logging information related to this is logged to a separate log file configured in the
log4j.properties CAPABILITYAppender (refer to the section Setting logging appenders, page 51).
While performing profiles across instances, if Content Transformation Services identifies a
remote instance, capable of executing any of the inner atomic profiles of a nested profile, Content
Transformation Services caches this information up to the profileRefreshInterval attribute value
configured in the following tag. This value represents numbers of minutes.
<ProfileConfig ProfileConfigName="profileRefreshInterval" ProfileConfigValue="5"/>
Setting logging appenders
Separate Logging appenders are added to the log4j.properties for logging the polling and capability
caching information. Refer to the following entries in the log4j.properties file:
log4j.category.POLLINGAppender=INFO,
POLLINGAppender
log4j.appender.POLLINGAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.POLLINGAppender.File=<CTS_HOME>\\logs\\Polling_log.txt
log4j.appender.POLLINGAppender.Append=true
log4j.appender.POLLINGAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.POLLINGAppender.layout.ConversionPattern=%d{HH\:mm\:ss,SSS} %10r
%5p [%10t] %-20c - %5x %m%n
log4j.appender.POLLINGAppender.DatePattern=’.’yyyy-ww-dd
log4j.category.CAPABILITYAppender=INFO,
CAPABILITYAppender
log4j.appender.CAPABILITYAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.CAPABILITYAppender.File=<CTS_HOME>\\logs\\Capability_log.txt
log4j.appender.CAPABILITYAppender.Append=true
log4j.appender.CAPABILITYAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.CAPABILITYAppender.layout.ConversionPattern=%d{HH\:mm\:ss,SSS} %10r
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
51
Configuration and Administration Tasks and Tips
%5p [%10t] %-20c - %5x %m%n
log4j.appender.CAPABILITYAppender.DatePattern=’.’yyyy-ww-dd
The log files Polling_log.txt and Capability_log.txt corresponding to these appenders will
have the logs related to polling and capability caching information respectively. This information
will not be logged to the main CTS_log.txt file. The log level can be set to DEBUG for getting
more information.
Enabling performance and throughput logging
The ability to create a separate performance log file is available. The following entry in the
log4j.properties file will enable this functionality:
com.documentum.performancelogging.enabled=false
com.documentum.performancelogging.file=<CTS_HOME>\\logs\\Performance_log.txt
The default value is set to ’false’. Setting this value to ’true’ will create a Performance_log.txt
under <CTS_HOME>\logs folder.
Edit the value of the following entry to define the interval of rolling up performance log into storage
repository:
com.documentum.performancelogging.rollupInterval=24H
The value format is an integer number +H (case insensitive). For example, for an interval of 12 hours,
the value is 12H. If omitted, the value will be a default value of 24H. When the interval value has
been reached, the performance log will be parsed and a performance and throughput report xml will
be generated. Then, a zip file, which contains the report xml and the related style sheets, will be
uploaded to the storage repository as defined in the SessionService.xml.
ICMS web service provides a Metric Service to parse the zip files from the storage repository and
create metric report on the performance and throughput data.
Processing requests for local content
Content Transformation Services includes a configuration element called "processLocalContentOnly”,
which is useful in distributed environments to instruct Content Transformation Services to process
requests for content residing in local (near) file stores and not pick up requests for content in distant
files stores.
The configuration is in the file %CTS%\config\CTSServerService.xml. Under each
<QueueProcessorContext> node, there is a line:
<CTSServer AttributeName="processLocalContentOnly" AttributeValue=""/>
Valid values are YES or NO. The default is NO.
52
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Configuring Content Transformation Services for BOCS
or ACS
If required, use the Branch Office Caching Services (BOCS) documentation to install BOCS and
configure it for a global registry. The following section outlines the procedures required to configure
Content Transformation Services for BOCS.
The following are limitations of BOCS with Content Transformation Services:
• Inbound operations (saving renditions and checking-in) are not supported.
• Saving renditions is not supported due to the DFC limitation (IDfImportOperation does not
support adding renditions).
• Checking-in (version up) is not supported.
• XML documents are exported through DFC. DFC does not allow you to transfer XML contents
through BOCS/Accelerated Content Services (ACS) even though the BOCS/ACS options are
specified.
To configure Content Transformation Services for Branch Office Caching Services or
Accelerated Content Services:
1.
For all Content Transformation Services that use ACS or BOCS, update the
CTSServerService.xml file located at %CTS%\config\.
The file may be updated at the master configuration level:
<CTSServerConfig>
...
<BocsConfig networkLocationId="" allowBocsTransfer="true" preferAcsTransfer="true"
allowSurrogateTransfer="true" processOnlyParked="false"/>
...
</CTSServerConfig>
Overwrite the master settings, using repository specific preferences, through the queue processor
configuration:
<QueueProcessorContext DocbaseName="my_repository">
...
<CTSServer AttributeName="networkLocationId" AttributeValue=""/>
<CTSServer AttributeName="allowBocsTransfer" AttributeValue=""/>
<CTSServer AttributeName="preferAcsTransfer" AttributeValue=""/>
<CTSServer AttributeName="allowSurrogateTransfer" AttributeValue=""/>
<CTSServer AttributeName="processOnlyParked" AttributeValue=""/>
...
</QueueProcessorContext>
These options are based on IDfAcsTransferPreferences:
• networkLocationId: Preferred network location identifier, if multiple network locations can
be applied to the machine. The network location identifiers need to be configured in the global
registry repository. If this is not set, the first available network location identifier will be used.
• allowBocsTransfer: Specifies whether BOCS content transfer is allowed (default: true).
• preferAcsTransfer: Sets the accelerated content transfer preference (default: true).
• allowSurrogateTransfer: Specifies whether surrogate transfer is allowed (default: true)
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
53
Configuration and Administration Tasks and Tips
Note: Before signing off the queue item, Content Transformation Services performs a
canExecuteProfile check to verify if the content for a transformation is available. If any of
the content that participates in the transformation is not available for a particular Content
Transformation Services instance, it indicates that the content for a transformation is not available.
2.
Update the export operations.
If allowBocsTransfer or preferAcsTransfer is set and the ACS transfer is configured for the
repository, all the export operations will specify the ACS preference options and try to get the
transfer URLs for contents.
If the transfer URLs are returned, the contents will be downloaded through the URL protocols.
Note: If allowBocsTransfer = true, then preferAcsTransfer must be set to "true”, if the content
has to be retrieved through BOCS. This is a DFC requirement.
Configuring queue management for BOCS installations
Use the processOnlyParked feature to ensure that Content Transformation Services polls queue items
only from the content available at a specific BOCS location.
1.
Following are the requirements when the processOnlyParked = true:
• allowBocstransfer = true
• preferAcsTransfer = true
• allowSurrogateTransfer = true
• parkingServerName="BOCS_ABC" //object_name of the BOCS config object associated with
the BOCS server
• networkLocationId="BOCS_NETLOC" // Network location served by the BOCS_ABC. Ensure
that this networkLocation is server by BOCS_ABC.
Note: These settings can be specified at a global or master level (applicable to all repositories) or
at a local level (specific repository).
2.
To make the processOnlyParked settings global, navigate to the xpath: //CTSCustomConfig/
CTSServerConfig/BocsConfig and make the following modifications:
<BocsConfig allowBocsTransfer="true
allowSurrogateTransfer="true"
preferAcsTransfer="true"
networkLocationId="BOCS_NETLOC" <!--Network location served by the BOCS_ABC.
Make sure that this networkLocation is server by BOCS_ABC-->
processOnlyParked="true"
parkingServerName="BOCS_ABC"/> <!--object_name of the BOCS config object
associated with the BOCS server-->
3.
To make the processOnlyParked settings specific to a repository, add or modify the
following tags in one of the QueueProcessorContext node in the repository xpath :
//[email protected]="My_Docbasename":
<CTSServer
<CTSServer
<CTSServer
<CTSServer
<CTSServer
54
AttributeName="allowBocsTransfer" AttributeValue="true"/>
AttributeName="allowSurrogateTransfer" AttributeValue="true"/>
AttributeName="networkLocationId" AttributeValue="BOCS_netLOC"/>
AttributeName="preferAcsTransfer" AttributeValue="true"/>
AttributeName="processOnlyParked" AttributeValue="true"/>
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
<CTSServer AttributeName="parkingServerName" AttributeValue="BOCS_ABC"/>
Note: Ensure that you replicate the same values under all QueueProcessorContext nodes for a
repository or define these settings in one of the QueueProcessorContext nodes for a repository.
If different set of values are specified in different QueueProcessorContext nodes for the same
repository, then the behavior will not be as required.
4.
If local values are not defined, then global values are used as a fallback option.
Load balancing servers
The standard installation for Content Transformation Services consists of one repository with one
server. Additional servers can be added to an active repository to enhance its performance. Load
balancing can optimize performance by spreading transformation requests between multiple servers.
Load balancing can be achieved by adjusting settings in the CTSserverservice.xml file, in the
%CTS%\config folder. By default, Content Transformation Services is equipped with a standard
load balancing strategy.
The ideal load balancing strategy depends upon your environment and the specific servers in use.
Contact your Documentum consulting representative for load balancing guidance.
Configuring Content Transformation Services Load Balancer
The preferences.xml file (default location is C:\Documentum\CTS\config) allows
configuration for various aspects of load balancer functionality. The following details what each line
of the configuration file does.
This line is used to configure how Content Transformation Services should handle the request:
<LoadBalancer type="remote" URL="http://host:port/services/transformation/Load
Balancer/"sendMode="remote"/>
• type="local” - load balancer runs within the same JVM as the API client
• type="remote” && sendMonde="local” - call is made to the remote load balancer (specified in
URL="http://..." ) to retrieve the Content Transformation Services instance URL and the SBO
sends the request
• type="remote” && sendMonde="remote” - call is made to the remote load balancer to select
the instance and send the request
These two lines control failover retries for the case where a request is sent to Content Transformation
Services but comes back with an error:
<ServerProperty Description="Allow a number of retries if a request sent to CTS
fails" Key="FailoverRetries" Value="1"/>
<ServerProperty Description="Wait between failover retries (seconds)"
Key="FailoverWait" Value="1”/>
Specify how frequent the load balancer should refresh its "CTS occupancy level” cache:
<ServerProperty Key="CTSOccupancyPollingInterval" Description="Specify occupancy
polling interval in seconds" Value="7"/>
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
55
Configuration and Administration Tasks and Tips
Specify the number of repository connection retries (in case <Repositories> node is not configured):
<ServerProperty Key="ConnectionRetries" Description="Specify connection retries
(in case Repositories section is not configured )" Value="10”/>
Control failover for the scenario where no Content Transformation Services instances are found that
are available to execute a request (that is, an instance is busy or starting up, meaning there is chance
in the near future it could become available):
<ServerProperty Key="AvailabilityRetries" Description="Number of retries when
CTS instances are not available" Value="0"/>
<ServerProperty Key="AvailabilityWait" Description="Number of seconds to wait
for rechecking availability" Value="0"/>
Use this configuration element to specify a list of semicolon separated Content Transformation
Services instances (host name as it appears in cts_instance_info). It can be used to have one or
more instances process only asynchronous requests or scale up the load balancer by assigning a
specific set of Content Transformation Services instances to one load balancer and a different set of
Content Transformation Services instances to another load balancer (Content Transformation Services
instances from the same repository):
<ServerProperty Key="CTS_SkipList" Description="list of cts instances (semicolon
separated) to skip (scalability)" Value="CTS1;CTS3"/>
The ”InstanceSelector” property specifies the selection algorithm used by the load balancer. The new
value points to the occupancy based implementation:
<ServerProperty Key="InstanceSelector" Description="Specify an implementation class
for instance selection "
Value="com.emc.documentum.cts.lb.workers.OccupancyBasedSelector"/>
Note: The InstanceSelector value is used internally and should not be changed.
Configuring the Server for SSL Mode
Content Transformation Services Server and Content Transformation Services Web Services can be
configured to run in SSL mode (that is, https instead of http).
This is enabled at the application server level, where each application server has their own procedure
to make it handle https. However, Content Transformation Services must be updated to accept
the new SSL port.
For any real time requests, the Content Transformation Services WebServices server communicates to
the Content Transformation Services Server through http. Content Transformation Services Server
bundles the Jetty application server with it. To configure this communication in SSL (https) mode,
the following procedures have been provided.
To configure Content Transformation Services WebServer to run in SSL mode, consult the publicly
available reference material.
To configure Content Transformation Services Server to run in SSL mode:
1.
Jetty’s status can be verified as follows:
a.
Start the Content Transformation Services Server.
b. Run the following query against the repository to get the Jetty running url:
Select websrv_url, hostname from cts_instance_info
56
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
c.
2.
Try the attribute value of websrv_url from a browser to see if it is running.
Configure Jetty to run in SSL mode. Refer the Eclipse website for detailed information.
a.
The Jetty config files (jetty-6.1.7.jar and jetty-util-6.1.7.jar) can be found on the Content
Transformation Services server under <CTS_HOME>/jetty/lib.
b. To verify the new SSL url, run the following url from the Content Transformation Services
server browser: https://<localhost>:<ssl_port>/cts/
c.
If the url is successful, update the cts_instance_info object in the repository to set the new
url to websrv_url attribute by running the following query:
Update cts_instance_info object set websrv_url=<new_ssl_url> where
hostname=<ctsserver_hostname_here>
d. Restart the Content Transformation Services server.
e.
Restart Content Transformation Services WebServices.
Using a profile description bigger than 192 bytes
The profile description length for new or edited profiles is up to 192 bytes. Note that Russian
characters can be either 2 or 3 bytes. To use a description that exceeds 192 characters, perform the
following procedure:
1.
Run the following DQL queries against the repository:
EXECUTE ALLOW_BASE_TYPE_CHANGES WITH ALLOW_CHANGE_FLAG=1
2.
Alter type dm_sysobject modify subject char(300):
EXECUTE ALLOW_BASE_TYPE_CHANGES WITH ALLOW_CHANGE_FLAG=0
3.
For a second successive run we need to change it to (301):
EXECUTE ALLOW_BASE_TYPE_CHANGES WITH ALLOW_CHANGE_FLAG=1
4.
Alter type dm_sysobject modify subject char(301). ( The reason for providing the size as 301 is,
the size specified for the subject attribute should be greater than the previous value, else server
throws an error)
EXECUTE ALLOW_BASE_TYPE_CHANGES WITH ALLOW_CHANGE_FLAG=0
Caution: Use caution when running DQLs against the repository as any input errors may
cause damage.
Automating thumbnail or proxy creation for custom
formats
To automate thumbnail or proxy creation for custom formats derived from an existing
rich_media_enabled supported Content Transformation Services dm_format:
1.
Set the richmedia_enabled flag to "1” for the custom format by running the following DQL:
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
57
Configuration and Administration Tasks and Tips
update dm_format object set richmedia_enabled = 1 where name=’custom_format_name’
2.
If the dm_format name and dos_extension are different for a custom format, the
FormatMapperService.xml file (under \CTS\config folder) should be updated as follows:
<FormatMapper CTSFormat="dos_extension" DocumentumFormat="dm_format_name"/>
3.
Check out the following system profiles from the repository:
• register_legacy (provided that LEGACY is turned on as forClients in the
CTSProfileService.xml)
• register_xcp (provided that xCP is turned on as forClients in the CTSProfileService.xml)
• thumbnail (if it is an image format)
• autoGenProxy (if it is an image format)
• pdf_processing, thumbnail_pdfstoryboard , autoGenProxy_pdfstoryboard, and
storyboard_pdfstoryboard (if the custom format is a flavor of PDF format)
• powerpoint_registration (if the custom format is a flavor of PowerPoint format)
4.
Add the custom format entry to the appropriate profiles.
5.
Check in the profiles.
6.
Restart Content Transformation Services.
Performing bulk transformation requests for documents
Sometimes, it is useful to submit transformation requests in bulk. Such scenarios can occur when
you have legacy documents that were ingested prior to deployment of a Content Transformation
Services. Also, you may want to resubmit a number of documents for a specific job because Content
Transformation Services failed to process them initially and the job requests were removed.
Content Transformation Services provides a tool that can request transformation requests
for a group of documents. This tool is deployed under %CTS%\docbases\<your_
repository>\CTSServerScript\.
Use \config\script.xml to configure the process, then use \bin\script.bat to run it. By default, the
tool will use the script.xml from the location mentioned above but you can also modify the script
batch file to use a different configuration file.
The EMC Documentum Content Transformation Services Transformation Suite Development Guide provides
details on how to use the batch script to submit bulk transformations.
Improving the performance of Content Transformation
Services
Note: The best practices and test results are derived or obtained after testing the product in the EMC
testing environment. Every effort is made to simulate common customer usage scenarios during
performance testing, but actual performance results will vary due to differences in hardware and
software configurations, data, and other variables.
58
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
The following suggestions may be implemented to achieve a better throughput with Content
Transformation Services when used in an asynchronous transformation scenario. Asynchronous refers
to a scenario where a client submits a batch of transformation requests to the Content Server, and the
Content Transformation Services servers subsequently fetches tasks from the Content Server queue
asynchronously, to invoke the transformation process and import the renditions into the repository.
• Content Transformation Services delivers a better performance for transformation of documents
when compared to the transformations in previous Content Transformation Services releases,
such as Media Transformation Services, Advanced Document Transformation Services, and
Audio/Video Transformation Services.
• Except for PDF to PDFA transformations which involve GhostScript processing, Content
Transformation Services stands to gain over Advanced Document Transformation Services the
most in terms of performance.
• Better throughput (requests/minute) can be achieved with multi-threaded Content Transformation
Services configuration. The configured number of working threads supplied with Content
Transformation Services is enough to derive a throughput improvement compared to a
single-threaded configuration.
• For a given configuration of CPU and memory, an increase in number of threads may not increase
throughput linearly. It will flatten out at some point where resource utilization will be a bottleneck.
• To achieve more throughputs, more CPU cores can be added to a Content Transformation Services
server.
Figure 8. Throughput
• To achieve more throughputs with large scale transformations and high availability environments,
more Content Transformation Services servers can be added.
• Better performance and throughput can be achieved when Content Transformation Services is
deployed on dedicated servers, as with increased throughput comes increased resource utilization.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
59
Configuration and Administration Tasks and Tips
Figure 9. Content Transformation Services resource usage
Content Transformation Services clean up job
Content Transformation Services provides a generic clean up job utility for cleaning up orphaned or
invalid objects from the repository, provided that the deletion can be performed through a specific,
configured DQL.
The following unused transformation related requests or response objects are examples of orphaned
objects:
• During a transformation request using Content Transformation Services, a transformation request
object of the dm_transform_request type is created in the repository. This object may remain in
the repository if the clearOnExit flag on the CTSRequest object is not set to TRUE.
• Similarly, a dm_cts_response object is created in the repository during every transformation
process, if the reporting configuration is enabled in the repository. These objects can get
accumulated in the repository over time causing a disk space issue.
A Server Java method is implemented for the Content Transformation Services CleanUp Job. The
Transformation DAR is responsible for deploying this server job and performing additional docbase
object updates. The job is made inactive Out-of-the-Box. If required, the job can be enabled through
Documentum Administrator.
The execution of this method is made further configurable using an XML file. This job can be used to
clean up objects, provided that the objects can be identified through a DQL. Out-of-the-Box, this job is
used to delete orphaned objects from transformation or response objects.
60
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Job configuration options
Jobs are made further configurable using ctsJobs.xml, which is deployed in the repository as
part of DAR installation process. This configuration option is provided for the easy enhancement
of this feature. The configuration file, ctsJobs.xml, is deployed into the repository folder
/System/Applications/Transformation as part of the DAR installation process.
One or more <Job> tags can be associated with any job to initiate more than one deletion
process. For example, the same default cts_cleanup method or job can be used for deleting both
dm_transform_request and dm_cts_response objects, where these objects are detected through
different DQLs. Out-of-the-Box, the following DQLS are configured in the ctsJobs.xml for deleting
request or response objects.
• Cleanup DQL entry for deleting transformation request objects:
<Job name="cts_cleanup" description="delete the orphaned transformation
related request objects">
<ServerProperty Key="delegate_class" Description="delagate class"
Value="com.emc.documentum.ct.job.services.DefaultCleanUpService" />
<ServerProperty Key="dql" Value="select r_object_id from dm_transform_request
where DATEDIFF(day, "r_creation_date", DATE(TODAY))>10" Description="DQL
to identify the object to be deleted" />
</Job >
• Cleanup DQL entry for deleting transformation response objects:
<Job name="cts_cleanup" description="delete the invalid transformation
related response objects">
<ServerProperty Key="delegate_class" Description="delagate class"
Value="com.emc.documentum.cts.job.services.DefaultCleanUpService" />
<ServerProperty Key="dql" Value="select r_object_id from dm_cts_response
where DATEDIFF(day, "r_creation_date", DATE(TODAY))>10" Description="DQL
to identify the object to be deleted" />
</Job >
Content Transformation Services job Log4j configuration
The log file for this job can be made available on the Content Server by updating the following
log4j.properties file.
$Documentum\jboss7.1.1\server\DctmServer_MethodServer\deployments\
ServerApps.ear\APP-INF\classes\log4j.properties
Add the following entry in the log4j.properties file to obtain the Content Transformation
Services job related log information:
log4j.category.com.emc.documentum.cts.job=DEBUG, CTSJobsAppender
log4j.appender.CTSJobsAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.CTSJobsAppender.File=$DOCUMENTUM/jboss7.1.1/server/
DctmServer_MethodServer/logs/cts_jobs.log
log4j.appender.CTSJobsAppender.Append=true
log4j.appender.CTSJobsAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.CTSJobsAppender.layout.ConversionPattern=%d{HH\:mm\:ss,SSS}
%5p [%10t] %c{1} - %5x %m%n
log4j.appender.CTSJobsAppender.DatePattern=’.’yyyy-ww-dd
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
61
Configuration and Administration Tasks and Tips
Changing the hostname of the Content Transformation
Services server machine
To change the name of the host machine when a Content Transformation Services product is installed
and configured against a repository, perform the following configuration changes:
1.
Stop all Content Transformation Services services.
2.
Update the hostname in the following fields of the Windows Registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\CTS
• agentURL
• wsurl
HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\CTS\AdminAgent
• Hostname
3.
Rename the key to reflect the new hostname in the Windows Registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\CTS\MTS\Docbases[docbase
Name][hostname].
4.
Update the Content Transformation Services configuration file located at:
C:\Documentum\CTS\config\CTSServerService.xml.
• Take a backup of the CTSServerService.xml file.
• Search and replace references to the old hostname with the new hostname in the
CTSServerService.xml file.
5.
Update the cts_instance_info object with the following DQL command:
UPDATE cts_instance_info OBJECT SET hostname = ’[newName]’, SET agent_url =
’http://[newName]:9095/CTSAgent/CTSAgent’, SET websrv_url = ’http://[newName]:
9096/cts/’ WHERE hostname = ’[oldname]’
6.
Change the hostname and restart the Content Transformation Services host.
Resolving issues with email content containing double
byte characters
When you import emails with double byte characters in the subject, content, and attachment names, it
is seen that in the subject and attachment names, the double byte characters are corrupted and appear
as "???”. For the renditions to be created without character corruption, it is recommended that you
install Arial Unicode MS font on the Content Transformation Services server machine.
PDF compliance not working
For PDF/A and PDF/X compliance, the latest version of Ghostscript is required. The EMC
Documentum Environment and System Requirements Guide document contains information about the
supported version.
62
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
To enable PDF/A compliance, install Ghostscript and edit <GSlatest version>/lib/PDFA_
def.ps, and update the following line:
Change:
/ICCProfile (ISO Coated sb.icc) % Customize.
To:
/ICCProfile (C:/Documentum/CTS/lib/USWebCoatedSWOP.icc) % Customize.
Note: USWebCoatedSWOP.icc is a sample CMYK icc profile. You can choose the required CMYK icc
profile. However, ensure that the icc profile file path does not have any empty spaces.
To enable PDF/X compliance, install the latest version of Ghostscript and edit <GSlatest
version>/lib/PDFX_def.ps, and update the following line:
Change:
/ICCProfile (ISO Coated sb.icc) def % Customize or remove.
To:
%/ICCProfile (ISO Coated sb.icc) def % Customize or remove.
Configuring WebServices in a single sign-on
environment
If you are using a single sign-on (SSO) environment that is enabled with Kerberos authentication,
then you must set up the runtime property in the WebServices client code. Add the following code in
the WebServices client code:
IServiceContext context = contextFactory.newContext();
theContext.SetRuntimeProperty("TsRepo", "your_Repository_name_here");
theContext.SetRuntimeProperty("TsRepo_Username", "your_Username_here");
Configuration tasks specific to Advanced
Document Transformation Services
This section contains procedures for the following document-based configuration tasks that are
performed with Advanced Document Transformation Services.
• Creating thumbnails and storyboards for MSG assets, page 64
• Configuring the Doc10 plug-in, page 64
• Controlling the size of PDF renditions, page 65
• PDF customization, page 65
• Generating a specific number of storyboard renditions, page 76
• Adding a signature page, page 77
• Creating PDF renditions and enabling thumbnail and storyboard renditions on import, page 78
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
63
Configuration and Administration Tasks and Tips
• Customizing printing and rendition output, page 81
• Configuring change tracking, page 84
• Transferring document attributes, page 84
Creating thumbnails and storyboards for MSG assets
To create thumbnails, preview, and storyboards for the MSG format on import or registering, proceed
as follows:
The register_xcp.xml will contain the following InnerProfile OOTB for creating thumbnails and
storyboards for MSG assets:
<InnerProfile path="/System/Media Server/System Profiles/msg_
registration_xcp" waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="true" InnerProfileToken=
"overwrite_rendition" Literal="true"/>
<InnerTokenMapping InnerProfileToken="doc_token_targetFormat"
Literal="true" LocalProfileToken="pdf"/>
</InnerProfile>
Add the InnerProfile content above to the register_legacy.xml, if the value of the <ForClients> tag in
the CTSProfileService.xml is LEGACY.
Configuring the Doc10 plug-in
Documentum 7.1 includes a Third Party slides library feature for faster and multi-threaded
transformation of Microsoft PowerPoint files to PDFs. This feature addresses the performance
issues associated with the Microsoft Office single-threaded bottle neck in the Advanced Document
Transformation Services 6.7.X product. However, there may be issues with fidelity in some instances.
These fidelity issues have been handled by introducing the Doc10 plug-in, which is similar to the
Microsoft PowerPoint-based plug-in.
The following entries must be added to the CTSPluginService.xml to enable this plug-in for
Advanced Document Transformation Services:
<CTSPlugin DELEGATE_CLASS="com.documentum.cts.plugin.doc10.Doc10Plugin"
CONFIGFILE="C:\DOCUME~1\CTS\config\doc10\doc10.xml"/>
All Microsoft PowerPoint to PDF file transformations go through the document_to_custom_pdf.
xml and document_to _pdf.xml profiles. Hence, an option is provided to convert Microsoft
PowerPoint formats to PDF using the Microsoft Office application by adding the DOC10 plug-in as
the primary plug-in and DOC6 as the secondary plug-in. You can choose to enable the Doc10 plug-in
by making the following change to the profiles.
<CommandFilePath mptype="DOC10">
/System/Media Server/Command Line Files/document_to_pdf.xml
</CommandFilePath>
<CommandFilePath mptype="DOC6">
/System/Media Server/Command Line Files/document_to_pdf.xml
</CommandFilePath>
On uncommenting, the Doc10 plug-in becomes the chosen plug-in to carry out the Microsoft
PowerPoint to PDF conversion. This also gives the advantage of failover in case there is an issue
64
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
in processing the file by the Doc10 plug-in. In such cases, the Doc6 plug-in takes over the PDF
conversion.
Note: To use the Doc 10 plug-in, install Microsoft PowerPoint 2007 SP3 (32-bit) on the Advanced
Document Transformation Services server that is installed on Windows Server 2008 R2 SP1 (64-bit)
operating system.
The following log4j entries should be added to <CTS_HOME\config\log4j.properties to enable
Doc10 plug-in logs:
log4j.category.com.documentum.cts.plugin.doc10=DEBUG,Doc10Plugin
log4j.appender.Doc10Appender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.Doc10Plugin.File=<CTS_HOME>\\logs\\Doc10_log.txt
log4j.appender.Doc10Plugin.Append=true
log4j.appender.Doc10Plugin.layout=org.apache.log4j.PatternLayout
log4j.appender.Doc10Plugin.layout.ConversionPattern=%d{HH\:mm\:ss,SSS}
ndi %10r %5p [%10t] %-20c{1} - %5x %m%n
log4j.appender.Doc10Plugin.DatePattern=’.’yyyy-ww-dd
Controlling the size of PDF renditions
Conversion of Microsoft Office documents to PDF results in large-sized documents.
To create small-sized PDF renditions from Microsoft Word documents, set the following options in
the document_to_pdf.xml command line file:
<PDFSETTINGS TEXTCOMPRESSION="Flate" PRESERVEFORMFIELDS="false">
<FONTEMBEDDING ENABLED="Yes" PARTIALFONTS="Yes" STANDARDFONTS="No"/>
</PDFSETTINGS>
Note: Content Transformation Services must be restarted for the command line file changes to take
effect.
PDF customization
This section provides information about the DOC6 plug-in customizations, which are exposed to
the users through command line files and system profiles. These customizations are specific only
to the transformation of Microsoft Word documents to PDF format. The customization options are
included in the document_to_pdf command-line profile and can be configured by specifying profile
parameters (InnerTokenMapping) through the following system profiles:
• document_registration
• legacy_to_pdf.xml
• document_registration_xcp
The following sections provide information about XML elements that are found in the
document_to_pdf command line profile.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
65
Configuration and Administration Tasks and Tips
TRANSFORMATION
This is the root element of the job ticket and contains the settings provided as inputs to the DOC6
plug-in to process the documents.
Element Name
Acceptable Values
Description
TRANSFORMATION
This element has no attributes
and does not accept values.
Root element
SETTINGS
This is the child of the TRANSFORMATION element and contains all the customization settings
available for the Doc6 plug-in.
Element Name
Acceptable Values
Description
SETTINGS
This element has no attributes
and does not accept values.
Denotes the customization
settings available for the Doc6
Plug-in.
MSWORDSETTINGS
This is the child of the SETTINGS element and contains customizations applicable to source
documents that are in the Microsoft Word format.
Element Name
Acceptable Values
Description
MSWORDSETTINGS
This element has no attributes
and does not accept values.
Denotes the customization
settings applicable to Microsoft
Word source documents.
TOC
This is the child of the MSWORDSETTINGS element and allows users to:
• Generate the Table of Contents, Table of Tables, and Table of Figures
• Control the look and feel of the Table of Contents
66
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ENABLED
Yes
Enables or
disables the
creation of
the Table of
Contents.
No
Enables or
disables the
creation of
the Table of
Contents.
Yes
No (Default
value)
SHOWTOC
Yes
No (Default
value)
CONTENTBOOKMARKS
Yes (Default
value)
No
DOCUMENTBOOKMARKS
Yes (Default
value)
No
doc_token_toc_
enabled
Enables or
disables the
creation of a
bookmark on top
of the Table of
Contents, which
reads "Table of
Contents".
No
Enables or
disables the
creation of a
bookmark at
the start of
the document
content.
No
MARGINBOTTOM
Number
(Default value =
0.5)
Specifies the
bottom margin
of the Table of
Contents page.
No
MARGINLEFT
Number
(Default value =
0.5)
Specifies the
left margin of
the Table of
Contents page.
No
MARGINRIGHT
Number
(Default value =
0.5)
Specifies the
right margin
of the Table of
Contents page.
No
MARGINTOP
Number
(Default value =
0.5)
Specifies the
top margin of
the Table of
Contents page.
No
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
67
Configuration and Administration Tasks and Tips
MAXLEVEL
ORIENTATION
1, 2, 3 (Default
value), 4, 5, 6, 7,
8, 9
Specifies the
maximum level
of headings that
the Table of
Contents must
include.
Portrait (Default
value)
Specifies the
page orientation
of the Table of
Contents page.
Landscape
SHOWPAGENUMBERS
Yes (Default
value)
No
TABLEADERSTYLE
DottedLine
(Default value)
DashedLine
Underline
None
TOTANDTOFTABLEADERSTYLE
DottedLine
(Default value)
DashedLine
Underline
None
SHOWTOT
Yes
No (Default
value)
SHOWTOF
Yes
No (Default
value)
Yes
doc_token_toc_
maxLevel
Yes
doc_token_toc_
orientation
Specifies if
the Table of
Contents should
display the page
numbers for
each item.
No
Specifies the
tab leader
style between
the Table of
Contents items
and their page
numbers.
No
Specifies the
tab leader style
between the
items of the
Table of Tables
and Table of
Figures and their
page numbers.
No
Enables or
disables the
creation of the
Table of Tables.
Yes
Enables or
disables the
creation of the
Table of Figures.
doc_token_tot_
enabled
Yes
doc_token_tof_
enabled
TOCNAME
Contents
(Default value)
Caption for
the Table of
Contents.
No
TOTNAME
Tables (Default
value)
Caption for the
Table of Tables.
No
TOFNAME
Figures (Default
value)
Caption for the
Table of Figures.
No
68
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
HEADER
This is the child of the MSWORDSETTINGS element and allows users to add headers to the
generated PDF.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ENABLED
Yes
Yes
No (Default
value)
Enables or
disables the
creation of
headers.
Helvetica
(Default value)
Name of the font
for the header.
Yes
Numeric
(Default value =
- 10
Specifies the font
size.
Numeric
Specifies the font
color.
Yes
Specifies the
layer where the
header is placed.
Yes
Specifies
text that is
left-justified.
Yes
FONTNAME
FONTSIZE
FONTCOLOR
LAYER
Foreground
(Default value)
Background
TEXTLEFT
TEXTCENTER
TEXTRIGHT
PAGES
Text
Text
Text
All (Default
value), First,
Last, Even, Odd
Specifies the
center text.
Specifies
text that is
right-justified
Specifies the
pages to which
headers are
applied.
doc_token_headers
doc_token_h_
fontName
Yes
doc_token_h_
fontSize
doc_token_h_color
doc_token_h_layer
doc_token_h_
textLeft
Yes
doc_token_h_
textCenter
Yes
doc_token_h_
textRight
Yes
doc_token_h_
pages
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
69
Configuration and Administration Tasks and Tips
FOOTER
This is the child of the MSWORDSETTINGS element and allows users to add footers to the generated
PDF.
Element Name
Acceptable Values
Description
Contains Profile
Parameter
ENABLED
Yes
Yes
No (Default value)
Enables or disables
the creation of
footers.
Helvetica (Default
value)
Name of the font for
the footer.
Yes
Numeric (Default
value = - 10
Specifies the font
size.
Yes
Numeric
Specifies the font
color.
Yes
Specifies the layer
where the footer is
placed.
Yes
Specifies text that is
left-justified.
Yes
Specifies the center
text.
Yes
FONTNAME
FONTSIZE
FONTCOLOR
LAYER
Foreground
(Default value)
Background
TEXTLEFT
Text
TEXTCENTER
TEXTRIGHT
PAGES
Text
Text
All (Default value),
First, Last, Even,
Odd
doc_token_footers
doc_token_f_
fontName
doc_token_f_fontSize
doc_token_f_color
doc_token_f_layer
doc_token_f_textLeft
doc_token_f_
textCenter
Specifies text that is
right-justified
Yes
Specifies the pages
to which footers are
applied.
Yes
doc_token_f_textRight
doc_token_f_pages
MARKUP
This is the child of the MSWORDSETTINGS element and controls the generation of markup and
comments in the PDF.
70
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Element Name
Acceptable Values
Description
Contains Profile
Parameter
PRINTTYPE
DocumentWithMarkup
(Default)
Enables or disables
the generation of
word markup.
Yes
Enables or disables
the generation of
word comments.
Yes
DocumentContent
PDFNOTES
Yes
No (Default value)
Doc_token_PrintType
doc_token_NoteIcons
HYPERLINKS
This is the child of the MSWORDSETTINGS element and controls the generation of hyperlinks
in the PDF.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ENABLED
Yes
Enables or
disables the
generation
of PDF Link
Actions.
Yes
No (Default
value)
doc_token_
enableHyperlinks
PDFSETTINGS
This is the child of the MSWORDSETTINGS element and provides customization options that must
be specified for the output PDF. It denotes the customization settings applicable to the PDF output
documents.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
TEXTCOMPRESSION
Flate
Enables the
compression of
PDF content.
No
Specifies if you
need to preserve
the Microsoft
Word form fields
as is in the PDF
or convert them
to text.
No
None (Default
value)
PRESERVEFORMFIELDS
False
True (Default
value)
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
71
Configuration and Administration Tasks and Tips
PAGE
This is the child of the PDFSETTINGS element and controls the look of the document pages.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ORIENTATION
Portrait (Default
value)
Specifies the
page orientation.
Yes
Landscape
doc_token_page_
orientation
MARGINLEFT
Numeric
(Default value =
0.5)
Specifies the left
margin for the
document.
No
MARGINRIGHT
Numeric
(Default value =
0.5)
Specifies the
right margin for
the document.
No
MARGINTOP
Numeric
(Default value =
0.5)
Specifies the top
margin for the
document.
No
MARGINBOTTOM
Numeric
(Default value =
0.5)
Specifies
the bottom
margin for the
document.
No
PAGESIZE
A4 (Default
value)
Specifies the
page size.
Yes
Letter
doc_token_page_
size
PAGEINDEX
0 (Default value)
Specifies the
start page
number in the
Microsoft Word
document from
which the PDF
must be saved.
No
PAGECOUNT
-1 (Default
value)
The number of
pages to save. -1
denotes that all
pages must be
saved.
No
BOOKMARKS
This is the child of the PDFSETTINGS element and controls the generation of bookmarks in the PDF.
72
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ENABLED
Yes
Enables or
disables the
generation of
bookmarks
based on the
heading styles.
Yes
No (Default
value)
CREATEDOCUMENTBOOKMARKS
Yes
No (Default
value)
MAXLEVEL
1, 2, 3 (Default
value), 4, 5, 6, 7,
8, 9
Enables or
disables the
generation of
bookmarks
based on the
heading styles
available in the
document.
Specifies the
maximum level
of heading styles
to be included in
the bookmarks
generated.
doc_token_
enableBookMarks
Yes
doc_token_
enableBookMarks
Yes
doc_token_
bookmark_
MaxLevel
FONTEMBEDDING
This is the child of the PDFSETTINGS element and controls the embedding of fonts into documents.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ENABLED
Yes (Default
value)
Enables or
disables the
embedding of
fonts in the PDF.
No
Controls how
fonts are
embedded in the
PDF documents.
If yes, subsets
of fonts are
embedded into
documents.
No
Specifies
whether
Windows
standard
No
No
PARTIALFONTS
Yes (Default
value)
No
STANDARDFONTS
Yes (Default
value)
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
73
Configuration and Administration Tasks and Tips
No
fonts must be
embedded or
not.
OPTIMIZE
This is the child of the PDFSETTINGS element and allows the creation of a web optimized PDF
for a quick web view.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ENABLED
Yes
Specifies if the
PDF has to be
web-optimized.
Yes
No (Default
value)
doc_token_
optimize
PDFVERSION
This is the child of the PDFSETTINGS element and allows you to specify the version of the PDF.
Element Name
Acceptable
Values
Description
VERSION
PDFVERSION14, Specifies the
PDFVERSION15 PDF document
(Default value), version.
PDFVERSION16,
PDFVERSION17
Contains Profile
Parameter
Yes
doc_token_
pdfVersion
JPEGIMAGECOMPRESS
This is the child of the PDFSETTINGS element and allows the compression of JPEG images embedded
in the document to reduce the final PDF file size.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
QUALITY
0 to 100
Specifies the
quality of the
JPEG image.
Yes
100 (Default
value)
74
doc_token_
jpegquality
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
SECURITY
This is the child of the PDFSETTINGS element and allows users to add PDF security to the PDF
files created.
Element Name
Acceptable
Values
Description
Contains Profile
Parameter
ENABLED
Yes
Enables or
disables PDF
security.
Yes
No (Default
value)
ENCRYPTIONMODE
40-bit (Default
value)
Specifies the
encryption level.
128-bit
NOCHANGINGANNOTATION
Disabled
(Default value)
Enabled
NOCHANGINGDOCUMENT
Disabled
(Default value)
Enabled
NOCONTENTACCESSIBILITY
Disabled
(Default value)
Enabled
NODOCUMENTASSEMBLY
Disabled
(Default value)
Enabled
doc_token_
enableSecurity
Yes
doc_token_
encryptionMode
Controls the
addition or
modification
of annotations.
When using
the 40-bit
encryption,
this option also
allows you to fill
form fields.
No
Controls the
modification of
the document
contents.
Yes
Controls the
text extraction
and graphics
to support
accessibility.
doc_token_
changesAllowed
Yes
doc_token_
enableAccess
Yes
Controls the
assembly of
doc_token_
the document
docAssembly
(for example,
the insertion
or deletion of
pages). When
using the 40-bit
encryption, this
option is ignored
and document
assembly is
allowed when
NOCHANGING-
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
75
Configuration and Administration Tasks and Tips
DOCUMENT is
set to "Disabled”.
NOFORMFIELDFILLIN
Disabled
(Default value)
Enabled
NOPRINTING
Disabled
(Default value)
Enabled
NOSELECTIONCOPYINGCONTENT
Disabled
(Default value)
Enabled
OPENPASSWORD
SECURITYPASSWORD
Text
Text
Yes
Controls the
filling in of
doc_token_
forms. When
formFieldFilling
using the 40-bit
encryption,
this option is
ignored and
filling in form is
allowed when
NOCHANGINGDOCUMENT is
set to "Disabled”.
Controls the
printing of the
document.
Controls the
copying of
content.
Specifies the
password for
opening the
document.
Specifies the
password for
modifying the
security settings.
Yes
doc_token_
printing
Yes
doc_token_
allowCopy
Yes
doc_token_
secOpass
Yes
doc_token_
secCpass
Generating a specific number of storyboard renditions
On importing a document, Content Transformation Services can be modified to generate a specific
number of storyboard renditions instead of generating all renditions.
1.
Stop Content Transformation Services. Update the CTSProfileService.xml to set the
forClient field to "LEGACY" instead of "XCP". Start Content Transformation Services.
2.
If you require only 10 pages of storyboard, then add the following InnerTokenMapping to
both JPEG_LRES and JPEG_STORY storyboard_pdfstoryboard inner profiles (PDF_processing
profiles) and check-in the profile.
<InnerTokenMapping LocalProfileToken="10" InnerProfileToken="doc_token_maxPages"
Literal="true"/>
The register_legacy.xml must be updated with following profile sequence, so this feature works
for Document, PDF, MSG, and TIFF formats.
76
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
!-- For PDF formats-->
<ProfileSequence>
<InnerProfile path="/System/Media Server/System Profiles/pdf_processing"
waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="true" InnerProfileToken="overwrite_rendition"
Literal="true"/>
</InnerProfile>
<!-- For TIFF formats -->
<InnerProfile path="/System/Media Server/System Profiles/tiff_registration"
waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="true" InnerProfileToken="overwrite_rendition"
Literal="true"/>
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken="doc_token_targetFormat"
Literal="true"/>
</InnerProfile>
<!-- For MSG formats -->
<InnerProfile path="/System/Media Server/System Profiles/msg_registration"
waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="true" InnerProfileToken="overwrite_rendition"
Literal="true"/>
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken="doc_token_targetFormat"
Literal="true"/>
</InnerProfile>
<!-- For all types of document formats -->
<InnerProfile path="/System/Media Server/System Profiles/document_registration"
waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="true" InnerProfileToken="overwrite_rendition"
Literal="true"/>
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken="doc_token_targetFormat"
Literal="true"/>
</InnerProfile>
</ProfileSequence>
Adding a signature page
addSignature_adts is a user profile, which allows users to add a signature page to Microsoft Office
or PDF documents. This profile converts the provided document to PDF and adds a pre-defined
signature page to the output. This is specially useful if a company wants to append its logo to specific
documents or other legal regulations, usage limitations, company info, disclaimers, and so on.
To specify a suitable signature document, perform the following steps after installation:
1.
Login as an administrator.
2.
Using Documentum Administrator, navigate to the following location: /System/Applications/
Signature.
3.
Check out the blank signature_template.pdf.
4.
Replace the blank signature_template.pdf with your custom PDF signature file of the
same name.
5.
Set the world permission to "READ”.
6.
Check in the custom PDF.
You can append this custom PDF to documents that need to be generated.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
77
Configuration and Administration Tasks and Tips
Creating PDF renditions and enabling thumbnail and
storyboard renditions on import
To automatically create PDF renditions when importing content, first enable the particular format for
rich media, and then edit the register_xxxx.xml file. Refer to Understanding the Register profile,
page 43 to make the relevant changes to the register_xxxx.xml.
Content Transformation Services can also create thumbnail and storyboard renditions when
importing content.
Rich media enabling formats
This procedure is essential for proper processing of imported content. If formats are not enabled for
rich media, the Content Server will not pass them to the Content Transformation Services queue.
To enable formats for rich media:
1.
Run the following DQL statement:
update dm_format object set richmedia_enabled = 1 where name
in (’<format name>’)
For example, to create thumbnails and storyboards for Microsoft Excel and Word formats, run the
following DQL statement:
update dm_format object set richmedia_enabled = 1 where
name in (’excel8book’,’msw8’)
This table lists some examples of the format mapping used in Documentum systems. Use these
format names in DQL.
Table 5. Documentum format mappings for Content Transformation Services
Description
Documentum name
(includes Office 2003)
Documentum name
(Office 2007 only)
Documentum name
(Office 2010)
HTML
html
Microsoft Excel (XLS,
XLSX)
excel8book
excel12book
excel14book
Microsoft Excel (XLT)
excel8template
excel12template
excel14template
Microsoft PowerPoint
(POT)
ppt8_template
ppt12template
ppt14template
Microsoft PowerPoint
(PPT)
ppt8
ppt12
ppt14
Microsoft Word (DOC,
DOCX)
msw8
msw12
msw14
Microsoft Word (DOT)
msw8template
msw12template
msw14template
PDF
pdf
78
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Creating a PDF rendition on import
After enabling the formats for rich media, modify the Register Profile to activate the PDF rendition
on import.
To activate the PDF rendition on import:
1.
In the repository, browse to System/Media Server/System Profiles and check out the Register
Profile.
2.
Open the Register Profile in an XML or text editor.
3.
Change the following tag:
<Format source="<sample>" target="<sample>"/>
to
<Format source="<Add source format here>" target="<Add target format here>"/>
For example, to enable PDF renditions for Microsoft Word documents, your tag would look like
the following:
<Format source="msw8" target="msw8"/>
Note: Source and target formats are the same in the register profile. This is because processing
does not start from this profile; the source is passed to the next profile.
4.
Add the following tags to the <ProfileSequence> section of the relevant register_xxxx.xml, if
it is not already included:
<InnerProfile path="/System/Media Server/System Profiles/
document_to_pdf" waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken=
"doc_token_targetFormat" Literal="true"/>
<InnerTokenMapping LocalProfileToken="PDFVersion15"
InnerProfileToken="doc_token_pdfVersion" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Automatic" InnerProfileToken
="doc_token_usePrinterMetrics" Literal="true"/>
<InnerTokenMapping LocalProfileToken="600" InnerProfileToken=
"doc_token_resolution" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Yes" InnerProfileToken=
"doc_token_optimize" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Yes" InnerProfileToken=
"doc_token_enableBookMarks" Literal="true"/>
<InnerTokenMapping LocalProfileToken="DocumentContent"
InnerProfileToken="doc_token_printType" Literal="true"/>
<InnerTokenMapping LocalProfileToken="false" InnerProfileToken
="overwrite_rendition" Literal="true"/>
<InnerTokenMapping LocalProfileToken="legacy" InnerProfileToken=
"transformation_type" Literal="true"/>
<!security settings>
<InnerTokenMapping LocalProfileToken="No" InnerProfileToken=
"doc_token_enableSecurity" Literal="true"/>
<InnerTokenMapping LocalProfileToken="40bit" InnerProfileToken=
"doc_token_encryptionMode" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Disabled" InnerProfileToken=
"doc_token_changesAllowed" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Disabled" InnerProfileToken=
"doc_token_enableAccess" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Disabled" InnerProfileToken=
"doc_token_docAssembly" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Disabled" InnerProfileToken=
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
79
Configuration and Administration Tasks and Tips
"doc_token_formFieldFilling" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Disabled" InnerProfileToken=
"doc_token_printing" Literal="true"/>
<InnerTokenMapping LocalProfileToken="Disabled" InnerProfileToken=
"doc_token_allowCopy" Literal="true"/>
<InnerTokenMapping LocalProfileToken=" " InnerProfileToken=
"doc_token_secOpass" Literal="true"/>
<InnerTokenMapping LocalProfileToken=" " InnerProfileToken=
"doc_token_secCpass" Literal="true"/>
</InnerProfile>
5.
Save the file.
6.
Check the file into the repository.
7.
Restart Content Transformation Services.
Registering formats to enable thumbnails and storyboards
After rich-media enabling the formats, modify the system profiles, register.xml and
register_legacy.xml to activate the thumbnail and storyboard rendition creation on import of
MS Office and image formats.
Note: This procedure is applicable only if register_legacy.xml is targeted in register.xml profile.
To register the formats:
1.
In the repository, navigate to System/Media Server/System Profiles and check out the following
files: register.xml and register_legacy.xml.
2.
Open register.xml and register_legacy.xml in an XML or text editor.
3.
Change or add the following tag in both the register.xml and register_legacy.xml files:
<Format source="<sample>" target="<sample>"/>
to
<Format source="<Add source format here>" target="<Add target format
here>"/>
For example, to enable thumbnails and storyboards for Microsoft Word documents, your tag
would look like the following:
<Format source="msw8" target="msw8"/>
To enable thumbnails and storyboards for image formats, your tag will look like the following:
<Format source="gif" target="gif"/>
Note: Source and target formats are the same in the register profile. This is because processing
does not start from this profile; the source is passed to the next profile.
4.
Navigate to System/Media Server/System Profiles and check out the document_registration.
xml file.
5.
Add the following image formats, if you require thumbnails for images: jpeg, gif, png, tiff,
photoshop6, photoshop7, photoshop8, cr2, crw, wmf, and bmp.
For example:
<Format source="gif" target="pdf"/>
80
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
For Microsoft Office formats, ensure that the document_registration.xml file contains
tags similar to the following :
Format source="msw8" target="pdf"/>
6.
Add the following tags to the <ProfileSequence> section of the register_legacy.xml file:
<!--This extracts properties for office formats. Add if required-->
<InnerProfile path="/System/Media Server/System Profiles/
document_extract_props" waitOnCompletion="true" useTargetFormat=
"true">
</InnerProfile>
<!--This will generate thumbnail, proxy and storyboards for
all document & image formats-->
<InnerProfile path="/System/Media Server/System Profiles/
document_registration" waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken=
"doc_token_targetFormat" Literal="true"/>
</InnerProfile>
7.
Save the files.
8.
Check the files back into the repository.
9.
Restart Content Transformation Services.
Customizing printing and rendition output
Various printing and rendition processes can be configured in the legacy profiles. By default, these
processes are disabled. You can modify the profiles to:
• Save the PDF text (PDT) file
• Store PDF metadata
• Configure legacy transformations to replace previous renditions, instead of storing multiple
renditions
These configuration procedures are described in this section.
Saving PDF Text files
The PDF Text rendition of a document is the text file used specifically for term-hit highlighting. By
default, PDF Text files are not saved to the repository. To store the PDF Text rendition of a document
in the repository, modify the legacy_to_pdf profile.
To save PDF Text renditions in the repository:
1.
Log in to the Content Transformation Services configured repository as an administrator user.
2.
Navigate to System\Media Server\System Profiles\.
3.
Check out the legacy_to_pdf profile.
Note: If this file is not immediately visible, select Show All Objects and Versions from the
Show list box.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
81
Configuration and Administration Tasks and Tips
4.
Open the legacy_to_pdf file from the checkout folder on the local machine.
5.
Uncomment the following section:
<!-- uncomment the below section to enable the storing of pdf text files -->
<!-<InnerProfile path="/System/Media Server/System Profiles/
transformToText" waitOnCompletion="false" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="pdftext" InnerProfileToken=
"target_format" Literal="true"/>
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken=
"source_format" Literal="true"/>
<InnerTokenMapping LocalProfileToken="True" InnerProfileToken=
"doc_token_storePDTRendition" Literal="true"/>
<InnerTokenMapping LocalProfileToken="1" InnerProfileToken=
"target_page_modifier" Literal="true"/>
<InnerTokenMapping LocalProfileToken="false" InnerProfileToken=
"overwrite_rendition" Literal="true"/>
<InnerTokenMapping LocalProfileToken="legacy" InnerProfileToken=
"transformation_type" Literal="true"/>
</InnerProfile>
-->
6.
Save and close the file.
7.
Check in the modified profile to the repository.
PDF text renditions of documents are now stored in the repository.
Storing PDF metadata
The storing of PDF metadata is also configured in the legacy_to_pdf profile. By default, PDF
metadata is not stored.
To store PDF metadata in the repository:
1.
Log in to the Content Transformation Services configured repository as an administrator user.
2.
Navigate to System\Media Server\System Profiles\.
3.
Check out the legacy_to_pdf profile.
Note: If this file is not immediately visible, select Show All Objects and Versions from the
Show list box.
4.
Open the legacy_to_pdf file from the checkout folder on the local machine.
5.
Uncomment the following section:
<!-- uncomment the below section to enable the storing of pdf metadata-->
<!-<InnerProfile path="/System/Media Server/System Profiles/
embedMetadataToContent_adts" waitOnCompletion="false" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken=
"target_format" Literal="true"/>
<InnerTokenMapping LocalProfileToken="pdf" InnerProfileToken=
"source_format" Literal="true"/>
<InnerTokenMapping LocalProfileToken="True" InnerProfileToken=
"doc_token_embedMetadata" Literal="true"/>
<InnerTokenMapping LocalProfileToken="embed_metadata"
InnerProfileToken="target_page_modifier" Literal="true"/>
<InnerTokenMapping LocalProfileToken="false" InnerProfileToken=
82
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
"overwrite_rendition" Literal="true"/
<InnerTokenMapping LocalProfileToken="legacy" InnerProfileToken=
"transformation_type" Literal="true"/>
</InnerProfile>
-->
6.
Save and close the file.
7.
Check in the modified profile to the repository.
PDF metadata of documents is now stored in the repository.
Configuring for rendition replacement
By default, Content Transformation Services allows for multiple PDF and HTML renditions from the
same source file. In other words, each time a user transforms a file, an additional rendition is created
and stored. If you would prefer that subsequent renditions replace previous renditions of a source
document, this can be configured using the following procedure.
To overwrite existing renditions when transforming files:
1.
Log in to an applicable application (such as Digital Asset Manager) as an administrator user.
2.
Navigate to System\Media Server\System Profiles.
3.
Check out the following profiles:
• legacy_to_html
• legacy_to_pdf
Note: If these files are not immediately visible, select Show All Objects and Versions from the
Show list box.
4.
Open the legacy_to_html.xml file from the checkout folder on the local machine.
5.
Locate the following tag within the <InnerProfile> section:
<InnerTokenMapping LocalProfileToken="false"
InnerProfileToken="overwrite_rendition" Literal="true"/>
and change it to:
<InnerTokenMapping LocalProfileToken="true"
InnerProfileToken="overwrite_rendition" Literal="true"/>
6.
Save and close the file.
7.
Open the legacy_to_html.xml file from the checkout folder on the local machine.
8.
Repeat Step 5.
9.
Save and close the file.
10. Check in the two files.
Content Transformation Services will now store only one PDF or HTML rendition for each source file.
To replicate this behavior when the Reset Renditions option is applied, modify the register.xml
file in the same way.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
83
Configuration and Administration Tasks and Tips
Configuring change tracking
By default, Content Transformation Services does not pass change tracking to output PDFs. However,
change tracking can be enabled by configuring the legacy_to_pdf profile.
To enable change tracking:
1.
In the repository, browse to System/Media Server/System Profiles and check out
legacy_to_pdf.xml.
2.
Open the file in a text editor.
3.
Change this line:
<InnerTokenMapping LocalProfileToken="DocumentContent"
InnerProfileToken="doc_token_printType" Literal="true"/>
to:
<InnerTokenMapping LocalProfileToken="DocumentWithMarkup"
InnerProfileToken="doc_token_printType" Literal="true"/>
4.
Save the file.
5.
Check in the file to the repository.
Transferring document attributes
A document’s attributes are its descriptive characteristics, such as name, title, author, creation
date, object ID, or subject. You can set the values for some attributes. Other attributes, such as the
document’s creation date, are set by the system.
Content Transformation Services lets you transfer these attributes to a document’s PDF rendition (but
not to a document’s HTML rendition). Use the attributes for identification or tracking purposes after
the PDF document is exported from the repository where the source document resides.
Note: Some attributes, like repository ID, may not be visible when viewed through Document Info
in Adobe Exchange.
You can also transfer attribute information to custom plug-ins, where the plug-in needs to know
certain information about a document (such as type, author, or source type).
For example, write a plug-in that looks for certain attributes identifying a document as a Standard
Operating Procedure (SOP). If those attributes are found, the plug-in prints a special cover page, or
adds or subtracts context-sensitive information before the document is rendered into PostScript
format.
Transferring document attributes to PDF and embedding metadata
To transfer attributes, edit the appropriate command-line files of Content Transformation Services.
84
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
The following command-line files are responsible for transferring the attributes from the source
document to the PDF rendition:
• embedMetadataToContent_adts.xml (used by the transformation profiles for embedding the
metadata)
Define the attribute mapping for PDF renditions under the <PDF_DOC_INFO> tag of these
command-line files. The syntax is:
value = object_alias.attribute[repeating_spec]
An example would appear as follows:
<PDF_DOC_INFO>
...
...
<MetadataMapper name="DCTMobjectTitle" value="title"
token="doc_metadata_dctmTitle"/>
...
...
</PDF_DOC_INFO>
The attribute token is used internally by the server code, and has to be named with the prefix
doc_metadata_ . For example:
token=" doc_metadata_dctmTitle”
Table 6. Attribute mapping arguments
Argument
Description
key
Key can be an existing attribute or a user-defined
attribute. Examples: author, subject, title,
producer.
object_alias
When omitted or specified as o, the object_alias
indicates that the following attribute is that of a
sysobject or one of its subtypes (the document
being rendered). Other valid object_aliases are:
• d (repository config object)
• s (server config object)
• q (attributes from special runtime-computed
items)
Refer to the EMC Documentum Content Server
Administration and Configuration Guide for more
information about configuration objects.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
85
Configuration and Administration Tasks and Tips
attribute
In the case of o, s, and d object aliases, attribute
dynamically maps the attribute. In the case
of the q object, the only currently available
attributes are sentby, login_ticket, and username.
value
For repeating attributes, value defines the
repeating attribute separator (for example, a
comma or a slash). If no separator is defined, and
the attribute is repeating, Content Server maps
only the first attribute in the series [element 0].
Here are some examples of attribute mapping syntax.
The first example shows an attribute where the object alias (o) is implied:
<MetadataMapper name="Subject" value="subject"
token="doc_metadata_subject"/>
The following example shows an attribute mapped with specified object alias:
<MetadataMapper name="DCTMSourceContentType" value="o.a_content_type"
token="doc_token_sourceContentType"/>
The following example shows a comma-separated list of keywords from sysobject:
<MetadataMapper name="Keywords" value="keywords[,]"
token="doc_metadata_keywords"/>
The following example shows a list of authors, separated by // (two forward slashes):
<MetadataMapper name="Author" value="authors[//]"
token="doc_metadata_author"/>
Note: Restart Content Transformation Services for the changes in the command line files to take effect.
Viewing the attributes in the PDF rendition
To see the transferred attributes for a PDF rendition, choose Document Properties in Adobe Acrobat.
Configuration tasks specific to Media
Transformation Services
This section contains procedures for the following image-based configuration tasks that are
performed with Media Transformation Services.
• Configuring the PowerPoint2 plug-in, page 87
• Managing PowerPoint registration, page 88
• Selecting a colorspace, page 90
• Generating the background color for thumbnails from transparent PDF files, page 91
• Improving the quality of JPEG image files converted from SVG format, page 92
• Configuring the Image3 plug-in, page 92
86
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Configuring the PowerPoint2 plug-in
The Microsoft Office-based PowerPoint2 plug-in has been reintroduced in this release of Content
Transformation Services because of better stability and reduced data loss, which was seen in
PowerPoint transformations in Content Transformation Services 6.7.x products.
The PowerPoint1 and PowerPoint 2 plug-ins are bundled along with Media Transformation Services.
Only the PowerPoint1 plug-in is turned on by default. To use the PowerPoint2 plug-in, add the
following in the CTSPluginService.xml file:
<CTSPlugin DELEGATE_CLASS="com.documentum.cts.plugin.powerpoint2.PowerPointPlugin"
CONFIGFILE="%CTS_HOME%\PowerPoint2\PowerPoint2.xml"/>
The configuration files for the PowerPoint1 and PowerPoint2 plug-ins are located in the
%CTS_HOME%\config\powerpoint1 and %CTS_HOME%\config\powerpoint2 folders on the
Media Transformation Services server respectively.
All the OOTB Media Transformation Services profiles and system profiles will refer to the
PowerPoint1 plug-in only. Hence, PowerPoint registration, assembly, conversions, slide generation,
property extraction and storyboarding is handled by the PowerPoint1 plug-in OOTB. To use the
PowerPoint2 plug-in instead, do the following:
1.
Check out the corresponding profile(s) or system profile(s).
2.
Change the mptype attribute of CommandFilePath element (for example, extraction).
Change
<CommandFilePath mptype="POWERPOINT1">
/System/Media Server/Command Line Files/ppt_extract_props.xml
</CommandFilePath>
To
<CommandFilePath mptype="POWERPOINT2">
/System/Media Server/Command Line Files/ppt_extract_props.xml
</CommandFilePath>
3.
Check in the profile in to the repository.
Note: The name and content of the command line files are the same for the PowerPoint1 and
PowerPoint2 plug-ins. Hence, changing the plug-in name in profiles or system profiles is adequate.
The following OOTB profiles or system profiles can be switched to use either of the two plug-ins:
• ppt_conversion
• powerpointDefaultStoryboard
• powerpointRegistration
• powerpointRegistrationStoryboard
• powerpointStoryboard
• ppt_assembler
• ppt_extract_props
• ppt_slide_generator
• thumbnail
• thumbnail_ppt
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
87
Configuration and Administration Tasks and Tips
• autoGenPreviewProxy
• autoGenProxy
Note: To use the PowerPoint2 plug-in, install Microsoft PowerPoint 2007 SP3 (32-bit) on the Media
Transformation Services server that is installed on Windows Server 2008 R2 SP1 (64-bit) operating
system.
Make the following changes in the log4j.properties file (located at %CTS_HOME%\config\log4j.
properties) to enable logging for the PowerPoint2 plug-in:
log4j.category.com.documentum.cts.plugin.powerpoint2=DEBUG, Powerpoint2Appender
log4j.appender.Powerpoint2Appender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.Powerpoint2Appender.File=<CTS_HOME>\\logs\\Powerpoint2_log.txt
log4j.appender.Powerpoint2Appender.Append=true
log4j.appender.Powerpoint2Appender.layout=org.apache.log4j.PatternLayout
log4j.appender.Powerpoint2Appender.layout.ConversionPattern=%d{HH\:mm\:ss,SSS}
ndi %10r %5p [%10t] %-20c{1} - %5x %m%n
log4j.appender.Powerpoint2Appender.DatePattern=’.’yyyy-ww-dd
After you make these changes, restart Content Transformation Services.
Managing PowerPoint registration
Due to complex processing during PowerPoint registration, the total time taken to complete
registration can be substantial depending on the number of slides in the presentation. This prevents
other PowerPoint registrations from being completed. To mitigate this, the PowerPoint registration
process is split into two steps: Image Rendition generation and Slide generation. Among these two
processes, the Slide generation process takes the longest time. To split this registration process, you
must have at least two Media Transformation Services machines configured to the same repository.
PowerPoint Registration —> Primary MTS (Image Rendition generation) —> Delegate to —>
Secondary MTS (Slide generation).
The Primary Media Transformation Services machine generates image renditions and delegates
slide generation to the secondary Media Transformation Services machine. The secondary Media
Transformation Services machine generates all the slides and uploads them to the repository.
Following are the changes that must be made to the powerpoint1.xml to enable the process:
<PPT_IMPORT_PROCESSING MODE="STORYBOARDS_AND_SLIDES | STORYBOARDS _ONLY |
SLIDES_ONLY" IMAGE_RENDITION_PROPERTIES="FALSE">
<!-- XML below is read only by STORYBOARDS_ONLY mode MTS -->
<CTS_DELEGATE_QUEUE QUEUE_NAME="dm_mediaserver_ppt_a1">
<MIN_SLIDES_COUNT>10</MIN_SLIDES_COUNT>
</CTS_DELEGATE_QUEUE>
<CTS_DELEGATE_QUEUE QUEUE_NAME="dm_mediaserver_ppt_a2">
<MIN_SLIDES_COUNT>10</MIN_SLIDES_COUNT>
</CTS_DELEGATE_QUEUE>
<CTS_DELEGATE_QUEUE QUEUE_NAME="dm_mediaserver_ppt_b">
<MIN_SLIDES_COUNT>100</MIN_SLIDES_COUNT>
</CTS_DELEGATE_QUEUE>
</PPT_IMPORT_PROCESSING>
....
.....
</PREPROCESS_SLIDE_RENDITIONS>
88
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Note: This is only an example and can be customized as required.
The MODE parameter must contain one of the following values:
• STORYBOARDS_AND_SLIDES — By default the attribute value ‘STORYBOARDS_AND_SLIDES’
means that primary Media Transformation Services processes the PowerPoint registration
completely, without delegating slide generation to a secondary Media Transformation Services
instance. This means that the Media Transformation Services behaves as a regular Media
Transformation Services.
• STORYBOARDS_ONLY — The Media Transformation Services that is configured to split the
PowerPoint registration must have this value. This mode generates image renditions and
delegates slide generation to a secondary Media Transformation Services instance. If the minimum
slide size of the secondary Media Transformation Services is more than the current PowerPoint
file being processed, then the PowerPoint asset will be processed fully by Media Transformation
Services. In the above example, any slide deck between sizes 1 to 9 will be processed fully by the
primary Media Transformation Services itself without being delegated to the secondary Media
Transformation Services.
• SLIDES_ONLY — All the secondary Media Transformation Services that handle slide generation
must have this value. This mode generates all the slides and uploads them to the repository.
IMAGE_RENDITION_PROPERTIES turns off updating all the slide image renditions with height,
width, and format values. This saves considerable processing time. It is recommended to always
retain the value as "False”.
The <CTS_DELEGATE_QUEUE> elements list the secondary Media Transformation Services that can
be configured with the specific queue names and slide sizes that it processes. In the sample above,
three secondary Media Transformation Services instances are configured to handle PowerPoint files
of different sizes. The QUEUE_NAME should be unique and each queue should have a specific
secondary Media Transformation Services configured against it.
In this example, only slides with deck size 10 or above are delegated to the secondary Media
Transformation Services and smaller sized PowerPoint files (1-9 slides) are processed by the Media
Transformation Services that is marked as STORYBOARDS_ONLY (that is, the primary Media
Transformation Services). If you need all the slide generation to be delegated to the secondary Media
Transformation Services then at least one Media Transformation Services instance should be marked
with MIN_SLIDES_COUNT = 1.
Following are some sample load balancing scenarios based on the input slide sizes and sample
configuration provided above:
Slide Size
10
20
21
9
125
155
300
Delegated
to MTS
a1
a2
a1
Primary
MTS
b
b
b
Slide Size
125
5
75
146
65
210
400
Delegated
to MTS
b
Primary
MTS
a1
b
a2
b
b
Different secondary Media Transformation Services that have the same MIN_SLIDES_COUNT are
delegated based in a round robin manner to distribute the load evenly. The queue names must be
unique to ensure that registration tasks are picked up by specific Media Transformation Services
configured to those PowerPoint sizes.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
89
Configuration and Administration Tasks and Tips
Note: To disable the PowerPoint file split processing, specify MODE="STORYBOARDS_AND_
SLIDES”.
Configuring a primary Media Transformation Services instance
1.
Specify the attribute as MODE="STORYBOARDS_ONLY" to enable PowerPoint storyboard
processing and splitting the process to the secondary Media Transformation Services.
2.
List the secondary Media Transformation Services under the CTS_DELEGATE_QUEUE nodes.
3.
Create all users specified in the attribute QUEUE_NAME (for example, dm_mediaserver_ppt_a1)
with the same values as the default user "dm_mediaserver” using Documentum Administrator.
If this is not done, queue generation will fail with an exception.
4.
Retain IMAGE_RENDITION_PROPERTIES="FALSE" to improve the processing time as rendition
image attributes of width and height are not updated, thus saving considerable time.
Configuring a secondary Media Transformation Services instance
Note: This process requires one Media Transformation Services for each CTS_DELEGATE_QUEUE
node. The QUEUE_NAME should be unique to each secondary Media Transformation Services
instance.
1.
Specify the attribute as MODE="SLIDES_ONLY".
2.
Retain IMAGE_RENDITION_PROPERTIES="FALSE" to improve the processing time as rendition
image attributes of width and height are not updated, thus saving considerable time.
3.
Ensure that you modify the CTSServerService.xml file with the queue name configured in
the CTS_DELEGATE_QUEUE node.
For example: Replace dm_mediaserver with dm_mediaserver_ppt_a1
<QueueProcessorContext>
<CTSServer AttributeName="queueItemName" AttributeValue="dm_mediaserver_ppt_a1"/>
This indicates that this Media Transformation Services would not process any other Content
Transformation Services jobs but would remain dedicated to processing PowerPoint slides.
Remove <QueueProcessorContext> for QueueItemName ‘dm_autorender_win31’.
Note: Restart Content Transformation Services to implement any changes in the XML files.
Selecting a colorspace
To select a specific colorspace, edit the register_legacy.xml system profile and add the
following inner token to all profiles that generate thumbnails such as thumbnail, autoGenProxy,
autoGenPreviewProxy, and so on.
<!-- if RGB output images are needed -->
<InnerTokenMapping Literal="true" InnerProfileToken="doc_token_colorSpace"
LocalProfileToken="RGB"/>
90
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
or
<!-- if CMYK output images are needed -->
<InnerTokenMapping Literal="true" InnerProfileToken="doc_token_colorSpace"
LocalProfileToken="CMYK"/>
This will ensure that the output image corresponds to the specified colorspace.
Generating the background color for thumbnails from
transparent PDF files
When you open some PDFs in Acrobat Reader, they may appear as a white page. However, on
enabling the "Page Display / Show transparency grid" option in the Preferences menu, you can view
the content. Out-of-the-box, the Media Transformation Services server replaces the transparent
layers with white. Hence, you must configure this to another colour (for example, light gray) so
that the images can be seen.
To generate the preferred background color for PDF files, do the following:
Note: This solution may not work for all types of PDF files and is a third party limitation.
1.
Checkout the thumbnail_pdfstoryboard.xml system profile and ensure that Image3 is
the first plug-in in the list.
2.
Checkout the thumbnail_pdf_imw.xml command line (heavyweight) profile and modify
the following:
Add:
<PROP name="bgColor" type="string" token="doc_token_bgColor">#FFFFFF</PROP>
Change:
<Options>-limit memory
To:
<Options>-colorspace doc_token_colorSpace doc_token_sourceFile -limit memory
Change:
-quality 80
To:
-flatten -quality 80
Here, #FFFFFF is white, which can be changed to any color of choice. Navigate to the
Imagemagick website to check the color options available.
If PDF transparency is required in the Preview proxy images, then make similar changes to the
following files:
• System Profiles/autoGenPreviewProxy_pdfstoryboard and Command Line Files/autoGenProxy_
pdf_imw.xml
• System Profiles/autoGenProxy_pdfstoryboard and Command Line Files/autoGenProxy_pdf_
imw.xml
If PDF transparency is required in PDF storyboards for the background color of choice, do the
following:
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
91
Configuration and Administration Tasks and Tips
1.
Checkout the storyboard_pdfstoryboard.xml system profile and ensure that Image3 is
the first plug-in in the list.
2.
Checkout the storyboard_pdf_imw.xml command line (heavyweight) profile and modify
the following:
Change:
<Options>-limit memory
To:
<Options>-colorspace doc_token_colorSpace doc_token_sourceFile -limit memory
Change:
-quality 80
To:
-bordercolor #FFFFFF -border 0 -alpha off -quality 80
Here, #FFFFFF is white, which can be changed to any color of choice. Navigate to the
Imagemagick website to check the color options available.
Improving the quality of JPEG image files converted
from SVG format
The quality of the SVG file converted to JPEG using the resize_preserveRatio profile is 80% by
default. To increase the quality to 100%, update the value of "doc_token_quality" in the TransformTo
and Resize profiles as follows:
InnerTokenMapping LocalProfileToken="100" InnerProfileToken=
"doc_token_quality" literal="true"
Configuring the Image3 plug-in
The Image3 plug-in has some extra options — over and above the standard configuration options for
plug-ins — that can be configured through the plug-in’s configuration file. The following sections
detail these options and how they can be configured:
• ICC profiles, page 92
• COM Server parameters, page 93
• Pixel cache parameters, page 93
• Timeout configuration, page 94
ICC profiles
The ICC profiles section of the configuration file holds a list of individual ICC profiles. Specify one
ICC profile per colorspace. An ICC profile is specified in an ICC_PROFILE_INFO XML tag:
<ICC_PROFILE_INFO profile_token="doc_token_cmyk_profile" colorspace="CMYK">
C:\Documentum\CTS\Image3\required\color\USWebCoatedSWOP.icc
92
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
</ICC_PROFILE_INFO>
The value of the XML element is the fully qualified path to the ICC profile. The attributes are
as follows:
• profile_token – the token in the profile that will be substituted with the path of the ICC profile.
• colorspace – the colorspace of this profile.
Two ICC profiles will be used in conjunction to perform color conversions when doing
transformations.
The Image3 plug-in is configured out-of-the-box with a CMYK and RGB profile, which will be used to
convert CMYK images to RGB when creating thumbnails and low-resolution JPEGs.
Note: ICC version 4 profiles are not supported.
COM Server parameters
There are two configurable parameters relating to the COM Server:
• Process name
This is the name of the COM Server that performs the work based on the ImageMagick library. It
should always be IMW_COMServer.exe.
• Pool size
The value of this configuration parameter is the maximum number of ImageMagick COM servers
that can be running at one time.
Pixel cache parameters
A number of parameters can be configured for the pixel cache in the Image3 plug-in.
Table 7. Pixel cache parameters for Image3 plug-in
Parameter name
Function
Memory size
Sets the maximum amount
of memory in megabytes to
allocate for the pixel cache from
the heap. When this limit is
exceeded, the image pixels are
cached to memory-mapped
disk.
XML attribute
doc_token_limit_memory
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
93
Configuration and Administration Tasks and Tips
Parameter name
Function
Memory map size
Sets the maximum amount of
memory map in megabytes
to allocate for the pixel cache.
When this limit is exceeded, the
image pixels are cached to disk.
Area size
Sets the maximum width
x height of an image that
can reside in the pixel cache
memory. Images that exceed
the area limit are cached to
disk.
XML attribute
doc_token_limit_map
doc_token_limit_area
Timeout configuration
If your installation of Content Transformation Services will be processing large images, configure the
timeout value in the image3.xml configuration file. This value will determine how long Content
Transformation Services will maintain an image in its processes before calling a timeout and causing
the processing to fail.
Content Transformation Services requires at least 2 GB of free memory to process large images. If you
expect to process large dimensioned images, it may be necessary to raise the default timeout value,
taking your computer’s capabilities into consideration.
This value can be configured in the image3.xml file:
• application_monitor_timeout
This is the number of seconds to wait for an image file to process before terminating it and logging
the timeout. With the default of 30 minutes, this value appears as follows:
<APPLICATION_MONITOR_TIMEOUT>1800</APPLICATION_MONITOR_TIMEOUT>
The timeout value should be based on the hardware on the machine in question, and the number
of and size of the images. If you are experiencing timeouts with this default value, increase it in
the config file.
Configuration tasks specific to Audio/Video
Transformation Services
This section contains procedures for the following audio and video-based configuration tasks that are
performed with Audio/Video Transformation Services.
• Configuring Content Server required for large video files, page 95
• Creating different default preview formats on import of video files, page 95
94
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Configuration and Administration Tasks and Tips
Configuring Content Server required for large video
files
When importing a video file larger than 2.5 GB, the renditions, thumbnail, and storyboard are not
created. The Content Server must be configured to allow processing of files larger than 2.5 GB.
To configure Content Server for transforming video files larger than 2.5 GB:
1.
Locate the file server.ini at the following location:
• On Windows, %DOCUMENTUM%\dba\config\<repository>
• On non-Windows, $DOCUMENTUM/dba/config/<repository>
2.
Open the file in a text editor.
3.
Locate the section [SERVER_STARTUP].
4.
Add the client_session_time key and a value for timeout_in_minutes. The value for
timeout_in_minutes should be at least twice your expected maximum video duration, depending
on the machine’s performance.
For example, for a largest expected video size of 2 GB, set it to:
client_session_timeout = 120
5.
Restart the Content Server and Content Transformation Services product.
Creating different default preview formats on import
of video files
Out of the box, Content Transformation Services creates Flash 9 renditions for the default preview
rendition of video files. This can be changed to other formats like WMV, MPEG4, QuickTime, and
WebM. Some profile changes are required to set the default preview rendition to another format.
For example, to configure Content Transformation Services to generate the WMV format as the
default preview, instead of Flash 9, the following profile changes must be made:
1.
Check out the video_registration profile from the following folder in the repository:
\System\MediaServer\System Profiles.
2.
Uncomment the to_wmv "InnerProfile” snippet. This will enable the WMV rendition to be
generated out of the box.
3.
Move the entire "default_proxy_format” tag from the to_flash9 section to the to_wmv section
and update the following format:
<InnerTokenMapping LocalProfileToken="wmv" InnerProfileToken=
"default_proxy_format" Literal="true"/>
Ensure that the "default_proxy_format” tag is not present for more than one rendition.
4.
Check in the video_registration profile.
5.
Restart the Content Transformation Services product.
Note: If Content Transformation Services is configured for the xCP client, the same change will
have to be made in the video_registration_xcp profile, instead of the video_registration profile. The
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
95
Configuration and Administration Tasks and Tips
video_registration_xcp profile does not have the default_proxy_format tag present for any rendition
by default, but it can be added afresh for any of the two existing OOTB renditions (MPEG4 or WebM).
96
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Chapter 4
Creating a Content Transformation
Services WebServices Activity
Install the latest version of the following software before creating a Content Transformation Services
WebServices Activity:
• xCelerated Composition Platform (xCP) Designer
• Content Server
Note: Ensure that you deploy the Content Transformation Services WebServices
(transformation.ear or transformation.war files) in a supported application server,
according to the EMC Documentum Content Transformation Services Installation Guide.
To create a Content Transformation Services WebServices Activity, first create endpoints, and then
create a process with the Content Transformation Services WebServices Activity.
Endpoints represent a connection to external services, for example, an SMTP host or a web service
URL. To create a WebServices Activity for invoking Content Transformation Services, create an
endpoint for:
• ProfileService
• TransformationService
To create an endpoint:
1.
In xCP Designer, navigate to Application and click Endpoints.
2.
Click + and create two endpoints of type WebService (SOAP).
3.
For the first endpoint, in the dialog box, type a valid name and the WSDL URL to point to the
Content Transformation Services ProfileService.
When transformation.ear is deployed, ProfileService wsdl will look like:
http://<CTSWS_HostName_or_IP>:<port>/services/transformation/ProfileService?wsdl
When transformation.war is deployed, ProfileService wsdl will look like:
http://<CTSWS_HostName_or_IP>:<port>/transformation/services/transformation
/ProfileService?wsdl
4.
For the second endpoint, in the dialog box, type a valid name and the WSDL URL to point to
the Content Transformation Services TransformationService.
When transformation.ear is deployed, TransformationService wsdl will look like:
http://<CTSWS_HostName_or_IP>:<port>/services/transformation/
TransformationService?wsdl
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
97
Creating a Content Transformation Services WebServices Activity
When transformation.war is deployed, TransformationService wsdl will look like:
http://<CTSWS_HostName_or_IP>:<port>/transformation/services/transformation
/TransformationService?wsdl
Note: The xCP Designer Help contains detailed information for providing valid names to endpoints.
To create a process with a Content Transformation Services WebServices Activity:
1.
In xCP Designer, navigate to Processes and create a new process.
2.
Click Process Properties to open a dialog box.
3.
Under Data, add a new package with the Name sourcedoc and the Type Base Content.
4.
Create the process variables as shown in the following table:
Table 8. Process Variables
Process Variable
Name
Value Description
profilename
Default value: document_to_pdf (can be any profile name which has to
be executed). Type: String
profileid
Leave the value empty. Type: String
parametername
Default value: any parameter you want to pass. Type: String
parametervalue
Default value: any default value for the parameter. Type: String
targetformat
Default value: pdf (can be any value depending on the profile selected).
Type: String
objectidvaluetype
Set the default value to OBJECT_ID. Type: String
Note: The variable names, "parametername” and "parametervalue” in the table above, are
provided as examples. If the profile chosen requires more parameters, you must supply all
parameter names and values, as appropriate.
5.
Create a Call Web Service activity using drag and drop of the icon from Activities to Process
Designer.
6.
Double-click Call Web Service in Process Designer to open the Activity Inspector dialog box.
7.
Select the endpoint that you created for profileservice. In the Operation drop-down list, select
getProfileByName and click Next.
8.
Authentication for a Content Transformation Services web service can be done in a single or
chained manner. The xCP Designer Help contains instructions for setting up the SOAPHeader
required for calling a Documentum Foundation Services (DFS)-based web service.
The following code example uses a single authentication process by providing a <ServiceContext>
to each web service call. In the "SOAPHeaderElement[0]" create a "Concat" function and
append the following two strings, changing the userName, password, and repositoryName
as appropriate.
<ServiceContext xmins="http://context.core.datamodel.fs.documentum.emc.com/"
xmlns:ns2="http://properties.core.datamodel.fs.documentum.emc.com/"
xmlns:ns3="http://profiles.core.datamodel.fs.documentum.emc.com/"> <identities
xmins:xsi="http://www.w3.org/2001/XMLSchema=instance" repositoryName="<RepoName>"
password="<Password>" userName="<UserName>" xsi:type="RepositoryIdentity"/>
98
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Creating a Content Transformation Services WebServices Activity
</ServiceCeontext>
9.
Map the profilename process variable created above to SOAPBody > parameters >
getProfileByName > profileName.
10. Map the ProcessData > Execution Data > docbase > name to SOAPBody > parameters >
getProfileByName > repository.
11. Click Next to view the Output Message Mapping in the Activity Inspector dialog box. Map the
SOAPBody > parameters > getProfileByNameResponse > return > ProfileId > ObjectId > id to
ProcessData > Variables > profileid.
12. Create a second Call Web Service activity using drag and drop of the icon from Activities.
Double-click Call Web Service to open the Activity Inspector dialog box.
13. Select the endpoint that you created for transformationservice. In the Operation drop-down
list, select addJob and click Next.
14. In Input Message Mapping, select "SOAPHeaderElement[0]" and create a "Concat" function in it.
In the Concat function, add the following strings to provide the repository name, user name, and
password, as appropriate:
<ServiceContext xmins="http://context.core.datamodel.fs.documentum.emc.com/"
xmlns:ns2="http://properties.core.datamodel.fs.documentum.emc.com/"
xmlns:ns3="http://profiles.core.datamodel.fs.documentum.emc.com/"> <identities
xmins:xsi="http://www.w3.org/2001/XMLSchema=instance" repositoryName="<RepoName>"
password="<Password>" userName="<UserName>" xsi:type="RepositoryIdentity"/>
</ServiceCeontext>
15. Map the parameters as shown in the following table:
Table 9. Process Data Parameters
Process Data Parameters
SOAP Input
ProcessData > packages >
sourcedoc > Object ID
SOAPBody > parameters > addJob > jobticket > @sourceObjectId
ProcessData > packages
> sourcedoc > Content >
Format
SOAPBody > parameters > addJob > jobticket > @sourceFormat
ProcessData > Variables >
profileid
SOAPBody > parameters > addJob > jobticket > Profile >
ProfileId > ObjectId > @id
ProcessData > Variables >
targetFormat
SOAPBody > parameters > addJob > jobticket > @targetFormat
ProcessData > Variables >
parametername
SOAPBody > parameters > addJob > jobticket >
ParamProperties[0] > @name
ProcessData > Variables >
parametervalue
SOAPBody > parameters > addJob > jobticket >
ParamProperties[0] > @value
ProcessData > Variables >
objectIdValueType
SOAPBody > parameters > addJob > jobticket > Profile >
ProfileId >@valueType
ProcessData > Variables >
profileName
SOAPBody > parameters > addJob > jobticket > Profile > @name
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
99
Creating a Content Transformation Services WebServices Activity
16. Click Next. You can map the response to any process variables you prefer or leave it empty.
17. Deploy the process as part of the xCP application, using the xMS server or a different method
(according to the xCP documentation). The process or workflow is ready for execution using
any client application (for example, Document Administrator).
100
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Chapter 5
Troubleshooting
This chapter provides troubleshooting information for errors encountered from Content
Transformation Services products. In addition, consult the EMC Documentum Content Transformation
Services Installation Guide for additional information regarding items that can affect the installation of
your products.
Troubleshooting tips for Content
Transformation Services products
The following are troubleshooting tips and topics for Content Transformation Services products.
• Storing the intermediate output of chain profile to docbase, page 102
• Preserving temporary or intermediate files to debug a problem, page 102
• Error events and log files, page 103
• A transformation request fails, page 104
• A profile error occurs, page 104
• Cannot add a rendition to a particular format, page 105
• If Content Transformation Services server cannot communicate to the repository, page 105
• Content Transformation Services fails to function, page 106
• Content Transformation Services Administration Agent gives AGENT_INACCESSIBLE message,
page 106
• Content Transformation Services fails to transform any document to PDF (using Tools->Transform)
that is imported to a web cabinet as WP admin user, page 107
• Content Transformation Services is not responsive after a set of transformations, page 107
• Manual re-configuration of Content Transformation Services instance if the repository is deleted,
page 108
• Profile modifications, page 109
• Rendition failures due to expired login tickets, page 109
• Content Transformation Services Queue Item Cleanup — Pre-Processing delay, page 110
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
101
Troubleshooting
• After restarting Content Server, Content Transformation Services throws a "server communication
failure” exception, page 110
• Users with version permission get Inbox notification on legacy transformations, page 110
• Transparency in PNG renditions lost for Illustrator files, page 111
• Preserving ICC profiles during transformations, page 111
• Text wrapping problems with large double byte characters, page 111
• Embedding metadata for date datatype other than default, page 111
• Troubleshooting storyboard issues generated by the PDFStoryboard plugin, page 112
• Resolving issues with email content containing double byte characters, page 112
• Performance degradation due to add_rendition_properties settings, page 112
Storing the intermediate output of chain profile to
docbase
There is an option to store the output of an intermediate profile to the docbase.
Note: This option is available only for chain profiles.
Add the following as one of the InnerTokenMapping to the InnerProfile entries of required profiles:
<InnerTokenMapping LocalProfileToken="true"
InnerProfileToken="store_result_in_repo" Literal="true"/>
Example 5-1.
To store the intermediate PDF output from the document_to_pdf profile which is part of the
document_registration_xcp chain profile, add InnerTokenMapping to document_to_pdf InnerProfile
as shown in the following code snippet:
<ProfileChain>
<InnerProfile path="/System/Media Server/System Profiles/document_to_pdf"
waitOnCompletion="true" useTargetFormat="true">
<InnerTokenMapping LocalProfileToken="true"
InnerProfileToken="store_result_in_repo" Literal="true"/>
...
</InnerProfile>
...
</ProfileChain>
Preserving temporary or intermediate files to debug a
problem
There is a configuration option to preserve temporary or intermediate files. This configuration should
only be used when debugging a problem and disabled as soon as it is no longer required.
The configuration can be overwritten (when "false”) via profile. For the profile, the values are:
102
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Troubleshooting
0 – NO (do not keep temp files)
1 – YES (keep temp files)
The configuration element is in CTSServerService.xml (%CTS_HOME%\Config):
<KeepTempFiles>NO</KeepTempFiles>
By switching this value to YES, input files as well as plug-in results will not be deleted after a
transformation. Also, this value can be overwritten by a profile parameter:
<Parameter name="keep_temp" label="Keep temporary files" controltype="list"
datatype="string" default="0" isRequired="false">
<ValueList>
<Value label="No">0</Value>
<Value label="Yes">1</Value>
</ValueList>
</Parameter>
The output and source files can be found at the following locations:
• for outputs — %CTS_HOME%\cache
• for source files — %CTS_HOME%\docbases\<docbase_name>\config\temp_sessions
Note: The default location for %CTS_HOME% is C:\Documentum\CTS
Note: To reflect changes made to CTSServerService.xml, Content Transformation Services
must be restarted.
Error events and log files
Any time Content Transformation Services fails to process a particular item, it queues an event
(dm_mediaserver_error) to the Inbox of the repository user defined as the system operator in the
server configuration file. The first step in troubleshooting is to check the system operator’s Inbox
for any messages that might explain the error.
Additionally, review the CTS_Log.txt log file. This log file contains errors and exceptions that are
specific to the server. The default location of the log file on the Content Transformation Services host,
is in the following directory:
%CTS_HOME%\logs
Plug-in error exceptions are sent to individual log files that are specific to each plug-in. These plug-in
log files allow you to quickly troubleshoot exceptions that are specific to each plug-in. For example,
errors relating to the Image3 plug-in are found in the Image3_Log.txt log file.
The plug-in log files are located in the %CTS_HOME%\logs directory on the Content Transformation
Services host.
Note: If logging is enabled separately in log4j.properties, log files will be in the
%CTS_HOME%\docbases\<docbase name>\config\logs folder. Otherwise, they are in the main logs
directory at %CTS_HOME%\logs.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
103
Troubleshooting
A transformation request fails
Occasionally, a transformation request may fail to process, or may process incorrectly. Typically, an
examination of any error messages will indicate the problem.
The following actions can be performed to determine the cause of a transformation request failure.
To troubleshoot the failure of a transformation request:
1.
Check for error messages in the system operator’s Inbox indicating that the source file may not
adhere to system specifications. For example, the file may be corrupted, or compression or other
similar features (such as codec) of the file may not be supported by Content Transformation
Services.
2.
Check that disk space and memory on the Content Transformation Services server host, and the
Content Server host, is sufficient to handle the requested file transformation.
3.
Restart the Content Transformation Services server host and attempt the transformation again.
Restarting the server will not affect the queue.
A profile error occurs
Errors related to profiles may occur. For example, if a profile was edited and updated manually,
there may be issues with the XML file.
There are a number of ways to determine the cause of a profile error.
To identify the cause of a profile-related error:
1.
Check the Inbox of the system operator for error messages. Error messages here may indicate
the cause of the error.
2.
Check the CTS_log.txt log file or the main Documentum log file, log4j.log, for exceptions.
3.
If you suspect the profile itself to be the cause of the error, use Documentum Administrator or
WDK client to make sure you have three folders in the repository for profiles:
• /System/Media Server/Profiles
• /System/Media Server/System Profiles
• /System/Media Server/Command Line Profiles
These folders should be created when you install Content Transformation Services. Make sure
the profile is in the correct folder.
4.
Ensure that the command-line file referenced by the profile (dm_media_profile object) exists in the
appropriate folder (above) and that the name in the profile is identical to the actual file name. For
example, if a dm_media_profile object resize contains the following link to its command-line file,
/System/Media Server/Command Line Profiles/resize.xml
5.
Ensure that the ProfileSchema.dtd is stored in the repository folder:
/System/Media Server/Profiles
104
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Troubleshooting
6.
If a new user profile is not appearing in the WDK application, but the log file indicates that
the profile was successfully imported, ensure that the following tags appear in the profile file
(typically after the <Formats> section):
<Filters>
<Filter name="CTSProduct" value="<CTS product initialism>" />
<Filter name="Visibility" value="Public" />
</Filters>
Caution: The value of <CTSproduct> must ONLY be that product that is configured to
the docbase, which means that, it can be any one of the following three values: MTS,
ADTS and AVTS. If Media Transformation Services is configured and the value of <CTS
product initialism> is set to "AVTS”, then this profile will not be executed by the Media
Transformation Services server.
7.
Restart the Content Transformation Services.
Cannot add a rendition to a particular format
If Content Transformation Services cannot add a rendition to a particular format, first check the
Inbox of the system operator for error messages, and then check the CTS_log.txt file. Look for a
detailed message that describes the problem. For example, the message "Object with id=...does not
exist” would indicate that the object was deleted from the repository before the server could add
a rendition to it.
If Content Transformation Services server cannot
communicate to the repository
Content Transformation Services connects to the repository using a repository SuperUser account.
If the Content Transformation Services server cannot log in to the repository, ensure that a valid
repository SuperUser is identified for the product to use.
To identify the cause of a Content Transformation Services server not logging in
to the repository:
1.
Ensure that the repository is running.
2.
Check your network connections.
3.
Check that the Connection Broker is running.
4.
Check that the dfc.properties file points to the Connection Broker that recognizes your
repository.
5.
Log in to the Content Transformation Services host as an administrator.
6.
Open the Content Transformation Services service directory, located in the directory:
%CTS_HOME%\config
7.
Open the SessionService.xml file in any text or XML editor.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
105
Troubleshooting
8.
Check the values of the MediaServerName attributes userName and passwordFile of the Content
Transformation Services element:
<CTSServer AttributeName="userName" AttributeValue="<admin_user"/>
<CTSServer AttributeName="passwordFile" AttributeValue="C:\
DOCUME~1\CTS\docbases\<repository_name>\config\pfile\
mspassword.txt"/>
9.
Ensure that you have configured the SessionService.xml file to the proper user in the
repository who has SuperUser access. If necessary, check with the repository administrator to
verify user name and password information.
For more information on the repository user name and password, see Chapter 2, Administering
and Configuring Content Transformation Services through Documentum Administrator.
10. Save and close the SessionService.xml file.
11. Restart the Content Transformation Services server and/or the repository.
Content Transformation Services fails to function
If Content Transformation Services fails to function and you receive an error message when
attempting transformations, the error may occur if the Global Registry does not have the current
version of Content Transformation Services DARs configured against it. The Global Registry is a
common repository where commonly used DAR files are installed.
Ensure that Rich_Media_Services and Transformation DAR files are run against the Global Registry
repository. Refer to the EMC Documentum Content Transformation Services Installation Guide.
Content Transformation Services Administration Agent
gives AGENT_INACCESSIBLE message
If the Content Transformation Services Administration node in Documentum Administrator is
showing an AGENT_INACCESSIBLE message, it indicates that Documentum Administrator was
unable to connect to the agent. This could be as a result of a number of reasons:
1.
The server method on the Content Server is not running.
Check the service on the Content Server machine. There should be a service called Documentum
Java Server Method.Documentum Administrator
2.
The Content Transformation Services Administration Agent is not running.
There is a service called Documentum Content Transformation Services Admin Agent
on the Content Transformation Services machine for the agent. If this service is running,
you should be able to ping the agent by opening your browser and pointing it to
http://machinename:<port>/CTSAgent/CTSAgent (the default port is 9095). It should respond
with a page saying "Content Transformation Services Agent" if it is running.
If the Admin Agent is not running, see Starting and stopping the Content Transformation Services
Administration Agent, page 26 to start the Content Transformation Services Admin Agent.
3.
106
The server method on the Content Server is not there.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Troubleshooting
You can look for the server method using Documentum Administrator (Administration > Job
Management > Methods). Do a search for CTSAdminMethod. Content Server must be version
6.x or higher.
4.
There is no space left on the Content Transformation Services Administration Agent machine.
Check the machine to ensure that there is available space.
Content Transformation Services fails to transform
any document to PDF (using Tools->Transform) that is
imported to a web cabinet as WP admin user
A transformation request reaches the Content Transformation Services server but fails with an
exception.
This occurs because WP Documents work with ’application_code’. So any session that does not have
any application_code associated with it will be treated as a Read only session.
To resolve this issue, in the dfc.properties files, set dfc.application_code=dm_wcm. This will
ensure all sessions created will have application_code associated with it.
Content Transformation Services is not responsive
after a set of transformations
Content Transformation Services is not responsive after a set of transformations and does not poll new
queue items from the repository, even if the QueueProcessorContext threads are active and running.
The issue happens when Content Transformation Services fails to find the cts_
resources.properties and dam_resources.properties files under the %DFC User
Directory%\config folder. This is fixed so that during startup, Content Transformation Services
checks to see if these files are available in the specified folder, and if not found, will throw an
exception in the CTS_log.txt file and stop the service. The log file will give more information
about the expected location of these files. This issue normally happens if Content Transformation
Services is installed in a ’non-default’ location.
For older version of the product, resolve this issue as follows:
• Check to see if there is a stderr.log file created under %CTS%\config folder or perform a
search on the host for this file.
• If the file has any exceptions logged, there could be an issue:
java.lang.RuntimeException: cts_resources.properties file not found:
C:\Documentum\CTS\lib\documentum\config\cts_resources.properties (The system
cannot find the path specified)
• Place these files under the folder specified, and then restart the Content Transformation Services
services.
The issue occurs mainly because the system is not getting the correct "DFC User Directory"
location through the dfc call. This is something configured in the dfc.properties file either
through dfc.data.dir or dfc.user.dir property. In case these entries are missing in the
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
107
Troubleshooting
dfc.properties file, DFC will be using the ’current working directory\documentum’ as the dfc
user directory.
Manual re-configuration of Content Transformation
Services instance if the repository is deleted
If a repository configured with Content Transformation Services is permanently unavailable, some
manual re-configuration is necessary. For example, if the repository cannot be recovered after a crash,
or if the repository is deleted without removing all instances of Content Transformation Services, this
procedure is required. Without manual re-configuration, the Content Transformation Services fails to
start for all repositories that the Content Transformation Services server was configured against, not
just the deleted repository. You will see the following error in the CTS_log.txt file:
11:28:08,406 INFO [ main] CTSServerHandlerImpl - ***************
11:28:08,718 ERROR [ main] CTSServerHandlerImpl - Unable to start
the default handler.
com.documentum.cts.exceptions.internal.CTSServiceManagerException:
Unable to start the default handler.
Cause Exception was: A new instance of ICTSService with SUBTYPE =
CTSPLUGIN could not be created
com.documentum.cts.exceptions.internal.CTSServiceException: Unable
to start the default handler.
at com.documentum.cts.impl.services.CTSServiceBaseImpl.startAll
(CTSServiceBaseImpl.java:930)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.start
(CTSServiceBaseImpl.java:565)
at com.documentum.cts.services.CTSServiceManager.getServiceBySubType
(CTSServiceManager.java:545)
at com.documentum.cts.impl.services.ctsserver.CTSServerHandlerImpl.
getMediaPluginHandler(CTSServerHandlerImpl.java:1074)
at com.documentum.cts.impl.services.ctsserver.CTSServerHandlerImpl.
start(CTSServerHandlerImpl.java:541)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.startAll
(CTSServiceBaseImpl.java:925)
at com.documentum.cts.impl.services.CTSServiceBaseImpl.start
(CTSServiceBaseImpl.java:565)
at com.documentum.cts.services.CTSServiceManager.registerServices
(CTSServiceManager.java:268)
at com.documentum.cts.services.CTSServiceManager.bootstrapServiceFramework
(CTSServiceManager.java:161)
at com.documentum.cts.services.CTSServiceManager.getInstance
(CTSServiceManager.java:118)
at com.documentum.cts.services.ctsserver.CTSServerStartup.main
(CTSServerStartup.java:107)
To fix this, perform the following procedure on the Content Transformation Services host:
1.
Navigate to %CTS%\config (for example, C:\Documentum\CTS\config).
2.
Make a backup copy of the following files:
• CTSProfileService.xml
• CTSServerService.xml
• SessionService.xml
108
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Troubleshooting
3.
In any text or XML editor, open the CTSProfileService.xml file and remove the entire
<ProfileManagerContext> tag for the repository that is no longer available.
4.
In any text or XML editor, open the CTSServerService.xml file and remove the entire
<QueueProcessorContext> tags for the repository that is no longer available. There are two of
these tags for each repository that has been configured, so you will need to remove both entries
for the repository that is no longer available.
5.
In any text or XML editor, open the SessionService.xml file and remove the entire
<LoginContext> tag for the repository that is no longer available.
6.
Delete the folder for the repository that is no longer available under %CTS%\docbases (for
example, %CTS_HOME%\docbases).
7.
Open the Windows Registry Editor (go to Start > Run > regedit).
8.
For the Content Transformation Services installed, delete the folder with the repository name
that is no longer available under:
HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\CTS\MTS\Docbases
For example, the full path for Content Transformation Services, including the repository name,
will appear as:
HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\CTS\MTS\Docbases\<docbase-name>
9.
Stop the Content Transformation Services service.
10. Delete the Content Transformation Services log files.
11. Start the Content Transformation Services service.
Profile modifications
When there are changes made to the profile, the changes will be loaded automatically to the profile.
However, restarting the Content Transformation Services server ensures that the cache, which
Content Transformation Services maintains for all profiles, is created afresh.
Rendition failures due to expired login tickets
In some cases, users may experience rendition failures resulting from expired login tickets. The
following error message appears in the log file:
[DM_SESSION_E_START_FAIL]
[DM_SESSION_E_LDAP_AUTHENTICATION_FAILED]
[DM_SESSION_E_LDAP_BIND]
A KeepSessionTimeOut node exists in the SessionService.xml file, to prevent the caching of
login tickets.
However, if the KeepSessionTimeOut node is changed from its default of 0, this error may occur.
Ensure that the value for the KeepSessionTimeOut node is less than the ticketed session expiry timeout
value in the server.ini file for a given repository.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
109
Troubleshooting
Content Transformation Services Queue Item Cleanup
— Pre-Processing delay
If a delay in starting up the Pre-Processing becomes noticeable, it can be fixed by
updating the markerInterval entry to have the same or lesser value of queueInterval in the
CTSServerService.xml file:
<CTSServer AttributeName="markerInterval" AttributeValue="10"/>
<CTSServer AttributeName="queueInterval" AttributeValue="10"/>
After restarting Content Server, Content Transformation
Services throws a "server communication failure”
exception
After Content Server is restarted, Content Transformation Services throws "server communication
failure" exception and has to be restarted to work. Configuration options are available to help improve
the Content Transformation Services response rate for reconnecting if the Content Server is restarted.
Note: Try updating only the Content Transformation Services host first, then the Content Server
host if necessary.
There are two main configuration elements:
1.
Add the following to the dfc.properties file:
dfc.session.keepalive.enable = true
2.
Add the following registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameter\KeepAliveTime
and set the DWORD value to 300000(Decimal)
Two additional operating system settings to consider adjusting are Keepalive interval and
Keepalive retry
Note: ’Keepalive’ is a networking concept, not a Documentum feature. More details on how
these setting work and how to set them can be obtained from operating system documentation or
other resources.
Users with version permission get Inbox notification
on legacy transformations
To fix this problem, perform the following procedure:
1.
Check out the legacy_to_pdf system profile from the repository, in the folder:
\System\Media Server\System Profiles.
2.
Modify ALL of the innerprofile entries to have an additional innertokenmapping tag for
"add_rendition_properties" token in it as follows.
<InnerProfile path="/System/Media Server/System Profiles/document_to_pdf"
110
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Troubleshooting
waitOnCompletion="true" useTargetFormat="true">
..
..
<InnerTokenMapping LocalProfileToken="false" InnerProfileToken=
"add_rendition_properties" Literal="true"/>
</InnerProfile>
If LocalProfileToken is set to false, properties will NOT be added to the rendition. The default
value will be true. If the tag is missing or if the value is "true" properties will be added. If the user
has only VERSION permission, set this attribute value to "false" so that at least the renditions will
be created as in previous versions.
3.
Check in the legacy_to_pdf system profile.
Transparency in PNG renditions lost for Illustrator files
PNG renditions made from AI files lose their transparency when using Content Transformation
Services.
For example, backgrounds lose their transparency and appear as white when the images appear on a
webpage that has a non-white background color.
To maintain an image’s transparency remove the -flatten option from the profile command line file.
Preserving ICC profiles during transformations
To allow Content Transformation Services to preserve the ICC profile associated with ICC-aware files
(for example, Photoshop files), remove the following from the Command Line file generating the
desired rendition(s):
-strip and +profile icc -profile "doc_token_cmyk_profile" -profile "doc_token_rgb_profile"
Text wrapping problems with large double byte
characters
When double-byte characters are entered and given a large font size using the Add Text profile, some
of the text is lost as it does not wrap.
Embedding metadata for date datatype other than
default
If you want to embed metadata to content for a date datatype and you want to specify a date
format other than the default which is MM/dd/YYYY HH:mm:ss, add an attribute dateFormat to
the MetadataMapper line in the embedMetadataToContent.xml command line file specifying the
format to use. For example:
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
111
Troubleshooting
<MetadataMapper name="date_created" value="cch_photo.date_created" datatype="date"
dateFormat="yyyy-MM-dd" token="doc_metadata_date_created"/>
where cch_photo is the custom type created and date_created is the attribute for the cch_photo type.
Troubleshooting storyboard issues generated by the
PDFStoryboard plugin
When you attempt to use the PDFStoryboard plugin to generate storyboards from PDFs that contain
image content only, which were generated by the Doc6 plugin, it is seen that the images do not
have content, and are blank.
Hence, it is recommended that you use the Image3 plugin to generate storyboards, since the
PDFStoryBoard plugin cannot produce images at a resolution higher than 96 dpi.
Resolving issues with email content containing double
byte characters
When you import emails with double byte characters in the subject, content, and attachment names, it
is seen that in the subject and attachment names, the double byte characters are corrupted and appear
as "???”. For the renditions to be created without character corruption, it is recommended that you
install Arial Unicode MS font on the Content Transformation Services server machine.
Performance degradation due to add_rendition_
properties settings
You may observe a degradation in performance when add_rendition_properties is set to "true” for
profiles. To improve performance, add the following inner token mapping to the inner profiles:
<InnerTokenMapping Literal="true" InnerProfileToken="add_rendition_
properties" LocalProfileToken="false"/>
If the tag is missing or if the value is set to "true”, properties will be added.
112
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Appendix A
Formats supported by Advanced
Document Transformation Services
Table 10. Capabilities Supported for Document Formats
Creates
Storyboard*
Creates LowResolution
Rendition*
Format
Creates
Thumbnail*
BMP
Y
DOC, DOCX
Y
Y
Y
DOT, DOTX
Y
Y
Y
Writes XMP
to Content
Extracts XMP
from Content
Y
Y
Y
EML
Y
HTML
Y
Y
Y
GIF
Y
Y
JPEG
Y
Y
MSG
Y
Y
Y
OTT
Y
Y
Y
ODS
Y
Y
Y
ODT
Y
Y
Y
PDF
Y
Y
Y
PNG
Y
Y
Y
POT, POTX
Y
Y
Y
PPT, PPTX
Y
Y
Y
PS
Y
Y
Y
RTF
Y
Y
Y
TIFF
Y
Y
Y
Y indicates that the capability is supported for the format.
* Thumbnail, storyboard, and low-resolution renditions are not available out of the box. Some
configuration is required.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
113
Formats supported by Advanced Document Transformation Services
Creates
Thumbnail*
Creates
Storyboard*
Creates LowResolution
Rendition*
TIFF
(multipage)
Y
Y
Y
POT, POTX
Y
Y
Y
PPT, PPTX
Y
Y
Y
XHTML
Y
Y
Y
XLS, XLSX
Y
Y
Y
XLT, XLTX
Y
Y
Y
Format
Writes XMP
to Content
Extracts XMP
from Content
Y indicates that the capability is supported for the format.
* Thumbnail, storyboard, and low-resolution renditions are not available out of the box. Some
configuration is required.
Table 11. Document Transformations Supported for Source and Target Formats
Source Format
Target Format
BMP
PDF, PDF/A, PDF/X
GIF
PDF, PDF/A, PDF/X
JPEG
PDF, PDF/A, PDF/X
TIFF (single and multi-page)
PDF, PDF/A, PDF/X
PNG
PDF, PDF/A, PDF/X
EPS
PDF, PDF/A, PDF/X
HTML
PDF, PDF/A, PDF/X,PS, PDF TEXT
PDF
PDF, PDF/A, PDF/X,HTML,PS, PDF TEXT
PS
PDF, PDF/A, PDF/X, PDF TEXT
RTF, TXT
PDF, PDF/A, PDF/X,HTML,PS, PDF TEXT
MSG
PDF, PDF/A,TXT
EML
PDF, PDF/A,TXT
OTT, ODS, ODT
PDF, PDF/A, PDF/X
XLS, XLT, XLSX, XLTX
PDF, PDF/A, PDF/X,HTML,PS, PDF TEXT
DOC, DOT, DOCX, DOTX
PDF, PDF/A, PDF/X,HTML,PS, PDF TEXT
114
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Formats supported by Advanced Document Transformation Services
Source Format
Target Format
POT, POTX(12,14), PPTX(12,14)
PDF, PDF/A, PDF/X,PS, PDF TEXT
PPT
PPS, PDF, PDF/A, PDF/X,PS, PDF TEXT
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
115
Formats supported by Advanced Document Transformation Services
116
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Appendix B
Formats supported by Media
Transformation Services
Table 12. Capabilities for Supported Media Image Formats
Input
Format
Create
Thumbnail
and LowResolution
Rendition
AI
Y
BMP
Y
CR2
Y
DNG
Y
EPS
Y
FPX
Y
Y
GIF
Y
Y
JPEG
Y
Y
JPEG2000
Y
Y
Y
PCD
Y
Y
Y
PCX
Y
Y
Y
PGM
Y
PNG
Y
Y
PNM
Y
Y
PPM
Y
PSD
Y
Y
SCT
Y
Y
Y
SGI
Y
Y
Y
SVG
Y
Y
Extract
Properties
Write XMP
to Content
Extract
XMP from
Content
Extract
EXIF
Metadata
Y
Resize
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y indicates that the capability is supported for the format.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
117
Formats supported by Media Transformation Services
Input
Format
Create
Thumbnail
and LowResolution
Rendition
Extract
Properties
TGA
Y
Y
TIFF
Y
Y
WBMP
Y
Y
WMF
Y
Write XMP
to Content
Extract
XMP from
Content
Extract
EXIF
Metadata
Resize
Y
Y
Y
Y
Y
Y
Y
Y indicates that the capability is supported for the format.
Table 13. Media Transformations Supported for Source and Target Formats
Source Format
Target Format
AI [1]
BMP, GIF, JPEG, JPEG2000, PBM, PGM, PNG,
PNM, PPM, PSD, TIFF, WBMP
BMP
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA,
CR2
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, JPEG2000
DNG
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, JPEG2000
EPS [1]
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, JPEG2000,
WBMP
FPX
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, JPEG2000, WBMP
GIF
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, JPEG2000,
WBMP
JPEG
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, JPEG2000,
WBMP
JPEG2000
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, WBMP
PDF [1]
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, JPEG2000, WBMP
Note:
1.
Content Transformation Services requires that the latest version of GhostScript be installed in
order to perform transformations where the source or target format is AI, EPS, or PDF.
2.
When performing a transformation in which PSD (Photoshop) is both the source and target
format (PSD to PSD), all of the layers are flattened.
118
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Formats supported by Media Transformation Services
Source Format
Target Format
PGM
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, JPEG2000, WBMP
PNG
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, JPEG2000,
WBMP
PNM
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, JPEG2000, WBMP
PPM
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, JPEG2000, WBMP
PSD [2]
PSD, JPEG, GIF, PNG, TIFF, BMP, PNM, PGM,
PPM, PBM, PCX, TGA, SGI, SCT, JPEG2000,
WBMP
SCT
PSD, JPEG, GIF, TIFF, BMP, PCX, TGA, SGI, SCT,
JPEG2000
SVG
PSD, JPEG, GIF, PNG, TIFF, BMP, SVG, PNM,
PGM, PPM, PBM, WBMP,JPEG2000
SGI
PSD, JPEG, GIF, TIFF, BMP, PCX, TGA, SGI, SCT,
JPEG2000
TIFF
PSD, JPEG, GIF, PNG,TIFF, BMP, PNM, PGM,
PPM, PBM, WBMP,JPEG2000
WBMP
PSD, JPEG, GIF, PNG,TIFF, BMP, PNM, PGM,
PPM, PBM, WBMP,JPEG2000
WMF
JPEG, GIF, PNG, TIFF, BMP, PNM, PGM, PPM,
PBM, PCX, TGA, SGI, SCT, JPEG2000, WBMP
Note:
1.
Content Transformation Services requires that the latest version of GhostScript be installed in
order to perform transformations where the source or target format is AI, EPS, or PDF.
2.
When performing a transformation in which PSD (Photoshop) is both the source and target
format (PSD to PSD), all of the layers are flattened.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
119
Formats supported by Media Transformation Services
120
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Appendix C
Formats supported by Audio/Video
Transformation Services
Table 14. Capabilities Supported for Audio and Video Formats
Creates
Thumbnail
Creates
Storyboard
Creates
Default
Rendition
Extracts
Properties
3G2
Y
Y
Y
Y
3GP
Y
Y
Y
Y
ASF
Y
Y
Y
Y
AVI
Y
Y
Y
Y
DV
Y
Y
Y
Y
F4V
Y
Y
Y
Y
FLV
Y
Y
Y
Y
GXF
Y
Y
Y
Y
LXF
Y
Y
Y
Y
M4V
Y
Y
Y
Y
MPEG
Y
Y
Y
Y
MPEG2
Y
Y
Y
Y
MPEG-4
Y
Y
Y
Y
MSS
Y
Y
Y
Y
QuickTime
Y
Y
Y
Y
RM
Y
Y
Y
Y
Format
Streamable*
Video Formats
Y
Y indicates that the capability is supported for the format.
*A properly configured Streaming Server and a client are required. For more information, see
your product documentation.
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
121
Formats supported by Audio/Video Transformation Services
Format
Creates
Thumbnail
Creates
Storyboard
Creates
Default
Rendition
Extracts
Properties
Streamable*
WMV
Y
Y
Y
Y
Y
WebM
Y
Y
Y
Y
MP3
Y
Y
WAV
Y
Y
WMA
Y
Y
Audio Formats
Y indicates that the capability is supported for the format.
*A properly configured Streaming Server and a client are required. For more information, see
your product documentation.
Table 15. Audio and Video Transformations Supported for Source and Target Formats
Source Format
Target Format
Video
3G2
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
3GP
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
ASF
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
AVI
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
FLV
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
F4V
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
DV
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
GXF
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
122
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Formats supported by Audio/Video Transformation Services
Source Format
Target Format
LXF
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
M4V
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
MPEG
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
MPEG2
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
MPEG-4
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
MSS
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
Quicktime
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
RM
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
WebM
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
WMV
3GP, 3GP2, AVI, DV, F4V, FLV, GXF, M4V, MPEG-4, MP3,
QuickTime, MPEG, MPEG2, WAV, WMA, WMV, MXF, RM,
WebM
Audio
MP3
3GP, 3GP2, AVI, F4V, FLV, M4V, MPEG-4, MP3, QuickTime,
MPEG, MPEG2, WAV, WMA, WMV, RM, WebM
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
123
Formats supported by Audio/Video Transformation Services
Source Format
Target Format
WMA
3GP, 3GP2, AVI, F4V, FLV, M4V, MPEG-4, MP3, QuickTime,
MPEG, MPEG2, WAV, WMA, WMV, RM, WebM
WAV
3GP, 3GP2, AVI, F4V, FLV, M4V, MPEG-4, MP3, QuickTime,
MPEG, MPEG2, WAV, WMA, WMV, RM, WebM
124
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Appendix D
Audio and Video Codecs
Table 16. Audio and Video Codecs Supported for Input Formats
Format
Video Codec
Audio Codec
FLV
Flash 8/VP6
MP3
FLV
Flash Screen Video
MP3
H264/AVC
PCM
Flash Video (Sorenson Spark)
AAC-LC
F4V
AVC
AAC-LC
WMA
–
Windows Media Audio 9.2
WMA V9 Pro
WMA V9 Voice
WAVE
–
PCM
PCM A-law
PCM mu-law
MP3
–
MPEG1 Layer3
MPEG2 Layer3
3GP/3G2
H.264/AVC
AAC-LC
MPEG-4
AMR - NB
H.263
MPEG4
AAC-LC
H.263
AMR
H.264
MP3
WebM
VP8
Vorbis
MSS
MPEG2
MPEG1 Layer2
MP4
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
125
Audio and Video Codecs
Format
Video Codec
M4V
MPEG4
H.263/AVC
Audio Codec
AAC-LC
H.263/AVC Intel
MXF
MPEG2
DVCPRO/DV
PCM
XDCAM HD
D-10 MPEG2 30/40/50
GXF
MPEG2
PCM
DV25/50
LXF
MPEG2
PCM
DV
DV25/50
PCM
DVCPRO25/50
MPEG1
MPEG2
AVI
MPEG1
MPEG1 Layer2
MPEG2
MPEG1 Layer3
MPEG2 [email protected]
Dolby5.1 AC3
MPEG2 4:2:2
MPEG1 Layer2
H.264/AVC
PCM
Intel I.263/H.263
MS ADPCM
IBM Motion JPEG
MP3
Intel Indeo iYUV 4:2:0
Intel ADPCM
Microsoft Video 1
MS CCITT A-Law
XviD MPEG-4 Video
MS CCITT U-Law
Uncompressed AVI Stream
FFmpeg MPEG-4
FFmpeg MPEG 1/2
AVI
Cinepak Radius
PCM
MP3
MS CCITT A-Law
MS CCITT U-Law
126
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Audio and Video Codecs
Format
Video Codec
Audio Codec
AVI
Huffman Lossless
PCM
MS ADPCM
MP3
Intel ADPCM
MS CCITT A-Law
MS CCITT U-Law
MS GSM 6.10
MPEG Audio layer2
WMV
ASF
WM V7
PCM
WM V8
Windows Media Audio 9.2
WM V9
WMA V9 Pro
WM9 VC-1
WMA V9 Voice
WM V7
Windows Media Audio 9.2
WM V8
WMA V9 Pro
WM V9
WMA V9 Voice
WM9 VC-1
QuickTime
H.264/AVC
AMR
Sorenson 1
A-law
U-law
MP3
AAC-LC
QuickTime
Sorenson 1
MACE 3:1
Sorenson3
MACE 6:1
Cinepak Radius
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
127
Audio and Video Codecs
Format
Video Codec
Audio Codec
QuickTime
Uncompressed
AAC-LC
AVID ABVB
PCM
AVID Meridian Interlaced
QDesign Music 2
AVID Meridian progressive
QualcommPureVoice
AVIDNuVista
Cinewave 8Bit YUV
MotionJPEG A
MotionJPEG B
MPEG4 Video
PhotoJPEG
Sorenson3
Cinepak Radius
H264/AVC
QuickTime
IMX30/40/50
PCM
DV25/50
DVCPRO25/50
DVCPRO HD
DNxHD
ProRes/ProResHQ
Table 17. Audio and Video Codecs Supported for Output Formats
Format
Video Codec
Audio Codec
AVI
Microsoft MPEG-4 V3
PCM
H.264/AVC
Raw Video (RAW I420)
Microsoft Video1
H.263
DV
DV 25
PCM
F4V
H.263
MPEG1 Layer3
128
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Audio and Video Codecs
Format
Video Codec
Audio Codec
FLV
Sorenson Spark
MPEG1 Layer3
MP4
MPEG4 Video
AAC-LC
H.264/AVC
MPEG1
MPEG1
MPEG1 Layer3
QuickTime
DV 25
PCM
QuickTime
Raw video (I420)
PCM
Sorenson Video 1
AAC-LC (MPEG4 Audio)
MPEG-4
H.264/AVC
Photo JPEG
WMV
Windows Media Video 8
(wmv2)
WMA2
WMA1
Windows Media Video 7
(wmv1)
MP3
–
MPEG1 Layer3
MPEG2 Layer3
WAV
–
PCM
WMA
–
WMA2
WMA1
3GP/3G2
H.264/AVC
AAC-LC
MPEG-4
AMR – Narrow Band
H.263
AMR- Wide Band
M4V
H.264/AVC
AAC-LC
MPEG2
MPEG2 [email protected]
MPEG2.5 Layer3
MPEG2 4:2:2
GXF
MPEG2 4:2:2
PCM
DV
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
129
Audio and Video Codecs
Format
Video Codec
Audio Codec
MXF
D-10 MPEG2 30/40/50
PCM
WebM
VP8
Vorbis
130
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Index
A
Admin password, changing, 26, 43
Advanced Document Transformation
Services
architecture, 14
description, 12
environment, 14
how it works, 12
architecture, 14, 16 to 17
attributes, 34
content_attr_name, 22
content_attr_value, 22
mapping syntax examples, 86
passing to plug-ins, 84
transferring from document to PDF, 84
viewing in PDF renditions, 86
audio
capabilities, 121
codecs, 125, 128
formats, 122
audio transformations
supported, 122
Audio/Video Transformation Services
architecture, 17
components, 17
environment, 17
general description, 17
plug-ins, 18
B
batch files, 26
BOCS
configuring, 53
C
caching configuration, 51
checked out documents, 13
checked out files, 11
codecs
audio and video, 125, 128
command-line files, 104
configuration objects, 85
configuring
caching, 51
changing login user name, 25
changing the logging level, 25
changing the maximum number of
queue items, 26
changing the notification setting, 25
changing the polling interval, 25
changing the queue item expiry, 26
changing the repository, 31
changing the system operator, 25
CTS for BOCS, 53
CTS load balancer, 55
CTS products using Configurator, 31
for distributed environment, 52
queue pre-processor, 49
repository, 31
configuring Streaming Server, 34, 36 to 37
Content Server
integrating Streaming Servers, 32
setting up storage areas, 33
storage of low-resolution
renditions, 21
Content Transformation Monitor
Services, 30
Content Transformation Services
configuring application timeouts, 50
description, 11
error message, 106
fails to function, 106
integrating Streaming Servers, 32
content_attr_name attribute, 22
content_attr_value attribute, 22
creating
PDF renditions, 78
storyboard renditions on import, 78
thumbnail renditions on import, 78
CTS
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
131
Index
file formats, 39
files, checked out, 11
format mapping table, 78
formats
codecs, audio and video, 125, 128
document transformations,
supported, 114
media transformations, supported, 118
rich media enabling, 78
D
G
default_storage, 34
details of a CTS instance, viewing, 26
distributed environment
configuring, 52
dm_document object, 21
dm_mediaserver_error, 103
dm_queue, 13
dm_register_asset, 19
dmi_queue_item object, 19
dmr_content object, 22
document
capabilities, 113
document transformations
supported, 114
documents, checked out, 13
Documentum Administrator
administrative tasks, 25
configuration tasks, 25
Create New Format Object page, 39
defining file formats, 39
Documentum format mapping, 78
DOS extensions, 39
generating
low-resolution renditions, 21
storyboards, 21
thumbnails, 20
Global Registry
CTS product, 106
E
embed_metadata setting, 82
endpoints, 97
errors, 103 to 105
log files, 26
receiving, 25
with plug-ins, 103
events, dm_mediaserver_error, 25, 103
extracting
media properties, 21
XMP metadata, 22
132
F
starting, 30
stopping, 30
CTS Admin Agent, 26
CTS Reporting Tool, 44
disable, 44
enable, 44
viewing reports, 45
CTS Service
changing user, 41
CTS_Log.txt, 103
H
HTML renditions, 12 to 13
HyperText Markup Language. See HTML
renditions
I
Inbox notifications, 25, 103 to 104
changing in DA, 25
configuring, 39
instance details, viewing, 26
K
Kerberos, 63
L
load balancing, 55
configuring, 55
local content
prioritizing, 52
locked
files, 11
locked documents. See documents, checked
out
log files, 103
viewing, 26
log in, 105
log4j.properties
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Index
setting appenders, 51
logging appenders
setting, 51
logging level
changing, 25
login user, identifying, 25
login_ticket attribute, 86
low-resolution renditions
generating, 21
storing, 21
supported file formats, 21
M
media image
capabilities, 117
media properties
examples of, 22
extracting, 21
storing, 22
Media Transformation Services
architecture, 16
components, 16
environment, 16
general description, 16
plug-ins, 16
media transformations
supported, 118
metadata, 22
modifying
register.xml, 78 to 80
monitor services, 30
multiple servers, 55
password, changing in Documentum
Administrator, 26
PDF
files, viewing repository attributes, 86
metadata, storing, 82
PDF renditions, 13
PDT files
saving, 81
plug-ins
Audio/Video Transformation
Services, 18
description, 15
errors, 103
passing attributes to, 84
prerequisites, 18
processing, 19, 21
standard, 15
polling interval, changing, 25
Portable Document Format. See PDF
PowerPoint objects, 21
processing files, 19
profiles, 104
Q
queue
managing, 46
queue items
changing the expiry, 26
changing the maximum number
allowed, 26
queue pre-processor
manage queue item, 49
N
R
notifications
changing in Documentum
Administrator, 25
configuring, 39
refreshing server, 26
register.xml, modifying, 78 to 80
registration
description, 18
extracting media properties, 21
generating low-resolution
renditions, 21
generating storyboards, 21
generating thumbnails, 20
XMP metadata, 22
renditions, 105
low-resolution, 21
storage of, 21
storyboard, 21
O
objects, 13 to 14
dm_document, 21
dmr_content, 22
overwriting renditions, 83
P
password, changing, 43
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
133
Index
thumbnail, 20
repeating attributes, 86
replacing previous renditions, 83
repository, 105
adding, 31
changing, 31
config object, 85
removing, 31
request
transcode_content, 23
rich media enabling formats, 78
S
saving
PDT files, 81
sentby attribute, 86
separators, 86
server
multiple, 55
refreshing, 26
starting, 26
stopping, 26
setting up Streaming Server, 33
settings
embed_metadata, 82
logging appenders, 51
storePDTRendition, 81
single sign-on, 63
source documents, 39
starting, 26
Content Transformation Services
products, 30
stopping, 26
Content Transformation Services
products, 30
storage areas
setting up for Streaming Servers, 33
storePDTRendition setting, 81
storing
PDF metadata, 82
storyboards
generating, 21
multi-page documents, 21
timecode, 21
Streaming Server, 34, 36 to 37
integration, 32
integration prerequisites, 32
setting up storage areas, 33
setup procedure, 33
134
system architecture, 14, 16 to 17
system operator user, identifying, 25
T
Thumbnail Server
storing thumbnails, 21
thumbnails
for slides, 21
generating, 20
storing, 21
timecodes, video, 21
timeout interval, 50
transcode_content request, 23
transferring document attributes to
PDF, 84
transformation
automated, 18
failure, 104
performing, 22
process, 22
profiles, 23, 104
user requested, 22
Transformation node, 46
Transformation queue
changing queue priority, 47
configuring queue management
fields, 49
deleting queue item, 48
managing, 46
viewing details of queue item, 47
viewing transformations, 46
troubleshooting, 104
with log files, 26
U
username attribute, 86
users, changing
for CTS Service, 41
for repository login, 25
system operator, 25
V
video
capabilities, 121
codecs, 125, 128
formats, 122
video transformations
supported, 122
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
Index
W
WebServices activity, 97
X
extracting, 22
Z
Zip files, 14
XMP metadata
EMC Documentum Content Transformation Services Transformation Suite Version 7.1 Administration Guide
135
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement