Controlling the Converters

By default Document Conversion Service automatically attempts to load all included converters. For a converter that requires a native application to load, that application must also be installed. Each converter also uses an application pool (multiple running instances of the application) to allow for parallel document processing.

 

You can reduce the amount of resources Document Conversion Service uses by only loading the converters for file types that you need to convert.

 

Applications Factories and Required Applications

Most converters use an application to print the file to the Document Conversion Service to convert the file.

See What Files Can I Convert? for a complete list of each converter and its associated application. If you need to use that converter you will also have the matching application installed.

 

The converters are each defined in their own sections in Document Conversion Service's application configuration file. Each converter definition consists of an application factory component and a converter factory component that uses the application factory.

The application factory component controls if the converter will be loaded and the maximum number of instances of each application that can be running at any one time (application pooling).

It also controls when any one in-use application instance is closed and a new one started to replace it in the pool (recycled). The recycling of an application is controlled both by number of documents processed and by the virtual size of the running application.

The converter factory component is responsible for any custom conversion settings particular to that converter and its application.

The Application Factory Component

The Document Conversion Service application configuration file contains the <AppFactories> collection of <AppFactory> items; one item for each converter. Each application factory is described in its own <AppFactory> section using a collection of key-value pairs in the <Settings> collection.

The <AppFactories> collection also has its own <Settings> collection that is used to describe default settings for all application factories. If any individual application factory does not contain one of the settings the default setting from this section is used.

See Application Factory Settings for a complete list of all settings.

The Conversion Component

The Document Conversion Service application configuration file contains the <PluginFactories> collection of <PluginFactory> items.

Each converter included has its own <PluginFactory> section and uses its matching application factory defined in the <AppFactories> collection. Each <PluginFactory> section is described using a collection of key-value pairs in the <Settings> collection.

The <PluginFactories> collection also has its own <Settings> collection that is used to describe default settings for the <PluginFactory> section for each converters . If any individual <PluginFactory> does not contain one of the settings the default setting from this section is used.