Oxygen Publishing Engine
DITA and XML automated publishing engine
About this software
Oxygen Publishing Engine is a command-line publishing tool that converts XML and DITA content into WebHelp, PDF, and other outputs using the DITA Open Toolkit and customizable transformations. It integrates with the oXygen product suite and supports scripting and automation for batch publishing workflows.
Designed for technical publishers, documentation teams, and integrators, it offers customization, PDF Chemistry and WebHelp generation, and can be invoked from CI pipelines or the oXygen editors.
Purchase
Oxygen Publishing Engine
In Stock
Delivery: 1 working day
This product is available, please contact us for the price
Do you need more information or looking for another license?
Benefits
- Automated XML publishing: Converts XML and DITA sources to WebHelp, PDF, and other outputs.
- WebHelp and PDF output: Produces responsive WebHelp and PDF using customizable transformation pipelines.
- CLI and automation: Command-line interface supports scripting for CI and batch publishing.
- Integration with oXygen: Works with oXygen editors and can be set as DITA-OT provider.
- Customizable and extensible: Supports customization, PDF Chemistry, and scripting via Oxygen SDK.
Available languages
- English
Support information
- Documentation and user manual: Comprehensive documentation and a user manual are available on the publisher site.
- Downloads and archives: Current releases and an archive of previous builds are available for download.
- Software Maintenance Program: SMP (maintenance) provides updates and maintenance for the licensed term.
- Technical support options: Technical support and contact information are listed on the Oxygen website.
- Community and events: Blog posts, webinars, and events such as DITA-OT Day are published on the site.
Frequently asked questions
What formats does the Publishing Engine produce?
The engine produces WebHelp and PDF outputs and uses the DITA Open Toolkit to generate other customizable formats and HTML outputs.
How is the Publishing Engine licensed?
Licenses are offered in core-based tiers (for example 2, 4, 8 cores) and are available with a Software Maintenance Program term.
How does it integrate with oXygen editors?
Set the DITA Open Toolkit option in the oXygen editor to use the Publishing Engine directory so oXygen invokes the engine for transformations.
What are the system requirements to run the engine?
The engine requires a Java/OpenJDK 17 runtime and runs on typical server hardware; recommended is a dual-core CPU with 4 GB RAM and available disk space.
Can the engine be automated in CI pipelines?
Yes; the Publishing Engine provides command-line tools and scripting support that enable integration into CI/CD and automated build pipelines.