IBM BJ0NJML Integration Guide - Page 111
Creation of Interface Tables
![]() |
View all IBM BJ0NJML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 111 highlights
Creation of Interface Tables The sequence of TRANSID identifies the sequence in which records are processed by the integration framework. For example, when employees and their phone numbers are entered into the system, the TRANSID values for the PO record must be lower than the TRANSID values for the PO receipt records that reference that PO. The primary difference between the MXIN_INTER_TRANS and MXOUT_INTER_TRANS queue tables is the direction of the interface table records that they track. The external system must write to the MXIN_INTER_TRANS queue table, and the integration framework must read from it. The integration framework writes to the MXOUT_INTER_TRANS queue table, and the external system reads from it. The external system can use the MXOUT_INTER_TRANS table or retrieve outbound records from interface tables. The interface queue tables are generated the first time that you create interface tables for an endpoint. Each endpoint has its own pair of interface queue tables and own a counter for maintaining the outbound TRANSID value. Creation of Interface Tables When an enterprise service and a publish channel use the same interface table, the Create Interface Tables dialog box displays a list of interface tables based on the uniqueness of the interface table name and its corresponding endpoint. You can create interface tables for enterprise services and publish channels when the associated object structures are marked as flat supported. The Support Flat Structure check box must be selected on the object structure. The alias conflict must also be resolved before an interface table is created. You can create interface tables for data synchronization on enterprise services and on publish channels. Interface tables do not support Query and Invoke operations. You can create interface tables for a specific endpoint. You must identify where the tables are created. The database location that is referenced by the endpoint can be a local database or a remote database. When you create interface tables on a local database, the columns are registered in the system data dictionary. Local interface tables that use a database table and a database column show all updates (except insertions and deletions) to a base column attribute (such as data type) when you run the database configuration operation. When columns are added to or deleted from the base table, you must regenerate the corresponding enterprise service and the publish channel interface tables to apply the column changes. No changes are applied in the remote databases. You must regenerate remote interface tables to apply the column changes. Interface Tables 97
![](/manual_guide/products/ibm-bj0njml-integration-guide-77e799f/111.png)