ATG Outreach Administration and Development Guide

As explained in the deployment chapters of the ATG Content Administration Programming Guide, deployment for ATG 2007.3 requires that you set up a matching destination repository for every versioned repository in your development environment and configure it to point to the unversioned database used by your target site. For ATG Outreach, the repository for which you must create a matching destination is the Outreach repository on the ATG Outreach server. (This repository is configured by OutreachRepository.properties, which is located in <ATG2007.3dir>\ACO2007.3\ACO\communication\base\config\config.jar.)

You need to configure a destination Outreach repository for every target you have; for example, if you deploy to both a staging and a production site, you need to configure two destination repositories, one for staging and one for production.

Two pre-configured .properties files that you can use for your destination repositories are provided with ATG Outreach:

These files are located in <ATG2007.3dir>\ACO2007.3\ACO\communication\base\config\config.jar.

The following example shows the contents of the preconfigured OutreachRepository_production.properties file:

#
# The initial values of the properties for the OutreachRepository
#
$class=atg.adapter.gsa.GSARepository

repositoryName=OutreachRepository_production

definitionFiles=\
  /atg/campaign/communication/outreachRepository.xml

lockManager=/atg/dynamo/service/ClientLockManager_production
dataSource=/atg/dynamo/service/jdbc/JTDataSource_production
idGenerator=/atg/dynamo/service/IdGenerator
XMLToolsFactory=/atg/dynamo/service/xml/XMLToolsFactory
transactionManager=/atg/dynamo/transaction/TransactionManager

checkTables=true

# since we are running on solid we want to simulate text searches
# this should be removed in a production system
simulateTextSearchQueries=true

#loggingDebug=true
#debugLevel=5

Configure the files as described in Setting Up Deployment in the ATG Content Administration Programming Guide. You can give your files any names you want; the convention _production and _staging is for convenience only. Locate the new files in the localconfig layer on the ATG Outreach server in a directory with the same path as the versioned Outreach repository, for example

<ATG2007.3dir>\home\localconfig\atg\campaign\communication\
OutreachRepository_production.properties

Configuring the Destination Repository Data Sources

For each destination OutreachRepository you created for the ATG Outreach server, you need to configure a data source to point to the database used by the target site. Some files preconfigured for this use are supplied with the Dynamo Application Framework in <ATG2007.3dir>\DAF\Deployment\Config\config.jar:

FakeXADataSource_production.properties
FakeXADataSource_staging.properties
JTDataSource_production.properties
JTDataSource_staging.properties

Extract these files as needed and configure them to point to the target database used by the ATG Outreach Production/Staging module. Locate the files on the ATG Outreach server in a localconfig directory specified by the datasource property of the destination OutreachRepository_*.properties file, by default /atg/dynamo/service/jdbc/.

For more information, refer to Setting Up Deployment in the ATG Content Administration Programming Guide.

Adding the Destination Repositories as InitialRepositories

Make sure the new destination repositories are recognized on startup by ATG Content Administration. To do so, add them to the initialRepositories property of the ContentRepositories.properties file. Locate this file in your CONFIGPATH, for example at <ATG2007.3dir>\home\localconfig\atg\registry\ContentRepositories.properties. For more information, see Setting Up Deployment in the ATG Content Administration Programming Guide.

initialRepositories+=\
  /atg/campaign/communication/OutreachRepository_staging,\
  /atg/campaign/communication/OutreachRepository_production