Configurations

The behavior of scenario execution is controlled by a configuration, defined in XML files according to a schema (XSD). Configurations define the following:

Each scenario, scenario suite, and simulation definition can specify a configuration to use during its execution. Configurations are independent of these definitions; you can apply different configurations for different scenarios within a single scenario suite, for example.

Configurations are prioritized within an ordered hierarchy. You can define configuration files at each of the simulation, scenario suite, and scenario levels, with the most granular-level configuration taking priority. If a configuration is not defined within a particular scenario, for example, the configuration of its owning scenario suite is applied. At least one configuration must be defined within the hierarchy.

Executor

An executor is a Java class that determines how scenarios are executed. An executor acts as a proxy and can specify that scenarios are executed via the HTTP protocol within a Java EE environment, or locally in a Java SE environment. New executors can be defined by developers.

Databinding

Databinding is a transformation of data from one format to another. In scenario executions, input and output data mapping is performed by Java classes, specified in configuration files. Input data is mapped to Java objects for the Scenario Service Provider to process, and the reverse mapping is performed to produce output data in a human-readable format.

Examples of databinding used in Rule Scenario Manager include the following:

The databinding classes used during a scenario execution are defined in the configuration that applies to that scenario. Available classes can be those supplied with Rule Scenario Manager or new ones created by developers.

Related Concepts

Related Tasks

Related Reference

Related Samples