Restrictions of Subscribed Columns

An incoming message does not have to contain data for all the columns defined in the subscriber table. You can configure Subscription Service to expect only a subset of the columns. The service checks the repository for attributes defined in the class object definition of the subscriber table.

When a message arrives, the service iterates through the attributes in the class object definition of the subscriber table and looks for those same attributes in the incoming message.

When you configure the destination table, only subscribe to columns that can be updated. If you subscribe to a column that cannot be updated and a message arrives with no data for that column, a NULL value will be written to that column. The following two are examples:

If a source table is configured to send data for columns, c1, c2, and c3, and the destination table is configured to receive data for columns c1, c2, c3, c4, and c5, for the TIBCO ActiveEnterprise message and XML message wire format, columns c4 and c5 will be ignored and take on whatever default values they are supposed to have.
If a source table is configured to send data for columns, c1, c2, and c3, and the destination table is configured to receive data for columns c1, c2, and c3 but not configured to receive data for columns c4 and c5, columns c4 and c5 will retain the defaults applicable to both tables.

Note: When the publishing table is configured to use parent-child relationships, the Subscriber endpoint must use the same repository as the Publisher endpoint.