JetTrac PDFBatchMerge


This document is a guide to installing, configuring and using the JetTrac PDFBatchMerge Custom Agent. This document includes detailed instructions for installation and configuration of JetTrac PDFBatchMerge.


JetTrac PDFBatchMerge merges a set of static XFA or ACROFORM pdf templates with an XML file. It takes the leaf nodes of the .xml and merges them with the static pdf template.

JetTrac PDFBatchMerge is written in .Net Framework Version 4. At this time it is compatible with Windows only.

For additional information on JetTrac products, see the document What you need to know about JetTrac Java and Licensing available from the JetTrac website,

Technical Support:

If you need assistance in installing and configuring JetTrac PDFBatchMerge, call Pro Technology Automation, Inc. at 805-527-1248 ext. 0 or e-mail us at Please note that the JetTrac PDFBatchMerge license fee does not cover configuration services and technical support so there may be an additional charge. Please ensure you read these instructions carefully before calling for technical support.

Adobe/Accelio/JetForm note:

Adobe’s current name for the Central product is Adobe Central Pro Output Server. Previously it has been known as JetForm Central and Accelio Present Central, but these names all refer to the same product and JetTrac PDF Merge works the same way with all names and versions of Central.

Installation and Configuration:


Installing JetTrac PDFBatchMerge:

The files you need are:

Filename Description
DebenuPDFLibraryDLL0915.dll Application extension
ExitHandler.dll Application extension
JTPDFBatchMerge.exe Executable


Job Step Configuration Window in JobConfig for JetTrac PDFBatchMerge:

When setting up a job step using JTHighlightDiff in JobConfig the only lines of the config you need to worry about are the first and the last two, the Config file, the Input XML and the Output XML. If left as an asterisk * the input will be whatever file is in the data folder that triggered the job running. This works well if it’s the first step but if the input is also the output of a previous job step you would need to specify the fully qualified path of the input xml that will be merged into the pdfs. All other fields should be filled with the fully qualified path to the intended file. Eg: C:\JetTrac\…\input.xml
In JobConfig, file paths entered should not be in quotes.

As with all modules, there is a dropdown to select whether or not the job should stop completely if this step fails. If you select Yes, any error will terminate the job process and write to the log file what happened, if no, then the job will try to continue anyways. However if any steps further down the line rely on the output of a job set to not stop on error, they may not work properly.

For more specifics go to the JetTrac Field ServiceJobConfig page.


Setting up the Job Step in JetTrac JobConfig

Sample Command Line:

“C:\JTPDFBatchMerge.exe” “C:\JTPDFBatchMerge_Input.xml” “C:\JTPRDBatchMerge_Output.xml” “C:\JTPDFBatchMerge_config.ini” “C:\JTPDFBatchMerge.log”

Sample Config File:

#PDFMergeLocation=fully qualified path to pdfmerge.exe
#TemplateList=fieldname in xml for pipe delimeted list of forms to merge (fully qualified)
#OutputFileName=fully qualified path to output file name. use double quotes for string literals and no double quotes for field names from xml. Concatenate with plus signs. Special keyword for template file name (without extension) is "!FORMNAME"
#FormType="ACROFORM" or "XFA"

Note: If UAC is running you must first run from a batch file and uncheck “always check when running this program” when the UAC prompt comes up.


  1. Currently JTPDFBatchMerge will only work with a set of Acroforms, or a set of XFA forms. Mixing form types is not supported but will be in the future.
  2. JTPDFBatchMerge does not yet support JTPDFMerge’s new configuration file option. It will be supported in the future.