Integration Platform Technologies: Siebel Enterprise Application Integration > Creating and Maintaining Integration Objects >

Guidelines for Using Integration Components

The following are the guidelines for using integration components:

• Familiarize yourself with the business logic in the business components. Integration designers must use the presentation layer, or the user interface, to get a good sense of how the business component behaves, and what operations are allowed and not allowed.
• Design with performance in mind. For more information on performance and using integration objects, see Optimizing the Performance of Integration Objects.
• Design with maintenance in mind. For more information on maintenance, see Guidelines for Maintaining Integration Objects.
• Resolve configuration conflicts. During the development of your integration points, you might encounter issues with the configuration of business components that are configured to support interactive GUI usage, but do not satisfy your integration requirements.

  The following scenarios demonstrate two situations in which you might encounter such conflicts, and a possible solution for each case:

  Scenario 1. A business component such as Internal Product is made read-only for regular GUI usage, but you want your integration process to be able to update the Internal Product business component.

  Solution. Set the AdminMode user property on the integration object to Y. This allows the EAI Siebel Adapter to use the business component in an administrator mode.

  Scenario 2. Similar to scenario 2, a business component such as Internal Product is made read-only for regular GUI usage, but you want your integration process to be able to update the Internal Product business component. The only difference in this scenario is that the business component is used through a link that has NoUpdate property set to Y.

  Solution. Because there is a link with NoUpdate property set to Y, setting the AdminMode user property on the integration object to Y is not going to help. You must create the following exclusively for integration purposes:

  • A new link based on the original link with NoUpdate property Set to N.
  • A copy of the original business object referencing the new link instead of the original. Note that both links must use the same business component.

    NOTE:  Customized configurations are not automatically upgraded during the Siebel Repository upgrade, so use this option as a last resort.