Bookshelf Home | Contents | Index | PDF | ![]() ![]() |
Oracle Customer Hub (UCM) Master Data Management Reference > ASIs and Messages for Oracle Master Data Management Applications > Application Services Interfaces for Oracle Master Data Management Applications > About CRMML MessagesCustomer Relationship Management Markup Language (CRMML) is a Siebel XML specification for customer-centric data exchange with other enterprise applications and Oracle Customer Hub (UCM) applications. External applications send CRMML request messages to Siebel Business Applications and receive CRMML messages in response. CRMML messages contain an envelope, a header section, and a body section. The message specification focuses on the hierarchy and definitions of the header elements. It allows users to extend the body section with user-defined elements as long as the object descriptors in the header section describe the usage of the elements in a body section. Code Example of a CRMML MessageThe following example illustrates the layers of a CRMML message: <?xml version="1.0" encoding="UTF-8> <! CRMML Header section starts> <SystemId>www.mycompany.com</SystemId> <SystemRole>Insurance Application</SystemRole> <SystemName>Client UI System</SystemName> <SystemId>123-456-789</SystemId> <SystemRole>Service Provider</SystemRole> <SystemName>Siebel UCM System</SystemName> <MessageId>11SC3I2002053116:43:45</MessageId> <TransactionScope>any</TransactionScope> <Timestamp>01/01/2001</Timestamp> <EmailAddress>cifemail</EmailAddress> <FaxPhone>5555555555</FaxPhone> <FirstName>0099INFN</FirstName> <HomePhone>1111111111</HomePhone> Envelope and Header SectionThe CRMML message has one envelope element <CRMML>. <CRMML> is the root element for a message. It contains one optional header element <CRMHeader> and one or more body elements. The envelope has no attributes. The header includes elements for sender and receiver. The following is an example for communication parties: <! CRMML Header section starts> <SystemId>www.mycompany.com</SystemId> <SystemRole>Insurance Application</SystemRole> <SystemName>Client UI System</SystemName> <SystemId>123-456-789</SystemId> <SystemRole>Service Provider</SystemRole> <SystemName>Siebel UCM System</SystemName> In this code example, note the elements.
Both elements contain <SystemInfo> aggregate. In the example, sender is Client UI System and receiver is Siebel Master Data Applications System. Sender plays an insurance application role, and receiver plays a service provider's role. The header also contains a message descriptor that depicts the body of the message and objects inside the body sections. An example of the message descriptor follows: <! CRMML Header section starts> <MessageId>11SC3I2002053116:43:45</MessageId> <TransactionScope>any</TransactionScope> <TimeToLive>OneYear</TimeToLive>
The following object descriptor example illustrates the metadata for a remote procedure call in a message header: <ObjectId type="HREF" sytem="this">p1</ObjectId> <ObjectUsage>SoftwarePackage</ObjectUsage> <ObjectId type="HREF" sytem="this">m1</ObjectId> <ObjectUsage>Method</ObjectUsage> <ObjectId type="HREF" sytem="this">a1</ObjectId> <ObjectUsage>Argument</ObjectUsage> <InsertContactProfile ID="m1">
For an implementation of Oracle Customer Hub (UCM), the default usages of the first three elements are package, method, and argument. Therefore, no objective descriptor is required for Oracle Customer Hub (UCM) specific messages. Certain values in the header are automatically generated by the connector, but you can specify others in the envelope integration object. Table 309 describes the elements and how they are configured. For system-generated attributes, there is no configuration available. NOTE: The CRMML envelope object information can be configured. It contains custom fields and works for both input and output formats. However, business services for Oracle Customer Hub (UCM) refer to information in this object and look for specific XML values. Make sure the specific fields exist in the business services before configuring CRMML. Body SectionThe body section contains user-defined message elements. The following is an example body section and is one of the messages supported by Siebel Master Data Management Applications. <InsertContactProfile ID="m1"> The example indicates that an external application requests to insert a contact profile to the Siebel Master Data Applications database. The contact detail information is contained within the <Contact> aggregate. |
![]() ![]() |
Oracle Customer Hub (UCM) Master Data Management Reference | Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |