IBM BJ0NJML Integration Guide - Page 223

Integration Controls, Control Levels

Page 223 highlights

Integration Controls Integration Controls Control Levels Integration controls give you the ability to configure the behavior of any enterprise service or publish channel according to the requirements of individual organizations and sites. Processing rules and Java classes can access integration controls for evaluation purposes. Integration controls are defined at the system level. You can assign controls to one or more enterprise service and publish channel. The control values can be configured at the external system level. Two external systems that process the same enterprise service can share the same processing logic, class files, and processing rules, yet they process the data differently because they use different control settings. All system master data and documents are stored at the system level, organization level, or site level. For example, item data is stored at the system level, accounting information at the organization level, and storerooms, inventory, and work orders at the site level. An implied hierarchy exists among these levels, because organizations are defined for a system, and sites are defined within organizations. Accordingly, an integration control can be configured to override values at any of the following levels: Control Value System-level Organization-level Site-level Description A system-level value applies to all system organizations and sites. If the control is not configured for organization- or site-level values, system processing uses the system default. If the control is configured for organization-level values, or site-level values but none exists for a particular organization or site, system processing uses the system-level value. An organization-level value applies to all system sites within an organization. If a control is configured for organization-level values but none exists for a particular organization, system processing uses the system-level value. A site-level value applies to a specific site within a system organization. If a control is configured for sitelevel values but none exists for a particular site, system processing uses the organization value (if one exists) or the system-level value. Data that is processed by enterprise services or publish channels that use a control with an organization or site override must be at the organization or site level. Integration Framework Customization with Processing Rules 209

  • 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
Integration Framework Customization with Processing Rules
209
Integration Controls
Integration controls give you the ability to configure the behavior of any
enterprise service or publish channel according to the requirements of individual
organizations and sites. Processing rules and Java classes can access integration
controls for evaluation purposes.
Integration controls are defined at the system level. You can assign controls to one
or more enterprise service and publish channel. The control values can be
configured at the external system level. Two external systems that process the
same enterprise service can share the same processing logic, class files, and
processing rules, yet they process the data differently because they use different
control settings.
Control Levels
All system master data and documents are stored at the system level,
organization level, or site level. For example, item data is stored at the system
level, accounting information at the organization level, and storerooms,
inventory, and work orders at the site level. An implied hierarchy exists among
these levels, because organizations are defined for a system, and sites are defined
within organizations. Accordingly, an integration control can be configured to
override values at any of the following levels:
Data that is processed by enterprise services or publish channels that use a control
with an organization or site override must be at the organization or site level.
Control Value
Description
System-level
A system-level value applies to all system
organizations and sites. If the control is not configured
for organization- or site-level values, system
processing uses the system default. If the control is
configured for organization-level values, or site-level
values but none exists for a particular organization or
site, system processing uses the system-level value.
Organization-level
An organization-level value applies to all system sites
within an organization. If a control is configured for
organization-level values but none exists for a
particular organization, system processing uses the
system-level value.
Site-level
A site-level value applies to a specific site within a
system organization. If a control is configured for site-
level values but none exists for a particular site, system
processing uses the organization value (if one exists) or
the system-level value.