Print & PDF tools

If a site of yours makes PDFs — a print module, printable invoices, an entity-to-PDF feature — the two heavy lifters those modules shell out to are already installed on every BOA server, at their standard paths:

/usr/bin/wkhtmltopdf — renders a web page to a PDF (its sibling /usr/bin/wkhtmltoimage, for page-to-image, is there too);
/usr/bin/pdftk — merges, splits, and stamps PDF files.

Point your module at the system copy

When a print/PDF module asks where its binary lives, give it the system path — for example /usr/bin/wkhtmltopdf — instead of uploading your own build into the platform or a library folder. The system copies are kept executable and current for you; a private copy inside your codebase is one more thing to maintain, and modules find the system path without any of that.

There's nothing to enable and nothing to ask your host for — the binaries are part of every BOA server's standard toolkit.

Modules BOA manages — the other pieces BOA ships into or manages around your codebase.
Which file do I edit? — if a module wants its binary path in an INI or settings file.