How the TemplateEmailSender Works
(Doc ID 1577600.1)
Last updated on NOVEMBER 04, 2019
Applies to:Oracle Commerce Platform - Version 2006.3 and later
Information in this document applies to any platform.
This document describes the Oracle Commerce (ATG) TemplateEmailSender feature for sending templated emails to customers.
This document is aimed at developers and system administrators that wish to understand the different components, classes, and mechanisms of how the Oracle Commerce templated email sending works.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. What is the TemplateEmailSender?|
|2. Important classes to know about|
|2.1. Non distributed (non batched) email sending|
|2.2. Distributed (batched) mailing support|
|3. How the TemplateEmailSender works|
|3.1. Persist mailing information|
|3.2. Queue up the mailing|
|3.3. Establish new session|
|3.4. Check if the email contact can be emailed|
|3.5. Create templated email for each user|
|3.6. Handles problems while generating the email content|
|3.7. The email messages are sent via an EmailMessageSender implementation|
|3.8. The mailing is marked complete|
|3.9. The session is invalidated|
|4. Frequently Asked Questions|
|4.1. What is email batching?|
|4.2. What does the property updateProfileStatusesEveryNMessages configure?|
|4.3. What does the property updateBatchCountsEveryNMessages configure?|
|5. Common problems|
|5.1. Loopback request not configured correctly|
|5.2. Unexpected responses from the server when rendering the template|
|5.3 EmailRequestThread is dead Errors|
|5.4 Emails for one user are being sent to another user|