Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Palette Reference : Checkpoint

Checkpoint
Activity
The Checkpoint activity performs a checkpoint in a running process instance. A checkpoint saves the current process data and state so that it can be recovered at a later time in the event of a failure. If a process engine fails, all process instances can be recovered and resume execution at the location of their last checkpoint in the orchestration process. If a process instance fails due to an unhandled exception or manual termination, it can optionally be recovered at a later time, if the process engine is configured to save checkpoint data for failed processes. See TIBCO ActiveMatrix BusinessWorks Administration for more information about recovering failed process instances.
Only the most recent state is saved by a checkpoint. If you have multiple checkpoints in a process, only the state from the last checkpoint is available for recovering the process.
Placing a Checkpoint activity between a Receive activity and a Reply activity will result in a failure in the reply message if the process is recovered using the checkpoint. That is, a reply message must be sent from the same process that received the message, and a restart of the process causes an error. If your checkpoint must remain between the receive and reply, consider changing the WSDL to two one-way operations and use an Invoke activity to send the reply message.
Configuration
The Configuration tab has the following fields.
Join Condition
The Join Condition tab allows you to define an expression based on the values of the incoming transitions to the activity. If the expression evaluates to true, the activity is executed, if the expression evaluates to false, either the activity is bypassed or a fault is thrown. See Transitions and Join Conditions for more information about join conditions.
The Join Condition tab has the following fields.
Specifies what action to perform if the join expression evaluates to false. The following options are available:
Inherit setting — use the default action specified within the current scope. The current scope is either the current group containing the activity or the orchestration process if the activity is not within a group.
Bypass activity if false — skip the processing of the activity, set the outgoing transition conditions to false without evaluating them, and resume processing.
Throw fault if false — throw a joinFailure fault and switch control to an error-handling routine configured to catch all unhandled exceptions. If the exception is not caught, the fault is propagated to the calling environment.
The expression to evaluate to determine if the activity should be executed. The only data available to this expression is the value of any transitions into the activity. You can use the XPath Formula Builder to create the join expression.
Input
The input for the activity is the following:
A key value that is used to compare to other process instances to determine whether another process instance with the same duplicateKey value already exists.
See TIBCO ActiveMatrix BusinessWorks Process Design Guide for more information on detecting duplicate process instances.
Error Output
The Error Output tab lists the possible exceptions that can be thrown by this activity.
This exception is thrown in the event that the process instance is restarted and another process instance with the same value for the duplicateKey has been detected. The following is the schema of this exception:
msg — an error message indicating a duplicate process instance has been detected.
msgCode — code for the error message.
duplicateKey — value of the duplicateKey for the duplicate process.
previousJobID — ID of the process that already exists that has the same duplicateKey.
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved