Normally the dispatcher flush agents are configured on the
author under the section ‘Agents on Publish’ and activated for it to be
replicated to publish instances where it takes effect. This works when the same
configuration is needed on all the publish instances as any node that gets replicated would get replicated to all publishers for which a replication agent is configured
For cases where the configuration of dispatcher flush
agent(s) needed on each publish instance differs we can use one of the below
approach
Direct configuration on Publish instances
Make the configuration directly on Publish instance. This
involves logging in to each publish instance with admin credentials and
creating the required dispatcher flush agent configuration for that instance.
Avoid using this approach for higher environments. Could be a useful approach
for development and test environment to get the configuration done quickly.
Using CURL scripts to create dispatcher flush agents
Use CURL to create dispatcher flush agents needed on each
publish instance. This is the most widely used approach and the CURL scripts
can be maintained for recreating instances in case of server rebuilds.
Using packages to install the configuration on publish instances
Configure all the dispatcher flush agents needed on Author.
Create packages – one for each publish instance with flush agents needed for
that instance. Install the created package on the corresponding publish
instance.
No comments:
Post a Comment