Vous êtes sur la page 1sur 43

EMC® Documentum®

XML Transformation Services


Version 6.5

Release Notes
P/N 300-007-275 A01

EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright © 2007–2008 EMC Corporation. All rights reserved.
Published July 2008
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.
All other trademarks used herein are the property of their respective owners.

Revision History
July 2008: Initial publication for version 6.5 product release.
Table of Contents

Chapter 1 Product Description .............................................................................. 7


Features of XML Transformation Services .................................................... 7
Supported transformations by source and target formats .............................. 8
Supported XML standards .......................................................................... 9

Chapter 2 New Features and Changes ................................................................... 11


New features and changes for version 6.5 ..................................................... 11
Transformation and Profile web services .................................................. 11
Transformation web service................................................................. 11
Profile web service .............................................................................. 12
Enhanced real-time architecture .............................................................. 12
Additional outputs for DITA transformations ........................................... 12
Additional resolution renditions for graphic files ...................................... 12
Support for IPv6 environment ................................................................. 13

Chapter 3 Fixed Problems ..................................................................................... 15


Chapter 4 Environment and System Requirements ............................................... 17
Hardware requirements .............................................................................. 17
Software requirements ................................................................................ 18
XML Transformation Server requirements ................................................ 18
Rendering applications for supported source formats ............................... 19
Supported deployment scenarios for version 6.5 ........................................... 20
Supporting dual-stack operation (IPv4 or IPv6) ............................................ 20

Chapter 5 Known Problems and Limitations ......................................................... 23


Known problems ........................................................................................ 23
Strings not localized in the CTS Parameters tab – Russian/
Brazilian Portuguese (165304) .................................................................. 23
Configurator does not restart JBoss appServer (164380) ............................. 23
ctsTransform.jar not deleted after un-installing ctsActivity in
content server (164286)............................................................................ 24
The ctsActivity installer unable to restart the MethodServer
properly (164282).................................................................................... 24
Unable to install 6.5 CTS DAR against 5.3 SP6 global repository
(163088) ................................................................................................. 24
Start/Stop menu not enabled/disabled according to the CTS
instance (163325) .................................................................................... 24
Cannot configure a CTS instance as config files are not read
(150193) ................................................................................................. 25
Change user fails with an invalid response from the agent (150364) ............ 25
Option to view log files is not available (150185) ....................................... 25
CTS fails to start when configured against the global registry
(150077) ................................................................................................. 25

EMC Documentum XML Transformation Services Version 6.5 Release Notes 3


Table of Contents

ProfileSchema.dtd is not checked out to the proper location


(149930) ................................................................................................. 26
Login fails for users in trusted domains (149405) ...................................... 26
PDF created as new object created within a folder that contains
a random number for a name (149863) ..................................................... 26
ZIP_HTML file transformations are created within a folder that
contains a random number for a name (149882) ........................................ 26
Commented lines in config files are removed when a CTS
Configurator is run (106390) .................................................................... 26
Configuration by SuperUser will fail if user_os_name is blank
(112591) ................................................................................................. 27
CTS Admin Agent prevents CTS_log.txt from archiving (127418)............... 27
Ditamap transformations fail if path includes extended or
double-byte characters (144403) ............................................................... 27
Limitations................................................................................................. 27
Profile description limited up to 192 bytes ................................................ 28
DITAMAP document transformation fails due to spaces in
directory path (161399) ........................................................................... 28
Spaces in DITAMAP file names cause CHM transformations to
fail (137384) ............................................................................................ 28
Non-standard characters appear in output due to browser
settings (137389) ..................................................................................... 29

Chapter 6 Technical Notes ..................................................................................... 31


Confirming beginning of profile migration dialog box .................................. 31
Viewing log file of migrated profiles ........................................................ 32
Checking the version of a CTS product installer ............................................ 33
Manual re-configuration of XTS instance if the repository is deleted .............. 33
Configuring XTS to interact with Documentum Compliance
Manager objects in a repository ................................................................... 35

Chapter 7 Documentation ...................................................................................... 37


XML Transformation Services documentation set ......................................... 37
Obtaining the correct documentation ........................................................... 37

Chapter 8 Software Media, Organization, and Files ............................................... 39


