ESB Services for the Client Type of HTTP
The response is present under an IData variable in the pipeline, with a key whose value is the same as the name of the subscriber. For example, if the subscriber is named MyTwitter, then there will be a key in the pipeline with the same name.
The IData structure is:
[subscriber_name]
message
response.data
channel.endpoint
This IData variable contains the actual subscription response contents within the message pipeline variable, which contains the following pipeline variables:
response.data: A String value representing the HTTP response contents.
channel.endpoint: The value corresponds to the subscriber destination from which the response was received.
For HTTP streaming providers, if an ESB service is configured to consume incoming notification messages, the service may get triggered frequently as the back end may be sending periodic control messages to ensure connectivity. In such cases, the ESB service which consumes the notifications should be designed to ignore such control messages. The contents of the periodic connectivity messages and their frequency may vary from back end to back end. For more information, refer the back end specific streaming documentation, which provides information on how streaming notifications and control messages function for a given back end.