OpenEdge BPM dataslots to Java data types conversion

Managed Adapters Guide

Understanding the Managed Adapter framework : Framework components : Supported data types : OpenEdge BPM dataslots to Java data types conversion

The Managed Adapter dataslot configuration supports OpenEdge BPM dataslots to Java data types conversion, as listed in the following table.

OpenEdge BPM dataslots to Java data types conversion

Table 6. Supported data types for conversion
	Target data type
Source dataslot	java.lang.String	java.lang.Long	java.lang.Integer	java.lang.Double	java.lang.Float	java.lang.BigDecimal	java.lang.Timestamp	java.lang.Boolean	java.lang.Object	java.lang.Byte
Character	S	SF	SF	SF	SF	SF	SF	SF	S	NS
Integer	SC	SC	S	SC	SC	SC	SC	SC	S	NS
Int64	SC	S	SC	SC	SC	SC	SC	SC	S	NS
Decimal	SC	SC	SC	SC	SC	S	SC	SC	S	NS
Double	SC	SC	SC	S	SC	SC	SC	SC	S	NS
Logical	SC	NS	NS	NS	NS	NS	NS	S	S	NS
Object	SC	SF	SF	SF	S	SF	SF	SF	S	NS
DateTimeTZ	SC	SC	NS	SC	SF	SC	SC	NS	S	NS
Document	SC	NS	NS	NS	NS	NS	NS	NS	S	S
Raw	SC	NS	NS	NS	NS	NS	NS	NS		S
LongChar	S	SF	SF	SF	SF	SF	SF	SF	SF	NS

S: supported, no conversion performed

SF: supported, if the source is in proper format (True or False)

SC: supported, conversion performed

NS: not supported

Caution: The usage of the LongChar dataslot is suggested only if the data is larger than 32k. For any smaller value, the usage of Character dataslot is suggested. Using Longchar dataslot might cause significant increase in response time.

The maxPostSize value for LongChar feature is set to 2 MB in the DatabaseMapping file in the location: $DLC$\oebpm\server\conf\resources\common. To increase the size to 5MB, edit the <mapping> section as shown below:

<mapping>
<java>com.progress.lang.Longchar</java>
<dataslot>ABL_LONGCHAR</dataslot>
<database>LVARCHAR</database>
<database-mb>LVARCHAR</database-mb>
<size bytes="2097152">2097152</size>
</mapping>

<mapping>
<java>com.progress.lang.Longchar</java>
<dataslot>ABL_LONGCHAR</dataslot>
<database>LVARCHAR</database>
<database-mb>LVARCHAR</database-mb>
<size bytes="5242880">5242880</size>
</mapping>

Also, edit the server.xml file in the location: $DLC$\oebpm\jboss\server\portalServer\deploy\jbossweb.sar to add maxPostSize attribute as shown in the following tables: