Automatically publish content from Master-Publish instance in Asset Offloading | Community
Skip to main content
rsl_lucky
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

Adobe Employee
September 11, 2019

Hello Sailaxman,

What do you mean by replication not happening? Are you using the normal author-publish replication queue? Do you see any errors in logs? Can the replication agents replicate the other content like pages etc? Did you try to manually replicate the assets?

Regards,

Vishu

Adobe Employee
September 11, 2019

@sailaxmanr83887909 Are you expecting for assets to automatically get published?  This is not by design.  Assets will publish when a user clicks to Activate it or activate a page with assets in it. 

rsl_lucky
rsl_luckyAuthor
September 11, 2019

Hi Vish.dhaliwal,

Yes manual replication is happening if we trigger it on Master instance, but it should happen automatically as soon slave instance replication completes to Master.

Thanks

Sailaxman

rsl_lucky
rsl_luckyAuthor
September 11, 2019

@yanirac19051392

So you mean to say we cant publish content automatically only way to do is Manually ?

Adobe Employee
September 11, 2019

In this case, it has to be manual. There are different replication triggers though. Please review [1] and check which one fits your use case.

You may also create a custom workflow to replicate these assets as soon as they upload back in master.

[1] Replication

Adobe Employee
September 11, 2019

Can you explain the business usecase/need?  Why is there a need to automatically publish all assets that are uploaded to the instance (master)?

Asset offloading is designed to unburden the master instance from heavy asset ingestion.  It's doesn't come into play with activation of assets. 

Adobe Employee
September 11, 2019

I agree with Yanira's response, This is not by design.  Assets will publish when a user clicks to Activate it or activate a page with assets in it.

You need to think of author and publish as two entities and offloading in only implemented on the author with no trigger/process predefined to automatically replicate the content to publish.

That said, You can create a launcher from workflows that triggers a Replicate asset workflow on modification of "dam:Asset" on the master instance and that will replicate any assets that are being modified on the master to publish instance. You can read more about launchers at [1]

[1] Starting Workflows

Adobe Employee
September 11, 2019

You can run a test with a modified OOTB DAM UPDATE ASSET OFFLOADING, you can simply add Activate Page/Asset step:

rsl_lucky
rsl_luckyAuthor
September 12, 2019

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

rsl_lucky
rsl_luckyAuthor
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.