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 ishttp://localhost:4503/bin/receive.
multiple author and publish environments can be configured.
REPLICATION (AUTHOR TO PUBLISH)
Navigate to the support page on the author environment. http://localhost:4502/content/geometrixx/en/support.html
Edit the page to add some new text.
Activate Pageto publish the changes.
Open the support page on the publish environment: http://localhost:4503/content/geometrixx/en/support.html
You can now see the changes that you entered on author.
This replication is actioned from the author environment by the:
Default Agent (publish) This agent replicates content to the default publish instance. Details of this (configuration and logs) can be accessed from the Tools console of the author environment; or: http://localhost:4502/etc/replication/agents.author/publish.html.
REPLICATION AGENTS - OUT OF THE BOX
The following agents are available in a standard AEM installation:
Reverse Replication Used for replicating from publish to author. Reverse replication is not used for Communities features, such as forums, blogs, and comments. It is effectively disabled as the outbox is not enabled. Use of reverse replication would require custom configuration.
Static Agent This is an "Agent that stores a static representation of a node into the filesystem.". For example with the default settings, content pages and dam assets are stored under/tmp, either as HTML or the appropriate asset format. See theSettingsandRulestabs for the configuration. This was requested so that when the page is requested directly from the application server the content can be seen. This is a specialized agent and (probably) will not be required for most instances.