Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

HTTP as a Source

When HTTP is a source, the Jitterbit Integration software performs a GET action to retrieve data from the URL that is created by the source information. A connection is made to the URL that is created as a combination of the host, port, path, file name, and query string.

HTTP as a Target

When HTTP is a target, the Jitterbit Integration software performs a POST action to post data to the URL that is created by the source document. This is very different than using HTTP as a source, where the source location supplies the data for the transformation. When using HTTP as a target, the user is using the HTTP POST method to actually post data to a URL that should be recognized by the Web server. This provides great power to the user, in that the transformation process has the ability to produce a document that can be understood by a server-side script-enabled Web page, CGI, or ISAPI filter.

NOTE: HTTP POST can include virtually any type of payload, but must be understood by the Web server that is receiving it.

 The user supplies the header information for the post action in the target definition. An ASCII text message is then formed by using this header information, a blank line, and the transformed information from the source. For example, let’s say that there is a transformation from a database query to an XML document. The transformation name is “TRAN1”. The data is retrieved from the source, and transformed to the XML document format defined in the transformation. Next, the Target header information (defined by the user in the target definition) is added to the beginning of the XML document, along with a blank line, and then the XML content.

The final document in the first step is then passed to the target URL using an HTTP POST command.

Similar to HTTP as a Source, a response is returned from the HTTP request and is parsed by the software. If the message indicates success, nothing more is done. When an error message is received, it is used as part of the error logging process for the operation.

On This Page

Related Topics

There is no content with the specified labels

Last updated: 

  • No labels