Bookshelf Home | Contents | Index | Search | PDF

Siebel eFinance for Teller Connector to IBM WebSphere Business Component Composer Guide > Teller IFX Connector Roadmap > Configuring the External Integration Object >

Examining an Existing External Integration Object

---

To learn more about the external integration object, open and study a standard external integration object, such as tllr.BrnOpenRs, in Siebel Tools. Examine how the hierarchy is preserved, how the cardinality and data type are indicated, and how to relate an integration component to an XML element in the message definition.

To open the integration object definition in Siebel Tools

Open Siebel Tools.
Choose Integration Object from the Object Explorer Window.
In the Objects Window, query for integration object tllr.BrnOpenRs.
Expand the Integration Object in the Object Explorer Window and choose the child object Integration Component.

The integration components are shown in the figure below.

Notice the following features of the integration components:

Aggregates and elements are treated the same and map to integration components.
SiebelFINSIXMLContainer is always the root integration component. This is a system-defined integration component and should not be modified.
The property Parent Integration Component and the property Cardinality are used to preserve the hierarchy and cardinality information.
The integration component name mimics the XML tag except:
The dot in the XML tag is replaced with an underscore.
Numbers are appended to resolve naming conflicts.
If the integration component represents an element that can have a value, it will have at least one Integration Component Field child object, which is PCDATA.
If the integration component represents an aggregate that cannot have a value, it will have no Integration Component Field child object.
In the Object Explorer Window, choose child object Integration Object User Prop.

The user properties are shown in the figure below.

Notice the following features of the integration objects user properties:

Property IFX Service Name is used to provide information about what IFX Service this message belongs to. It is a required user property.
Property Ignore Undefined XML Tags is for internal use only and is a required user property.

NOTE:  If the underlying DTD changes, it is necessary to revise your integration object definition accordingly. Be careful of changes to commonly used aggregates, as this will force you to regenerate external integration objects for many messages.

Bookshelf Home | Contents | Index | Search | PDF