Minimizing Integration Object Size.doc

Minimizing Integration Object Size The size of an integration object and its underlying business components can have an impact on the performance of the EAI Siebel Adapter. To minimize this impact, you can:



Consider copying business objects and business components and modifying them to remove any elements (such as scripts, joins, multi-value fields, user properties, and so on) that you do not require in the Siebel EAI context. Base your integration objects on these relatively streamlined object definitions. Verify that user keys on your integration objects make effective use of indexes when queries are performed.  Inactivate unneeded integration components and integration component fields in your integration objects. Activate only the components and fields needed for message processing, according to your business needs.  Inactivate unneeded fields for each underlying business component. For fields that are unneeded, if Force Active is set to TRUE, set it to FALSE. Setting Force Active to FALSE prevents the EAI Siebel Adapter from processing these fields. If you do not inactivate these fields, the adapter processes them even when they are not actually included in the integration object.

1. 2. 3. 4.

Try creating index if necessary. Avoid using a boolean index if possible as a driving index. Try changing business component search spec or sort spec. Outer join specifications. Index all new Primary Keys and Foreign keys.