This section describes how to perform ATG Outreach setup tasks if you did not use CIM to complete the post-installation configuration.
Creating the Database Schema for the ATG Outreach Server
Follow these steps to create the database tables required by the ATG Outreach server.
If you haven’t done so already, create the database tables for the ATG Content Administration system. See the ATG Content Administration Programming Guide for instructions. Make sure the database tables and data are up to date for ATG 9.3.
Run the following SQL script to create the ATG Outreach tables:
<ATG9dir>\ACO9.3\ACO\sql\install\database\management_ddl.sql
Note that the schema created by the management_ddl.sql script includes the reporting log tables used by older versions of ATG Outreach. These tables are still required by ATG Outreach 9.3.
Configuring the ATG Outreach Server Data Source
The ATG Outreach server relies on the database instance configured for the underlying ATG Content Administration system. (This database stores the “versioned” campaign assets checked in to the ATG Content Administration system. It also stores the profiles of ATG Content Administration and ATG Outreach users.) Initially, the ATG Content Administration system uses the default ATG data source, which points to the SOLID evaluation database. If you haven’t already done so, you need to reconfigure this data source so it points to a production-quality database. For more information, see the ATG Content Administration Programming Guide.
Configuring the External Profile Repository Data Source
If you have not done so already, configure the data source used by the external profile repository on the asset management (ATG Content Administration) server so that it points to the database on the production server. For ATG Outreach, it is important to set this data source correctly so that the segment count and Profile Browser features reference external profiles.
Configure the
/atg/dynamo/service/jdbc/JTDataSource_productioncomponent on the asset management server to point to the production database. (You must complete this step even if you are using the SOLID evaluation database.)Configure the
/atg/dynamo/service/jdbc/JTDataSourcecomponent on the asset management server to point to the versioned database. (You do not need to complete this step for SOLID but you do need to do it for a production-quality database.)Configure the
/atg/dynamo/service/jdbc/JTDataSourcecomponent on the production server to point to the production database. (You do not need to complete this step for SOLID but you do need to do it for a production-quality database.)
For detailed information, see Configuring Profile Repository Data Sources in the ATG Business Control Center Administration and Development Guide for detailed information.
Importing the Initial ATG Outreach Data
To import the initial ATG Outreach data into your database:
Make sure your
DYNAMO_HOMEandJAVA_HOMEenvironment variables are set.DYNAMO_HOMEshould point to<ATG9dir>\homeandJAVA_HOMEshould point to the JDK root directory (C:\Program Files\Java\jdk1.5.0_16, for example).If you haven’t done so already, import the initial ATG Content Administration data. See the ATG Content Administration Programming Guide for instructions.
Run the following ATG Outreach scripts:
<ATG9dir>\ACO9.3\ACO\install\importACOManagement.{bat|sh}
<ATG9dir>\ACO9.3\ACO\install\importACO-Outreach.war.{bat|sh}Creating the Database Schema for the Production/Staging Module
Follow these steps to create the database tables required by the ATG Outreach Production/Staging module.
If you haven’t done so already, create the database tables for the ATG Adaptive Scenario Engine. For instructions, see the Configuring Databases and Database Access chapter in the ATG Installation and Configuration Guide.
Run the following SQL script to create the ATG Outreach tables:
<ATG9dir>\ACO9.3\ACO\sql\install\database\runtime_ddl.sql
Configuring the Production/Staging Data Sources
The ATG Outreach Production/Staging module uses the database configured for the ATG Adaptive Scenario Engine. The ATG Adaptive Scenario Engine is preconfigured to use its own data source, which initially points to the SOLID evaluation database. For information about overriding this default configuration, see the ATG Installation and Configuration Guide.
