2-16 Administrators Guide for Conversion
■
The GET_FILE service is used to deliver the file, so no PDF highlighting or byte serving is available. This can be resolved by overriding the template and
reconfiguring the web server.
■
A simple template is used; the browser’s Back button might not be functional and layout differences might occur. This can be resolved by overriding the template
and reconfiguring the web server.
■
There is no reduction in the number of files because there is still an HCST file in the weblayout directory. However, there can be disk space savings if the native
vault file is large.
■
This setting has no affect on files that are sent to a refinery for conversion; that is, if a file is sent to a refinery for conversion, another content server setting controls
whether web-viewable files or a copy of the native file are placed in the weblayout directory, and an HCST file cannot be used. For more information, see
Configuring the Content Server Refinery Conversion Options on page 2-16.
To configure the content server to place an HCST file in the weblayout directory instead of a copy of the native file, complete the following steps:
1.
Open the content server config.cfg file located in the IntradocDirconfig directory in a text editor.
2.
Include the IndexVaultFile variable, and set the value to true: IndexVaultFile=true
3.
Save your changes to the config.cfg file.
4.
Restart the content server.
2.2.8 Configuring the Content Server Refinery Conversion Options
You can configure several options that affect how a content server interacts with its refinery providers, including how the content server should handle pre and
post-converted jobs. These settings are made using the Inbound Refinery Conversion Options page.
To configure how the content server should handle pre and post-converted jobs, complete the following steps:
1. Log into the content server as an administrator.
2. Choose Administration, Refinery Administration, Conversion Options. The
Refinery Conversion Options Page is displayed.
3. Enter the number of seconds between successive transfer attempts for
pre-converted jobs. The default is 10 seconds.
4. Enter the total number of minutes allowed to transfer a single job before action is
taken. The default is 30 minutes.
5. Enter the native file compression threshold size in MB. The default threshold size
is 1024 MB 1 GB. Unless the native file exceeds the threshold size, it will be compressed before the content server transfers it to a refinery. This setting enables
Important: The InboundRefinerySupport component must be
installed and enabled on the content server and at least one Inbound Refinery provider enabled to make the Inbound Refinery Conversion
Options page available.
Managing Conversions 2-17
you to avoid the overhead of compressing very large files for example, large video files. If you do not want any native files to be compressed before transfer,
set the native file compression threshold size to 0.
6.
If you want the conversion to fail when the time for transferring a job expires, select the check box.
7.
Determine how you want the content server to handle failed conversions. If a file is sent to a refinery and conversion fails, the content server can be configured to
place a copy of the native file in the weblayout directory Refinery Passthru. To enable passthru, select the check box. To disable passthru, clear the check box.
Please note the following important considerations:
■
When a file is sent to the refinery for conversion, an HCST file cannot be used instead of a copy of the native file. For more information on configuring how
the content server handles files that are not sent to the refinery, see Configuring the Content Server for PassThru Files
on page 2-15.
■
This setting can also be overridden manually using the AllowPassthru variable in the config.cgf file located in the IntradocDir\config\ directory.
8. Click Reset if you want to revert to the last saved settings.
9. Click Update to save your changes.
10.
Restart the content server. For additional details about using content server and refinery settings to manage
conversion queues, see Managing Refinery Conversion Queues
on page 2-31.
2.2.9 Overriding Conversions at Check-In
