Set the timeout for operations to wait for the Data channel to catch up.

Set the configuration property to the set of ScenarioIDs that the client wishes to ignore.

Set the configuration property to the set of ScenarioIDs in which the client is interested.

Set the boolean configuration property to indicate if the service should discover instances automatically.

This disables the default behavior of discovering all scenario instances upon creating the scenario service and can be used as an alternative to the scenario inclusion/ exclusion filter as it allows discovering scenario definitions without necessarily having to discover all of their instances. Typically, a client will then need to call requestInstances on a IScenarioDefinition and wait for the discovery state to become COMPLETED before it can interrogate the instances of a scenario (the call to requestInstances is automatic if this property is not set).

Set the boolean configuration property to indicate if the Data channels (EventServiceChannels), created for listening to scenario instance output variable updates, should use strong or soft references to events in the inbound event queue.

Set the boolean configuration property to indicate if the Data channels (EventServiceChannels), created for listening to scenario instance output variable updates, should be subscribed to the normal Data channel (possibly throttled), or the Raw Data channel (always unthrottled).

Set the configuration property to filter by a given user. Scenario service clients have the ability to listen on a per-user channel for updates from a scenario. This can significantly reduce the number of updates the client needs to discard if it is only concerned with one user’s scenarios and/or DataViews.

If the setUsernameFilter() method is used, the scenario(s) listened for must be configured to send updates on the per-user channels — this is done by sending a com.apama.scenario.ConfigureUpdates event with key sendThrottledUser or sendRawUser set to true, either for all scenarios or just the scenario(s) that the client is interacting with.

Alternatively, when starting, API clients can set the Java system property com.apama.scenario.filterUser to specify what user the ScenarioService listens to updates for (currently, one ScenarioService is only able to listen to updates for one user).

The user "*" is handled specially — all clients will receive updates for the user "*", even if filtering for a specific user.