The RenditionService2 will use the Local Transform Service if it is available. If not, the service with fallback to the transformers performed the Legacy Transform Service.
The original RenditionService is now deprecated as it supports synchronous requests or requests that have callbacks that must be processed on the same node.
Prior to ACS 6.0, legacy transformers ran within the same JVM as the ACS repository. They and their supporting code has been deprecated and will go away at some point.
Services still using V0 REST API and legacy transformers:
Text extract for Solr (NodeContentGet webscript). Search Services 1.5 will make use of Local Transform Service.
Synchronous transforms used by Share web app (v0 scripts, rules, actions). ACS 6.3 will make use of Local Transform Service.
Building a new Transformer for Local Transform Service
From ACS 6.2 it is possible to create custom transforms that run in separate processes known as Transformer Engines. The same engines may be used in Community and Enterprise Editions.
They may be directly connected to the ACS repository as Local Transforms, but in the Enterprise edition there is the option to include them as part of the Transform Service which provides more balanced throughput and better administration capabilities.
You can learn how to create a Transformer Engine and how to migrate your legacy transformer in:
Transformers are exposed to the Local Transform Service as HTTP Endpoints, so the Markdown to PDF Transformer provides the transform endpoint as http://alf-tengine-markdown:8090/transform inside the Docker Network:
Share web application expects PDF renditions to be created with the name pdf, so after this request is performed, the preview will be available in Share UI.
A new Children named as cmdf will allow Share to provide the Preview
Using the new Transformer with Share and ACS 6.2
In order to apply transformations from Local Transform Services in Share by default, a simple behaviour can be developed. This behaviour can use the new RenditionService2 to provide a PDF rendition everytime a Markdown content node is created or updated.
The sample project includes a folder named markdown-rendition that includes an Alfresco SDK Repository artifact implementing this behaviour.