Download the file pdfunit-monitor-<VERSION>.zip
from the project's site:
http://www.pdfunit.com/en/download/index.html.
Unzip the file into a folder, for example into PROJECT_HOME/lib/pdfunit-monitor-VERSION
.
In the following text that folder is referred to as PDFUNIT_MONITOR_HOME.
The folder PDFUNIT_MONITOR_HOME contains a script named startPDFUnitMonitor.bat
to start the PDFUnit-Monitor under Windows and startPDFUnitMonitor.sh
to
start it under Unix.
If you want to store PDFUnit-Java in a directory other than PDFUNIT_MONITOR_HOME/lib
,
you have to change the CLASSPATH. Look for the variable PDFUNIT_JAVA_HOME in
the start script.
If you have licensed PDFUnit, add the folder containing the license key file license-key_pdfunit-java.lic
to the classpath.
You are welcome to evaluate PDFUnit without a license. In that case the number of tests is limited to 50. And you have to solve a simple math question which is shown in a message box. If you calculate successfully, the test will run, otherwise you have to restart your test and calculate again.
Sometimes, the message box is covered by other applications and PDFUnit-Monitor is blocked. Minimize all applications to look for the message box.
The PDFUnit-Monitor and PDFUnit-Java need a license when they are used in a commercial context. Write a mail to info[at]pdfunit.com and ask for a license. You will receive an answer as soon as possible.
The license fee is calculated individually. A small company should not pay as much as a big company, and someone testing only a few PDF documents, of course, pays less. And if you want to get a free license, give us some reasons. It is not impossible.
If you have ordered a license you will receive a ZIP file and a separate file
license-key_pdfunit-java.lic
. Install the contents of the ZIP file
as described above and include the license file in your classpath.
Any change to the license file makes it unusable. If this happens, contact PDFUnit.com and ask for a new license file.
If you have a problem with the configuration, start the script
verifyInstallation.bat
or verifyInstallation.sh
.
You will get a detailed problem analysis. See chapter
5.4: “Verifying the Configuration”.