IBM E02HMLL-I Implementation Guide - Page 289

Furthermore, many delivered collaboration templates manipulate a variable named processingBusObj and leave the triggeringBusObj variable untouched. The processingBusObj variable is typically declared at the scenario level rather than the template level, though, so it is not displayed in the "Variables" view. To have the processingBusObj variable available in the "Variables" view, move the declaration for the variable from the scenario definition to the template definition. You can filter the "Variables" view to only display variables of certain types. Do the following to filter the "Variables" view: 1. Do one of the following to display the "Variables Filter" dialog: v Click Filter in the title bar of the "Variables" view v Click the down-facing arrow in the upper-right-hand corner of the title bar of the "Variables" view and select Filter from the drop-down menu Collaboration Debugger displays the "Variables Filter" dialog, as shown in Figure 90: Figure 90. Variables filter 2. Use the following techniques to configure your filter settings: v Enable the All Types checkbox to display all supported variable types v Enable only the checkboxes for specific variable types to display only those types v Click Reset to apply the default filter settings 3. Click OK. Debugging a collaboration Use the following workflow as a guideline to efficiently debug a collaboration object: 1. Create the collaboration template, create a collaboration object based on it, deploy both to the InterChange Server Express instance, and make sure that the collaboration object is started. 2. Start the Collaboration Debugger perspective as described in "Starting Collaboration Debugger" on page 259. 3. Attach Collaboration Debugger to the collaboration object as described in "Attaching Collaboration Debugger" on page 266. 4. Set breakpoints in desired locations, as described in "Working with breakpoints" on page 271. Chapter 13. Using Collaboration Debugger 277