Setting up your integration

After the Source and Target endpoints are configured, you are ready to define the mappings. Understanding the Cast Iron® guidelines for implicit conversion between data types is key to setting up your integration. Before proceeding, familiarize yourself with the information in this section.

When you use the Integration editor to define your mappings, you are presented with a list of source and target fields with two columns of anchor points. You define mappings by connecting these anchor points. For more information about mappings, details on valid data types, and how to convert data types, see Defining the mappings.

The following table shows the specific guidelines for implicit casting between data types. The Source column specifies the source data used in the mapping conversion. The Target column shows the derived target. The Comment column provides any necessary additional information about the selected operation.
Table 1. Cast Iron Express® guidelines for casting between data types.
Source Target Comment
Any String All data types are converted to string.
Any Boolean “T," “t,” “true,” “TRUE,”, “tRuE,” “1” and similar are cast to “TRUE.” Anything else is cast as “FALSE.”
String Number Converts a string that contains a numeric representation such as "10" or "3.14" into a decimal number type.
Note:
Strings which do not contain numbers result in a failure when the source data is processed.
String Integer Converts a string that contains an integer numeric representation such as "10" into an integer number type. Strings which do not contain integer numbers result in a failure when the source data is processed. Users can avoid this situation by using Round, Ceiling, or Floor functions to convert from decimal number strings to integer types.
Number Integer Converts a decimal number such as 10 or 3.14 into an integer. For non-integer numbers the value is automatically converted in the same way as if the user applied the Round function. Users can enforce more specific control of the conversion by using a Round, Ceiling, or Floor function.



Feedback | Notices


Timestamp icon Last updated: Thursday, 2 June 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.api.omniapps.doc/integrations_settingupintegration.html