Integration Platform Technologies: Siebel Enterprise Application Integration > EAI UI Data Adapter Business Service > EAI UI Data Adapter Business Service Methods >

Execute Method


The Execute method allows you to perform multiple operations on multiple business components. It is the only method that operates on internal nodes. The Execute method returns the same kind of object that the InsertLeaves method returns. For more information, see InsertLeaves Method.

NOTE:  the Execute method requires a status object only when it contains an insert operation on a child integration component instance. However, because the EAI UI Data Adapter processes in a top-down fashion, it adds a status object to the integration object instance even if an insert operation is not present.

The operations are defined by the operation attribute on the integration component instance. An integration component instance can have the following operations as defined in Table 36:

Table 36. Operation Attributes for Execute Method
Operation
Description

update

Updates the integration component instance

insert

Inserts the integration component instance

delete

Deletes the integration component instance

skipnode

Matches integration component instances and process children

CAUTION:  Operations must be specified on every integration component instance. If an operation is not specified, an implicit Synchronize operation will be performed, which will delete all unmatched child integration component instances.

Execute Method Arguments

Table 37 lists the method arguments used with the Execute method. For a description of the methods, see EAI UI Data Adapter Business Service Method Arguments.

Table 37. Method Arguments for Execute
Method Argument Name
Type

BusObjCacheSize

Input

LOVLanguageMode

Input

SiebelMessage

Input / Output

Example of Using the Execute Method

The following example demonstrates using the Execute method to perform update, insert, and delete operations on child object. Note that the skipnode operation is defined on the parent object.

Request

The following is an example of a request:

<SiebelMessage MessageType="Integration Object" IntObjectName="Account" IntObjectFormat="Siebel Hierarchical">
   <ListOfAccount>
      <Account operation="skipnode">
         <Id>1-1-1111</Id>
         <ListOfBusiness_Address>
            <Business_Address operation="update">
               <Id>2-2-2222</Id>
               <Postal_Code>94402</Postal_Code> <!--Postal Code changed-->
            </Business_Address>
            <Business_Address operation="insert">
               <Postal_Code>94402</Postal_Code>
               <City>San Mateo</City>
               <Street_Address>2215 Bridgepointe Parkway</Street_Address>
               <State>CA</State>
               <Country>USA</Country>
            </Business_Address>
         </ListOfBusiness_Address>
         <ListOfContact>
            <Contact operation="delete">
               <Id>4-4-4444</Id>
            </Contact>
         </ListOfContact>
      </Account>
   </ListOfAccount>
</SiebelMessage>

Response

The following is an example of a response:

<SiebelMessage MessageId="42-21YQ" MessageType="Integration Object" IntObjectName="Account" IntObjectFormat="Siebel Hierarchical">
   <ListOfAccount>
      <Account>
         <Id>1-1-1111</Id>
         <Mod_Id>3</Mod_Id>
         <ListOfBusiness_Address>
            <Business_Address>
               <Id>2-2-2222</Id>
               <Mod_Id>1</Mod_Id>
            </Business_Address>
            <Business_Address>
               <Id>42-53Q2W</Id>
               <Mod_Id>0</Mod_Id>
            </Business_Address>
         </ListOfBusiness_Address>
      </Account>
   </ListOfAccount>
</SiebelMessage>

Integration Platform Technologies: Siebel Enterprise Application Integration Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices.