While creating templates for Touch-Optimized GUI

In AEM 6.0, most of the functionalities are accessible through Touch-Optimized UI. When you create a template using Sightly or JSP, before extending the page component, the Classic UI displays the content in a page created based on the template. Of course, the page is displayed without the sidekick and other functionalities.


This behavior, however, changes with Touch-Optimized UI. To appear page’s content in Touch-Optimized GUI, the page’s template should extend the page component using sling:ResourceSuperType . You can extend a Sightly or JSP page component to a template. It’s irrespective of the templating language (Sightly \ JSP).

Slightly, some Sightly

AEM 6.0 introduces Sightly – a new templating language. Sightly replaces JSP as the most preferred templating language for AEM. Sightly helps you to separate your design from your code. The intention is to bring more front-developers to AEM component development. By providing a demarcation between the design and the development departments, Adobe expects to reduce the go-to-market time for AEM development projects.

For more information on Sightly, visit Adobe documentation.

Sightly can used in three ways:

  • Pure HTML
  • HTML + server-side JavaScript
  • HTML + Java

In the following example, Sightly is used as pure HTML to display the name of a page:

Code in template

<h1>Page Title</h1>

The same example can be rewritten in Sighlty and JavaScript. This example doesn’t represent the best practice. However, it shows how to demarcate the logic using JavaScript:

Code in template

