Overview Configuring Content Servers to Send Jobs to Refineries

Managing Conversions 2-9

2.2 Configuring Content Servers to Send Jobs to Refineries

This section covers the following topics: ■ Overview on page 2-9 ■ About Conversions on page 2-10 ■ Passing Content Items Through the Refinery and Failed Conversions on page 2-12 ■ About MIME Types on page 2-12 ■ Using the File Formats Wizard on page 2-13 ■ Using the Configuration Manager on page 2-14 ■ Launching Configuration Manager on page 2-14 ■ Adding File Formats on page 2-14 ■ Editing File Formats on page 2-15 ■ Adding File Extensions on page 2-15 ■ Editing File Extensions on page 2-15 ■ Configuring the Content Server for PassThru Files on page 2-15 ■ Configuring the Content Server Refinery Conversion Options on page 2-16 ■ Overriding Conversions at Check-In on page 2-17 ■ Changing the Size of Thumbnails on page 2-18 ■ Refinery Conversion Job Status Page on page 2-18 ■ IBR Provider Status Page on page 2-19

2.2.1 Overview

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. In addition, application developers can create custom conversions. File formats are generally identified by their Multipurpose Internet Mail Extension MIME type, and each file format is linked to a specific conversion. Each file extension is mapped to a specific file format. Therefore, based on a checked-in file’s extension, the content server can control if and how the file is processed by refineries. The conversion settings of the refineries specify which conversions the refineries accept and control the output of the conversions. Consider the following example: the doc file extension is mapped to the file format applicationmsword, which is linked to the conversion Word. This means that the content server will attempt to send all Microsoft Word files with the doc file extension checked into the content server to a refinery for conversion. As another example, if the xls file extension is mapped to the file format applicationvnd.ms-excel, which is linked to the conversion PassThru, Microsoft Excel files are not sent to a refinery. Instead, the content server can be configured to place either a copy of the native file or an HCST file that points to the native vault file in the weblayout directory. This means that users must have an application capable of opening the native file installed on their computer to view the file. 2-10 Administrators Guide for Conversion Figure 2–1 Mapping File Formats to a Conversion When a file is checked into the content server and its file format is mapped to a conversion, the content server will check to see if it has any refinery providers that accept that conversion and are available to take a conversion job. This means that: ■ Refinery providers must be set up for the content server. For details, see Configuring Refinery Providers on page 2-5. ■ The refinerys need to be configured to accept the conversion. For details, see Setting Accepted Conversions on page 2-22.

2.2.2 About Conversions