Invoking LiveCycle using APIs

Adobe LiveCycle is J2EE-based enterprise software that consists of services that operate within a shared infrastructure. Service operations typically consume or produce documents. By using LiveCycle, you can combine process management with electronic forms, document security, and document generation in an integrated and cohesive set of services. These services can be accessed from inside and outside the firewall.

Client applications can programmatically invoke LiveCycle services using a Java API, web services, Remoting, and REST. Using Administration Console, you can configure a service to expose an endpoint that lets LiveCycle services by programmatically invoked. By default, most services are pre-configured to expose Remoting, Java, and web service endpoints.

Your business requirements determine which invocation method to use. For example, using the Java API, you can integrate LiveCycle functionality into your Java enterprise applications, such as Java Entity and Message beans. Likewise, you can integrate LiveCycle functionality into .NET projects (or other projects developed with development environments that support web service standards) using web services.

Services require a service container to run, similar to how Enterprise JavaBeans™ (EJBs) require a J2EE container. LiveCycle includes only one implementation of a service container. The service container is responsible for managing the lifetime of a service, including deploying it and ensuring that all requests are sent to the correct service. It also manages documents that a service consumes or produces.

Note: Programming with LiveCycle does not include information on how to invoke LiveCycle using Watched Folders or e-mail.

// Ethnio survey code removed