<div class="component-name" data-sly-use.component="component.js">
<h1>Page Title</h1>


        return {
        title: currentPage.getTitle()

The next example shows how the same logic is implemented using Sightly + Java combination:

Code in template

<div class="component-name" data-sly-use.component="Component">
<h1>Page Title</h1>


package apps.your.directory.structure;
import com.adobe.cq.sightly.WCMUse;
import com.day.cq.wcm.api.Page;
public class Component extends WCMUse
private String CurrentPageTitle;

   public void activate() throws Exception 
   final Page currentPage = getCurrentPage();

   public String getCurrentPageTitle()
   return CurrentPageTitle;

Integrating Search&Promote with AEM

Search&Promote allows you to create an index of your site by crawling your site in a regular interval. It helps you to implement powerful search functionalities in your website. In AEM 5.6.1, there are some out-of-the-box Search&Promote components that make integration easy. Some of these components use hardcoded values that you may need to change in the component’s JSP page. You need to work with a Search&Promote consultant and understand the xml format, specifically the fieldnames, in which the results are provided.  Use the fieldnames in the JSP pages.

For example, if the fieldname for product description in the xml file is “desc,” rewrite the method in the Search Results component’s JSP page as:

Note: Search&Promote components are available at libs/cq/searchpromote/components.

Watch out AEM 6.0 release that is scheduled to be in May end. It has some cool integration workflows to avoid these workarounds.

Using the Target component in AEM 5.6.1

The Target component in AEM 5.6.1 allows you to create an MBox in your page and then create various experiences. It works like the Targeting feature provided with the context menu. You would have noticed that after you drag and drop the Target component to a page, the component becomes invisible.

To make the Target component visible in the page, bring up Client Context and associate it with a Campaign.


Accessing previous versions of a page using CRXDE Lite

You can access the previous version of a page using CRXDE Lite:

  1. Login to CRXDE Lite.
  2. Move to the page for which you created versions.
    It would be present in the /content folder.
  3. Examine the jcr:content node of the page.
  4. Click the value of the jcr:versionHistory property.
    It will take you to the node that has all the versions you created.

Issues while importing a product catalog from Hybris to AEM

I faced some issues while importing a product catalog from Hybris to AEM with the 5.6.100 packages. The following were the error messages:

  • Cannot server request to /libs/commerce/products
  • Cannot serve request to ProductDataServelet

Recently, Adobe has released packages of version 5.6.200. I didn’t face the issue with these packages. If you face these issues, use the latest packages.

Developing a multifield widget for a CQ component

I had to develop a multifield widget for a CQ component. My requirement was to present the What’s New documents for a product’s releases. There could be many releases in an year. These need to be captured in a table row. A product release is associated with a specific product name and a What’s New URL.

To cut the story short, let me present you with some screenshots. The following is the dialog box where a user enters the release information:


In this case, in an year, the product had two releases. One in March and the second one in Dec. The details are displayed as follows in the publish instance:


March being the third month, it’s displayed in the third column, and for the obvious reason, Dec is displayed in the 12th column. It displays the release name as a hyperlink to the What’s New doc.

Follow these steps to develop this widget:

  1. Install the Custom Multifield Widget. Follow Adobe’s instructions on how to do it. We will develop the component based on the Custom Multifield Widget that you will install as
    a part of the instructions.
  2. Copy the extjstraining/clientlib folder to your app/yourCompany folder, where you want to develop your component.
  3. Create a component in yourCoumpany folder.
  4. Now, expand to the extjstraining/components/customwidgets folder.
  5. Expand the multifield dialog box.
  6. Copy the multi node to your component’s dialog.
  7. Change the xtype of the node that you copied in the fieldConfig as follows:
  8. In yourCompany folder, open the clientlib/js/CustomWidget.js file.
    1. Add one more text field as follows:
      //new textfield start
      this.allowText = new CQ.Ext.form.TextField({


      listeners: {

      change: {


      fn: this.updateHidden




    2. Set value for the new text field as follows:
      // overriding CQ.form.CompositeField#setValue

      setValue: function(value) {

      var parts = value.split(“/”);






    3. Change the xtype as follows:
      // register xtype
      CQ.Ext.reg(‘ejstcustom1′, Ejst.CustomWidget);
  9. In yourCompany folder, open the clientlib/js/exercises.js file. Upadate the provider options for the drop-down list as follows:
  10. Now, you can create the component’s JSP to format the values entered by the author:
    PropertyIterator propertyIterator= currentNode.getProperties();



    Property currentProperty=propertyIterator.nextProperty();

    String currentValue=””;
    if(currentProperty!=null &&
    currentProperty.getName()!=null &&




    Value[] values=currentProperty.getValues();
    String[] months={“Jan”,”Feb”,”March”,”April”,”May”,”June”,”July”,”Aug”,”Sep”,”Oct”,”Nov”,”Dec”};
    int[] table=new int[12];
    String[] version=new String[12];
    int k=0;

    for(Value value:values)
    String[] splitValue=currentValue.split(“/”);

    for (int i=k; i<months.length; i++)
    if (splitValue[0].equals(months[i]))



    for (int m=0; m<table.length; m++)
    if (table[m] == 1)
    out.write (“<td>”+version[m]+”</td>”);
    out.write(“<td>”+” “+”</td>”);




  11. Test the component.

Starting Hybris after installing with AEM

After you install the Hybris packages, if the Hybris server is not getting automatically restarted after an AEM restart, search for hybrisserver.bat. This file helps you to restart the Hybris server.

Accessing CQ pages using a dispatcher configuration

When you set up a dispatcher for Adobe CQ using Apache web server, the request to the specified port should serve CQ pages. Also, verify whether the pages are saved in the cache folder. If the requests are served, but the pages are not cached, most probably you are accessing the pages that contain authentication info in the header.

By default, dispatcher doesn’t cache requests with  authentication info. (This can be enabled by the allowAuthorized property in the dispatcher.any file.) Ensure that you cleared the cookies before accessing the pages.

FTPing files to Scene 7 server

In Scene 7, if the file size exceeds certain limit, you need to upload the file using FTP. You need to create an ftp account and then put your files to the ftp server. Later the files need to be uploaded from the ftp server to Scene 7.

The first step is to enable your ftp account:

  1. After logging in, go to Setup > Media Portal.
  2. Select FTP Accounts.
  3. Select the user ID and create a password and click Save.
  4. Note down the FTP Accounts Username created. This is your user ID for the ftp login.


Find out the ftp server address.

  1. Check with your admin.
  2. Or, go to Setup > Application Setup > General Settings.
  3. See SCENE7 FTP account. Server details are displayed there.


  1. Now ftp to the server with the user id and password you created.
  2. Put your files there.

When you upload the file from ftp server to Scene 7, you can’t really select the files. So put only those files that you want to push to a specific folder.

  1. Log in Scene 7, and upload the files from ftp server.
  2. Select the folder > Upload.
  3. Select Via FTP from the top bar. This option is enabled only after you enable the ftp account.
  4. Select the folder displayed and click Submit Upload.