Modify transactions bean

A list of updates can be applied to multiple items in the FTM database by using the modify transactions bean.

The payload class name for the modify transactions bean is com.ibm.paydir.ima.txacc.app.bridge.payment.ModifyPaymentsBean.

Since it implements the transaction action interface, it can contain any number of transaction actions in a single message, as well as another modify transactions bean.
Notes:
  1. Try to avoid embedding another modify transactions bean because it might lead to an infinite loop.
  2. Be careful not to reuse any transaction action instances when adding them to the modify transactions bean because it could corrupt the previous beans. Always create a new instance of any transaction action, apply the requisite mutations, and add it to the modify transactions bean.

When queried, the modify transactions bean returns ACTION_MODIFY_LIST as its action code. Querying it for the payment ID always returns zero because the action applies to multiple transactions.

The caller can use the mutator methods that are shown in the following table to configure the modify transactions bean. The add action method can be called multiple times, with different transaction actions, to build a complete set of updates.
Table 1. ACTION_MODIFY_LIST request
Method name Takes data type Description
addAction PaymentAction Adds the specified transaction action to the list of transaction actions.

The modify transactions bean is useful for collecting large updates in a single message that the Transaction Server processes at once. The transaction action uses a single database connection with a single phase commit for all updates. Too many transaction actions transferred in a single modify transactions instance can cause a log buffer full database condition. Break the update into smaller chunks before sending them to the Transaction Server to correct the database condition.