As shown in the following diagram, there are two main parts to the ATG Outreach system:
The ATG Outreach server runs in your development environment and enables ATG Outreach users to create and manage campaigns via the ATG Business Control Center. It takes advantage of the asset management (“versioning”) and deployment facilities provided by the underlying ATG Content Administration system.
The ATG Outreach Production/Staging module runs on all staging, production and e-mail rendering servers (your deployment targets). It provides run-time support for deployed campaigns, monitors the status of campaign-generated scenarios, and collects and processes reporting data.
For a diagram of an ATG server configuration that shows how the ATG Outreach pieces relate to other applications, refer to the ATG Multiple Application Integration Guide.
Your business goals and specific technical requirements determine the number and kind of servers you set up within your campaign development and production environments. (For configuration guidelines, see the ATG Content Administration Programming Guide.) Note that you have the option of rendering e-mail content from your ATG Outreach production server(s) or from one or more dedicated rendering servers. An e-mail rendering server is configured just like an ATG Outreach production server (and requires access to the same content and profile repositories), but it does not serve web content. Dedicated rendering servers are recommended for high-volume e-mail campaigns. For testing purposes, you can set up an ATG Outreach staging server with test profiles and e-mail addresses.
