JDBC Data Type to Java Data Type Mapping Constraints
Integration Server has some constraints when mapping JDBC data types to Java data types.
If you select one of the following Java data types, the data type will map exactly to the Input/Output tab in Designer:
![*](chapterTOC_bullet.png)
java.lang.String
![*](chapterTOC_bullet.png)
java.lang.Byte
![*](chapterTOC_bullet.png)
java.lang.Boolean
![*](chapterTOC_bullet.png)
java.lang.Character
![*](chapterTOC_bullet.png)
java.lang.Double
![*](chapterTOC_bullet.png)
java.lang.Float
![*](chapterTOC_bullet.png)
java.lang.Integer
![*](chapterTOC_bullet.png)
java.lang.Long
![*](chapterTOC_bullet.png)
java.lang.Short
![*](chapterTOC_bullet.png)
java.util.Date
![*](chapterTOC_bullet.png)
java.math.BigDecimal
![*](chapterTOC_bullet.png)
java.math.BigInteger
![*](chapterTOC_bullet.png)
java.lang.Object
Those data types not included in this list will map to java.lang.Object. In these cases, if the JDBC data type you specify is for input, you will need to pass in the object with the selected Java data type. If the JDBC type is for output, you can cast the object to the selected Java data type.