AEM Publish - Newbie - Publish question | Community
Skip to main content
sergiu_carabet
sergiu_carabet
July 24, 2018
Solved

AEM Publish - Newbie - Publish question

  • July 24, 2018
  • 13 replies
  • 3023 views

Hi all,

Our company is developing the first AEM project with the AEM 6.3 version of Adobe Experience Manager. We created our project based on the Maven archetype version 12.

We encounter a problem on our test machine. We deploy the project on both author and publish instances via a Jenkins job (that just calls maven mvn -PautoInstallPackage clean install (on author) and mvn -PautoInstallPackagePublish clean install on the publish instance.

In the author instance everything looks fine, content can be configured, visualised in preview mode correctly.

On the publish instance the header component which is part of an editable template disappears, and content is not correctly displayed.

Is there an additional step, like clearing some caches or similar that we have to execute after a deploy, so that the content on the publish instance is displayed correctly?

What we found till now after a small research is just to recompile the jsps on the publish instance:

http://<HOSTNAME>:4503/system/console/slingjsp?reset and there 'Recompile all JSPs' option is used.

This solves the problem in the browser where it is executed, but it needs a login in the backend of AEM and it does not fix it for every browser.

So this is not a viable solution. This problem currently complicates a lot the testing of the project on many physical devices, (as we are still in the development phase of the project).

Could you please advise what can we do in order to visualise correctly the content in all browsers / devices also on the publish instance?

Thank you,

Sergiu

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 joerghoh

I assume that you messed up the permissions on your publish instance. By default anonymous should be able to see some more paths.

Jörg

13 replies

Show previous replies
sergiu_carabet
sergiu_carabetAuthor
August 1, 2018

hi Jörg,

Thank you for the help and for pointing me in the correct direction. I found the problem and it is what you have mentioned related to having the right permissions. The group everyone was not having the read permissions for the editable templates, and this is the reason why the page looked good as soon as we logged in the backend.

Now this works properly also for anonymous users. Thanks a lot for your help.

One last thing related to your comment:

Would you be so kind and point me to some documentation where I can read more about the best practices related to deployment. Or could you sketch a recommendation of how to change the deployment pipeline to be a better one that the current maven based one?

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
August 2, 2018

Hi,

glad that you were able to find the issue on your own.

Regarding the deployment: you should establish a way, which gives you better control over the deployment process. Starting everything via maven is a nice way, but requires to have a lot of different pom files for the different stages. Also you don't have a retry capability in case something goes wrong in the first place (maybe due to bad timing, some seconds later the system would have settled and the request would have been successful). I was told that there are some plugins for Jenkins would allow you to deploy to AEM more smoothly.

sergiu_carabet
sergiu_carabetAuthor
August 3, 2018

Thank you. I will have a look at this AEM Jenkins plugin.

Terms & ConditionsAccessibility statement

Loading footer...