The following examples show the modules to include in your EAR files for ATG Outreach if you do not require ATG Commerce features.
For the ATG Outreach server:
runAssembler –standalone OutreachServer.ear -m ACO.communication.base
ARF.base ARF.BIZUI ARF.WSCAPDafEar.Admin
<additional modules>
If you do not use ATG Customer Intelligence reporting features, omit the ARF.base
, ARF.BIZUI
, and ARF.WSCAP
modules.
You can include the following optional –layer
commands when you start the ATG Outreach server:
Option | Notes |
---|---|
| Include this option if you want to deploy ATG Outreach campaigns to a staging server as well as a production server. Among other changes, this option enables the appropriate staging and production workflow. See Configuring an ATG Outreach Staging Environment for more information. |
| Include this option if you want to use the e-mail preview feature (see E-mail Preview). |
Example:
runAssembler –standalone OutreachServer.ear –layer Preview -layer staging
ARF.BIZUI ARF.WSCAP
-m ACO.communication.base ARF.baseDafEar.Admin
<additional modules>
For the ATG Outreach Production/Staging module:
runAssembler –standalone OutreachProductionStaging.ear
PublishingAgent
-m ACO.communication.runtime
ACO.Communication.DWDafEar.Admin
<additional modules>
If you do not use ATG Customer Intelligence reporting features, omit the ACO.Communication.DW
module.
If you are running the ATG Outreach data loading module on a separate server, omit ACO.Communication.DW
from the EAR file for the Production/Staging module and create a separate EAR file for the data loading module:
runAssembler –standalone OutreachDataLoader.ear
ACO.Communication.DW
–mDafEar.Admin
Notes:
The
–standalone
flag is required in all cases.The
DafEar.Admin
module shown in the list starts the ATG Dynamo Server Admin. This module is optional.
For detailed instructions on assembling ATG applications, see the ATG Programming Guide.