File Conversions, Composers, and Properties

Files Conversions

The Compose component automatically converts all inbound and outbound messages to PostScript and then PDF format. The resulting PDF file becomes a temporary file that the server uses as the basis for additional file conversions.

Note: The required delivery format of an inbound or outbound message may be different than PDF. This requires the Compose component to perform additional file conversion tasks so that the server can deliver the message in the required file format.

For example, suppose you use the Web Client to create a fax that has a Word document attachment. An outbound fax requires TIFF format, so the Compose component converts the entire fax, including the Word document, into PDF format and then into TIFF format so that the server can deliver the fax as a single TIFF file.

You can choose the conversion methods that you want the Compose component to use when it converts a particular file type into PDF.

Single and Multiple Composers

An Upland AccuRoute server that performs the conversion tasks for the Compose component is called a Composer. If your server performs conversion tasks, it is called the local Composer. If other servers in the same domain perform conversion tasks, these servers are called remote Composers.

You can modify the properties of each Composer, including the types of jobs the Composer can handle, the types of source files the Composer can accept, the types of conversions the Composer can perform, and the types of templates the Composer can render.

You can use any combination of local and remote Composers to distribute the conversion workload to other servers. When you use multiple Composers, the server automatically balances the workload to all available Composers.

Note: For an environment with multiple Composers, each Composer must have a unique license key. For additional Composer licenses, contact your Account Manager.

Composer Properties

When modifying Composer properties, you can:

Specify how the server uses the Composer. The Composer can be configured to process inbound messages, outbound messages, Embedded Directives, and confirmation messages.
Specify the types of documents that are converted on a Composer. Examples of document types are BMP, DOC, GIF, HTM.
Enable the final forms that can be generated on a Composer. Examples of final forms are TIFF G3, TIFF G4, PDF, and text PDF.
Select the types of cover page templates that a Composer can convert. Examples of template types are DOC, HTM, HTML, OMTPL, and RTF.
Specify a composer class.
Specify a large job composer.

File Conversions, Composers, and Properties

Files Conversions

Single and Multiple Composers

Composer Properties

See also