Oracle相關(guān)文檔-Siebel詳細說明書-EAI5

XMLReference:SiebelEnterpriseApplicationIntegration

SiebelInnovationPack2016May2016

Copyright?2005,2016Oracleand/oritsaffiliates.Allrightsreserved.

Thissoftwareandrelateddocumentationareprovidedunderalicenseagreementcontainingrestrictionsonuseanddisclosureandareprotectedbyintellectualpropertylaws.Exceptasexpresslypermittedinyourlicenseagreementorallowedbylaw,youmaynotuse,copy,reproduce,translate,broadcast,modify,license,transmit,distribute,exhibit,perform,publish,ordisplayanypart,inanyform,orbyanymeans.Reverseengineering,disassembly,ordecompilationofthissoftware,unlessrequiredbylawforinteroperability,isprohibited.

Theinformationcontainedhereinissubjecttochangewithoutnoticeandisnotwarrantedtobeerror-free.Ifyoufindanyerrors,pleasereportthemtousinwriting.

IfthisissoftwareorrelateddocumentationthatisdeliveredtotheU.S.GovernmentoranyonelicensingitonbehalfoftheU.S.Government,thefollowingnoticeisapplicable:

U.S.GOVERNMENTENDUSERS:Oracleprograms,includinganyoperatingsystem,integratedsoftware,anyprogramsinstalledonthehardware,and/ordocumentation,deliveredtoU.S.Governmentendusersare“commercialcomputersoftware”pursuanttotheapplicableFederalAcquisitionRegulationandagency-specificsupplementalregulations.Assuch,use,duplication,disclosure,modification,andadaptationoftheprograms,includinganyoperatingsystem,integratedsoftware,anyprogramsinstalledonthehardware,and/ordocumentation,shallbesubjecttolicensetermsandlicenserestrictionsapplicabletotheprograms.NootherrightsaregrantedtotheU.S.Government.

Thissoftwareorhardwareisdevelopedforgeneraluseinavarietyofinformationmanagementapplications.Itisnotdevelopedorintendedforuseinanyinherentlydangerousapplications,includingapplicationsthatmaycreateariskofpersonalinjury.Ifyouusethissoftwareorhardwareindangerousapplications,thenyoushallberesponsibletotakeallappropriatefail-safe,backup,redundancy,andothermeasurestoensureitssafeuse.OracleCorporationanditsaffiliatesdisclaimanyliabilityforanydamagescausedbyuseofthissoftwareorhardwareindangerousapplications.

OracleandJavaareregisteredtrademarksofOracleand/oritsaffiliates.Othernamesmaybetrademarksoftheirrespectiveowners.

IntelandIntelXeonaretrademarksorregisteredtrademarksofIntelCorporation.AllSPARCtrademarksareusedunderlicenseandaretrademarksorregisteredtrademarksofSPARCInternational,Inc.AMD,Opteron,theAMDlogo,andtheAMDOpteronlogoaretrademarksorregisteredtrademarksofAdvancedMicroDevices.UNIXisaregisteredtrademarkofTheOpenGroup.

Thissoftwareorhardwareanddocumentationmayprovideaccesstoorinformationaboutcontent,products,andservicesfromthirdparties.OracleCorporationanditsaffiliatesarenotresponsibleforandexpresslydisclaimallwarrantiesofanykindwithrespecttothird-partycontent,products,andservicesunlessotherwisesetforthinanapplicableagreementbetweenyouandOracle.OracleCorporationanditsaffiliateswillnotberesponsibleforanyloss,costs,ordamagesincurredduetoyouraccesstooruseofthird-partycontent,products,orservices,exceptassetforthinanapplicableagreementbetweenyouandOracle.

DocumentationAccessibility

ForinformationaboutOracle'scommitmenttoaccessibility,visittheOracleAccessibilityProgramwebsiteat/pls/topic/lookup?ctx=acc&id=docacc.

AccesstoOracleSupport

OraclecustomersthathavepurchasedsupporthaveaccesstoelectronicsupportthroughMyOracleSupport.Forinformation,visit/pls/topic/lookup?ctx=acc&id=infoorvisit

/pls/topic/lookup?ctx=acc&id=trs

ifyouarehearingimpaired.

Contents

XMLReference:SiebelEnterpriseApplicationIntegration1

