The Publish Web Content campaign action makes it possible for business users to publish text or binary content to a target site. In order to support the publication of binary web content, you need to install a DistributorServer
component on your HTTP server machine(s).
A standalone DistributorServer
is included in the Oracle ATG Web Commerce Web Server Extensions 9.3 distribution, which you can download from the Oracle Web site. (For detailed installation and configuration instructions, refer to the Content Distribution chapter in the ATG Programming Guide.) By default, the DistributorServer
listens for connections on port 8810 and caches binary files in the <ATGWebServerExtensions_dir>\home\doc
directory. For example:
port=8810
cacheDirectory=C:\\ATG\\ATGWeb9.3\\home\\doc
You can change these settings by editing the <ATGWebServerExtensions_dir>\home\localconfig\atg\dynamo\server\DistributorServer.properties
file.
In addition to installing the DistributorServer
on your HTTP server machine(s), you need to configure the /atg/campaign/communication/ContentDistributorPool
components on the ATG Outreach server and each ATG Outreach Production/Staging instance. See the Configuring the ATG Outreach Environment chapter for details.
Note: The ATG Adaptive Scenario Engine includes its own DistributorServer
under <ATG9dir>\Distributor
. If you’re running an HTTP server and ATG Outreach on the same machine, you can run this DistributorServer
component instead of the standalone version (described above). Add the Distributor
module to the runAssembler
command that you use to start your application server so that it is included in the assembled EAR file. Then add it as an initial service by editing the <ATG9dir>\home\localconfig\atg\dynamo\Initial.properties
file:
initialServices+=/atg/dynamo/server/DistributorServer