Filters and filter chains > Filter reference > LiveCycle filter settings

LiveCycle filter settings
StreamServer can use a LiveCycle output filter to invoke LiveCycle processes that are deployed within Adobe LiveCycle ES and exposed through web services. These web services can be used to integrate LiveCycle processes into the StreamServer pipeline when processing documents.
The filter settings are described in the table below.
The host name or IP address of the server hosting LiveCycle ES. For example:
localhost
8080
The name (case sensitive) of the service to invoke. This name must be the same as the corresponding process created in LiveCycle Workbench ES.
User name to connect to the server hosting LiveCycle ES. Used in case of basic HTTP authentication.
Password to connect to the server hosting LiveCycle ES. Used in case of basic HTTP authentication.
Make asynchronous calls to the service. This option is used when invoking long-lived LiveCycle services.
Make synchronous calls to the service. This option is used when invoking short-lived LiveCycle services.
Only used together with asynchronous calls. This is the interval (milliseconds) used to check for a response to the invocation request.
The root certificate used when HTTPS is used as web service protocol (secure communication). The certificate must be available from a resource set connected to the Platform.
A list of custom keys (key-value pairs) to include in the invocation request.
To be able to handle custom keys, the service must have a variable named optionsMap of the type map. All custom keys defined here will be added to the optionsMap variable in the invoked service.
The values provided can be extracted in the receiving LiveCycle process by using an XPath expression in the LiveCycle process.
Examples of custom keys are passwords for creating password encrypted PDF files. For example:
Key: pdfpassword
Value: encrypted
OpenText StreamServe 5.6 Updated: 2013-03-01