i-net PDFC offers an extensive API to compare documents on an automatic basis, in batches, locally or remote.

With the provided Java API you can call i-net PDFC from a Java program to compare multiple PDF files programmatically. You can find more information in the online Java API documentation or in the SDK directory: "java/javadoc".

There are additional Samples coming with the SDK and online at our GitHub page.

With the provided .Net (C#) API you can call i-net PDFC from a .Net program to compare multiple PDF files programmatically. You can find more information in the online .Net API documentation.

There are additional Samples coming with the SDK. You can find it in the SDK directory: "dotnet".

You can use i-net PDFC within a Jenkins job to compare PDF files automatically.

The i-net PDFC installation package contains a sample Ant script and a Java sample that executes i-net PDFC as JUnit test. This sample can be found in the directory: <install-dir>/Documentation and Samples/Java - Samples/src/test/java/junit.

To integrate i-net PDFC sample with Jenkins, the following requirements must be fulfilled:

1. Jenkins must be installed and configured, so that Ant scripts can be executed
2. the CompareTwoFoldersAsUnitTest.java file in the directory '<install-dir>/java/samples/junit' must be compiled and packaged into a Java archive (.jar)
3. the Ant script from the sample requires a directory containing all JARs from i-net PDFC and a JUnit JAR and the previously created sample JAR.

To integrate the provided sample into Jenkins / Hudson, just do the following steps.

• create a free-style software job in Jenkins / Hudson
• under the 'Advanced Project Options' select 'Use custom workspace' and enter the directory containing the Ant build script
• Select 'Invoke Ant' under the 'Build' section of the job
• open the 'Advanced...' options of the Ant build and add the following 3 properties
  • source_dir=<path to the source pdf files>
  • reference_dir=<path to the reference pdf files>
  • libraries_dir=<path to the directory containing all required libraries>
• under the 'Post-build Actions' select 'Publish JUnit test result report' and enter 'junit-reports/*.xml'
• save the configuration and run the new job