1. Integration Platform Technologies: Siebel Enterprise Application Integration Guide
  2. Creating a Siebel Integration Component to Represent an MVG

Creating a Siebel Integration Component to Represent an MVG

To create a Siebel integration component to represent an MVG, it is necessary also to create two integration components:

  • The first integration component represents the parent business component. In the example, this is the Account business component. This integration component contains only the fields that are defined in the parent business component, but which are not based on MVGs. The Multivalue Link property and the Multivalue property are empty for these fields.

  • The second integration component represents the MVG business component. In the example, this is the Business Address business component. The second integration component has one integration field for each field based on the given MVG in the parent business component. An integration component user property will be set on this integration component to tell the EAI Siebel Adapter that it is based on an MVG business component. If the MVG is a regular MVG, then the user property is named MVG. If the MVG is an Association MVG, then the user property is named MVGAssociation. In both cases, the value of the user property is Y.

The following figure shows an integration component based on an MVG and its user property value in Siebel Tools.


Integration Component Based on MVG Business Component. This image is described in surrounding text.

The EAI Siebel Adapter business service must know the names of the MVG fields as they are defined in the parent business component, which in this example is Account, and also the names of the MVG fields as they are known in the business component that represents the MVG, which in this example is Account Business Address. As shown in the following figure, the integration component fields represent the MVG.


Integration Component Fields Representing MVG. This image is described in surrounding text.

To represent both names, each field is assigned an integration component field user property named MVGFieldName, or AssocFieldName if the integration component user property is MVGAssociation. The value of the integration component field user property is the name of the field shown in the parent business component, which in this example is Business Address.