Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. Cluster Merge Rules
  13. Forced Link and Unlink
  14. System Backup and Restore
  15. Batch Utilities

Integration Object

Integration Object

The basic mapping of data contained in a Siebel Business Component (BC) to an IDT is through an Integration Object (IO). A Siebel Integration Object will be set up with all the fields in the Business Component that are desired in the IDT. Then the IDT can be set up to match the XML Tag names for the Integration Object. What follows is an example of an XML message based on such an Integration Object.
The corresponding MDM-RE UST definition can be found in the
Configuring MDM-RE
section. You must always include
RowId
as an active field in your IO as it will be used as the primary key in the IDT.
<?xml version="1.0" encoding="UTF-16"?> <?Siebel-Property-Set EscapeNames="false"?> <SiebelMessage MessageId="1-3HPY" IDS_OP="A" IDS_SYSTEM="testx218 IDS_IDT="IDS_01_CONTACT" MessageType="Integration Object" IntObjectName="ISS IO Contact" IntObjectFormat="Siebel Hierarchical"> <ListOfIssIoContact> <Contact> <Alias></Alias> <BirthDate>01/14/1932 00:00:00</BirthDate> <FirstName>Jean</FirstName> <LastName>Murasawa</LastName> <MiddleName></MiddleName> <City></City> <Country></Country> <PostalCode>765048832</PostalCode> <StreetAddress></StreetAddress> <RowId>12-ZT80P</RowId> </Contact> </ListOfIssIoContact> </SiebelMessage>

0 COMMENTS

We’d like to hear from you!