Integration Platform Technologies: Siebel eBusiness Application Integration Volume ll > Creating and Maintaining Integration Objects >

About Optimizing Performance for Using Integration Objects

To optimize your integration object performance, you may want to consider the following.

Size of Integration Object

The size of an integration object and its underlying business components can have an impact on the latency of EAI Siebel Adapter operations. You should inactivate unnecessary fields and components in your integration objects.

Force-Active Fields

You should reexamine any fields in the underlying business component that are force-active. Such fields are processed during integration even if they are not included in the integration component. You might want to consider removing the force-active specification from such fields, unless you absolutely need them.

Picklist Validation

Siebel applications have two classes of picklists—static picklists based on lists of values and dynamic picklists based on joins.

Setting the property PICKLIST to Y in the integration object field directs the EAI Siebel Adapter to validate that all operations conform to the picklist specified in the field. For dynamic picklists, this setting is essential to make sure the joins are resolved properly. However, for unbounded static picklists, this validation may be unnecessary and can be turned off by setting the PICKLIST property to N. Even for bounded static picklists, validation in the adapter can be turned off because the Object Manager can perform the validation. Turning off the validation at the EAI Siebel Adapter level means that picklist-related warnings and debugging messages will not show up along with other EAI Siebel Adapter messages. This also means that bounded picklist errors will not be ignored, even if Ignore Bounded Picklist is set to Y.

As well as certain warnings and messages not appearing, setting the integration component field user property PICKLIST to N, also causes fields be auto-filled. In this instance, providing a single value to a particular field causes the value of the field to be auto-filled. This especially occurs when the picklist is based on an MLOV. If the EAI Siebel Adapter is performing the validation (PICKLIST = Y), auto filling of the field does not occur. In this case, the EAI Siebel Adapter supports only an exact match for the particular field.

NOTE:  Performing the validation of a bounded picklist in EAI Siebel Adapter is about 10% faster than performing the validation in the Object Manager.