Page Operations
Browse SpaceDescription
The HTTP client step performs a simple call to a base URL with options appended as shown below:
http://<URL>?param1=value1¶m2=value2&..
The result is stored in a String field with the specified name.
Options
The following table describes the options available for the HTTP client step:
| Option | Description |
|---|---|
| Step name | Name of the step; this name has to be unique in a single transformation |
| URL | The base URL string |
| Accept URL from field? |
Enable this option if you want to get the URL from a previous step. Enabling this will also allow you to specify the name of the input field. |
| Result fieldname | The name of the field to store results |
| Parameters | Area where you define the parameter name-value pairs to pass on the URL |
FAQ
The HTTP client step doesn't do anything
Q: The HTTP client step doesn't do anything, how do I make it work?
A: The HTTP client step needs to be triggered. Use a Row generator step generating e.g. 1 empty row and link that with a hop to the HTTP client step.
The HTTP client step and SOAP
Q: Does the HTTP client support SOAP?
A: No, it just calls an URL with arguments. Future steps may provide SOAP functionality, Work is underway on a WebService step supporting WSDL. The first experimental version appeared in PDI v2.5.0
Example
samples/transformations/HTTP Client - simple retrieval example.ktr