Deactivate assets | Adobe Higher Education
Skip to main content
K
Kevin_GTa
Level 5
March 26, 2019

Deactivate assets

  • March 26, 2019
  • 1 の返信
  • 5115 ビュー

Hi All,

We are running AEM 6.0. We only set up Author-to-Pub and Pub-to-Web agents, but there is no invalidate flush agent. The current setups are not good for assets such as images and PDF's. The problem is that whenever an asset is deactivated or modified, we cannot see the asset having the correspondent action, either deleted or updated. I figured that we are checking the "On Receive" option on the "Triggers" tab, see attached.

I like to have that option checked, but concern about the subsequent impact on the dispatcher server. Any idea of the dis/advantages checking that? Or do I have another way to the deactivation more responsive without a significant impact on the dispatcher compared to the current settings?

Thanks!

    このトピックへの返信は締め切られました。

    1 の返信

    Gaurav-Behl
    Gaurav-Behl
    Level 10
    March 26, 2019

    What is "Web" in this case? Is it AEM publish server or Apache server?  Do you have the following setup:

    Author > Pub1 > Pub2  > Web server (Dispatcher)

    Is "On Receive" turned on on Pub1? Do you mean to day that you don't have any dispatcher flush agent/invalidation agent configured on either servers?

    K
    Kevin_GTa作成者
    Level 5
    March 26, 2019

    "Web" is the dispatcher. We do not have the setup as you laid out. We have the following setups:

    Author:

        Agents on author:

            Author-to-publisher

        Agents on publisher:

            No active agents

    Publisher:

        Agents on author:

            No active agents

        Agents on publisher:

            Publisher-to-dispatcher

    The attached image is the "Publisher-to-dispatcher" on the publisher. Yes, we don't have any flush agent on either server.

    Gaurav-Behl
    Gaurav-Behl
    Level 10
    March 26, 2019

    I suspect that "Publisher-to-dispatcher" agent is your dispatcher flush agent.

    What is the "Serialization Type" of "Settings" tab of "Publisher-to-dispatcher" agent?

    Do you see HTTP headers configured in Extended tab?

    In any case, the purpose of turning-on "On Receive" is that this agent (publisher-to-dispatcher) would trigger automatically as soon as it receives any replication event from author server

    Similar explanation goes for "On-modify". When a content author would modify anything on this publish server (which doesn't make sense because of lack of authoring capabilities), this agent would trigger.

    "On-Modify" makes sense on author and not on publish servers unless there is a specific use case. On author, it would trigger replication event as soon as the modified content is saved.

    I'm not aware of the purpose of keeping a "replication agent" on publish server instead of "flush/invalidation" agent. To me, it doesn't make sense. Probably, you have a TTL based cache flush setup rather than an event based cache flush setup.

      契約条件Accessibility statement

      Loading footer...