IBM BJ0NJML Integration Guide - Page 90

Additional Considerations, Boolean columns, Encrypted fields, Character encoding, Date format

Page 90 highlights

Object Structure Element Additional Considerations Boolean columns Encrypted fields Character encoding Date format Null columns Number format In inbound transactions, a tag that represents a boolean field must contain a value of 0 (false) or 1 (true). If the tag does not contain a 0 or a 1, the object generates an error. If the XML does not include a tag for a boolean field, the object updates the corresponding database value with the default value (0 or 1) that is defined for that column. In inbound transactions, the attribute that represents the maxencrypted field must contain a value of 0 (false) or 1 (true). When the attribute value is 1 the system applies a decryption process to the received data. When the attribute value is 0 the system does not decrypt the received data. If the attribute does not contain a 0 or a 1, the system does not decrypt the received data. If the XML field does not include a tag for an encrypted field, the system does not decrypt the received data. The integration XML uses UTF-8 encoding. If an inbound transaction specifies any other encoding, the entire message must use that encoding. If an error is encountered during the processing of an inbound transaction that uses encoding other than UTF-8, the entire error XML that is written is encoded as UTF-8. The integration XML supports the following ISO 8601 date format. 2004-12-06T10:11:58-05:00 If a tag in an inbound transaction contains no value, the processing logic updates the corresponding database column with a null value. If the XML does not include a tag for a particular field, the processing logic does not update that field in the database. Regardless of the locale setting of the application server or the database, all decimal fields must use a period (.) as the decimal placeholder. Do not format numbers to the left of the placeholder. This format applies to inbound and outbound data. $1,738,593.64 must be in the following format: 1738593.64 76 Integration Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330

Object Structure Element
76
Integration Guide
Additional Considerations
Boolean columns
In inbound transactions, a tag that represents a boolean field must contain a value
of 0 (false) or 1 (true). If the tag does not contain a 0 or a 1, the object generates an
error. If the XML does not include a tag for a boolean field, the object updates the
corresponding database value with the default value (0 or 1) that is defined for
that column.
Encrypted fields
In inbound transactions, the attribute that represents the maxencrypted field
must contain a value of 0 (false) or 1 (true). When the attribute value is 1 the
system applies a decryption process to the received data. When the attribute
value is 0 the system does not decrypt the received data.
If the attribute does not contain a 0 or a 1, the system does not decrypt the
received data. If the XML field does not include a tag for an encrypted field, the
system does not decrypt the received data.
Character encoding
The integration XML uses UTF-8 encoding. If an inbound transaction specifies
any other encoding, the entire message must use that encoding. If an error is
encountered during the processing of an inbound transaction that uses encoding
other than UTF-8, the entire error XML that is written is encoded as UTF-8.
<?xml version="1.0" encoding="ISO-8859-2"?>
Date format
The integration XML supports the following ISO 8601 date format.
2004-12-06T10:11:58-05:00
Null columns
If a tag in an inbound transaction contains no value, the processing logic updates
the corresponding database column with a null value. If the XML does not
include a tag for a particular field, the processing logic does not update that field
in the database.
Number format
Regardless of the locale setting of the application server or the database, all
decimal fields must use a period (.) as the decimal placeholder. Do not format
numbers to the left of the placeholder. This format applies to inbound and
outbound data.
$1,738,593.64 must be in the following format: 1738593.64