Signature Service API Quick Starts

The following Quick Starts are available for the Signature service:

Description

Java API (EJB)

Java API (SOAP)

Web service API (MTOM)

Web service API (Java SwaRef)

Adding Signature Fields

Quick Start (EJB mode): Adding a signature field to a PDF document using the Java API

Quick Start (SOAP mode): Adding a signature field to a PDF document using the Java API

Quick Start (MTOM):Adding a signature field using the web service API

Quick Start (SwaRef):Adding a signature field using the web service API

Retrieving Signature Field Names

Quick Start (EJB mode): Retrieving signature field names using the Java API

Quick Start (SOAP mode): Retrieving signature field names using the Java API

Quick Start (MTOM): Retrieving signature field names using the web service API

Quick Start (SwaRef): Retrieving signature field names using the web service API

Modifying Signature Fields

Quick Start (EJB mode): Modifying a signature field using the Java API

Quick Start (SOAP mode): Modifying a signature field using the Java API

Quick Start (MTOM): Modifying a signature field using the web service API

Quick Start (SwaRef): Modifying a signature field using the web service API

Digitally Signing PDF Documents

Quick Start (EJB mode): Digitally signing a PDF document using the Java API

Quick Start (SOAP mode): Digitally signing a PDF document using the Java API

Quick Start (MTOM): Digitally signing a PDF document using the web service API

Quick Start (SwaRef): Digitally signing a PDF document using the web service API

Digitally Signing Interactive Forms

Quick Start (EJB mode): Digitally signing a XFA-based Form using the Java API

Quick Start (SOAP mode): Digitally signing a XFA-based Form using the Java API

Quick Start (MTOM): Digitally signing a XFA-based Form using the web service API

Not available

Certifying PDF Documents

Quick Start (EJB mode): Certifying a PDF document using the Java API

Quick Start (SOAP mode): Certifying a PDF document using the Java API

Quick Start (MTOM): Certifying a PDF document using the web service API

Quick Start (SwaRef): Certifying a PDF document using the web service API

Verifying Digital Signatures

Quick Start (EJB mode): Verifying a digital signature using the Java API

Quick Start (SOAP mode): Verifying a digital signature using the Java API

Quick Start (MTOM): Verifying a digital signature using the web service API

Quick Start (SwaRef): Verifying a digital signature using the web service API

Verifying Multiple Digital Signatures

Quick Start (EJB mode): Verifying multiple digital signatures using the Java API

Quick Start (SOAP mode): Verifying multiple digital signatures using the Java API

Quick Start (MTOM): Verifying multiple digital signatures using the web service API

Quick Start (SwaRef): Verifying multiple digital signatures using the web service API

Removing Digital Signatures

Quick Start (EJB mode): Removing a digital signature using the Java API

Quick Start (SOAP mode): Removing a digital signature using the Java API

Quick Start (MTOM): Removing a digital signature using the web service API

Quick Start (SwaRef): Removing a digital signature using the web service API

LiveCycle operations are organized into the following API 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 (MTOM) - Demonstrates using a .NET client proxy and MTOM. (See Invoking LiveCycle using MTOM.)

  • 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.)

    Remarque : 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.)