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.
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 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.