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.
Summary of Contents for BJ0NJML - Service And Asset Management
Page 12: ...xii Integration Guide ...
Page 14: ...xiv Integration Guide ...
Page 16: ......
Page 31: ...Integration Framework for User Interface Integration Integration Framework Architecture 17 ...
Page 32: ...Integration Framework for User Interface Integration 18 Integration Guide ...
Page 60: ...Synchronous Inbound Integration Processing 46 Integration Guide ...
Page 122: ...Configuring External Systems 108 Integration Guide ...
Page 142: ...Non queue Error Management 128 Integration Guide ...
Page 154: ...Integration Components 140 Integration Guide ...
Page 156: ......
Page 172: ...Writing Custom Handlers 158 Integration Guide ...
Page 176: ...Queue Tables 162 Integration Guide ...
Page 190: ...IBM WebSphere MQ 176 Integration Guide ...
Page 212: ...Inbound Message Receipt 198 Integration Guide ...
Page 226: ...Integration Controls 212 Integration Guide ...
Page 252: ...Predefined External System Modifications 238 Integration Guide ...
Page 263: ...Web Service Queries Integration Queries 249 ...
Page 264: ...Web Service Queries 250 Integration Guide ...
Page 272: ...Integration Web Service Invocations 258 Integration Guide ...
Page 276: ...Multilanguage Attributes 262 Integration Guide ...
Page 293: ...Integration Module Invocation Integration Modules 279 ...
Page 294: ...Integration Module Invocation 280 Integration Guide ...
Page 302: ...Associating a Condition with a Signature Option 288 Integration Guide ...
Page 320: ...Work Order Collaboration Switches 306 Integration Guide ...
Page 324: ...310 Integration Guide ...