Java data types to OpenEdge dataslots conversion

Managed Adapters Guide

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

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

Java data types to OpenEdge dataslots conversion

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

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: