Set up targeted e-mail as described earlier in this chapter.

Set the enabledAsTemplateMailServer property in the atg/userprofiling/email/TemplateEmailSender component to true.

Make sure that the TemplateEmailSender is in the initialServices list so that it will be started when the server is launched.

Check that caching is configured as shown for the following repository item descriptors in the userProfile.xml file.

<item-descriptor name="mailing" cache-mode="locked" />
<item-descriptor name="mailBatch" cache-mode="locked" />
<item-descriptor name="mailServer" cache-mode="disabled" />

Note the cache mode is set automatically in the liveconfig configuration layer, so if you are deploying a live site, you can simply add the liveconfig configuration layer to the environment for all the distributed e-mail servers. See the Configuring Dynamo chapter of your application server’s ATG Installation and Configuration Guide for information about the liveconfig configuration layer.

However, if you are working in a non-production environment that does not include the liveconfig configuration, you must set the cache mode manually as shown above.

Check that lock managers are configured to prevent conflicts among threads. Specifically, check that you have a ServerLockManager enabled on the machine that acts as the lock server. On each machine that will render e-mail threads, make sure you have a ClientLockManager pointing to the ServerLockManager. For more information, see Locked Caching in the ATG Repository Guide.

If you are sending mailings programmatically, make sure that the template e-mail system is set up to perform persistent mailings. See Stopped E-mail Campaigns for more information. (If you are using scenarios to send the mailings, persistence is handled automatically.)