Chapter1:What’sNewinThisRelease

Chapter2:OverviewofSupportforXMLinSiebelBusiness

Applications

AboutXML9

SiebelCRMIntegrationandXML9

MetadataSupportforXML11

SpecialCharactersinXMLDocuments11

Chapter3:XMLRepresentationofPropertySets

MappingBetweenPropertySetsandXML13

ElementandAttributeNaming13

PropertySetExamplesandTheirXMLRepresentation15

ProperlyFormattedPropertySets16

Chapter4:XMLRepresentationofSiebelIntegration

ObjectInstances

AboutRepresentingSiebelIntegrationObjectInstancesasXMLDocuments19

IntegrationObjects19

ElementsandAttributes20

HowXMLNamesAreDerivedfromIntegrationObjects21

ElementsWithinaSiebelIntegrationObjectDocument22

SiebelMessageElement22

ObjectListElement23

IntegrationComponentElements23

ComponentContainerElements24

IntegrationFieldElements25

ExampleXMLDocument25

XMLSchemaDefinitions(XSDs)26

DocumentTypeDefinitions(DTDs)27

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation3

Pack2016

Contents■

Chapter5:XMLIntegrationObjectsandtheXSDWizard

CreatingXMLIntegrationObjectswiththeXSDWizard29

SupportedXSDElementsandAttributes30

StructureofXSDXMLIntegrationObjects36

Chapter6:XMLIntegrationObjectsandtheDTDWizard

CreatingXMLIntegrationObjectswiththeDTDWizard39

HowtheDTDWizardCreatesXMLIntegrationObjects40

Chapter7:SiebelXMLConverters

AboutSiebelXMLConverters45

EAIXMLConverter46

XMLHierarchyConverter51

EAIIntegrationObjecttoXMLHierarchyConverter57

XMLConverter60

SiebelXMLConverterBusinessServiceComparison62

EAIXMLWritetoFileBusinessService63

EAIXMLReadfromFileBusinessService66

Chapter8:ScenariosforSiebelEAIXMLIntegration

Scenario1:ProcessofInboundIntegrationUsingSiebelXML71

Scenario2:ProcessofOutboundIntegrationUsingExternalXMLandanXSDorDTD

72

AppendixA:UsingXMLFiles

UsinganXMLDocumentasInput75

InsertingFileAttachmentsUsingXML78

RemovingEmptyXMLTags78

AppendixB:SampleXMLforSiebelEAIEffectiveDating

Operations

AboutSiebelEAIEffectiveDatingOperations81

SampleXMLforField-RelatedSiebelEAIEffectiveDatingOperations81

SampleXMLforLink-RelatedSiebelEAIEffectiveDatingOperations91

4XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovationPack2016

Contents■

Index

5

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

Contents■

6

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

1

What’sNewinThisRelease

What’sNewinXMLReference:SiebelEnterpriseApplication

Integration,SiebelInnovationPack2016

Nonewfeatureshavebeenaddedtothisguideforthisrelease.Thisguidehasbeenupdatedtoreflectonlyproductnamechanges.

NOTE:SiebelInnovationPack2016isacontinuationoftheSiebel8.1/8.2release.

What’sNewinXMLReference:SiebelEnterpriseApplication

Integration,SiebelInnovationPack2015

Nonewfeatureshavebeenaddedtothisguideforthisrelease.Thisguidehasbeenupdatedtoreflectonlyproductnamechanges.

NOTE:SiebelInnovationPack2015isacontinuationoftheSiebel8.1/8.2release.

7

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

What’sNewinThisRelease■

8

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

2

OverviewofSupportforXMLinSiebelBusinessApplications

ThischapterprovidesanoverviewofsupportforExtensibleMarkupLanguage(XML)inSiebelBusinessApplications.Itincludesthefollowingtopics:

■

AboutXMLonpage9

■

SiebelCRMIntegrationandXMLonpage9

■

MetadataSupportforXMLonpage11

■

SpecialCharactersinXMLDocumentsonpage11

AboutXML

XMListheindustrystandardforpreciselyrepresentingdatafromvirtuallyanysource,storedinvirtuallyanyformat.Inappearance,itissimilartoHTML,butwhileHTMLexplainsadocumentintermsofhowitshoulddisplaydatainaWebbrowser,XMListhedata(ormoreprecisely,thedatafromanapplicationrepresentedasXML).

