You can run and debug projects in BusinessEvents Studio, using test data to understand how BusinessEvents rules behave in response to inputs. Debugger shows potential problems in execution of rules and rule functions. You can also simply test a project by running it against test data. You can run multiple engines at the same time, for example, one engine’s processing unit might run an inference agent while another’s runs a cache agent.
The TIBCO BusinessEvents Decision Manager add-on product also uses the tester for testing decision tables. The Decision Manager project tester enables technical and non-technical users to test rules, rule functions, and decision tables.BusinessEvents Debugger allows you to control the execution of a project by setting breakpoints, stepping through your code, suspending launched programs, examining the contents of variables, providing rule input, and so on.BusinessEvents Debugger integrates with the Eclipse Java development toolkit debugger. Much of the functionality is standard Eclipse debugger functionality. See the Eclipse help for details on features such as breakpoint preferences and other functionality. This chapter explains only the BusinessEvents-specific features.You can debug local projects using their CDD and EAR files, and you can also debug remote engines.
Declarative Programming and Stepping Step into, step over, and step return may not behave as you might expect. In a declarative rule language like BusinessEvents, unlike with a procedural language, there is no predetermined path through the code. The inference engine logic determines the next action (next rule) based on various conditions and settings, not the rule itself.Running projects to test them works in a way similar to debugging, without the ability to add break points and so on. For testing purposes, you choose options to run the engine, rather than to debug the engine.Before you debug or test a project, you define settings needed to launch the engine, using a launch configuration file.You can add multiple launch configurations for one project, each configured for different purposes. For example, you may want to test the effect of different startup arguments. Or if you are using cache OM, you could create one configuration for the processing unit (PU) that runs an inference agent, and one for the PU that runs the cache agent.When you test or debug an engine, you must assert test data directly to working memory. The test data in the working memory triggers rules in the normal way, so you can observe conflict resolution and run to completion cycles in the engine.Tester Data You can create and save concept and event instance data for later use. You can then assert this data selectively when running or debugging the engine.Rule Data You can provide data as it is expected by rules in the Rule Data tab of the Debugger perspective. See Working with Rule Data.After every run, TIBCO BusinessEvents creates a consolidated results file in XML format. It has detailed information on the test run. This results XML file is easy to view and compare.
Copyright © TIBCO Software Inc. All Rights Reserved.