PDF Utilities Service API Quick Starts

The following Quick Starts are available for the PDF Utilities service.

Description	Java API (EJB)	Java API (SOAP)	Web service API (Base64)	Web service API (Java SwaRef)
Converting PDF Documents into XDP Documents	Quick Start (EJB mode): Converting a PDF document to an XDP document using the Java API	Not Available	Quick Start (Base64): Converting a PDF document to an XDP document using the web service API	Not Available
Converting XDP Documents into PDF Documents	Quick Start (EJB mode): Converting an XDP document to a PDF document using the Java API	Not Available	Quick Start (Base64): Converting an XDP document to a PDF document using the web service API	Not Available
Retrieving PDF Document Properties	Quick Start (EJB mode): Retrieving PDF document properties using the Java API	Not Available	Quick Start (Base64): Retrieving PDF document properties using the web service API	Not Available
Summary of steps	Quick Start (EJB mode): Sanitizing PDF documents	Quick Start (SOAP mode): Sanitizing PDF documents
Setting PDF Document Save Modes	Quick Start (EJB mode): Setting the save style for a PDF document using the Java API	Not Available	Quick Start (Base64): Setting the save style for a PDF document using the web service API	Not Available
Sanitizing PDF Documents

LiveCycle operations are organized into the following Quick Start categories:

Java API (EJB) - Demonstrates using the LiveCycle strongly-typed API and the connection mode is set to EJB. (See Setting connection properties.)
Java API (SOAP) - Uses the LiveCycle strongly-typed API and the connection mode is set to SOAP.
Web service API (Base64) - Demonstrates using a .NET client proxy and MTOM. (See Invoking LiveCycle using Base64 encoding.)
Web service API (SwaRef) - Demonstrates using Java proxy classes and SwaRef. These Java proxy classes are separate from the LiveCycle strongly-typed API. (See Invoking LiveCycle using SwaRef.)

注意： Quick Starts located in Programming with LiveCycle are based on the LiveCycle Server being deployed on JBoss Application Server and the Microsoft Windows operating system. However, if you are using another operating system, such as UNIX, replace Windows-specific paths with paths that are supported by the applicable operating system. Likewise, if you are using another J2EE application server, ensure that you specify valid connection properties. (See Setting connection properties.)