TCC - Handling multiple entry points in a call graph

Handling multiple entry points in a call graph

If two entry-points are included in the same call graph, two transactions will be identified for the parts of the call graph that are situated below the entry points. As a consequence, the transaction that is “higher up” could be recorded by the CAST Transaction Configuration Center as empty, whereas the “lower” transaction will be correct. In this case it is recommended to only retain the entry point that is “higher up” so that the the most complete transaction is recorded. As a consequence the number of “empty” transactional functions will decrease.

For example, if the call graph contains the following transaction: A > B > C > D where D is an end-point or data-entity and where A and C are entry-points, then the CAST Transaction Configuration Center will record a transaction for A > B (empty) and one for C > D.

In this example, we would retain only the “higher placed” entry-point (A) to ensure that the C > D transaction was discarded.