Starting ATG Campaign Optimizer on your Application Server

To start ATG Campaign Optimizer on IBM WebSphere, Oracle WebLogic, or JBoss Application Server, use the <ATG10dir>/home/bin/runAssembler script to create an EAR file for each ATG Campaign Optimizer module. You can then deploy the resulting EAR files to your application server and start them according to the instructions in your application server documentation. You can find detailed information about the runAssembler script in the ATG Platform Programming Guide.

Note: If you used CIM to set up ATG Campaign Optimizer, the EAR files have already been assembled and deployed, so you do not need to follow the procedures in this section. The ATG Campaign Optimizer modules start up automatically when you start the application server. Refer to your application server documentation for more information.

Note that your SQL database and the DistributorServer must be running before you start your ATG applications. To start the DistributorServer on your HTTP server machine(s), run the startNucleus -m Distributor command under <ATGWebServerExtensions_dir>\home\bin.

To assemble a J2EE application that includes ATG Campaign Optimizer, you execute a command in this format:

runAssembler [options] output-file-name
–m module-list

Be sure to specify all ATG Campaign Optimizer modules or submodules that you want to work with, plus the application module that includes the Web application you are testing, plus any other ATG modules required. For example, you could use the following command to assemble an application in development mode that includes ATG Campaign Optimizer without ATG Commerce extensions:

runAssembler –standalone COServer.ear -m ABTest.runtime
 ABTest.management.Versioned ABTest.reporting
 DafEar.Admin <additional modules>

If your installation includes ATG Commerce, include additional modules that allow business users to include ATG Commerce elements in tests. For example:

runAssembler –standalone COServer.ear -m DCS-ABTest.runtime
   DCS-ABTest.management.Versioned DafEar.Admin <additional modules>

You can include the following optional –layer commands when you start the ATG Campaign Optimizer server:

Option

Notes

-layer staging

Include this option if you want to deploy ATG Campaign Optimizer tests to a staging server as well as a production server. Among other changes, this option enables the appropriate staging and production workflow. See Managing Workflows for more information.

-layer preview

Include this option if you installed the preview feature. See Previewing Tests for more information.

For example:

runAssembler –standalone COServer.ear –layer preview –layer staging
-m ABTest.runtime  ABTest.management.Versioned ABTest.reporting
 DafEar.Admin <additional modules>

If you are running the ATG Campaign Optimizer Reporting module on a separate server, omit ABTest.reporting from the EAR file for the Production/Staging module and create a separate EAR file for the reporting module:

runAssembler –standalone COReporting.ear
–m ABTest.reporting DafEar.Admin

Notes:

For detailed instructions on assembling ATG applications, see the ATG Platform Programming Guide.