Invocation API Quick Starts

The following Quick Starts are available for programmatically invoking LiveCycle services:

Description	Remoting API	Java API	Web service API
Invoking Human-Centric Long-Lived Processes	Invoking a long-lived process using Remoting	Quick Start: Invoking a long-lived process using the Invocation API	Quick Start: Invoking a long-lived process using the web service API
Invoking a short-lived process using the Invocation API	N/A	Quick Start: Invoking a short-lived process using the Invocation API	N/A
Invoking LiveCycle using Base64 encoding (Java web service proxy)	N/A	N/A	Quick Start: Invoking a service using Java proxy files and Base64 encoding
Invoking LiveCycle using Base64 encoding (.NET web service proxy)	N/A	N/A	Quick Start: Invoking a service using base64 in a Microsoft .NET project
Invoking LiveCycle using MTOM (.NET web service example)	N/A	N/A	Quick Start: Invoking a service using MTOM in a .NET project
Invoking LiveCycle using SwaRef (Java web service example)	N/A	N/A	Quick Start: Invoking a service using SwaRef in a Java project
Invoking LiveCycle using BLOB data over HTTP (Java web service example)	N/A	N/A	Quick Start: Invoking a service using BLOB data over HTTP in a .NET project
Invoking LiveCycle using BLOB data over HTTP (.NET web service example)	N/A	N/A	Quick Start: Invoking a service using BLOB data over HTTP in a Java project
Invoking LiveCycle using DIME (Java web service example)	N/A	N/A	Quick Start: Invoking a service using DIME in a Java project
Invoking LiveCycle using Remoting	Quick Start: Invoking a short-lived process by passing an unsecure document using (Deprecated for AEM forms) LiveCycle Remoting	N/A	N/A
Passing secure documents to invoke processes using Remoting	Quick Start: Invoking a short-lived process by passing a secure document using Remoting	N/A	N/A
Invoking custom component services using Remoting	Quick Start: Invoking the Customer custom service using Remoting	N/A	N/A

LiveCycle operations are organized into the following Quick Start categories:

Java API (EJB) - Uses 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) - Uses a .NET client proxy and MTOM. The .NET client proxy is created. (See Invoking LiveCycle using MTOM.)
Web service API (Base64) - Uses a .NET client proxy and Base64. The .NET client proxy is created. (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. The Java proxy files are created. (See Invoking LiveCycle using SwaRef.)

Note: Quick Starts located in Programming with LiveCycle are based on 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.)