XML Over HTTP Writer Output Adapter


The TIBCO StreamBase® XML-Over-HTTP Output Adapter is suitable for posting tuples to an HTTP server. Tuples are posted as HTTP POST transactions where a parameter named tuple is set to the URL-encoded version of the serialized input tuple as XML. The adapter does not support fields in the input tuple of type list or tuple.

Tuples can be buffered into single POST calls by setting the flushInterval parameter. The number of messages to post in any interval can be limited by specifying a Max Message Cache size. When using Max Message Cache, messages above the limit are not delivered.


The XML Over HTTP Writer adapter is configured with the properties shown in the following table. Properties are set in the Properties view, Adapter Settings tab.

Property Description Default
URL (string) The URL to HTTP post to. None
Flush Interval (optional string) How often to deliver messages to the specified URL, in milliseconds. If set to 0, messages are delivered immediately. See the next property for the case where this parameter is required. 0, write immediately
Max Message Cache (int) The maximum number of messages to queue each interval. If set to 0, unlimited messages are cached per interval. If this parameter is set, the Flush Interval parameter must also be set and its value must be greater than 0. 0, unlimited
Log Level Controls the level of verbosity the adapter uses to send notifications to the console. This setting can be higher than the containing application's log level. If set lower, the system log level will be used. Available values, in increasing order of verbosity, are: OFF, ERROR, WARN, INFO, DEBUG, TRACE. INFO

Typechecking and Error Handling

URL must be a parseable URL.

If Max Message Cache is set, must be 0 or greater, and Flush Interval must be set and greater than 0.

The input stream cannot contain fields of type list or tuple

If specified and those conditions are not met, typechecking fails.

Suspend/Resume Behavior

On suspend, all cached messages are delivered.

On resumption, caching is restarted. The first message delivery occurs at resume time + Flush Interval.