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:
Property | Description |
---|---|
| Class name Default: |
| The location of the scenario configuration XML file Default: |
| Specifies that this scenario server should not run any scenarios or process any events. This property is ignored if it is set on the To disable the component entirely, see Disabling the Scenario Manager Component. |
| Determines whether the component will start along with a server. See Disabling the Scenario Manager Component. |
| The location of the Dynamo Messaging System file that contains Default: |
| Read-only flag that indicates whether this scenario server is a global server (see Global, Individual, and Process Editor Servers). Default: |
| Writes debug information about scenarios to the Default: 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: |
| The maximum number of times the system attempts to deliver the same message if an error occurs during delivery. Set to Default: |
| The Nucleus path of the Default: |
| The Nucleus path of the profile repository where profile and scenario information is stored Default: |
| Read-only flag that indicates whether this server is the process editor server (see Global, Individual, and Process Editor Servers). Default: |
| The Nucleus path of the registry that stores scenario definitions Default: |
| The Nucleus path of the Default: |
| The Nucleus path of the Default: |
| The Nucleus path of the Default: |
| Determines whether the Scenarios module gets event information from the scenario event registry (in the Default: |
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.
Property | Description |
---|---|
| Name of the profile repository property that contains the item’s repository ID. Default: |
| Name of the profile repository item’s property that is used to store the set of scenario instances associated with the profile. Default: |
| Name of the repository item descriptor that describes a user profile. Default: |