Xml Format For "Request" Or "Delivery" Metadata - IBM 4.6.x User Manual

Ibm user guide adapter for siebel ebusiness applications 4.6.x
Table of Contents

Advertisement

XML format for "request" or "delivery" metadata

At the end of this XML format are the extended data elements. The extended data
elements for adapter request and delivery events represent data from the business
object being processed. This data includes the name of the business object, the key
(foreign or local) for the business object, and business objects that are children of
parent business objects. The children business objects are then broken down into
the same data as the parent (name, key, and any children business objects). This
data is represented in an extended data element of the event definition. This data
will change depending on which business object, which keys, and which child
business objects are being processed. The extended data in this event definition is
just an example and represents a business object named Employee with a key
EmployeeId and a child business object EmployeeAddress with a key EmployeeId.
This pattern could continue for as much data as exists for the particular business
object.
<eventDefinition name="createEmployee"
"2004-05-13T17:00:16.319Z"
for messages to be sent/sorted logically
of the source component.
server name...example is "WQMI"
extension name is always the business object verb followed by the business
object name
parent="event">
<property name ="creationTime" //Comment: example value would be
required="true" />
<property name="globalInstanceId" //Comment: Automatically generated
by Common Event Infrastructure
required="true"/>
<property name="localInstanceId"
object verb+business object name+#+app name+ business object identifier
required="false"/>
<property name="sequenceNumber"
required="false"/>
<property name="version" //Comment: Version of the event...value is
set to 1.0.1
required="false"
defaultValue="1.0.1"/>
<property name="sourceComponentId"
path="sourceComponentId"
required="true"/>
<property name="application"
source application generating the event...example is
"SampleConnector#3.0.0"
path="sourceComponentId/application"
required="false"/>
<property name="component"
path="sourceComponentId/component"
required="true"
defaultValue="ConnectorFrameWorkVersion#4.2.2"/>
<property name="componentIdType"
and meaning of the component
path="sourceComponentId/componentIdType"
required="true"
defaultValue="Application"/>
<property name="executionEnvironment" //Comment: Identifies the
environment#version the app is running in...example is "Windows 2000#5.0"
path="sourceComponentId/executionEnvironment"
required="false" />
<property name="instanceId" //Comment: Value is business object
verb+business object name+#+app name+ business object identifier
path="sourceComponentId/instanceId"
required="false"
<property name="location"
path="sourceComponentId/location"
//Comment: This
//Comment: Value is business
//Comment: Source defined number
//Comment: The name#version of the
//Comment: This will be the name#version
//Comment: specifies the format
//Comment: The value of this is the
Appendix C. Common Event Infrastructure
117

Advertisement

Table of Contents
loading

Table of Contents