Summary
NOTE: This data encoder sends the object in Server XML format to the profile's
_datainput.
Some Lobster Integration profiles need an object's complete internal data structure. For this case, choose the Server data encoder. This reference describes its output format for integration specialists and IT admins.
Purpose
The Server data encoder passes a Lobster Data Platform object to a Lobster Integration profile. The transfer uses the Server XML format. The format fully represents the object's internal data structure. The target profile receives the data at the _data input.
In the Call profile behavior, you select the encoder using the value SERVER. Older sources also call this format the _pro XML format.
The encoder writes the XML in UTF-8. If the input value is $null, it creates an empty nil element.
NOTE: For examples of the Server XML format, see the article Object to server XML.
Parameters
You do not configure parameters for the Server data encoder. The encoder outputs the data structure unchanged.
Difference from other data encoders
The XML data encoder sends the object as Client XML and is deprecated. The JSON data encoder sends the object in JSON format. The Server data encoder uses the internal Server XML format instead and keeps the data structure unchanged.
Counterpart: Server data decoder
The Server data decoder accepts Server XML as input from _data. Together, the encoder and decoder form the outbound and return path of the object transfer.