AEM/CQ5

How to find top issues encountered by AEM server

Statement : Easiest way to check if any issues encountered by AEM, If you are not going through the Log file on daily basis, monitor an inbox console of AEM touch UI at least once in a day.

Environment : AEM 6.3 GA

Solution :

Go to this path : http://localhost:4502/aem/inbox
Look at the High priority items and fix it.
The highlighted items might be security related or functionality related or imp log file error related.
That's it!.

How to tail log files of AEM in windows OS using Jtail.jar file

Statement - Jtail.jar file to tail logs while AEM is running in Windows OS similar to tail in Linux OS
Environment - AEM 6.3 GA

Solution :

Go to this path : D:aem\crx-quickstart\opt\helpers
Search -->for Jtail.jar file --> select and right click on this file to open with J-->ava platform SE binary
A console will appear -->click on file -->new-->browse to path of log file location and select any log file for the tail.

Hit some pages URL in browser and you can see the logs are getting generated in the console and this will be helpful for troubleshooting any issues.

That's it!

How to to find Maven dependencies of package/classes in AEM through Felix console

Statement - Find the Maven dependencies
Environment - AEM 6.3 GA

Solution :

Go to the Felix console URL: http://localhost:4502/system/console/depfinder
Enter the class or package name which show error stating not resolved in the OSGI console of bundle tab where your bundle shows in stop status.
This is a tool which provides the maven dependencies to be added in the POM.XML file based on the key in of class/package name.
in this example org.apache.sling.commons.scheduler has dependency issue follow the below steps to generate maven dependencies.
Click on FIND to find out the Maven dependencies.
add above Maven dependencies to pom.xml file and rebuild the project and deploy the code base to AEM.
Similarly if you want know the maven dependencies use this tool to generate.
That's it!