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


Chapter 8 Testing and Deploying Orchestration Processes : Testing Orchestration Processes

Testing Orchestration Processes
All of the features and functionality of testing process definitions described in TIBCO ActiveMatrix BusinessWorks Process Design Guide are available in the TIBCO ActiveMatrix BusinessWorks BPEL Extension for testing orchestration processes. For example, you can set breakpoints within orchestration processes and step through the processes as they execute. There are some additional testing features and functionality in the ActiveMatrix BusinessWorks BPEL Extension. This section describes the features available only in the ActiveMatrix BusinessWorks BPEL Extension.
Loading And Starting Orchestration Processes
Similar to process definitions with process starters in TIBCO ActiveMatrix BusinessWorks, orchestration processes require an incoming message to begin execution. Therefore, you can load orchestration processes into the test process engine, but they cannot execute until a message is received. Also, the Service resource is used to route messages to the correct orchestration process, so a Service resource must also be loaded into the test engine.
To test orchestration processes, you can create a TIBCO ActiveMatrix BusinessWorks process definition that invokes operations on a service. You can use the Invoke Service activity within a process definition to invoke a ActiveMatrix BusinessWorks BPEL Extension service. You can also use some other activity that generates a message in the proper format, such as SOAP Request Reply, if the service has endpoints exposed by way of SOAP.
When starting a test engine session, you should load the following resources in the Select Processes to Load dialog:
a Service resource that uses one or more orchestration processes as implementations of its operations. The referenced orchestration process(es) is loaed automatically by the Service resource.
Colors and Icons in Test Mode
When stepping through an orchestration process, activities and transitions in the process change color to indicate what is occurring during the execution. The colors are similar to the colors used when testing a TIBCO ActiveMatrix BusinessWorks process definition. Table 8 describes the colors and icons in test mode and their significance.
The orchestration process is paused at this activity. This could be either because the activity has a breakpoint set or because the Step to Next Activity or Run To This Resource menu item was used.
The activity has not yet executed, but it is the next activity to execute when execution continues.
The activity is currently executing, but the focus is not on the activity. This can occur if you have multiple paths in your orchestration process and the focus is not on the current path.
This icon indicates the activity has been skipped. This occurs when an activity’s join condition evaluates to false.

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