To deploy the invite external users 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 invite external users 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.
Note: In the illustration below, a BootstrapImpl class is shown. This section does not discuss how to create a BootstrapImpl class. For information, see Defining the service’s Bootstrap implementation.
The following illustration shows the Java project’s content that is packaged into the invite external users handler’s JAR file.
You must package the invite external users 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. Only one invite external users handler can be deployed at a given time. (See Deploying your component.)