Bookshelf Home | Contents | Index | Search | PDF

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

Best Practices

---

Familiarize yourself with the business logic in the business components. Integration designers should 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. See Performance Considerations.
Design with maintenance in mind. See Siebel Integration Objects Maintenance and Upgrade.
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 three different situations in which you might encounter such conflicts and a possible solution for each case.

Scenario 1. Your integration requires explicitly setting a primary child, but the business component configuration does not allow that because the related MVLink has Auto Primary property set to Default.

Solution. Change the Auto Primary property from Default to Selected. This enables EAI Siebel Adapter to change the Auto Primary property according to the input request, while making sure that there is always a primary child selected.

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.

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 3. 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. Since 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 need the 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 the same business component should be used by both links.

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

Bookshelf Home | Contents | Index | Search | PDF