As an alternative to Componize DITA XProc pipelines, you can use the DITA-OT Server. This solution allows to use
any version of the DITA-OT toolkit.
Why having a DITA-OT Server for Componize ?
Using the DITA-OT Server is recommended against the standard Componize DITA-OT Pipelines as soon as there is a requirement for modern DITA-OT server and plugins. Using Componize pipelines remains interesting when speed performance is needed.
Understanding how the DITA-OT Server cooperate with the Componize server
Using an external DITA-OT Server, the Componize server is responsible for providing files to the DITA-OT Server. The DITA-OT Server processes the files and returns result publication file(s) plus a log file to the Componize server.
How to parameterize a DITA-OT server standard plugin
You parameterize Componize standard plugins of the DITA-OT Server using a DITA-OT DITA-OT property file, plus all other parameterization files that are needed.
How to run any new DITA-OT plugin of the DITA-OT Server
For running a new plugin you need to target your usecase : the output media type exists (or not) or you need to modify the standard Componize DITA-OT pipeline or not.
How to manage a new DITA-OT plugin with a new media type
Managing a new plugin for a new media-type needs parameterizations both on the Componize server to declare the media-type and on the DITA-OT Server for deploying the plugin.
How to migrate from Componize DITA-OT Pipelines to DITA-OT Server
The migration process is the same as for a DITA-OT 1.8.5 server to a modern DITA-OT server if there were no customizations of the Componize XProc pipelines. Otherwise, you need to replace all XProc specifics by the ANT target equivalents.
How to debug the DITA-OT Server
The DITA-OT Server is easily debugged by a local DITA-OT implementation, for example working on a oXygen plateform. For a server debugging, all intermediate steps are located in differents temporary directories.