IBM BJ0NJML Integration Guide - Page 246

Predefined Object Structure Modifications By default, nonpersistent columns are excluded in the object when the object structure is created. If you modify the object structure, you can include new nonpersistent columns to the object definition in the object structure. Interface Table and Flat File Considerations If you use the object structure in interface tables or flat files, check whether duplicate column names exist in the object structure. If duplicate names exist, modify the alias value for the duplicate columns. Modifying the alias ensures that all column names are unique and the system can generate the interface table or flat file without errors. Interface tables require that all columns that are included in the corresponding object have an alias name of 18 or fewer characters. Predefined Object Structure Modifications Content Objects of an Object Structure Object Columns Interface Table and Flat File Considerations You can modify predefined object structures, subject to the following restrictions. You can add objects to a predefined object structure, but you cannot delete predefined objects from the object structure. You can circumvent this restriction by copying the predefined object structure to create a user-defined object structure, and deleting objects from the copy. You can include and exclude persistent and nonpersistent columns within the scope of the standard validations. Outbound messages include the columns for objects that you add to an object structure. Test inbound messages to ensure that the added object columns are processed successfully. If the object columns are not processed successfully, add an enterprise service processing class to handle the inbound processing. If you use the object structure in interface tables or flat files, check for object structure column duplications. If you use interface tables, regenerate the table for every enterprise service or publish channel that uses the modified object structure. Endpoint Creations Handler An endpoint identifies a location and the processing logic of data publication. In the defined endpoint handler, you can identify how to route outbound data to a specific location. You also can define which data format the integration framework uses by using the handler. A handler specifies how to route outbound data to a specific endpoint location in a specific format. When you create a handler, you identify the Java class file that contains the associated processing logic. You then associate the handler with the endpoint location when you create an endpoint. 232 Integration Guide