Thisdatacanbefromanapplicationscreen,sometimescalledascreenscraping,itcanbetheoutputfromadatabase,oritcanbeanapplicationexecutedusingprocessinginstructionsthatrunOracle’sSiebeleScript,forexample.

TherearealsotechnologiesthatexplainXMLdocuments.TheseareknownasmetadatabecausethedatawithinthesedocumentsisusedtodescribeandformattheinformationinanXMLdocument.ExamplesofmetadatadocumentsincludeXSDs(XMLSchemaDefinitions),DTDs(DocumentTypeDefinitions),andXDRs(XMLDataReduced),whicharesupportedbySiebelBusinessApplications.

SiebelCRMIntegrationandXML

SiebelBusinessApplicationssupportforXMLallowsyoutocommunicatewithanySiebelapplicationorexternalapplicationthatcanreadandwriteXML(eitherarbitraryXMLorSiebelXML,alsoknownastheSiebelMessageformat).

XMLdocumentsaredelivereddirectlytoandfromSiebelBusinessApplications,orthroughmiddlewareusinganyofthesupportedtransports:HTTP,IBMWebSphereMQ,File,andsoon.XMLcommunicatedinthiswaycanquerytheSiebelDatabase,upsert(updateorinsert)data,synchronizethetwosystems,deletedata,orexecuteaworkflowprocess.

Objectsfromvarioussystems,suchasSiebelbusinessobjectsandOracleapplicationdata,canberepresentedasSiebelintegrationobjects.

9

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

OverviewofSupportforXMLinSiebelBusinessApplications■SiebelCRMIntegrationandXML

SiebelCRMcanalsocommunicatebidirectionallywithWebservicesusingSimpleObjectAccessProtocol(SOAP),andRepresentationalStateTransfer(REST)throughSiebelApplicationIntegration(SAI)forOracleFusionMiddleware.Fordetails,seeIntegrationPlatformTechnologies:SiebelEnterpriseApplicationIntegrationandSiebelApplicationIntegrationforOracleFusionMiddleware

Guide.

NOTE:Ifyoudoaminimalclientinstallation,makesureyouselecttheXMLparseroption;otherwise,youwillencounterthefollowingerrorwhenattemptingtorunanyclientprocessthatusestheXMLparser:UnabletocreatetheBusinessService‘EAIXMLConverter.’TheXMLparserisincludedbydefaultinthefullinstallation.

XMLIntegrationObjects

TheIntegrationObjecttypeofXMLisavailablewithinSiebelBusinessApplicationstorepresentexternallydefinedXMLdocuments,wheretheobject’sXMLrepresentationiscompliantwiththeXSDorDTDsuppliedbyyourtradingpartnerorexternalsystem.ThistypeofintegrationobjectsupportsarepresentationofXMLdocuments.

NOTE:SiebelXSDdoesnotsupporttheuseof<import>and<include>elementsandthe<any>attribute.Toimplementthe<import>or<include>functionality,placetheschemadefinitionintoasinglefile.

BidirectionalDataFlow

Figure1

showsthebidirectionalprogressofXMLdocumentsintoandoutofSiebelBusinessApplications.

Figure1.DocumenttoIntegrationObjectFlow

NOTE:FordetailsonintegrationobjectsandWebservices,seeIntegrationPlatformTechnologies:SiebelEnterpriseApplicationIntegration.ForanoverviewofSiebelEAI,seeOverview:SiebelEnterpriseApplicationIntegration.

10

OverviewofSupportforXMLinSiebelBusinessApplications■MetadataSupportfor

XML

MetadataSupportforXML

ForsendingandreceivinginformationforSiebelObjectsinanXMLformatbetweenOracleandexternalsystems,OraclesupportsthemetadatarepresentationsforXMLknownasXSDs(XMLSchemaDefinitions),DTDs(DocumentTypeDefinitions),andXDRs(XMLDataReduced,aMicrosoftspecification).SupportforXSDsandDTDsgivesyouawaytocommunicatewithexternalsystemsusingexternallydefinedXMLdocuments,insteadofhavingtousetheSiebelXSDandDTDformat.

