Application Services Interface Reference > Application Services Interfaces (ASIs) > ASI Data Synchronization Services >

Data Mapping for ASI Release Independence

Within data synchronization, a data map translates the data in the form of integration objects between an internal integration object and an interface integration object, making ASIs release-independent.

Data synchronization services use data mapping to translate data between integration objects and support a subset of methods that are used by the EAI Siebel adapter, such as Insert, Update, and Delete. See Data Synchronization Methods for ASIs for more information. An ASI usually requires two types of data maps—one for each direction, as shown in Figure 7. For more information about data mapping, see Business Processes and Rules: Siebel eBusiness Application Integration Volume IV.

Figure 7.  Mapping Between Integration Objects

For ASIs using data synchronization services, there are two types of data mapping—implicit data mapping and explicit data mapping.

Implicit Data Mapping for Integration Objects

Data synchronization services support implicit data mapping when the internal integration object is a subset or exactly the same as the interface integration object; the reverse also holds true. Implicit mapping occurs when:

• A source component maps to a target component with the same name.
• A source component maps to a target component and both components have fields with the same name.
• Data synchronization service does not specific a data map.

Every component, field, and child component is mapped between integration objects.

Figure 8 shows an example of implicit mapping between two integration objects. In this diagram, components and fields with the same name are automatically mapped; data synchronization services map these fields when a data map is not specified.

In Figure 8, the child component, Organization, which appears on the interface integration object only, is not mapped because it is not considered important to the ASI. Consequently, the two integration objects are sufficiently similar, and a data map is not necessary. Implicit mapping ignores any components and fields unique only to the interface or internal integration object, but not both.

NOTE:  Implicit data mapping requires that the root components of the internal and interface integration objects have the same name.

Figure 8.  Implicit Data Mapping

Explicit Data Mapping for Integration Objects

You must define an explicit data map whenever a component or field name of an interface integration object does not exactly match the component or field name of the internal interface object.

Siebel Systems provides prebuilt explicit data maps for its ASIs. These data maps make sure that the ASIs are release-independent.

NOTE:  To preserve the release-independent properties of fields, do not alter Siebel-defined explicit data maps except when you deactivate fields.

Automatic Mapping for Integration Objects

You can automatically extend a data map for an integration object whenever new components and fields have been added to an existing ASI. Within the Data Map Administration screen, the Auto-Map feature enables you to automatically create submaps for these new components and fields. The Auto-Map feature checks the definition of the internal integration object and the interface integration object, finds components and fields of the same name with no current map, and creates the data map for it.

You can use automatic mapping and explicit mapping together.

Upgrading Data Maps for Integration Objects

When the Siebel application is upgraded, a three-way merge is performed on the internal and interface integration objects. This merge makes sure that the customer's extensions to these objects carry forward to the new version.

If an explicit data map exists in the previous version of the ASI, a new version of the map replaces the old with the Siebel application upgrade. Any automatic mapping is regenerated. The automatic mapping exposes the customer's extensions through the new version of the interface.