Inbound Refinery Process Overview

1.5 Inbound Refinery Process Overview

Inbound Refinery refinery manages file conversions and provides thumbnailing functionality and serves as a provider to Content Server. When a file is checked into the content server, a copy of the native file is stored in the native file repository either on a file system or in a database. The native file is the format in which the file was originally created, for example, Microsoft Word. If the file format is not set up to be converted, 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 web-viewable file repository. This means that the file is passed through to the library in its native format. Users must then have an application capable of opening the native file installed on their computer to view the file. If the file format is set up to be converted, the content server creates a conversion job in its pre-converted queue. The content server then attempts to deliver the conversion job to one of its active refinery providers, which is a refinery that is configured to accept the conversion and is not busy. The content server sends the conversion parameters to an active refinery. If the refinery does not accept the job, the content server tries the next available refinery. When a refinery accepts the job, the content server then uploads a ZIP file, containing the conversion data and the file to be Table 1–5 TIFF Converter: For Converting TIFF Files to PDF Component Name Component Description Enabled on Server TiffConverter Enables Inbound Refinery to convert single or multipage TIFF files to PDF complete with searchable text. Inbound Refinery Server TiffConverterSupport Enables Content Server to support TIFF to PDF conversion. Content Server Table 1–6 HTML Converter: For Converting Microsoft Office Documents to HTML Component Name Component Description Enabled on Server HtmlConverter Enables Inbound Refinery to convert native Microsoft Office files created with Word, Excel, Powerpoint and Visio to HTML using the native Office application. Inbound Refinery Server MSOfficeHtmlConverterSupport Enables Content Server to support HTML conversions of native Microsoft Office files converted by Inbound Refinery and returned to Content Server in a ZIP file. Requires that ZipRenditionManagement component be installed on the Content Server. Content Server ZipRenditionManagement Enables Content Server access to HTML renditions created and compressed into a ZIP file by Inbound Refinery. Content Server Introduction 1-7 converted, to the refinery. The content server also places an entry in its RefineryJobs table, which it uses to track the conversion job. The refinery places the conversion job in its pre-converted queue. The refinery then attempts to perform the specified conversion. When the refinery finishes processing the conversion job, it places it in its post-converted queue. The content server polls the refinery periodically to see if conversion jobs in its RefineryJobs table have been completed. When the refinery reports that it has finished processing a conversion job, the content server downloads any converted files for example, a web-viewable thumbnail file and a PDF file from the refinery, places the conversion job in its post-converted queue, and kicks off any post-conversion functionality as needed. If a conversion is successful, the converted files, such as a web-viewable thumbnail file and a PDF file, are available to the content servers users through their web browser. In the case of an videos, images, or graphic files, additional renditions and rendition information are available on the Rendition Information tab of the Content Information page. If a conversion fails, the content server can be configured to place a copy of the native file in the web-viewable file repository. In this case users must also have an application capable of opening the native file installed on their computer to view the file. 1-8 Administrators Guide for Conversion 2 Managing Conversions 2-1 2 Managing Conversions Inbound Refinery offers a variety of conversion options depending on what components are installed and enabled on Content Server and Inbound Refinery. At minimum, the following components must be installed and enabled for basic conversion: This section covers the following topics: ■ Section 2.1, Configuring Content Server and Refinery Communication