The main Nucleus component responsible for scenario operations on each scenario server is /atg/scenario/ScenarioManager. The following table lists the properties of the ScenarioManager component:




Class name

Default: atg.scenario.ScenarioManagerService


The location of the scenario configuration XML file

Default: /atg/scenario/scenarioManager.xml


Specifies that this scenario server should not run any scenarios or process any events. This property is ignored if it is set on the ScenarioManager component of a process editor server.


The location of the Dynamo Messaging System file that contains message-source and message-sink definitions for global events.

Default: /atg/dynamo/messaging/


Read-only flag that indicates whether this scenario server is a global server (see Global, Individual, and Process Editor Servers).

Default: false. Set to true at runtime for global servers and for the process editor server.


Writes debug information about scenarios to the debug.log file and to the ATG console window.

Default: false

For more information on this property and the other debugging properties in this component, see Monitoring and Debugging Scenarios.


Displays an informative message rather than a long series of errors in cases where a server attempts to run scenario created by another server. See Monitoring and Debugging Scenarios for more information.


The maximum batch size to use when performing batch operations on scenario instances. Batch operations come into play when you perform scenario actions on a large number of profiles (for example, sending an e-mail message to a large group of users). It may not be possible to perform the entire operation in a single transaction because databases have a fixed size for their transaction logs. Thus, the action is executed in batches over multiple transactions. The batch size needs to be large enough to minimize the overhead of independent queries, but small enough so that you do not fill up the transaction log when processing changes for each of the items in the batch. See also Minimizing the Number of Collective Elements.

Default: 1000


The maximum number of times the system attempts to deliver the same message if an error occurs during delivery. Set to -1 to have the system try an unlimited number of times.

Default: 1


The Nucleus path of the MessagingManager component that is used to obtain information about DMS messages

Default: /atg/dynamo/messaging/MessagingManager


The Nucleus path of the profile repository where profile and scenario information is stored

Default: /atg/userprofiling/ProfileAdapterRepository


Read-only flag that indicates whether this server is the process editor server (see Global, Individual, and Process Editor Servers).

Default: false. Set to true at runtime for the process editor server.


The Nucleus path of the registry that stores scenario definitions

Default: /atg/registry/Scenarios


The Nucleus path of the SDLParser component, which interprets the scenario definitions

Default: /atg/scenario/SDLParser


The Nucleus path of the ServerName component that provides this ATG server’s name

Default: /atg/dynamo/service/ServerName


The Nucleus path of the TransactionManager component

Default: /atg/dynamo/transaction/TransactionManager


Determines whether the Scenarios module gets event information from the scenario event registry (in the scenarioManager.xml file) or the Dynamo Messaging System registry. If true, the scenario event registry is used. This property exists to allow compatibility with versions of ATG products before 6.0.0. For more information, refer to Using Scenario Events.

Default: False

In addition, the following properties of ScenarioManager specify the item descriptor and property names that are used to store scenario-related information in the profile repository. These must correspond to the names specified in the repository template. Do not change them unless you make the corresponding changes in the repository template as well.




Name of the profile repository property that contains the item’s repository ID.

Default: id


Name of the profile repository item’s property that is used to store the set of scenario instances associated with the profile.

Default: scenarioInstances


Name of the repository item descriptor that describes a user profile.

Default: user

loading table of contents...