|Bookshelf Home | Contents | Index | PDF|
When integration object documents are sent to an external system, they might be encapsulated within a SiebelMessage element. This element identifies the document as a Siebel message and indicates that the document includes integration object instances. It can also provide metadata, such as the integration object type and a message ID.
Since the Object List element is optional, SiebelMessage can include a Root component element to allow cases when the Object List element is left blank (omitted). For details on Object List element, see Object List Element.
The SiebelMessage element can contain a number of attributes, which are known as the Message Header attributes. In addition, you can add arbitrary attributes to the SiebelMessage element. An XSD or DTD for the document can be dynamically generated inline to include all present attributes. The following standard attributes have well-defined meanings.
For integration object messages, the SiebelMessage element includes exactly one object list element. Since only one object list element is permitted in each XML document, only one integration object type can be represented in a given document.
|XML Reference: Siebel Enterprise Application Integration||Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.|