Configuring the Scenario Service Provider

To customize how resources are assigned to scenario suites, you need to configure the Scenario Service Provider (SSP).

The SSP can start multiple threads to execute scenario suites that are run from the Decision Center Enterprise console, and can use an assigned thread priority to determine which thread is used. The SSP must be configured if you want to control the executed threads.

When you execute a scenario suite from the Enterprise console, the SSP creates a thread dedicated to the execution of this scenario suite. If a simulation is divided into a number of scenario suite parts, the SSP creates one or more threads to execute the simulation parts concurrently.

Note:

The SSP always creates one or more threads to run a scenario suite.

At run time, the SSP client runs a scenario suite runner using an SSP service. For parallel execution of a simulation, a scenario suite runner:

initializes the IlrKPIResultAggregator
retrieves the scenario suite part from the IlrParallelScenarioProvider instance
creates one private runner instance per part, which instantiates a scenario provider to run the part
performs the KPI calculation for all of the returned scenario suite parts

To run a simulation part, each runner:

creates an execution context
initializes the KPI
gets a scenario using the scenario iterator
executes the ruleset to test with scenario data
performs the tests
performs the KPI calculations

The scenario suite runner returns the result to the SSP service, which then returns the result to the client. The implementation classes must be added to the SSP archive (testing.war/WEB-INF/classes or testing.war/WEB-INF/lib) before it is deployed and configured on an application server. You can then write an SSP client that runs the SSP service using the public API, or enable a custom scenario suite format in Rule Designer with the scenario provider and the list of KPIs to define and run a simulation in parallel from Decision Center. For more information, see the ilog.rules.dvs.core and ilog.rules.dvs.ssp API packages.