Software Media .......................................................................................... 39
Organization .............................................................................................. 39
Files ........................................................................................................... 39

Chapter 9 Installation ............................................................................................. 41


Chapter 10 Troubleshooting and Getting Help ........................................................ 43

4 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Table of Contents

List of Figures

Figure 1. Profile Migration Process Confirmation Dialog Box .......................................... 32

EMC Documentum XML Transformation Services Version 6.5 Release Notes 5


Table of Contents

List of Tables

Table 1. XML Transformation Services features ............................................................. 7


Table 2. Supported transformations with XML Transformation Services by
source and target formats ............................................................................ 8
Table 3. XML standards supported by XTS ................................................................... 9
Table 4. XML Transformation Services host hardware requirements ............................... 17
Table 5. XML Transformation Services host software requirements ................................ 19
Table 6. Rendering applications for supported source formats ....................................... 20

6 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 1
Product Description

XML Transformation Services is server software that generates copies of documents in Portable
Document Format (PDF), HyperText Markup Language (HTML), and Compiled HTML Help
(CHM). You can use Documentum client applications to request a rendition of a document stored in
a Documentum repository.
Designed primarily for technical publication organizations, XML Transformation Services is part of a
seamless approach to storing, managing, and transforming XML, DITA, and DITAMAP content.

Features of XML Transformation Services


The following are the features that XML Transformation Services offers.

Table 1. XML Transformation Services features

Feature Comments
Runs as a Windows Service and
intelligently handles exceptions raised
by native applications.
Transforms XML, DITA, and XML source files in DITA and DocBook
DITAMAP files into PDF, HTML, standards are supported.
ZIP*, Compiled HTML Help (CHM);
Eclipse Help**, Java Help**, RTF**,
DocBook.**
Transform XML to PDF. The target output is PDF only.
Filters the output based on a variety By default, filters for operating systems,
of parameters. audience levels, revisions, and product names
are available. These filters are configurable.
See for details.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 7


Product Description

Feature Comments
Creates a new rendition each time a
file is transformed.
Transforms a document as part of a CTS Activity Template is included. Profile
business workflow process using the configuration required. See for details. See
CTS Activity Template. XML Transformation Services Installation Guide
for installation instructions.
Integrates with entire Documentum
product suite.
* ZIP output is valid for DITA source files only.
**Output is valid for DITAMAP source files only.

Supported transformations by source and


target formats
The supported transformations are dependent upon the installation of a variety of
applications on the XML Transformation Server, as detailed in Table 6, page 20.
With the required supporting applications installed, XML Transformation Services can
perform the following transformations.

Table 2. Supported transformations with XML Transformation Services by source and


target formats

Source format (input) XML standard Target formats


(output)
XML DITA PDF, HTML, ZIP
DocBook PDF, HTML,
Compiled HTML
Help (CHM)
XML XML Schema PDF
DITA DITA PDF, HTML, ZIP
DITAMAP DITA PDF, HTML,
Compiled HTML
Help (CHM), Java
Help, Eclipse Help,
RTF, and DocBook

8 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Product Description

Supported XML standards


The following XML standards are supported out of the box.

Table 3. XML standards supported by XTS

XML standard Supported version


DITA 1.1
DocBook 4.5

EMC Documentum XML Transformation Services Version 6.5 Release Notes 9


Product Description

10 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 2
New Features and Changes

This section gives an overview of the enhancements and added functionality for Content
Transformation Servicesversion 6.5.

New features and changes for version 6.5


The following new items apply:
• Transformation and Profile web services, page 11
• Enhanced real-time architecture, page 12
• Additional outputs for DITA transformations, page 12
• Additional resolution renditions for graphic files, page 12
• Support for IPv6 environment, page 13

Transformation and Prole web services


Content Transformation Services web services provide an interface to CTS transformation
capabilities with transform request and profile management features.

Transformation web service

The Transformation web service enables applications to request transformations from


the CTS suite of products in both synchronous and asynchronous modes. For further
information regarding the Transformation web service, see XML Transformation Services
Administration Guide and EMC Documentum Enterprise Content Services Reference guide.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 11


New Features and Changes

Prole web service

