HTTP and Lobster_data
Lobster_data (that is, the HTTP service on the Integration Server and a profile in Lobster_data) can communicate with other systems both as an HTTP(S) server and as an HTTP(S) client. By which we either mean the unencrypted HTTP protocol or the SSL encrypted HTTPS.
Lobster_data Profile as HTTP Server
Phase 1, Input Agent HTTP(S)
An external HTTP(S) client sends a request to the HTTP service of the Lobster Integration Server. The data is passed to a matching profile that uses an event-driven Input Agent of type HTTP(S) in phase 1. The output data of the profile can be returned as a response to the HTTP(S) client
To transfer data to Lobster_data, the HTTP request method POST should be used.
When transferring data, the processing is synchronous, i.e. the response will be sent after the processing of the profile is complete.
Phase 1, Any Time-driven Input Agent Triggered by HTTP Request
An external HTTP(S) client sends a request to the HTTP service of the Lobster Integration Server. That starts a matching profile with a time-driven Input Agent and option Triggered by/HTTP request. This Input Agent collects its input data via its configured data source (e.g. a database), i.e. the data does not come from the HTTP request itself.
The profile can only retrieve request parameters as variable values from the client request. Those variable values can then, for example, be used in the mapping of the profile or to parameterize the Input Agent, e.g. in the WHERE clause of a database select.
The output data of the profile (if written as a file under a specified path) can be returned to the triggering HTTP(S) client as the response, as described in the section Trigger.
The HTTP request method GET is usually used for triggering.
Lobster_data Profile as HTTP Client
Phase 1, Time-driven Input Agent HTTP
A profile uses a time-driven Input Agent of type HTTP in phase 1. It sends a request to an external HTTP(S) server. The response of the server is received by the profile as input data.
Phase 6, Response Route HTTP(S)
A profile sends its output data to an external HTTP(S) server in a Response Route of type HTTP(S) in phase 6. The response of the server can be forwarded by Message to a subsequent profile. More details in section Profile Chains.