Working With Image and Video Conversions 4-29
The following table lists the columns of the Video Format Preferences table and their function:
4.4.11 Enabling Plug-in Debugging Logs
The standard log outputs from FlipFactory are found in the stdout.log file located in the FlipFactory installation directory. Additional logging detail can be found by
enabling the plug-in logging. To enable FlipFactory plug-in debugging, perform these steps:
1.
Stop the Flip Engine service.
2. Open the log4j.properties file located in the FlipFactory_install_dir in a standard
text editor.
3.
Delete the symbol in front of the following entries in the log4j.properties file:
■
log4j.logger.com.stellent.refinery.ff=DEBUG
■
log4j.rootLogger=ERROR, IBRPlugin
4.
Save the log4j.properties file and restart the Flip Engine service. Information regarding plug-in output is now logged to FlipFactory_install_
dirstdout.log.
Column Name Definition
format Configurable name displayed in the choice list of an embedded player.
pickOrder_win Determines the order a format is selected on a Windows operating
system. pickOrder_mac
Determines the order a format is selected on a Macintosh operating system.
pickOrder_other Determines the order a format is selected on an operating system other
than Windows or Macintosh.
4-30 Administrators Guide for Conversion
5
Working with XML Conversions 5-1
5
Working with XML Conversions
Inbound Refinery can convert native files to either FlexionDoc or SearchML-styled XML, as well as process XSL transformation using Xalan XSL transformer. XML
conversions require the following components to be installed and enabled on the specified server:
This section discusses how to work with XML conversions and how to troubleshoot the conversion process. The section contains the following sections:
■
Configuring XML Converter Conversion Settings on page 5-1
■
Troubleshooting XML Converter Problems on page 5-6
5.1 Configuring XML Converter Conversion Settings
This section covers the following topics:
■
Configuring Content Servers to Send Jobs to Inbound Refinery on page 5-1
■
Setting Accepted Conversions on page 5-2
■
Setting XML Files as the Primary Web-Viewable Rendition on page 5-2
■
Setting XML Files as an Additional Rendition on page 5-3
■
Setting Up XSL Transformation on page 5-4
5.1.1 Configuring Content Servers to Send Jobs to Inbound Refinery
File extensions, file formats, and conversions are used in Content Server to define how content items should be processed by Inbound Refinery and its conversion add-ons.
You must configure each content server to send files to refineries for conversion. When a file extension is mapped to a file format and a conversion, files of that type will be
sent for conversion when they are checked into the content server. You can configure
Component Name Component Description
Enabled on Server
XMLConverter Enables Inbound Refinery to
produce FlexionDoc and SearchML-styled XML as the
primary web-viewable file or as independent renditions, and can
use the Xalan XSL transformer to process XSL transformations.
Inbound Refinery Server
XMLConverterSupport Enables Content Server to support
XML conversions and XSL transformations.
Content Server
