Because running the global scenario server places an additional burden on your Dynamo server, consider configuring the global servers to not accept any user sessions. Do this by setting the drpEnabled property to false in the /atg/dynamo/Configuration component for that Dynamo instance. Specifically, this may be a good idea if you anticipate creating a lot of scenarios that will run primarily on a global server - for example, scenarios that send e-mail to a large number of visitors at a predetermined time.

 
loading table of contents...