Run existing project transformation scenario with Oxygen Publishing Engine?
Posted: Mon Apr 13, 2020 8:43 pm
Hi, I am testing out the Oxygen Publishing Engine for a DITA project I'm working on, but it seems largely undocumented.
I have several Oxygen transformation scenarios that I like to run manually from within the editor, but I want to set up an integration server that builds outputs using these transformation scenarios with a command line interface.
Based on the contents of the engine package, it looks like a version of the DITA-OT and some Oxygen plugins. I have installed the package contents and trial license file, and I can get a build to work if I copy the console output command that is created when I run the transformation in the Oxygen editor and run that command manually. I don't like this solution because if I have to create a parameters file for all of the stuff included in my transformation scenario, and if I make changes to the transformation scenario, they are not automatically propagated to the command I've hacked together.
Since this is a (rather expensive) commercial offering from Oxygen, I am expecting that there is a more complete and tightly integrated solution that I am just unable to find documentation for. What I would like to do is point to an Oxygen project file (which contains my transformation scenario definitions), an input file to be transformed, and the name of the transformation scenario to use (similar to the options I pick in the Oxygen GUI when I run a transform) and then my output is generated.
How can I do this? Thanks!
I have several Oxygen transformation scenarios that I like to run manually from within the editor, but I want to set up an integration server that builds outputs using these transformation scenarios with a command line interface.
Based on the contents of the engine package, it looks like a version of the DITA-OT and some Oxygen plugins. I have installed the package contents and trial license file, and I can get a build to work if I copy the console output command that is created when I run the transformation in the Oxygen editor and run that command manually. I don't like this solution because if I have to create a parameters file for all of the stuff included in my transformation scenario, and if I make changes to the transformation scenario, they are not automatically propagated to the command I've hacked together.
Since this is a (rather expensive) commercial offering from Oxygen, I am expecting that there is a more complete and tightly integrated solution that I am just unable to find documentation for. What I would like to do is point to an Oxygen project file (which contains my transformation scenario definitions), an input file to be transformed, and the name of the transformation scenario to use (similar to the options I pick in the Oxygen GUI when I run a transform) and then my output is generated.
How can I do this? Thanks!