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

AEM Publish - Newbie - Publish question

  • July 24, 2018
  • 13 replies
  • 3012 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
New Participant
July 25, 2018

We are not in an early phase of the project so a switch now to AEM 6.4 is not an immediate option. Of course we want to migrate it also to 6.4 but we want to do with without the time pressure that we currently have for the implementation.

I had a look to the logs of the publish instance, and I see following error messages when the header of the page is not displayed:

24.07.2018 20:04:07.759 *INFO* [10.240.10.8 [1532451847749] GET /content/serviceplan/en/test-page.html HTTP/1.1] com.day.cq.wcm.foundation.TemplatedContainer page has no template assigned

24.07.2018 20:04:07.759 *WARN* [10.240.10.8 [1532451847749] GET /content/serviceplan/en/test-page.html HTTP/1.1] com.day.cq.wcm.foundation.TemplatedContainer template has no structure support

Regarding deployment, could you please advice for better options than the maven deploy? Could you eventually point me to some documentation for best practices related to deployment for test and live environments?

smacdonald2008
smacdonald2008
New Participant
July 24, 2018

WHen you manually publish your pages - are you seeing issues?

joerghoh
joerghoh
Employee
July 24, 2018

If you are at an early stage in your project, I suggest to you to switch to AEM 6.4; that is not likely to fix your problem, but help you to be more up-to-date.

As the next step you should really think about your deployment pipeline; this maven plugin it good for local development, but I don't consider it a good choice to deploy a larger amount of machines (how do you determine errors during deployment? The error handling of the plugin is quite poor, and it also doesn't check the results of the installation, like validating that bundles are up etc).

And finally regarding your problem: Recompiling all scripts is rarely a solution, but only a workaround. I would expect that there are messages in the log indicating a problem, either during deployment time or while requesting a page.

Jörg

Terms & ConditionsAccessibility statement

Loading footer...