About Native File Conversion Identifying MIME Types

Managing Repository Content 2-3

2.2 Native Content Conversion

This section covers these topics: ■ About Native File Conversion on page 2-3 ■ Identifying MIME Types on page 2-3 ■ Native Applications and Content Conversions on page 2-4 ■ Associating File Types with Conversion Programs on page 2-4

2.2.1 About Native File Conversion

When Content Server is configured as a provider for an Inbound Refinery instance, Content Server must be told what file formats to pass to the refinery for conversion, based on the file extension. This can be done in two ways: ■ using the File Format Wizard, accessed from the Refinery Administration folder in the Administration tray ■ using the File Formats option of the Configuration Manager applet to map file extensions .doc, .txt, and so on to file formats then mapping file formats to the conversion option on the refinery. The second option provides more flexibility in mapping different file extensions to different conversion options. After the job is passed from Content Server to Inbound Refinery, the refinery configuration determines how the native file is converted and returned to Content Server. File formats are automatically configured during installation; however, you can add or change them as necessary. See the Oracle Fusion Middleware Administrators Guide for Conversion for more details about conversions. In addition to using the Configuration Manager to handle file conversions, you can use the File Formats Wizard. To access that functionality, click Administration then Refinery Administration from the Main menu.

2.2.2 Identifying MIME Types

It is recommended that you name new file formats by the MIME Multipurpose Internet Mail Extensions type corresponding to the file extension for example, the format mapped to the doc file extension would be applicationmsword. When a content item is checked in to Content Server, the content item’s format is assigned according to the format mapped to the file extension of the native file. If the native file is not converted, Content Server includes this format when delivering the content item to clients. Using the MIME type for the format assists the client in determining what type of data the file is, what helper applications should be used, and so on. Note: If Content Server is not configured to work with an Inbound Refinery instance, you do not need to specify how to convert native files. They will all be passed through to the web site in their native format. 2-4 Application Administrators Guide for Content Server You can identify the MIME type by checking the list of registered MIME types at http:www.iana.orgassignmentsmedia-typesindex.html .

2.2.3 Native Applications and Content Conversions