Replication

• publish (activate) content from author to dispatcher
• Explicitly flush content from the Dispatcher cache
• Return user input (for example, form input) from the publish environment to the author environment (under control of the author environment) - reverse replication which is not always used

Replicating from Author to Publish

Replication, to a publish instance or dispatcher, takes place in several steps:

• the author requests that certain content be published (activated); this can be initiated by a manual request, or by automatic triggers which have been preconfigured.
• the request is passed to the appropriate default replication agent; an environment can have several default agents which will always be selected for such actions.
• the replication agent "packages" the content and places it in the replication queue
• the content is lifted from the queue and transported to the publish environment using the configured protocol; usually this is HTTP.
• a servlet in the publish environment receives the request and publishes the received content; the default servlet is http://localhost:4503/bin/receive .
• multiple author and publish environments can be configured.

Batch Replication

The batch replication does not replicate individual pages or assets, but waits for the fist threshold of the two, based on time or size, to be triggered. It then packs all replication items into a package, which is then replicated as one single file to the publisher. The publisher will unpack all the items, save them and report back to the author.

Documentation

• Replication
• Troubleshooting Replication