Interface table end point processing

Support of interface tables relies on the creation of the table based on the configuration of the objects and columns included (and excluded) in the related object structure.

If a new persistent attribute is added to an object, and that object is in an object structure that is associated with an interface table, end point processing can encounter an error writing to the interface table if the table has not been re-created to reflect the updated object structure. So, when a new column is added by a customization or by through the installation of an industry solution or a partner solution, the related interface table must be recreated. This is true even if the new column added is not intended to be integrated with other applications.

Using a new system property, mxe.int.usedbinfoforifacetb, processing for interface tables no longer requires an exact match between the object structure and the interface table. When the system property is set to 1 (true), the interface process refers to the existing table to determine what to insert into the table rather than the object structure definition. This process avoids invalid column name errors when the end point is writing to the interface table.

In order to support any newly added attribute in an interface table, the table must be regenerated to align with the object structure definition.

Related to this change, there is a utility available on the IBM Integrated Service Management Library that can check an interface table and its related object structure to identify out of sync conditions. This utility can also update the object structure to exclude columns when those columns do not exist in the interface. See this link for more information: http://www-304.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10MA58.