Configure - Configure - Alfresco - Alfresco Transform Service - Alfresco/Alfresco-Transform-Service/1.5/Alfresco-Transform-Service/Alfresco-Transform-Service/Configure - 1.5

The Transform Router (T-Router) configures Transform Engines (T-Engine) transformers automatically by retrieving the engine transform configurations from each configured T-Engine. The engine transform configurations provide the transformer configuration, including the supported transformers, and their transform options.

For more information on the format of the transform configuration and instructions on how to create a transform configuration files for a custom engine, see Creating a T-Engine.

T-Engines are added to the T-Router by adding the engine's URL and JMS queue name used by each and every engine. See next section for the URL and JMS queue name property format.

The T-Router supports 2 types of transformers:

• Single-step transformer: This maps transformation requests to a single T-Engine, which can directly transform the source media type to the target media type with the provided transform options and source file size.

For example: image/png to image/png is handled by the IMAGEMAGICK transformer.

• Pipeline transformer: This maps transformation requests to a sequence of intermediate transformation requests steps, which are handled by multiple T-Engines. These transformers handle situations where there is no single engine that can directly transform one media type to another, but that can be achieved through intermediate media types and transformations.

For example: application/msword to image/png can't be directly performed by one single engine, but it can be handled by LIBREOFFICE (which would generate application/pdf) and then PDF_RENDERER.

Single-step transformers map to a transformer, which in turn maps to a T-Engine. Each T-Engine can have multiple transformers defined in its configuration. The single-step transformers are configured automatically from T-Engine transform configuration files.

Pipeline transforms map to a pipeline transformer, which in turn maps to a series of single-step transformers. These are defined through configuration files in the T-Router. This is described in the later section about pipelines.

A T-Engine is intended to be run as a Docker image, but may also be run as a standalone process.

For an overview of the Transform Service, including the T-Router, T-Engines, Local transforms, Legacy transforms etc see overview.