To determine PDF/A compliancy, perform the following steps:
Include project files.
Create a DocConvert client
Reference a PDF document used to determine PDF/A compliancy.
Set run-time options.
Retrieve information about the PDF document.
Include project files
Include the necessary files in your development
project. If you are creating a client application by using Java,
include the necessary JAR files. If you are using web services,
make sure that you include the proxy files.
The following
JAR files must be added to your project’s class path:
adobe-livecycle-client.jar
adobe-usermanager-client.jar
adobe-docconverter-client.jar
adobe-utilities.jar (required if LiveCycle is deployed
on JBoss Application Server)
jbossall-client.jar (required if LiveCycle is deployed
on JBoss Application Server)
For information about
the location of these JAR files, see Including LiveCycle Java library files.
Create a DocConvert client
Before you can programmatically perform
an DocConverter operation, you must create a DocConverter client.
If you are using the Java API, create a DocConverterServiceClient object.
If you are using the DocConverter web service API, create a DocConverterServiceService object.
Reference a PDF document used to determine PDF/A compliancy
A PDF
document must be referenced and passed to the DocConverter service
in order to determine whether the PDF document is PDF/A-compliant.
Set run-time options
You can set a run-time option that determines
how much information is tracked during the conversion process. That
is, you can set nine different level that specify how much information
the DocConverter service tracks when it converts a PDF document
to a PDF/A document.
Retrieve information about the PDF document
After you create the
DocConverter service client, reference the PDF document, and set
the run-time options, you can determine whether the PDF document
is a PDF/A-compliant document.