The upcoming release for Adapter pack will have support for Siebel integration objects. This feature will allow users to invoke Siebel Business Service "EAI Siebel Adapter" to operate against any Siebel integration object. EAI Siebel Adapter business service exposes following operations for manipulation of siebel integration objects:

1.Query

2. Insert

3. Update

4. Upsert

5. Delete

6. Synchronize

Siebel adapter will have runtime support for all of these operations though Siebel adapter won't publish these objects schema. What that means is users are supposed to create schema for required integration object using Siebel Tools. Based on that schema users must prepare the input XML. This input XML should be embodied into siebel adapter request message as CDATA node if required Business Service Method expects Hierarchy as input. On the response side, adapter would put Integration object response into siebel adapter response message as CDATA node.

Here a sample for execute Query on integration object "Sample Contact"

----------------------SampleContactQuery.xml-----------------------------------------------------------------------------------

 <Query xmlns=”http://Microsoft.LobServices.Siebel/2007/03/BusinessServices/EAI_x0020_Siebel_x0020_Adapter/Operation>

 <QueryRequestRecord>

  <OutputIntObjectName xmlns="http://Microsoft.LobServices.Siebel/2007/03/BusinessServices/EAI_x0020_Siebel_x0020_Adapter">Sample Account</OutputIntObjectName>

  <SearchSpec xmlns="http://Microsoft.LobServices.Siebel/2007/03/BusinessServices/EAI_x0020_Siebel_x0020_Adapter">[Account.Name] LIKE '*'</SearchSpec>

  </QueryRequestRecord>

  <QueryInOutRecord /> 

  </Query>

 ----------------------End SampleContactQuery.xml----------------------------------------------------------------------------

 

 

Above XML is normal siebel adapter request message. It doesn't have any special XML node.  

Now lets look at Sample insert xml request:

----------------------------------------------SampleContactInsert.xml-----------------------------------------------------------------

<Insert
xmlns="http://Microsoft.LobServices.Siebel/2007/03/BusinessServices/EAI_x0020_Siebel_x0020_Adapter/Operation">
  <InsertRequestRecord />
  <InsertInOutRecord>
 <SiebelMessage xmlns="http://Microsoft.LobServices.Siebel/2007/03/BusinessServices/EAI_x0020_Siebel_x0020_Adapter">
    <![CDATA[<?xml version="1.0" encoding="UTF-16"?><SiebelMessage
 MessageId=""
 IntObjectName="Sample Account"
 MessageType="Integration Object"
 IntObjectFormat="Siebel Hierarchical"><ListOfSampleAccount><Account><CurrencyCode>INR</CurrencyCode><Location>Hyderabad</Location><Name>IntegrationObjectTest</Name></Account></ListOfSampleAccount></SiebelMessage>]]>
  </SiebelMessage>
  </InsertInOutRecord>
</Insert>

----------------------------------------------End SampleContactInsert.xml-------------------------------------------------------------

 

The node of our interest is <CDATA[[]]> node. It contains integration object representation which Siebel business service expects.

Note the first xml comment inside CDATA node (xmlversion and encoding) should be maintained as is, otherwise Siebel will refuse to accept the message.

More on Siebel Integration Object support will follow:-)