Siebel Marketing Installation and Administration Guide > Installing and Configuring Email Marketing >

Architecture of Siebel Email Marketing

An example of a typical architectural structure for Siebel Email Marketing components is shown in Figure 4. The Email Marketing components interact with Siebel Marketing as follows:

1. The Email Sending Daemon, located in the corporate network, listens for requests from the Siebel Marketing Server, then assembles each outbound email message for a campaign, and sends it to the Mail Transfer Agent for delivery.

   For more detailed information on how the Email Sending Daemon interacts with Siebel Marketing, see Email Sending Daemon Integration and Workflow.

2. The Mail Transfer Agent receives the email messages and forwards them to their destinations.
3. The Bounce Handler Daemon, located in the DMZ, tracks email messages that cannot be delivered and records the reason why the message cannot be delivered.
4. The Click Through Daemon, located in the DMZ, tracks clicks made by email recipients on links included in the email template that are supported by Siebel Marketing.

If Siebel Email Marketing components lose connectivity to the Siebel Server, then they queue all data and continue to function. After the connection is reestablished, queued data is processed.

Figure 4. Architecture of Siebel Email Marketing

Email Sending Daemon Integration and Workflow

Figure 5 shows a more detailed view of the Siebel Email Sending Daemon, its interrelationship with Siebel Marketing, and the outbound flow of work within this architecture. The following steps correspond with the numbers in the figure:

1. A workflow is launched to generate list files for each batch (subwave).
   • If Basic email personalization mode is implemented, then the Siebel Server generates the list files.
   • If Advanced email personalization mode is implemented, then the workflow calls Business Intelligence Web to generate a list that is formatted for email personalization, then Business Intelligence Presentation Server generates the list files.
2. The workflow waits until files are returned.
3. Workflow launches a subprocess for each file and then notifies the Email Sending Daemon of the location of each file.
4. The Email Sending Daemon retrieves each subwave list of Prospects and Contacts.
5. The Email Sending Daemon sends email to the Prospects and Contacts in each subwave list.

Figure 5. Email Sending Daemon Integration and Workflow