Scenario:
While performing an Insert operation with EAI Siebel Adapter. User identified the following behavior: Siebel was doing Query operation + Insert operation. This was taking more time and the agent had to wait for a long time to view the records
Solution:
The IC User Property "SuppressQueryOnInsert" is used for Insert operation. When this parameter is set with value "Y", the "EAI Siebel Adapter" Business Service (BS) is able to do a 'blind' insert of the record, whenever the following conditions are met:
1. The IC has a User Key defined.
2. The input message (SiebelMessage) received in the BS includes values for fields defined in this User Key.
3. The user property has effect only for an Insert operation.
Note that Keys are a 'must' and have to be added to the IC. When either, the IC has no User Key defined or the input message does not include values for User Key fields, there will be an error message.
Example:
Use the ”EAI Account” IO and set the User Property for its IC: "Account". This IC also includes a first User Key defined for field "Id". Using BS Simulator start a new test with BS EAI Siebel Adapter / Insert operation and include a SiebelMessage as input argument, with a value in field "Id" for Account.
a) Without the User Property defined, the Insert process executes a Select statement based on the User Key for the IC (Id).
b) After compiling the IO including the User Property "SuppressQueryOnInsert" with value "Y" for the "Account" IC, the 'blind' insert is executed. The Spool file for this case includes the Insert operation which runs without a Select statement for the User Key of the new record received.
NOTE: Most of Integration solutions implemented in Siebel will require a validation for the uniqueness of the new record before inserting it, so the option above has to be carefully considered