Siebel Connector for Siebel eBusiness Applications > Administration and Error Messages > Performance >

Multiple Channels

If you are publishing and receiving through a single channel and this does not meet your performance requirements, consider using multiple channels.

However, use caution when setting up multiple channels between two instances. Specifically, be sure you follow the recommendations explained below.

• Use different search specifications among all channels for the same integration object.
• Use search specifications that divide all data into disjoint sets, so that a given record is published through one and only one channel.

  In other words, define searchspec1 and searchspec2, for example, in such a way that the query result for searchspec1 and the query result for searchspec2 will not contain the same record. This rule applies to one-to-many, many-to-one, and many-to-many relationships.

• Define search specifications in such a way that any record you want to send or receive meets only one search specification at all times.

  In other words, the record must not jump channels.

• Siebel recommends basing your search specifications on some invariant field—such as the S-S Key Id field—which, once created, never change value. Thus, if the record is modified in the future, it will not cause the record to jump channels because it now meets a different, and unintended, search specification.