Try OpenEdge Now
skip to main content
Managed Adapters Guide
Sonic ESB Managed Adapter : Mapping OpenEdge ABL dataslots to Sonic ESB message
 

Mapping OpenEdge ABL dataslots to Sonic ESB message

Sonic ESB contains the following types of messages:
*Message: can have properties, but no content.
*Multipart Message: consisting of multiple parts, with each part having its own content ID and content Type. content Type can be any valid MIME type. Each part of the Multipart message can be mapped to CHARACTER dataslots.
*Text Message: The body of a Text message can be mapped to a CHARACTER dataslot.
*XML Message: The body of an XML message can be mapped to a CHARACTER dataslot. The content of any CHARACTER dataslot, copied to the XML message body, must be in XML format.
The following table lists the Sonic property types and the supported OpenEdge ABL dataslot type.
Table 19. Sonic Property type and supported dataslot
Sonic property type
Supported dataslots
boolean
LOGICAL
byte1
INTEGER
short2
INTEGER
int3
INTEGER
long
INT64
float4
OE Decimal type (Double)
double
OE Decimal type (Double)
string
CHARACTER
1 An exception is thrown if the value of the supported OpenEdge ABL dataslot does not fit the Sonic property type.

2 An exception is thrown if the value of the supported OpenEdge ABL dataslot does not fit the Sonic property type.

3 An exception is thrown if the value of the supported OpenEdge ABL dataslot does not fit the Sonic property type.

4 An exception is thrown if the value of the supported OpenEdge ABL dataslot does not fit the Sonic property type.

* Custom properties