Invalidating cache at path restkit
Depending on the level of detail required you can also set the Log Level to For Dispatcher Flush agents, the URI property is used only if you use path-based virtualhost entries to differentiate between farms, you use this field to target the farm to invalidate.
For example, farm #1 has a virtual host of Setting such permissions will not affect users replicating content (e.g. The replication framework does not use the "user session" of the current user to access replication agents when replicating pages.
The listeners poll the outboxes to collect any data entered and then distribute it as necessary.
This ensures that the author environment controls all traffic.
Do not use the "Test Connection" link for the Reverse Replication Outbox on a publish instance.
If a replication test is performed for an Outbox queue, any items that are older than the test replication will be re-processed with every reverse replication.
Other than issuing a followup command -DIS DB( ) SPACENAM( ) USE LOCKS on each of the affected tablespaces/indexes, is there another way to determine if the Runstats did it's job ...
I am trying to DROP/CREATE views that have 10 tables joined and I was wondering if there was a simpler way to determine id all the TS/IX were not inuse by a dynamic cached SQL even after Runstats gives a RC=0.
For Dispatcher Flush agents, the URI property is used only if you use path-based virtualhost entries to differentiate between farms, you use this field to target the farm to invalidate.
User data (users, user groups, and user profiles) are not replicated between author and publish instances.
For multiple publish instances, user data is Sling distributed when User Synchronization is enabled.
When a dispatcher handles HTTP requests for author or publish instances, the HTTP request from the replication agent must include the PATH header.
In addition to the following procedure, you must add the PATH header to the dispatcher list of client headers. Reverse replication is used to get user content generated on a publish instance back to an author instance.This is commonly used for features such as surveys and registration forms.