The Profile web service enables applications to access available transformation profiles
using various filtering mechanisms, as well as to update them if suitable permissions
are held by the application session. For further information regarding the Profile web
service, see XML Transformation Services Administration Guide and EMC Documentum
Enterprise Content Services Reference guide.

Enhanced real-time architecture


The CTS framework provides a real-time response to a transformation request. All
transformations requests that come in through the web service interface in synchronous
mode are sent directly to the CTS server without being placed in the Content Server’s
CTS queue. This improves the throughput of synchronous requests.

Additional outputs for DITA transformations


XML Transformation Services supports additional outputs for DITA transformations,
namely, Java Help, Eclipse Help, RTF, and Docbook. See XML Transformation Services
Administration Guide for additional information.

Additional resolution renditions for graphic les


XML Transformation Services replaces the graphic linked to an XML content with an
image of different resolutions according to the output format. See XML Transformation
Services Administration Guide for additional information.

12 EMC Documentum XML Transformation Services Version 6.5 Release Notes


New Features and Changes

Support for IPv6 environment


Media Transformation Services supports Internet Protocol version 6 (IPv6) in dual mode
(IPv4 & IPv6). For version 6.5, IPv4 and IPv6 addresses can co-exist in the same device.
See Environment and System Requirements chapter.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 13


New Features and Changes

14 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 3
Fixed Problems

