To deploy the external authorization handler to LiveCycle ES, you must package your Java project into a JAR file. You must ensure that the external JAR files on which the authorization handler’s business logic depends, such as the edc-server-spi.jar and adobe-rightsmanagement-client.jar files ,are also included in the JAR file. As well, the component XML file must be present. The component.xml file and external JAR files must be located at the root of the JAR file.
The following illustration shows the Java project’s content that is packaged into the external authorization handler’s JAR file.
You must package the external authorization handler into a JAR file. In the previous diagram, notice that .JAVA files are listed. Once packaged into a JAR file, the corresponding .CLASS files must also be specified. Without the .CLASS files, the authorization handler does not work.
Note: After you package the external authorization handler into a JAR file, you can deploy the component to LiveCycle ES. (See Deploying your component.)