TheSiebelapplicationincludesaSchemaGeneratorwizardtoassistinthecreationofXMLIntegrationObjects,usinganexternallydefinedXSDorDTD.TheXSDandDTDareusedtomapdatabetweentheSiebelapplicationandanexternalintegrationobject,andtotransformdata,asneeded.ThesetasksareconductedusingtheSiebelDataMapper.

SpecialCharactersinXMLDocuments

SpecialcharactersshouldberepresentedinaccordancewithXMLstandardsforthosecharactersinorderforthemtobecorrectlyinterpretedwithinSiebelBusinessApplications.Also,specifythecharactersetyouareusingifitisnotUTF-8(thedefault).

NOTE:ToeditanXMLdocumentincludingbinaryorencodeddata,useeditorssuchasMicrosoftNotepadorWordthatdonotconvertthedatauponsavingthefile.

Special(Escape)Characters

TheEAIXMLConvertercanhandlespecialcharactersforinboundandoutboundXML,asshownin

Table1

.Non-SiebelXMLshouldalreadyhandlespecialcharactersbeforeintegratingintotheSiebelapplication.Specialcharactersareindicatedbyenclosingthetextforthecharacterbetweenanampersand(&)andasemicolon(;).Also,iftheXMLispassedinaURL,thenURLencodingofspecialcharactersisrequiredasshownin

Table1

.

Table1.XMLEscapeCharacters(CharacterEntities)

Character

Entity

URLEncoded

<

<

%26lt%3B

>

>

%26gt%3B

&

&

%26amp%3B

“

"

%26quot%3B

'

'

%26apos%3B

UnicodeCharacter(Decimal)

%26%2309%3B

UnicodeCharacter(Hex)

°

%26%23x00B0%3B

Date

MustfollowtheISO8601format

Notapplicable

11

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

OverviewofSupportforXMLinSiebelBusinessApplications■SpecialCharactersin

XMLDocuments

DeclaringtheCharacterSetinUse

YoumustincludethefollowingparameterintheXMLversiondeclarationofyourXML,XSD,orDTDdocumenttodeclarethecharactersetinuse,ifitisnotthedefaultofUTF-8:

<?xmlversion="1.0"encoding="US-ASCII"?>

SupportedcharactersetsincludebutarenotlimitedtoASCII,UTF-8,UTF-16(BigorSmallEndian),UCS4(BigorSmallEndian),EBCDICcodepagesIBM037andIBM1140encodings,ISO-8859-1,and

Windows-1252.ThismeansthattheXMLparsercanparseinputXMLfilesintheseencodings.ThefollowingencodingscanbeusedintheXMLdeclaration:

■US-ASCII

■UTF-8

■ISO-10646-UCS-4

■ebcdic-cp-us

■ibm1140

■ISO-8859-1

■windows-1252

Thecharactersetdeclarationencodingmustappearaftertheversiondeclaration.Forexample:

<?xmlversion="1.0"encoding="US-ASCII"?>

TheoutputcanbeinoneofthefollowingXMLencodings:

■UTF-8

■UTF-16

■LocalCodePage

12

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

3

XMLRepresentationofProperty

Sets

ThischapterdiscussestheXMLrepresentationofpropertysetsandthemappingbetweenpropertysetsandXML.ItalsodiscussestheelementsandattributesnamingconversionperformedbytheXMLConverter.Itincludesthefollowingtopics:

■

MappingBetweenPropertySetsandXMLonpage13

■

ElementandAttributeNamingonpage13

■

PropertySetExamplesandTheirXMLRepresentationonpage15

■

ProperlyFormattedPropertySetsonpage16

MappingBetweenPropertySetsandXML

AnarbitrarypropertysethierarchycanbeserializedtoXMLandanXMLdocumentcanbeconvertedtoapropertysethierarchyusingtheXMLConverterbusinessservice.ThisserviceisusedbytheBusinessServiceSimulatorscreentosavepropertysetinputsandoutputstoafilefromeScript.

EachpartofapropertysetobjecthasacorrespondingXMLconstruct.

Table2

showsthemappingsbetweenpartsofapropertysethierarchyandtheirXMLrepresentation.

Table2.PropertySettoXMLMappings

PropertySet

Component

PropertySet

XMLRepresentation

Element

PropertySetType

