Best practices of Checkpoint activity in TIBCO BW: HTTP, Transactions and CalledProcesses
To know the function of checkpoint Click Here
- Do not place checkpoint right after a HTTP activity.
In general, HTTP activities do not require a checkpoint as the socket for the HTTP request is closed when the process engine crashes. So on a restart, HTTP response activity will return an error.
- Checkpoint should be placed outside of a transaction group
Checkpoint should not be placed within or in parallel to a transaction. Checkpoint activity should be placed outside of any transaction group.
- You should be aware of the implication of a checkpoint when calling a process from another.
Checkpoints save the state of an entire process instance. By default when a process calls another process, the called process is executed in the same process instance as the calling process.
- When a checkpoint occurs in a sub-process, the checkpoint saves the state of the current process instance.
- When a checkpoint occurs in a spawned sub-process, the checkpoint saves only the state of the spawned process.