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


Chapter 4 Working with Orchestration Processes : Activities Within Orchestration Processes

Activities Within Orchestration Processes
The activities in the ActiveMatrix BusinessWorks BPEL Extension palette are the building blocks of orchestration processes. Table 6 describes each activity and its use within an orchestration process.
Variables are useful for maintaining the status of an orchestration process or storing information to input into an activity.
Any kinds of errors encountered in an orchestration process can be caught and handled. You may want to design exception-handling routines to automatically deal with commonly encountered errors, or you may wish to use exception-handling routines to log or return detailed information.
Saves the state of the orchestration process so that it can be restarted from the checkpoint in the event of engine failure.
TIBCO ActiveMatrix BusinessWorks allows you to create automated business processes that execute your business logic. You can invoke a TIBCO ActiveMatrix BusinessWorks process from within an orchestration process.
Used to perform actions based on the time within an existing orchestration process. For example, you may wish to send daily reminders that a process is running, or you may wish to exit the process after it has been running for more than 5 days.
Used to perform actions based on an incoming message within an existing orchestration process. For example, once a new orchestration process is created to handle an incoming order, the On Event activity can wait for messages that request the status of the order.
Receives a message. The orchestration process waits for the incoming message before proceeding to the next activity in the flow.

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