Basic sample Project configurations

The SampleProject.dcpackage sample Project shows how ADEP and Production Print processes can be integrated. The provided example integrations can be used as a pattern for your implementation.

Sample 1 configuration – XML Input Data

The Sample 1 configuration illustrates a basic use case with synchronous post-processing, including document sorting and OMR marking.

You can connect the Process to the PDF encrypt output connector, install the sample LCA package, and configure the filter on the connector to point to the computer where the LCA is installed. This illustrates how Production Print can connect to an ADEP server, process a PDF, and return the PDF to Production Print.

Sample 2 configuration – ASCII Input Data

The Sample 2 configuration illustrates how to bind ASCII data to a form template.

1	Copy the file Invocie.grb from the samples directory to the input directory.

2	Verify that the output.pdf file is created in the output directory.

Sample 3 configuration – Dunning Notice Process

The Sample 1 and Dunning Notice Process configurations can be used together to illustrate remote invocation of Production Print from ADEP.

1	Install and deploy the LCA package on an ADEP server.

2	Invoke the DunningNoticeStage service with the DunningNotice.xml file as input (available in resources). The XML file and the DunningNotice.xdp are sent to Production Print.

The data file and the template will be merged and stored in the Production Print Post-processor repository.

3	Invoke the DunningNoticePrint service with the file lcpp.ppq (post-processor query file) as input. The PPQ file is sent to Production Print that will get the staged Dunning Notice from the Post-processor repository, format it as a PDF file, and write it to the output folder as output.pdf.

Sample 4 configuration – Dunning Notice Generate

The Dunning Notice Generate configuration illustrates how Production Print can be invoked with data and a template.

Production Print will merge the data and the template and return the result as an AFP file to ADEP.

1	Invoke the DunningNoticeGenerate service with the Dunning Notice.xml file as input. The resulting AFP file will be written to a file on the ADEP server (default c:\result.afp).

Sample 5 configuration – AFP2PDF

The Sample 5 configuration illustrates how AFP files can be converted to PDF files using the PreformatIN tool and dynamic overlays in the PageOUT Process.

The PreformatIN Event will read the PurchaseOrder.afp file through an AFP2LXF filter and apply a pattern match to identify the document type. The PageOUT Process will apply the dynamically generated LXF pages to a logical page each. The result will be rendered as PDF using a driver on the output connector.

1	Invoke the AFP2PDF configuration by submitting the purchaseorder.afp file to the Watchfolder2 input directory. The result is five PDF files in the output directory, one for each document in the AFP file.