IBM BJ0NJML Integration Guide - Page 224

Control Types, Boolean Controls, List Controls, Value Controls, Cross-reference Controls

Page 224 highlights

Integration Controls Control Types You can create four types of integration controls to meet your business needs. Boolean Controls A boolean integration control specifies a value of 0 (false) or 1 (true). List Controls A list integration control contains a list of values. You can enter multiple values for the control and optionally assign a system domain to the control. Assigning a domain ensures the validation of any value that is entered for that control, at any level. If a domain is not assigned, there is no validation of the values that are entered. For example, work orders are sent to an external system only if the status of the work order is APPR (approved) or COMPLETE. To determine whether to send the work order, the Java code or the processing rule can check the status of a work order against a list control that contains these two values. Value Controls A value integration control contains a single value. You can enter a single value for the control and optionally assign a system domain to the control. Cross-reference Controls A cross-reference control replaces one value with another. In a publish channel, a system value is converted to an external system value. In an enterprise service, an external system value is converted to a system value. You can optionally assign a system domain to a cross-reference control. If a domain is specified, any system value that is specified for the control is validated against that domain. If a domain is not assigned, there is no validation of the values that are entered. Cross-reference controls must have a one-to-one mapping between the system value and the external system value. If two system values are associated with an external system value, or two external system values with a system value, a processing error occurs. If you create the cross-reference control to function as a multiplication control on an enterprise service, one-to-many mappings can exist. A multiplication control is a cross-reference control that copies, or multiples, an inbound message for multiple organizations or sites. A multiplication control has one external value and multiple system values. Multiplication controls are always specific to the external system. You identify the control as a multiplication control on the Enterprise Service tab in the Enterprise Services application. For example, the system sites correspond to external system business units, but the two systems use different values for these entities. A cross-reference control can perform the translation between the two values. A cross-reference control in an enterprise service can translate business unit EX001 to system site MX001. In a publish channel, the same control can translate MX001 to EX001. 210 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

Integration Controls
210
Integration Guide
Control Types
You can create four types of integration controls to meet your business needs.
Boolean Controls
A boolean integration control specifies a value of 0 (false) or 1 (true).
List Controls
A list integration control contains a list of values. You can enter multiple values
for the control and optionally assign a system domain to the control. Assigning a
domain ensures the validation of any value that is entered for that control, at any
level. If a domain is not assigned, there is no validation of the values that are
entered.
For example, work orders are sent to an external system only if the status of the
work order is APPR (approved) or COMPLETE. To determine whether to send
the work order, the Java code or the processing rule can check the status of a work
order against a list control that contains these two values.
Value Controls
A value integration control contains a single value. You can enter a single value
for the control and optionally assign a system domain to the control.
Cross-reference Controls
A cross-reference control replaces one value with another. In a publish channel, a
system value is converted to an external system value. In an enterprise service, an
external system value is converted to a system value. You can optionally assign a
system domain to a cross-reference control. If a domain is specified, any system
value that is specified for the control is validated against that domain. If a domain
is not assigned, there is no validation of the values that are entered.
Cross-reference controls must have a one-to-one mapping between the system
value and the external system value. If two system values are associated with an
external system value, or two external system values with a system value, a
processing error occurs.
If you create the cross-reference control to function as a multiplication control on
an enterprise service, one-to-many mappings can exist. A multiplication control is
a cross-reference control that copies, or multiples, an inbound message for
multiple organizations or sites. A multiplication control has one external value
and multiple system values.
Multiplication controls are always specific to the external system. You identify the
control as a multiplication control on the Enterprise Service tab in the Enterprise
Services application.
For example, the system sites correspond to external system business units, but
the two systems use different values for these entities. A cross-reference control
can perform the translation between the two values. A cross-reference control in
an enterprise service can translate business unit EX001 to system site MX001. In a
publish channel, the same control can translate MX001 to EX001.