Within two weeks of the release, a more comprehensive list of the fixed problems in the release will
be posted on the Powerlink website (http://powerlink.EMC.com)

To view the list of xed problems:


1. Log into the Powerlink website.
You must have a software support agreement to log in and access the list of fixed
bugs.
2. From the Powerlink menu bar, select Support > Knowledgebase Search >
Documentation and White Papers Search.
The Knowledgebase Search screen appears.
3. In the Search For text box, enter Fixed.
4. From the Select Document Type(s) drop-down list, select FIXED BUGS LIST.
5. Select the product whose fixed problems you want to view.
a. Select Software from the Product Type drop-down list.
b. Select Content from the Product Family drop-down list.
c. Select the product name from the Product drop-down list.
d. Select the product version number from the Version drop-down list.
6. Click the Search button.
7. Scroll to the bottom of the page and select the fixed problems document from the list
of search results.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 15


Fixed Problems

16 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 4
Environment and System Requirements

This chapter lists the hardware (machine) requirements, software prerequisites, host requirements,
and software versions supported with this release of XML Transformation Services.
To take advantage of the full feature set of XML Transformation Services and to ensure the application
works properly, the XML Transformation Server must run the software specified in this section. The
client must supply the operating system and rendering products; all other prerequisites are bundled
with the XML Transformation Services installer.
This chapter contains the following sections:
• Hardware requirements, page 17
• Software requirements, page 18

Hardware requirements
Table 4, page 17 lists the hardware and configuration requirements for the XML
Transformation Services host.

Table 4. XML Transformation Services host hardware requirements

Requirements Details
Minimum hardware • Pentium 4, 1 GHz PC or better
• At least 1 GB of RAM for file manipulation.
Required RAM is twice the size of the largest
expected file to process. For example, if the largest
file expected is 1 GB, then XML Transformation
Server requires at least 2 GB RAM.
• Approximately 10 GB of hard disk space for
caching files (may depend on the type of files you
work with and expected number of concurrent
users)

EMC Documentum XML Transformation Services Version 6.5 Release Notes 17


Environment and System Requirements

Requirements Details
• 100bTX network card (or equivalent, depending
on network type)
The PC must also satisfy the minimum hardware
requirements for the operating system.
Configuration restrictions To ensure optimal system performance:
• XML Transformation Server should not be installed
on the same host as Content Server or the FAST
(Full Text Index) Server.

This configuration is not supported by Documentum.


Networking protocols TCP/IP, using the TCP/IP stack included with
Windows.

Software requirements
This section provides information on prerequisites and supported software
environments. Software must be installed, configured, and running properly on your
network before you install XML Transformation Server.
The tables in this section reflect the latest versions of third-party products that
are supported at the time of this release. For information on currently supported
environments and future updates, refer to Product Information on the Powerlink site
(http://powerlink.emc.com) at Support > Interoperability/Compatibility/Configuration
> Product Information.
For detailed information about the policies governing supported products, refer to the
Customer Guide available on the Powerlink site (http://powerlink.emc.com) at Support >
About EMC Customer Service > Software Customer Guide.

XML Transformation Server requirements


Table 5, page 19 specifies the supported operating systems, Documentum software, and
Microsoft components required for running XML Transformation Services.

18 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Environment and System Requirements

Table 5. XML Transformation Services host software requirements

Component Certified software Certification details


Operating Windows Server 2003 R2 with XML Transformation Services is
system* SP2 (32-bit version), Windows supported on English operating
Server 2003 SP2 (32-bit version) systems only.

On English operating systems,


XML can accept content in
single-byte character languages.
EMC Documentum Content Server Must be installed on a separate
Documentum 5.3, 5.3 SPx, 6, 6 SP1, 6.5 host.
products Documentum Foundation Installed with XML
Classes (DFC) 6.5 Transformation Server.
JRE Sun Java SDK 1.5.0_12 Internally packaged with DFC.
Rendering See Rendering applications for
applications supported source formats, page
19.
* Includes virtualized version of operating system running in any version of VMware
Intel-architecture (VMware ESX Server, GSX Server and Workstation).

Caution: To operate any one component of Content Transformation Services 6.5


products (ADTS, DTS, MTS, AVTS, and XML), all of the Content Transformation
Services components must also be at release 6.5. For example, if you upgrade
from Media Transformation Services 5.3 SP4 to 6.5, you must also upgrade other
Content Transformation Services components (for example, Advanced Document
Transformation Services 5.3 SP4) to 6.5. Failure to do so results in errors in your
Content Transformation Services software.

Rendering applications for supported source formats


The supported transformations are dependent upon the installation of a variety of
applications on the XML Transformation Server host, as detailed in the following table.
Applications listed as mandatory must be installed on the host, regardless of whether
you are transforming files of the related source format or not. Without these mandatory
applications, XML Transformation Services will not function properly.
Applications listed as optional are only required if you are transforming files of the
related target.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 19


Environment and System Requirements

Documentum does not support manual upgrades to any software installed by the XML
Transformation Services installer.format.

Table 6. Rendering applications for supported source formats

Source formats Required Mandatory or Target format


rendering optional
applications*
DITA, DITAMAP, MS HTML Help Optional CHM
XML Workshop 4.74.8702

Supported deployment scenarios for version


6.5
The following deployment scenarios are supported in version 6.5 (see caveats below):
• 5.3x Content Server + 6x Global Registry + 6x Client
• 6x Content Server + 5.3x Global Registry + 5.3x Client
• 6x Content Server + 6x Global Registry + 6x Client
Under the heterogeneous deployment scenario (5.3x Content Server + 5.3x Client and 6x
Content Server + 6x Client), not all functionality may be available (e.g. you should not
expect to see 6.5 functionality). If you have both 5.3, 6.0 or 6.5 applications, you will need
to set up a 6.0 or 6.5 Global Registry AND a 5.3 Global Registry. You CANNOT have
both a 5.3 and 6.0 or 6.5 application unless they are talking to separate Content Servers.
Note: Regardless of whether the Content Server version is 5.3, 5.3 SPx, 6, 6 SP1 or 6.5,
WDK-based applications require the presence of a Content Server 6, 6 SP1, 6.5 global
registry repository in order to function properly.

Supporting dual-stack operation (IPv4 or IPv6)


EMC Documentum 6.5 now supports dual-stack operation (IPv4 or IPv6) in addition to
previously supported native IPv4 operation. Support for dual-stack operation enables
EMC Documentum 6.5 products to use the appropriate protocol (IPv4 or IPv6) when
communicating with 3rd party products and other EMC Documentum products.

20 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Environment and System Requirements

Content Transformation Services supports dual mode (IPv4 & IPv6). By default, XML
Transformation Services and Content Server are set to both sockets.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 21


Environment and System Requirements

22 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 5
Known Problems and Limitations

This section identifies problems and limitations that may affect your use of the product.
Note: This section and the Technical Notes section may refer to platforms or features that are
not supported for this release of your product. Check Chapter 4, Environment and System
Requirements to verify requirements.
EMC Documentum makes the latest information about customer-reported issues and known
problems are posted on the Powerlink website (http://powerlink.EMC.com). You must have a
software support agreement to log in and access the list of issues.

Known problems
This section identifies problems and limitations that may affect your use of the product.

Strings not localized in the CTS Parameters tab –


Russian/ Brazilian Portuguese (165304)
CTSActivity Template has unlocalized strings in the CTS Parameters tab.

Congurator does not restart JBoss appServer (164380)


Multiple repositories support with CTS WebServices fails. The configurator does not
restart the "EMC Documentum Content Transformation WebServices" windows service
The workaround is to manually restart the "EMC Documentum Content Transformation
WebServices" windows service after configuring each repository.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 23


Known Problems and Limitations

ctsTransform.jar not deleted after un-installing


ctsActivity in content server (164286)
The workaround is to manually uninstall ctsTransform.jar:

1. Stop the Java Method Server.


2. Manually remove ctsTransform.jar from: $DOCUMENTUM_SHARED/jboss4.2.0/
server/DctmServer_MethodServer/deploy/bpm.ear/bpm.war/WEB-INF/lib folder.

The ctsActivity installer unable to restart the


MethodServer properly (164282)
The ctsActivity installer is unable to restart Java Method Server upon completion of
installation process. The workaround is to restart the repository after installing the
ctsActivity.jar.

1. Stop and start the repository to stop all processes that are running related to Java
Method Server.
2. Start Java Method Server manually to load ctsTransform.jar properly:
Run startMethodServer.sh from $DOCUMENTUM_SHARED/jboss4.2.0/server in a
non-windows platform.

Unable to install 6.5 CTS DAR against 5.3 SP6 global


repository (163088)
Installation of 6.5 CTS DAR against 5.3 SP6 global repository using Headless Composer
fails.

Start/Stop menu not enabled/disabled according to the


CTS instance (163325)
When a particular CTS instance is running, the CTS admin agent does not do anything.
Start/Stop buttons are not disabled/enabled accordingly to usage.

24 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Known Problems and Limitations

Cannot congure a CTS instance as cong les are not


read (150193)
User is unable to configure a CTS instance and set configuration parameters with values
from the CTSServerService.xml file. All fields are blank or default to the first option in
the list. The workaround is to configure the parameters directly on the CTS server.

Change user fails with an invalid response from the


agent (150364)
Changing the main user, with a valid name and password, results in the following error:
"An invalid response was received from the agent”. The workaround is to change the
password through Digital Asset Manager or change the user through the CTS server.

Option to view log les is not available (150185)


User is unable to retrieve a log file of a CTS product after selecting the log file for
viewing. The workaround is to access the log files from the CTS server.

CTS fails to start when congured against the global


registry (150077)
CTS fails to start successfully when configured against a global registry and results in the
following error in the CTS_log.txt for all profiles:
com.documentum.cts.exceptions.internal.CTSProfileServiceException:
[DM_VEL_INSTANTIATION_ERROR]error: "Cannot instantiate Java class"
Cause Exception was: Exception during updating profile cache pdf_processing
The workaround is to manually run the Transformation and Rich_Media_Services DARs
against the global registry after configuring the CTS product.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 25


Known Problems and Limitations

ProleSchema.dtd is not checked out to the proper


location (149930)
When checking out a transformation profile, the ProfileSchema.dtd file is not checked
out to the correct location. The user can locate the file in the same location as the profile
is checked out to.

Login fails for users in trusted domains (149405)


If a user from domain B requests a rendition from a docbase that is in domain A with a
trust to domain B, the "getlogin API” will fail.

PDF created as new object created within a folder that


contains a random number for a name (149863)
A PDF transformation is created within a folder (with a random number for a name) in
the folder of the source document. The workaround is to have the DITA content "fixed”
before import by populating all peer link elements with the scope =’local’ attribute.”

ZIP_HTML le transformations are created within a


folder that contains a random number for a name
(149882)
An exported zipped HTML file transformation results in a folder with a random number
for a name. The workaround is to have the DITA content "fixed” before import by
populating all peer link elements with the scope =’local’ attribute.”

Commented lines in cong les are removed when a


CTS Congurator is run (106390)
Commented lines in configuration files are removed when a CTS configurator is run.
For example, you have installed Media Transformation Services and then commented
out the pdfstoryboard plug-in in the CTSPluginService.xml config file. If you then install

26 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Known Problems and Limitations

another CTS product (such as AVTS or DTS), the line for the pdfstoryboard plug-in is
completely removed from the CTSPluginService.xml file.

Conguration by SuperUser will fail if user_os_name is


blank (112591)
If a SuperUser created in Documentum Administrator does not have a user_os_name
defined in the dm_user table, configuration of any Content Transformation Services
product will fail.
The user_os_name must be assigned in order for the SuperUser to have SuperUser
privileges. Alternatively, using the user_login_name field will result in successful
configuration.

CTS Admin Agent prevents CTS_log.txt from archiving


(127418)
If the CTS Admin Agent is running, the CTS_log.txt file does not archive properly
after each day. This results in one continuous CTS_log.txt file, making it difficult to
troubleshoot errors.

Ditamap transformations fail if path includes extended


or double-byte characters (144403)
If you select a DITAMAP source file that has extended or double-byte characters in the
file path (including file name), the transformation fails. Documentum recommends that
file names and references contain ASCII characters only.

Limitations
This section describes limits on the usability of current functionality. The limitations
may be part of the product design or may result from issues with associated third-party
products.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 27


Known Problems and Limitations

Prole description limited up to 192 bytes


The profile description length for new or edited profiles is up to 192 bytes. Please note
that Russian characters can be either 2 or 3 bytes. To use a description that exceeds 192
characters, the workaround is as follows:
Run the following DQL queries against the repository:
EXECUTE ALLOW_BASE_TYPE_CHANGES WITH ALLOW_CHANGE_FLAG=1
alter type dm_sysobject modify subject char(300)
EXECUTE ALLOW_BASE_TYPE_CHANGES WITH ALLOW_CHANGE_FLAG=0
For Second successive run we need to change it to (301):-
EXECUTE ALLOW_BASE_TYPE_CHANGES WITH ALLOW_CHANGE_FLAG=1
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

DITAMAP document transformation fails due to spaces


in directory path (161399)
DITAMAP target files fail to transform to HTML, CHM, Java Help, Eclipse Help and ZIP
properly. This is due to the CTSServerService.xml pointing to a path with spaces in it:
<CTSServer AttributeName="tempFileDir" AttributeValue="C:\PROGRA~1\
DOCUME~1\CTS\docbases\Repo1\config\temp_sessions"/>
The workaround is to set up a folder path in CTSServerService.xml that does not contain
any spaces, by updating the AttributeValue of AttributeName "tempFileDir" attributes as
per the following example:
<CTSServer AttributeName="tempFileDir" AttributeValue="C:\temp"/>

Spaces in DITAMAP le names cause CHM


transformations to fail (137384)
The DITA Open Toolkit does not support file names that contain spaces. Problems with
file and folder names may cause transformations to fail. For example, if DITAMAP
format files have spaces in their file paths, they cannot be transformed to Complied

28 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Known Problems and Limitations

HTML Help (CHM) format. As a workaround, the file should be renamed so that there
are no spaces.
Additionally the user can set up a temporary folder, without spaces, in
CTSServerService.xml, by updating the "tempFileDir" attributes as per the following:
<QueueProcessorContext DocbaseName="your_repository">
<CTSServer AttributeName="tempFileDir" AttributeValue="C:
\temp_sessions"/>
</QueueProcessorContext>

This should be changed for all <QueueProcessorContext> nodes.

Non-standard characters appear in output due to


browser settings (137389)
When transforming DocBook files to HTML, non-standard characters may appear in the
output file. This issue is related to browser settings. If you are using Internet Explorer,
correct this error by setting your browser to use the Unicode font.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 29


Known Problems and Limitations

30 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 6
Technical Notes

This section provides configuration and usability notes for current product features.

Conrming beginning of prole migration


dialog box
During installation of XML Transformation Services, a dialog box appears with the
following information:
• Creation of a pre-migration report of all profiles before they are upgraded.
• Confirmation of the beginning of the profile migration process
• Reminder to backup all profiles first before continuing.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 31


Technical Notes

Figure 1. Prole Migration Process Conrmation Dialog Box

Viewing log le of migrated proles


You can view the log file generated by the profile migration tool. This log file shows
the profiles that were processed, their status, and the reason why if any profiles were
not migrated. The default location of the log file of migrated profiles is C:\Program
Files\Documentum\CTS\docbases\<docbase_name>\migration\logfile.
The migration log file shows the result of the migration process:
migration_log_2007_292_1192813617312.txt ->
Migration log;

The migration report log shows a complete list of all profiles before they are upgraded:
migration_report_2007_292_1192813563921.txt ->
Report log

32 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Technical Notes

Checking the version of a CTS product installer


The following procedure allows you to check the version of a CTS installer (in this case,
the XML Transformation Services installer).
Navigate to the directory where the installer exists. Open a command prompt window.
Run the following command, using the full path to the Java executable on the machine,
if it is not defined as a system variable:
java -cp <installer_jar_file> DiShowVersion
For example, the full command for XTS is: java -cp xtsWinSuiteSetup.jar DiShowVersion.
This displays the full installer version.

Manual re-conguration of XTS instance if the


repository is deleted
If a repository configured with XML 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 XML Transformation Services, this procedure is recommended. Without manual
re-configuration, the XML Transformation Services fails to start for all repositories that
the XTS 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 - ***************
Content Transformation 6.5 - Release Build 0.134 ICTSService Framework
startup initiated. ***************
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)

EMC Documentum XML Transformation Services Version 6.5 Release Notes 33


Technical Notes

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 XML Transformation Services host:

1. Navigate to %CTS%\config (for example, C:\Program


Files\Documentum\CTS\config).
2. Make a backup copy of the following files:
• CTSProfileService.xml
• CTSServerService.xml
• SessionService.xml
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, C:\Program Files\Documentum\CTS\docbases).
7. Open the Windows Registry Editor (go to Start > Run > regedit).
8. For XML Transformation Services and all other Content Transformation Services
products installed, delete the folder with the repository name that is no longer
available under:
HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\CTS\<cts_product>\Docbases

For example, the full path for XTS, including the repository name, will appear as:
HKEY_LOCAL_MACHINE\SOFTWARE\Documentum\CTS\XTS\Docbases\<repository>

9. Stop the CTS service.


10. Delete the CTS log files.
11. Start the CTS service.

34 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Technical Notes

Conguring XTS to interact with Documentum


Compliance Manager objects in a repository
If XML Transformation Server is configured against a server that has Documentum
Compliance Manager (DCM) installed, certain JAR files and dbor.properties must be
copied to the XTS host. Otherwise, these errors may occur:
• An exception is thrown, which causes the XML Transformation Server to stop.
• Renditions requested through DCM fail.
• An error appears in the DCM log file (log4j.log).

To enable XTS to interact with DCM objects in a repository:


1. Copy the dcm.jar and dcmIModule.jar files (at C:\Program
Files\Documentum\Shared) from the DCM host to the repository on
the XTS host. Copy the files to this location: /System/Applications/dcm/dmc_dcm_
controlled_doc_aspect.
2. Update the classpath for the XTS service to include dcm.jar and dcmIModule.jar.
For example, the registry would include the following when the classpath is updated
for dcm.jar:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DocumentumCTS\
Parameters]
"AppParameters"="-Xbootclasspath:C:\\PROGRA~1\\DOCUME~1\\java\\1.5.0_12\
\jre\\lib\\rt.jar -Xms64m -Xmx256m -Djava.protocol.handler.pkgs=
sun.net.www.protocol -XJVMDir:
C:\\PROGRA~1\\DOCUME~1\\java\\1.5.0_12\\jre\\bin\\server\\
jvm.dll -DCTS_CONFIG_DIR=C:\\PROGRA~1\\DOCUME~1\\CTS\\config
-Dlog4j.configuration=file:C:\\Documentum\\config\\log4j.properties
-DOUTPUT_DIR=C:\\PROGRA~1\\DOCUME~1\\CTS\\logs -DOUTPUT_TEST_FILES=true
-DCLEAN_TEST_FILES=false -DMAX_WAIT_INTERVALS=5
-Djava.class.path=C:\\PROGRA~1\\DOCUME~1\\CTS\\lib\\cts.jar;
C:\\PROGRA~1\\DOCUME~1\\dctm.jar;
C:\\Program Files\\Documentum\\Shared\\dcm.jar;
C:\\Documentum\\config;
C:\\PROGRA~1\\DOCUME~1\\CTS\\lib -mainclass=com/documentum/bfc/services/
mediaserver/MediaServerStartup -servicename=DocumentumCTS
-displayname=Documentum Content Transformation Services
-wrkdir=C:\\PROGRA~1\\DOCUME~1\\CTS\\lib"

3. Copy the DCM entries from the dbor.properties file on the DCM application server
(or Content Server that has DCM repository running), and append them to the
dbor.properties file on the XTS host.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 35


Technical Notes

After this procedure is completed, the XML Transformation Server can create renditions
through DCM.

36 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 7
Documentation

This section describes the documentation related to this product.

XML Transformation Services documentation


set
These documents comprise the XML Transformation Services documentation set for this
version of the product:
• XML Transformation Services Release Notes, version 6.5 (this document)
• XML Transformation Services Installation Guide, version 6.5 (P/N 300-007-276)
• XML Transformation Services Administration Guide, version 6.5 (P/N 300-007-277)

Obtaining the correct documentation


The Powerlink site (http://powerlink.emc.com) contains the downloadable packages
for specific product versions along with the release notes, installation guide, and
other relevant documentation associated with the product version. To locate product
documentation, navigate to Support > Technical Documentation and Advisories >
Software ~ D ~ Documentation, then select your product.
Note: The majority of Content Management products are listed under Software D >
Documentum ?, where ? = a letter, or letters, in the alphabet.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 37


Documentation

Product documentation that is available online from the application (Help, for example)
does not appear as a separate item; it is automatically downloaded and installed with
the software.

38 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 8
Software Media, Organization, and Files

This section describes the media in which the software is available, the organization of the product
components in the available media, and the file names for all available product components which
can be downloaded.

Software Media
This product is available as an FTP download from the Powerlink website
(http://powerlink.EMC.com). You should have received instructions through email
regarding how to download products.

Organization
The Powerlink website (http://powerlink.EMC.com) provides access to
https://EMC.subscribenet.com/control/dctm/index, which provides a complete listing
of the products available for download.

Files
The following modules/files comprise the contents of this release:
• Documentum XML Transformation Services for Windows, version 6.5 (EXE)
• Documentum XML Transformation Services Release Notes, version 6.5 (PDF)
• Documentum XML Transformation Services Administration Guide, version 6.5 (PDF)
• Documentum XML Transformation Services Installation Guide, version 6.5 (PDF)

EMC Documentum XML Transformation Services Version 6.5 Release Notes 39


Software Media, Organization, and Files

• Documentum Content Transformation Services Activity Template for AIX, version


6.5 (TAR)
• Documentum Content Transformation Services Activity Template for HPUX, version
6.5 (TAR)
• Documentum Content Transformation ServicesActivity Template for Linux, version
6.5(TAR)
• Documentum Content Transformation Services Activity Template for Solaris, version
6.5 (TAR)
• Documentum Content Transformation Services Activity Template for Windows,
version 6.5 (EXE)
• Rich Media Services DAR, version 6.5 (ZIP)
• Transformation DAR, version 6.5 (ZIP)
• Documentum CTS API SDK, version 6.5 (ZIP)
• Documentum CTS Web Services SDK, version 6.5 (ZIP)

40 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 9
Installation

The instructions for installing the product are provided in the XML Transformation Services Installation
Guide. This section describes any additional installation issues.
Ensure that your system meets the requirements listed in Chapter 4, Environment and System
Requirements before installing the software.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 41


Installation

42 EMC Documentum XML Transformation Services Version 6.5 Release Notes


Chapter 10
Troubleshooting and Getting Help

Documentum’s technical support services are designed to make your deployment and management of
Documentum products as effective as possible. The Customer Guide to EMC Software Support Services
provides a thorough explanation of Documentum’s support services and policies. You can download
this document from the Powerlink site (http://powerlink.emc.com) by navigating to: Support >
Request Support > Software Customer Guide and Offerings.

EMC Documentum XML Transformation Services Version 6.5 Release Notes 43