Data Type Mapping

JSON	Integration Server
object	Document
string	String
number (integer)	Integer or Long Java wrapper. For more information about converting JSON integers, see the decodeIntegerAsLong input parameters in pub.json:jsonStreamToDocument and pub.json:jsonStringToDocument.
number (real)	Float or Double Java wrapper. For more information about converting real numbers, see the decodeRealAsDouble input parameter in pub.json:jsonStreamToDocument and pub.json:jsonStringToDocument.
true/false	Boolean Java wrapper
Array of JSON type	Array of Integration Server type If the JSON object contains a string array, Integration Server sets the corresponding field in the IS document type to String List. If the JSON object contains a two-dimensional string array, Integration Server sets the corresponding field in the IS document type to String Table. If the JSON object contains a array having different types of objects (for example, integer, string, etc.), Integration Server sets the corresponding field in the IS document type to Object List with Java wrapper type as UNKNOWN. Note: Integration Server does not support the following multi-dimensional arrays in JSON objects: Two-dimensional arrays of data types other than string Multi-dimensional arrays of three or more dimensions (three-dimensional, four-dimensional, etc.) For pub.json:jsonStringToDocument and pub.json:sonStreamToDocument, these kinds of arrays become an Object List of UNKOWN type. For IS document types created from a JSON object using Designer, these kinds of arrays become an Object with a Java wrapper type of UNKNOWN.
Array of null	Object List
null	null
All others	String Note: If an object has a toString() implementation, Integration Server uses that implementation. If the object does not provide a toString() implementation, Integration Server uses Object.toString(). Object.toString() returns the class name and hexadecimal representation of the hash code of the object, such as "javax.namining.InitialContext@3ae6f00b".

Note: If JSON text begins with an array at the root and the array is unnamed, when parsing the JSON text, Integration Server uses a fixed name of $rootArray for the array value. The $rootArray field appears in the pipeline. When creating a JSON response, if the pipeline contains $rootArray with an array value at its root, Integration Server discards the $rootArray name and transforms the array value into a JSON array.

Note: With regards to using Integration Server data types with JSON, Integration Server supports only those types that can be mapped to a JSON value as defined in https://tools.ietf.org/html/rfc7159#section-3. Integration Server can take any valid arbitrary JSON text and convert it to an IData. Integration Server must be able to convert the resulting IData to JSON text that is identical to the original text. If Integration Server cannot do that for an Integration Server data type, then Integration Server does not support the use of that data type with JSON. For example, com.wm.util.Table is not supported for JSON even though it is supported for XML. Integration Server embeds additional type information in XML when converting IData to XML. However, Integration Server cannot embed the additional type information in JSON because the additional type information is treated as JSON text. The resulting JSON text would not match the original JSON text.