Integration Framework for Data Exchange
8
Integration Guide
Integration Framework
for UI Integration
The integration framework provides a mechanism for you to navigate from a
system application user interface to an external application user interface. You can
define the context to facilitate the navigation into the external application
interface. The integration framework supports URL substitutions of any values of
any system business object. For example, you can configure the system to display
a specific part number in an external application.
You can use operational management product-specific features when you launch
to an operational management product application user interface. Features
include retrieving the registered host name of the operational management
product and a configured item source token for the operational management
product.
Through the Launch in Context application, you can navigate to any external
application other than the operational management product. You also can
navigate to a system user interface from an external application (Land in
Context).
Integration Framework for Data Exchange
The integration framework consists of individual data exchange components and
features.
Object Structures
An object structure is the common data layer that the integration framework uses
for all outbound and inbound application data processing. An object structure
consists of one or more business objects that make up the content of an XML
message. You can use the message content of a single object structure to support
inbound and outbound messages.
When you define multiple objects in the object structure, the objects must have a
reference to a valid parent-child relationship within the system.
The object structure has a Java definition class that you can code to perform logic
such as filtering for outbound messages. For inbound messages, you can use an
object structure Java processing class to invoke specific business object logic that
is beyond the normal integration framework insert, update, and delete
processing.
Actions
You use actions to implement an
automated or semi-automated
invocation of integration modules
and operational management
products by a process management
product. You can initiate actions from
user interface applications,
escalations, and workflows.
Component
Description
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 ...