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: