|
Upgrade Guide for DB2 UDB for z/OS and OS/390 > Postupgrade Tasks for a Development Environment >
Deleting Duplicate EIM Mappings
Upgrades: Release 6.x only. Environments: Development environment only. Any custom Enterprise Integration Manager (EIM) mappings that were added to previous versions of Siebel eBusiness applications will be automatically migrated to the new custom repository. If custom mappings are duplicated by new mappings added as part of Siebel version 7, errors will result when you use EIM. NOTE: Custom EIM mappings are only added to old _IF tables, not to new EIM tables. If you need to use the new EIM tables, you must manually add the customization to them.
The Database Server Configuration Wizard that you ran in Upgrading the Physical Schema generated a file called mapclash.txt. This file lists any custom EIM mappings that conflict with Siebel Systems-provided mappings. The file contains the columns illustrated and defined in Table 32.
Table 32. Mapclash.txt File Column Names and Definitions
|
|
IT_Name
|
Interface table name (example: S_ACCOUNT_IF) |
DT_Name
|
Destination table (base table) name |
DC_Name
|
Destination column (base table column) name |
Before proceeding with the upgrade, use Siebel Tools as described below to delete any custom mappings listed in this file. To delete duplicate custom EIM mappings
- Launch Siebel Tools and select Prior Customer Repository.
- From the Object Explorer, choose EIM Interface Table > EIM Table Mapping.
- From the EIM Table applet, select the interface table name (
IT_Name), for example, S_ACCOUNT_IF, and query for the interface table.
- From the EIM Table Mappings applet, choose the name assigned for the destination table (
DT_Name); for example, S_ORG_EXT_X.
- From the Object Explorer, choose EIM Table Mapping > Attribute Mapping.
The fourth column in this applet is the DC_Name.
- Delete the duplicate mappings.
| 
