Accessibility

Table of Contents

Invoking the LiveCycle ES Distiller API from Java

Installing the required JAR files

You will need the following LiveCycle ES client SDK JAR files for this tutorial:

  • adobe-encryption-client.jar
  • adobe-livecycle-client.jar
  • adobe-usermanager-client.jar

    These JAR files are located in the following path: {install directory}/LiveCycle<version>/LiveCycle_ES_SDK/client-libs/common

  • adobe-utilities.jar

    This file is located in the following path:

    {install directory}/LiveCycle<version>/LiveCycle_ES_SDK/client-libs/jboss

  • jbossall-client.jar

    This file is located in the following path:

    {install directory}/LiveCycle<version>/jboss/client

    (Use a different JAR file if LiveCycle ES is not deployed on JBoss.)

You will also need the third-party JAR files to use the SOAP stack rather than EJB endpoints. If you want to invoke a remote LiveCycle ES instance and there is a firewall between the client application and LiveCycle ES, then it is recommended that you use the SOAP mode. When using the SOAP mode, you have to include additional JAR files located in the following path:

{install directory}/LiveCycle<version>/LiveCycle_ES_SDK/client-libs/thirdparty

For information about the SOAP and EJB modes, see Setting connection properties in Programming with LiveCycle ES.