Setting Library Path for UNIX Platform

2-8 Administrators Guide for Conversion 4. Make sure the IP Address Filter field includes the IP or IPv6 address of each content server computer even if this is the same physical computer that is also running the refinery server. The default value of this field is 127.0.0.1|0:0:0:0:0:0:0:1 localhost, but you can add any number of valid IP or IPv6 addresses. You can specify multiple IP addresses separated by the pipe symbol |, and you can use wildcards for zero or many characters, and ? for single characters. For example: 127.0.0.1|0:0:0:0:0:0:0:1|10.10.1.10|62.43.163.|62.43.161.12?

5. Click OK when you are done, and restart the refinery server.

2.1.4 Setting Classpath to OpenOffice Class Files

If converting documents using OpenOffice, Oracle Inbound Refinery requires class files distributed with OpenOffice. You must set the path to the OpenOffice class files in the refinery intradoc.cfg file, located in the DomainHomeucmibrbin directory. To set the path in the intradoc.cfg file, do the following: 1. Navigate to the DomainHomeucmibrbin directory and open the intradoc.cfg file in a standard text editor. 2. At the end of the file, enter the following: JAVA_CLASSPATH_openoffice_ jars=OfficePathBasisprogramclassesunoil.jar:OfficePathUREjavaridl.ja r:OfficePathUREjavajurt.jar:OfficePathUREjavajuh.jar 3. Save and close the intradoc.cfg file. 4. Restart the refinery.

2.1.5 Setting Library Path for UNIX Platform

Oracle Content Server and Oracle Inbound Refinery use Outside In Technology. Ouside In Technology is dynamically linked with the GCC libraries libgcc_s and libstdc++ on all Linux platforms as well as both Solaris platforms and HPUX ia64. Oracle Content Server must be able to access these libraries, however Solaris and HPUX do not initially make these libraries available. If running Content Server or Inbound Refinery on either Solaris or HPUX, you need to obtain and install the GCC libraries and configure Content Server to find them. For information about configuring the library paths, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. Important: Make sure you always include the localhost IP address 127.0.0.1. Tip: Alternately, you can add IP addresses to the IP security filter directly in the config.cfg file located in the IntradocDirconfig directory. Add the IP or IPv6 address to the SocketHostAddressSecurityFilter variable. For example: SocketHostAddressSecurityFilter=127.0.0.1|0:0:0:0:0: 0:0:1|10.10.1.10|62.43.163. 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.