LiveCycle output connector

LiveCycle output connector
StreamServer can use a LiveCycle output connector 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 connector settings are described below.
Host
The host name or IP address of the server hosting LiveCycle ES. For example:
localhost
Port
The port used by the LiveCycle ES server. For example:
8080
Web service name
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
User name to connect to the server hosting LiveCycle ES. Used in case of basic HTTP authentication.
Password
Password to connect to the server hosting LiveCycle ES. Used in case of basic HTTP authentication.
Enable asynchronous communication
Asynchronous poll interval
Only used together with asynchronous calls. This is the interval (milliseconds) used to check for a response to the invocation request.
Root certificate for SSL communication
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.
Custom options
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