Need to automate content package creation and scheduling it weekly | Community
Skip to main content
Level 4
September 21, 2016
Solved

Need to automate content package creation and scheduling it weekly

  • September 21, 2016
  • 13 replies
  • 7347 views

Hi,

Is there a way we can automate content package creation on any environment and also schedule this creation?

Any pointers would be helpful.

 

We also open to the idea of creating repository backup but that should be automated and scheduled.

 

Regards,

Shallu Rohilla

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 smacdonald2008

Look at using Package Manager API and write a custom service. Fire off the service each week.  Look at this Javadoc. https://docs.adobe.com/docs/en/cq/5-5/javadoc/com/day/jcr/vault/packaging/PackageManager.html. Hope this helps.

13 replies

Adobe Employee
October 2, 2016

kautuksahni wrote...

Feike Visser wrote...

You can also look at crx2oak to push down content from your higher environments, also these command are 'just' os commands.

Thanks a lot Feike. This adds to my kitty.

Adding Documentation link here :- https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html

There are a couple of points to bear in mind when using crx2oak for this use case. First, both instances have to be shutdown in order to run the content migration and it is meant to be used when you have both AEM instances on the same box. Secondly, If you try and run it across a network, it could be very slow.

As this is 5.6, you can't use it to transfer from crx to crx, only cry to oak or oak to oak.

Regards,

Opkar

Adobe Employee
October 2, 2016

.

kautuk_sahni
Community Manager
Community Manager
October 3, 2016

Opkar Gill wrote...

kautuksahni wrote...

Feike Visser wrote...

You can also look at crx2oak to push down content from your higher environments, also these command are 'just' os commands.

Thanks a lot Feike. This adds to my kitty.

Adding Documentation link here :- https://docs.adobe.com/docs/en/aem/6-2/deploy/upgrade/using-crx2oak.html

There are a couple of points to bear in mind when using crx2oak for this use case. First, both instances have to be shutdown in order to run the content migration and it is meant to be used when you have both AEM instances on the same box. Secondly, If you try and run it across a network, it could be very slow.

As this is 5.6, you can't use it to transfer from crx to crx, only cry to oak or oak to oak.

Regards,

Opkar

 

Thanks a lot Opkar.

Everyday i am learning awesome things from Experts.

Thanks a lot. 

Kautuk Sahni