Atrium Integrator supported data types
The following table shows the supported external data store types and indicates whether you must define specific connection parameters when using that type. The following table lists the data types supported for each external database.
Supported data store types
Type |
Requires specific connection parameters |
---|---|
BMC Atrium CMDB |
Yes |
Comma separated value (CSV) flat file |
No |
XML |
No |
Databases
|
Yes |
BMC Atrium CMDB attribute data types and corresponding supported data types in external data stores
BMC Atrium CMDB attribute data type |
Oracle |
SQL |
DB2 |
Sybase |
XML and CSV |
MySQL |
---|---|---|---|---|---|---|
character |
number |
varchar |
int |
varchar |
string |
int |
currency |
number varchar |
number |
number |
number |
string |
int |
date |
date |
date/time |
date |
date/time |
date |
date/time |
date/time |
char |
date/time |
date |
varchar |
date |
varchar |
decimal |
Not applicable |
int |
int |
int |
int |
varchar |
diary |
number |
varchar |
int |
varchar |
string |
int |
integer |
number |
int |
int |
int |
number |
int |
real |
number |
int |
int |
int |
number |
int |
selection |
char |
int |
int |
varchar |
string |
int |
time |
char |
varchar |
varchar |
varchar |
date |
varchar |
Note
If a BMC Atrium CMDB attribute of the currency data type is mapped to an integer field in the external data store, the default allowable currency type (USD) in BMC Atrium CMDB is populated along with the integer field. However, if a BMC Atrium CMDB attribute of the currency data type is mapped to a varchar field in the external data store, Atrium Integrator sets the currency type based on the value that you have specified in the varchar field. For example, if the varchar field value is 2134 EUR, Atrium Integrator sets the currency type as EUR.
Note
Each value that is defined for a BMC Atrium CMDB attribute of the enum data type has an associated ID. A varchar field in the external data store can be mapped to the selection value that is defined for the attribute of the enum data type. An integer field in the external data store can be mapped to the associated ID that is defined for the attribute of the enum data type.
Comments
I would like to see attachment fields included in this diagram. If not included, can we assume that attachment fields are not supported by Atrium Integrator?
Hi Terje,
Thank you for your query. Will speak to the SME and respond at the earliest.
Regards,
Maithili
Hi Terje,
Attachment fields are supported by Atrium Integrator. Will revise the diagram soon.
Regards,
Maithili
Hi Terje,
Mapping of attachment field to a class attribute is not supported directly. However, there is a workaround. When DB is used as a source, you can go to the job and explicitly change the transformation for mapping DB - binary blob field to map to an attachment field using AROutput.
In case the source is CSV/ XML while creating AI job from console, there is no mapping required.
Thank you for pointing this out to us! Will add a note in the topic accordingly.
Regards,
Maithili