Posts Tagged ‘Adobe’


Like every product, AEM might also have some bugs/performance issues. These are solved by supplying hot fixes (simply like patches in Oracle WebCenter Sites) to the specific AEM version.

The Hot fixes for AEM 6.1 can be found at the below url

https://helpx.adobe.com/experience-manager/kb/aem61-available-hotfixes.html

How to apply these AEM Hot Fixes?

The hot fixes can be applied either through the package share or manually.

AEM 6.1 introduced the concept of deploying the Hotfixes manually. We will now see how to deploy the downloaded hotfixes manually.

1.   Login to the server

2.   Stop the instance.

3.   Create a new directory called install in <path-to-installation>/crx-quickstart/ directory.

4.   Copy the downloaded hot fixes to the install directory.

5.   Restart the instance.

6.   Go to the package manager and check whether all the hot-fixes are installed properly or not.

Advertisements

Below are the different logs which are generated by AEM. These logs can be found at <path-to-installation>/crx-quickstart/logs folder.

  1. access.log   –      All access requests to AEM WCM and the repository are registered here.
  2. audit.log      –      Moderation actions are registered here.
  3. error.log       –      Error messages (of varying levels of severity) are registered here.
  4. request.log  –      Each access request is registered here together with the response.
  5. stdout.log    –      Holds logging messages indicating events during startup.

In an AEM Instance,  error.log is the file which logs all the error messages. To change this file’s location and name, search for the below bundles in the AEM Web Console, and open them.

  1. Apache Sling Logging Configuration
  2. Apache Sling Logging Logger Configuration

AEM Web Console can be opened at  http:// :/system/console/configMgr

The log file location and name can be changed under the LOG FILE text field.


In Information Technology, no software stands and plays alone for a long time. There are number of new technologies coming these days, getting popular, well noticed by customers / clients. But after some time, a day comes where these technologies are dominated by other technologies.

Coming to the Content Management Systems, there are many niche players like EMC, Oracle, etc. And Adobe joined them by redesigning Communique 4. It has released ADOBE DAY CQ5, basing on Communiqué 4. ADOBE DAY CQ5 is a new WEB EXPERIENCE MANAGEMENT SYSTEM.

What is Adobe Experience Manager?

Adobe Experience Manager helps you organize and manage the delivery of creative assets and other content across your digital marketing channels, including web, mobile, email, communities, and video.

Similar to Oracle WebCenter Sites,  ADOBE DAY CQ5 helps us to build compelling content-centric applications that combine Web Content Management, Workflow Management, Digital Asset Management and Collaboration sites.

Prerequisites for development within CQ

For the developers,  to build WEM site using the Day CQ5, following technologies are required:

  • HTML
  • CSS
  • JavaScript
  • JSP

The documentation for Adobe Day CQ5 can be accessed from http://dev.day.com/docs/en.html

I’m now starting with Day CQ5, and will be updating topics on Day CQ5 from now on.

ADOBE DAY CQ5