Elementname(ifTypeisnotspecified,thentheelementnameissettoPropertySet)

PropertySetValue

ElementCharacterData

Propertyname

Attributename

Propertyvalue

Attributevalue

ChildPropertySet

Childelement

ElementandAttributeNaming

ThepropertysetType(whichmapstoanXMLelementname)andthenamesofindividualproperties(whichmaptoXMLattributenames)donotnecessarilyfollowtheXMLnamingrules.Forexample,anamecanincludecharacterssuchasaspace,aquote,acolon,aleftparenthesis,orarightparenthesisthatarenotallowedinXMLelementorXMLattributenames.Asaresult,youmustperformsomeconversiontogenerateavalidXMLdocument.

13

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

XMLRepresentationofPropertySets■ElementandAttributeNaming

WhencreatinganXMLdocumentfromapropertysethierarchy,theXMLConverterwillmakesurethatlegalXMLnamesaregenerated.Therearetwodifferentapproachesprovidedtohandlenametranslation.TheapproachisdeterminedbytheEscapeNamesuserpropertyontheXMLConverterservice.ThisuserpropertycanbeeitherTrueorFa1se.

■True.IfEscapeNamesisTrue,instancesofillegalcharactersareconvertedtoanescapesequencethatusesonlylegalcharacters.Forexample,aspaceisconvertedtothecharacters_spc.WhenanXMLdocumentisparsedtoapropertysethierarchy,theescapesequencesareconvertedbacktotheoriginalcharacters.Forexample,thenameAccount(SSE)becomesAccount_spc_lprSSE_rpr.

Table3

showstheescapesequencesthatareusedbytheXMLConverter.

Table3.XMLConverterEscapeSequences

Characterin

PropertySet

Description

Space

GeneratedEscape

Sequence

_spc

_

Underscore

_und

“

DoubleQuote

_dqt

‘

SingleQuote

_sqt

:

Colon

_cln

;

Semicolon

_scn

(

LeftParenthesis

_lpr

)

RightParenthesis

_rpr

&

Ampersand

_amp

,

Comma

_cma

#

Poundsymbol

_pnd

/

(Forward)slash

_slh

?

QuestionMark

_qst

<

LessThan

_lst

>

GreaterThan

_grt

Illegalcharacters

Otherillegalcharactersnotlistedinthistable

_<Unicodecharactercode>

