|
|
Component: HTTP Sender
|
|
Invokes an internet resource using HTTP. This service is able to automatically submit HTML forms, and/or load the contents of Web-pages into the process data. This sort of thing is very useful when trying to integrate a LiveCycle process with any traditional Web-Application. Technically this service is able to perform an HTTP-Get or HTTP-Post on an internet resource. It can take any number of parameters and the values can be pulled from the process data. The response is passed back into the process data as a string.
|
Operations
|
Icon
|
Name
|
About
|
Link |
|
|
Send HTTP Request
|
Invokes an internet resource using HTTP. This service is able to automatically submit HTML forms, and/or load the contents of Web-pages into a process variable. For a detailed description of the http GET and POST services, please search the web.
Why use it
- One of your process needs to send an SMS (Mobile Phone text message) to a recipient. You have a SMS provider that allows you to send messages by filling in a form on their site.
- A process needs to perform search engine query - a query can be constructed as a URL with query parameters (for example, http://www.google.com/search?q=livecycle), and the resulting html results will be returned.
- You are communicating with a REST-style service (Representational State Transfer) instead of using Web Services. HttpSender allows you to do this very simply.
- This service is very useful when trying to integrate a LiveCycle process with any traditional Web-Application. Technically this service is able to perform an HTTP-Get or HTTP-Post on an internet resource. It can take any number of parameters and the response can be retrieved into process data.
|
Properties |
Input Parameters
|
HTTP Settings - Enter details about your HTTP request.
|
|
|
URL - The URL to connect to
HTTP Method - The method used to send HTTP request. Either GET or POST.
Request Body - Optional request body when choosing to use POST for HTTP Method.
Username - Optional username for authentication
Password - Optional password for authentication
|
|
Parameters - Configure HTTP request parameters.
|
|
|
Parameters - Parameters used to send request to URL. For GET, these will be appended to the URL. For POST, these will be embedded in the body of the request. Map structure: ParamName=>ParamValue.
|
|
Input GUI - Enter one row for each Parameter and value. Add/remove rows using '+' and '-'.
|
|
|
Name * - This is the name of a parameter name being passed to the HTTP resource. Click '+' to add a row and then enter the param name either literally (in quotes) or using the XPath Expression builder (by clicking on the '...' button).
Value - This is the value of a parameter name being passed to the HTTP resource. Enter the param value either literally (in quotes) or using the XPath Expression builder (by clicking on the '...' button).
|
|
Proxy Settings - If the HTTP request has to cross an HTTP proxy - enter those details here.
|
|
|
Enable Proxy - Check to enable proxy to connect to the specified URL. Many organizations require communication with the Internet to occur via a Proxy Server.
Proxy Server - Proxy Server
Proxy Port - Proxy Port
Proxy Username - Proxy username if proxy requires user authentication.
Proxy Password - Proxy password if proxy requires user authentication.
|
|
Test - Test your settings. Note that parameters are not used here as they may be looking at runtime data.
|
|
|
Test - Click on "Test" button to test sending HTTP request to the specified URL. Note: All parameters have to be specified literally for testing - no XPath parameters..
|
Output Parameters
|
Response - Apply response back into process data.
|
|
|
HTML Response - The HTML response from sending request to the specified URL. Type: String
Request Status - The request status code returned from sending request to the specified URL. Typical response codes include 400 (success) and 404 (page not found). Type: int
|
|
DOWNLOADS
DOCUMENTATION
|
|
Products
LiveCycle ES Components Installer
Business Process Techniques and Patterns