Automatically publish content from Master-Publish instance in Asset Offloading | Community
Skip to main content
rsl_lucky
rsl_lucky
New Participant
September 11, 2019
Solved

Automatically publish content from Master-Publish instance in Asset Offloading

  • September 11, 2019
  • 18 replies
  • 13263 views

Hi All,

We have implemented Asset offloading approach i.e Author instance (Master). Now Slave instance replicate back processed content to Master instance as per Offloading approach.

Now we want to replicate the content that got reflected in Master instance to Publisher.

Observed that replication is not happening on Master instance to Publisher after Slave instance completes its replication back to Master.

Could you any provide any points on this.

Thanks

Sailaxman

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by leoberliant

It's not a perfect approach, however, it works on my test env. Not sure, what is your real business case; you might need to revisit and improve the launch configuration.

Event Type : Modified,

Node Type : dam:Assets

Path : /content/dam(/.*)

Workflow : Your custom WF

Exclude LIst: cr:lastModified,dc:modified,jcr:lastModifiedBy,imageMap,event-user-data:changedByWorkflowProcess,dam:extracted,simsearchVersion,jcr:lastModified,dc:modified,dc:format,jcr:lastModifiedBy,imageMap,dam:scene7(.*),event-user-data:changedByWorkflowProcess

Run Mode(s) : Author

18 replies

rsl_lucky
rsl_luckyAuthor
New Participant
September 17, 2019

Thanks Berliant..it works & assets are getting published with renditions.

    L
    leoberliantAccepted solution
    Employee
    September 16, 2019

    It's not a perfect approach, however, it works on my test env. Not sure, what is your real business case; you might need to revisit and improve the launch configuration.

    Event Type : Modified,

    Node Type : dam:Assets

    Path : /content/dam(/.*)

    Workflow : Your custom WF

    Exclude LIst: cr:lastModified,dc:modified,jcr:lastModifiedBy,imageMap,event-user-data:changedByWorkflowProcess,dam:extracted,simsearchVersion,jcr:lastModified,dc:modified,dc:format,jcr:lastModifiedBy,imageMap,dam:scene7(.*),event-user-data:changedByWorkflowProcess

    Run Mode(s) : Author

      rsl_lucky
      rsl_luckyAuthor
      New Participant
      September 16, 2019

      Yes offloading is working perfectly fine with all metadata & renditions to Master but replication from Master to Publisher is happening with out Renditions.

      Could you share details to be mentioned in launcher in each param that would be available on Master.

        L
        leoberliant
        Employee
        September 16, 2019

        Do you mean that offloading (the worker instance) does not send rendition and metadata back to the master? Despite the Publishing process, does offloading topology work?

          rsl_lucky
          rsl_luckyAuthor
          New Participant
          September 16, 2019

          Hi, yes metadata node is created after changing event type to 'Modified',but observed that workflow instances are created & getting triggered continuously at the back-end & publishing it to instance. Also thumbnails are not generated in renditions folder(only original is available).

            L
            leoberliant
            Employee
            September 13, 2019

            AEM offloading workflow creates "jcr:content/metadata" node. The node is empty up until a worker extracts and sends metadata to the master.

            Can you test with "Modified event" and set Run Modes to Author only.

              rsl_lucky
              rsl_luckyAuthor
              New Participant
              September 13, 2019

              Yes created a custom workflow launcher and did. It is getting published to Publisher but with no metadata node on asset.

              Event Type : Created, Node Type : nt:unstructured, Path : /content/dam(/.*)/jcr:content/metadata,

              Run Mode(s) : Author & Publish, Conditions : dc:format!=,

              Workflow : Scheduled Page/Asset Activation

              Tried few diff scenarios as well but not working as expected. Any pointers here.

                L
                leoberliant
                Employee
                September 13, 2019

                You can try to create an additional workflow launcher and set a trigger to when metadata for an asset is created.

                  rsl_lucky
                  rsl_luckyAuthor
                  New Participant
                  September 13, 2019

                  @ Berliant,

                  Tried update as suggested DAM Update Asset Offloading workflow, but things didn't work out as expected.

                  Asset is getting replicated to Publisher as soon as it uploads to Master instance i.e before creation of renditions.

                  Throwing exceptions like "com.day.cq.dam.core.impl.AssetImpl getMetadataValue: metadata node does not exist for asset",

                  "SlingRequestProcessorImpl service: Uncaught SlingException java.lang.NullPointerException: null" etc.

                  Could any one suggest any other ways for publishing content to publisher as soon as Offloading of renditions on Master is complete.

                    rsl_lucky
                    rsl_luckyAuthor
                    New Participant
                    September 12, 2019

                    Thanks all for the inputs provided will try above approaches suggested.

                      Show more replies
                      Terms & ConditionsAccessibility statement

                      Loading footer...