When a scenario is created in the ACC, the corresponding SDL file is created in the scenario registry, and the updateProcess method is called on the /atg/scenario/ScenarioManager component. At this point, the scenario is registered with the Scenario Manager, and (assuming the scenario has been enabled) it starts running. Scenario registration basically amounts to transforming each scenario segment into an SSM, adding the resultant scenario/SSM information to the Scenario Manager, and updating the Scenario Manager’s internal message map to include the new event information.
The message map is used by the Scenario Manager to efficiently determine the following:
Which scenario segments are waiting for a particular event type
Where in the segment the scenario instance must be in order to be affected by the event
Whether the instance must be individual or collective
What event filter must be satisfied for the event to trigger the transition to the next SSM state
For example, suppose that our two scenario examples (promotion and invitation) are the only two scenarios registered with the server. When a “Registers” event is received by the Scenario Manager, the message map can be used to determine that the only segment waiting for it is the Promotion segment; the only instances affected by the event are the collective scenario instances in state 1. On the other hand, if a “Visits page” event comes in, the message map will reveal that only individual scenario instances in states 4 and 6 of the Promotion SSM are affected by the event; in addition, the event must satisfy the filter “in folder ‘/products/bikes/’” for the transition to be triggered.