■False.IfEscapeNamesisFalse,theXMLConverterremovesillegalcharacters.Thesecharactersincludethespace(),doublequote("),singlequote('),semicolon(;),leftparenthesis((),rightparenthesis()),andampersand(&).Forexample,theXMLConverterchangesthenameAccount(SSE)toAccountSSE.

NOTE:Theseconversionsarenotreversible:theoriginalnamescannotbeobtainedfromtheXMLnames.

14

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

XMLRepresentationofPropertySets■PropertySetExamplesandTheirXMLRepresentation

IfapropertysetinstancedoesnothaveavalueforitsTypemembervariable,theXMLConverterusesthenamePropertySetforthecorrespondingelement’sname.

PropertySetExamplesandTheirXML

Representation

ThefollowingisexamplesofdifferenttypesofpropertysetsthatareavailableandtheirXMLrepresentation:

AnArbitraryPropertySet

<?Siebel-Property-Set><PropertySet><Person>Jack</Person></PropertySet>

ASiebelMessage

<?Siebel-Property-SetEscapeNames="true"><PropertySet><SiebelMessageMessageID="1-

111"IntObjectFormat="SiebelHierarchical"MessageType="IntegrationObject"

IntObjName="SampleAccount"><ListOfSample_spcAccount>...</

ListOfSample_spcAccount></SiebelMessage></PropertySet>

AnXMLHierarchy

<?Siebel-Property-Set><PropertySet><_XMLHierarchy><Account><Contact>...</

Contact></Account><_XMLHierarchy></PropertySet>

15

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

XMLRepresentationofPropertySets■ProperlyFormattedPropertySets

Figure2

illustratesanexamplepropertysethierarchyandtheXMLthatwouldbegeneratedforeachcomponentofthehierarchy.TheXMLwasgeneratedwiththeEscapeNamesuserpropertysettoTrue.

Figure2.PropertySetandXMLwithEscapeNamesSettoTrue

ProperlyFormattedPropertySets

PropertysetsareusedinternallytorepresentSiebelEAIdata.Apropertysetisalogicalmemorystructurethatisusedtopassthedatabetweenbusinessservices.

TobenefitfromusingtheXMLConverter,besurethatanycodeyouuse,suchaseScriptorSiebelVB,correctlyrepresentspropertysetswithinSiebelBusinessApplicationsfortheXMLConverterBusinessService.Thisincludesnecessaryargumentsandvalues.Anexampleofsuchcodeis:

SetInputs=TheApplication.NewPropertySet

16

XMLRepresentationofPropertySets■ProperlyFormattedPropertySets

REMFillinSiebelMessageHeader

Inputs.SetType"SiebelMessage"

Inputs.SetProperty"MessageId",""

Inputs.SetProperty"MessageType","IntegrationObject"

Inputs.SetProperty"IntObjectName","SampleAccount"

Setsvc=theApplication.GetService("EAIXMLConverter")

SetXMLInputs=theApplication.NewPropertySet

SetXMLOutputs=theApplication.NewPropertySet

XMLInputs.AddChildInputs

svc.InvokeMethod"PropSetToXML",XMLInputs,XMLOutputs

17

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

XMLRepresentationofPropertySets■ProperlyFormattedPropertySets

18

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

4

XMLRepresentationofSiebel

IntegrationObjectInstances

ThischapterdescribestheXMLrepresentationofSiebelintegrationobjectinstances.Itincludesthefollowingtopics:

■

AboutRepresentingSiebelIntegrationObjectInstancesasXMLDocumentsonpage19

■

IntegrationObjectsonpage19

■

ElementsandAttributesonpage20

■

HowXMLNamesAreDerivedfromIntegrationObjectsonpage21

■

ElementsWithinaSiebelIntegrationObjectDocumentonpage22

■

ExampleXMLDocumentonpage25

■

XMLSchemaDefinitions(XSDs)onpage26

■

DocumentTypeDefinitions(DTDs)onpage27

AboutRepresentingSiebelIntegration

ObjectInstancesasXMLDocuments

YoucanrepresentanyintegrationobjectinstanceinSiebelBusinessApplicationsasanXMLdocument(orcreatedfromaproperlyformattedXMLdocument).Thismakesitconvenienttosaveanobjecttoafileforviewingortosenditoveratransport,suchasHTTPorIBMWebSphereMQ.YoucancontroltheformatoftheXMLdocumentthroughtheintegrationobjectdefinitionintheSiebelRepository.YoucanusetheEAIXMLConverterbusinessservicetoperformtranslationsbetweenintegrationobjectinstancesandthecorrespondingXMLrepresentation.

IntegrationObjects

IntegrationobjectsarelogicalrepresentationsofSiebelbusinessobjectsorexternalapplicationdata,suchasexternallydefinedXMLdocuments.AnintegrationobjectismetadatastoredintheSiebelRepository.Oneintegrationobjectcanbemappedtoanotherintegrationobject.Instancesofintegrationobjectsareusedinintegrationprocessesfordataexchange.Formoreinformationonintegrationobjects,seeIntegrationPlatformTechnologies:SiebelEnterpriseApplicationIntegration.

19

XMLReference:SiebelEnterpriseApplicationIntegrationSiebelInnovation

Pack2016

XMLRepresentationofSiebelIntegrationObjectInstances■ElementsandAttributes

Integrationobjectsaremadeupofthreedistinctdatasections:thecanonical,theexternal,andtheXML,asshownin

Figure3

.

Figure3.XMLIntegrationObjectDefinition

TheintegrationobjectschemaintheSiebelRepositoryiscomposedofthethreedatasectionsshownin

Table4

.

Table4.IntegrationObjectDataType

Name

Canonical

section

Purpose

Storesinformationaboutanobjectinacommonrepresentation.Thenamesusedforobjects,components,andfieldsarethenamesthatthedesignerwishestobevisible.ThedatatypesaretheSiebelbusinesscomponentfieldtypesthatareusedbytheObjectManager.

External

section

Storesinformationabouthowtheobject,component,orfieldisrepresentedintheexternalsystem.Forintegrationobjectsbasedonbusinessobjects,thiscanincludethebusinesso