Types of TC Steps

When you define a TC step, you can choose how it behaves. A TC step can behave in one of the following ways:

•

Commit and Continue - choose this option if you want to commit the current data at the current point in the business process and start a new transaction for subsequent steps using the same iProcess Background process. The benefit of choosing this option is that it is fast, as the same Background process starts the new transaction.

•

Commit and Concede - choose this option if you want to commit the current data at the current point in the business process and start a new transaction for subsequent steps, but using a different iProcess Background process. The iProcess Background process completes the first transaction and updates the database. It then sends a message back to the Mbox where the messages are stored. Processing continues when the iProcess Background process (either the same one that processed the first transaction or another one) reads the message from the Mbox and processes it. The benefit of choosing this option is that it enables load balancing because a different iProcess Background process can process the second transaction. The Commit and Concede method is also required if you are using a Tuxedo environment.

•

Abort - choose this option to abort an EAI step in an iProcess procedure. This option is always used with an iProcess Condition. A TC step that is configured with the Abort method must always follow an EAI step. It cannot follow any other type of step. See Defining a Procedural Abort of a Transaction for an example of a procedure that uses this method.