This section assumes that you're familiar with transformer concepts used in Alfresco Content Services and now in the Transform Service. A good place to start is the Content Services GitHub documentation, as the concepts and transformer configuration are identical.
Here's a very brief overview.
Each T-Engine may contain multiple transformers, as exposed via its /transform/config endpoint. Each transformer has a
list of supported transforms, which consist of:
- source and target media types (similar to mimetype)
- maximum supported source file size
- priority
The priority is used in resolving conflicts or to deliberately override existing transforms, where everything else is equal. Each transformer can also have a set of options, for example, an image processing transformer might have options for the target image parameters (resolution, aspect ratio, etc.). All of this information determines the transformer for each incoming request. Pipeline transformers can be defined in terms of other pipeline transformers. Pipelines examples are provided later.