ATG Content Administration Programming Guide

After setting up target site deployment agents, you can start them as described in the following sections:

Caution: Do not use any ATG Content Administration modules or the DAF.Deployment module with a standalone GSA lock manager server. Doing so causes the lock server to become a slave server of the deployment. It attempts to deploy files, and the deployment deadlocks as a result. Symptoms include the deployment cycling in a time out loop.

Running the Publishing Agent

To activate the Publishing agent on an ATG server, assemble an application that includes the following application module:

PublishingAgent

You also use non-versioned modules with your ATG Content Administration application on the target site. Once you have an application, deploy it to the appropriate server. For information on ATG modules and application assembly, see the ATG Installation and Configuration Guide.

Running the Publishing Web Agent

To use the Publishing Web agent with a Web server, make sure your JAVA_HOME environment variable is set; then change to the ATGWeb2007.3/home directory (in order to set the NUCLEUS_HOME environment variable) and enter one of the following commands:

This command starts up Nucleus and the PublishingWebAgent module.

If you also have a configured DistributorServer on the Web server (as part of a Content Distributor system), you can start up the Distributor and PublishingWebAgent modules at the same time, as in the following example:

bin/startNucleus –m PublishingWebAgent:Distributor

For information on Content Distributor systems, see the Content Distribution chapter in the ATG Programming Guide.