Integration Framework for Data Exchange
Integration Framework Architecture
9
The object structure is the building block of the integration framework that lets
framework applications to perform the following functions:
T
Publish and query application data
T
Add, update, and delete application data
T
Import and export application data
You also can use the object structure as a service to support inbound message
processing. You can invoke the object structure service as a Web service, as an
Enterprise JavaBean, or by using HTTP. The object structure service supports
system data updates, and queries that are started outside of the system.
Publish Channels
A publish channel is the pipeline for sending data asynchronously from the
system to an external system. Events that initiate publish channel processing are
object events (insert, update, and delete), application-initiated calls, and data
export.
The content of a publish channel XML message is based on the associated object
structure. When you trigger publish channel processing, the integration
framework builds the XML message based on the object structure. The system
then moves the message through multiple processing layers before placing the
message into a queue and releasing the initiator of the transaction.
The publish channel can use the following processing layers:
T
Processing rules – The integration framework provides a rule engine
where you can filter and transform the XML message. You can implement
rules in the Publish Channel application.
T
User exit – Represents a Java class that you can use to filter data, transform
data, and implement business logic. You can use this class as part of an
installation-customization.
T
Data processing class – Represents a Java class that you can use to filter,
transform data, and implement business logic. Adapters for Oracle and
SAP provide processing classes to support integration to these products.
T
XSL map – Represents an XSLT style sheet that you can use to transform
data and perform mapping of the XML message to another format.
After the system places the message into the queue, a polling thread (the system
cron task) picks up the message and sends it to an external system through a
configured endpoint. The endpoint identifies the protocol that the system uses to
send data, such as HTTP or Web services. The endpoint also identifies the
property values that are specific to that endpoint, such as URL, user name, and
password.
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 ...