HI,
We are in process to migrate to Cloud Manager. We are using AEM 6.5.5.
Question: Can someone point me to a good documentation which shows step by step how to install content packages through our Code base (i guess by using ui.content..?).
So far we were installing content package zips manually through Package manager.
Also need to know how we can tell the build to install the content package in Auth and not in Publisher...
Note: To clarify my requirement, I have latest contents in Stage and I want to install them in Prod using Maven. So when Prod build/install process will run, it needs to install Stage contents specified by certain path/package name in Stage into Prod...Is that possible..?
Solved! Go to Solution.
Views
Replies
Total Likes
hi @Mayukh007 - hope you have followed this link - https://docs.adobe.com/content/help/en/experience-manager-cloud-service/moving/home.html
You need to go deep into those links on the specific areas you are looking for guidance, it has everything.
If you are facing any specific issue, please call out, happy to share thoughts.
hi @Mayukh007 - hope you have followed this link - https://docs.adobe.com/content/help/en/experience-manager-cloud-service/moving/home.html
You need to go deep into those links on the specific areas you are looking for guidance, it has everything.
If you are facing any specific issue, please call out, happy to share thoughts.
You can embed packages inside package in POM like
AEM project pom uses profiles which can be used to deploy package only in Author.
Thank you for your suggestion Arun.
I have some doubts here:
1. In the pom.xml file "<artifactId>core.wcm.components.core</artifactId>" this artifact id is name of the content package zip file..?
2.If I have content sitting in Stage env and I want to zip it up and install in Prod, how will this step work...?
Views
Replies
Total Likes
Hi Arun, I tried to add this plugin in my pom:
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<version>0.0.24</version>
<extensions>true</extensions>
<configuration>
<failOnError>true</failOnError>
<userId>${crx.username}</userId>
<password>${crx.password}</password>
<subPackages>
<subPackage>
<groupId>my_packages</groupId>
<artifactId>manulife.aem.content</artifactId>
<filter>true</filter>
</subPackage>
</subPackages>
</configuration>
</plugin>
I am getting error:
[WARNING] No matching artifacts for Sub Packages: groupId=my_packages,artifactId=manulife.aem.content,filter=true,excludeTransitive=false
Can you please help me out here.
My target is to build the latest content in Stage and then install that in Prod assuming it will create a zip file with latest stage content with right filter and push it to artifactory. During Prod deployment it will pull it from artifactory and deploy those stage content in Prod.
I tried here by creating a content package in my local under group "my_packages" and the package name is "manulife.aem.content" with version 1.0. I am assuming it will rebuild the already uploaded package and then generate a zip file with content package which I can use in higher env..?
Views
Replies
Total Likes
All your troubles can be found on Adobe's documentation,
How to Build AEM Projects using Apache Maven : https://helpx.adobe.com/uk/experience-manager/6-3/sites/developing/using/ht-projects-maven.html
I hope this helps,
Brian.
Thank you Brian for the suggestion. So as per the doc, I need to add content paths in filter.xml under ui.content module like this:
<?xml version="1.0" encoding="UTF-8"?> <workspaceFilter version="1.0"> <filter root="/apps/myproject"/> <filter root="/content/myproject/sample-content"/> </workspaceFilter>
But if I have content sitting in Stage env and I want to zip it up and install in Prod, how will this step work...? This will build content package in Stage taking the contents I want using filters provided. But how it will deploy those content packages into Prod when I run Prod build..?
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
First of when we create a project out of any archetype it comes with auto upload of ui.content package. Where inital pages gets uploaded on AEM after the build.
But as we don’t want to build and deploy the pages every time, so remove the deployment of content pages using the filters inside ui.content.
So I guess in your current architecture your ui.content is deploying only conf and other items only. So along with that place the downloaded content inside the ui.content and add it into the filters. In this case along with conf folder content will also be deployed as part of every build.
But if you are totally not building and uploading the ui.content then you should go and update the POM.xml
Refer a sample project for the configuration https://github.com/adobe/aem-project-archetype
Thanks,
Nikhil
Views
Likes
Replies
Views
Likes
Replies