New Features Adobe Experience Manager(AEM) 6.2

New Features Adobe Experience Manager(AEM) 6.2


VERSION: 6.2, Released on APRIL 21, 2016
Product URL: https://docs.adobe.com/docs/en/aem/6-2.html

Brief:
AEM 6.2 comes with many changes and improvements including forms. AEM 6.2 Forms includes several new features and enhancements that further streamline and enhance creation, publishing, and working with forms, documents, and correspondences.

User Interface Improvements
AEM 6.2 ships with a new user interface that sets up the main modules as a drop down navigation

list. The interface still leverages Coral UI and for the most part, the detailed sections of each module are untouched. A new search box has come up on the top right corner to search also quick access to other solutions in the Marketing Cloud. The product navigation has moved from the side rail to an overlay.

AEM Mobile Apps
The Adobe Digital Publishing Suite and Adobe Phone Gap have been bridged to provide a seamless experience to customers to manage their mobile apps across multiple operating devices. A new dashboard is provided where in we can see all details of mobile applications. The key feature of this new tool allows customers to deploy native applications and leverage the power of Phone Gap to provide native APIs along with the power of DPS to create, manage and publish the content, once synched.

AEM Smart Tags
AEM 6.2 released a Beta functionality called 'Smart Tags' which allows for the system to automatically tag and discover digital assets. It can also be setup to bulk tag assets that are already in the system.

Search  Enhancements
Search enables navigating within the product and search all areas of the product. Prior to 6.2, Adobe

had invested in search capabilities with integrations to SOLR as well as a faceted search user interface in 6.0 and 6.1, but the comprehensive search capabilities provided in 6.2 will surely be most preferred by customers.

Content Fragments
Content creators can now use the power of assets and its referencing capabilities across multiple devices along with variations. The new content fragment section allows content fragments metadata to be created the same way how an asset metadata schema can be created using the Schema Editor.

Template Editor
AEM 6.2 provides set of built in templates. This helps authors to create templates immediately with a set of templates and components developed already. The core features allow content authors to insert components along with initial sets of content to create a structure for it to be leveraged to create pages under Sites. This also provides a user interface for content authors to leverage the Design view of the editor to preview what the template would like on other devices such as ipad and mobile

Asset insights
Assets Insights is a new and interesting feature in AEM 6.2 that allows assets usage to be tracked

across various channels such as websites, email campaigns, mobile devices, etc. Adobe Analytics enables the tracking functionality. The statistics that can be captured are items such as what assets have been downloaded, clicked on, conversion rates and other digital marketing trends, which helps the atuthor to add meta data more effectively.

Areas, Targeting
AEM 6.2 introduces Areas which leverages the power of AEM Multi site Manager. Effectively targeted content and personalization is possible through this. Areas provides a way to manage these personalized content in the same way content is managed for sites across multiple languages and locales. More localized targeting, which allows content authors globally to set up campaigns and also break inheritance if required as in normal hierarchy at specific page levels for local content.

--------------Similar Posts:----------

Integrate AEM With DOJO

Integrate AngularJS in AEM

Personalization in AEM

Replication Agents

New AEM Features

-------------------------------------------

Sightly/ HTL Tips

 Sightly Tips

For SIghtly Tutorial Visit our help page : http://aem-cq-tutorials.blogspot.com/p/htl-home.html

? Sightly comparing a string value
Say we have a string 'heroType' and having some values. We need to test its value to 'AL', we can use below code to compare it.

<div data-sly-test="${style.getHeroType == 'AL' }">Hello</div>

? Check a list's(formatList) size using below code
<sly data-sly-test.emptysize ="${subcategoryUse.formatList.size > 0 }" />

--------------Similar Posts:----------

Integrate AEM With DOJO

Integrate AngularJS in AEM

Personalization in AEM

Replication Agents

New AEM Features

-------------------------------------------

? Check a list item count is greater than zero in sightly
Java List : shopList; Use class : subcategoryUse

<sly data-sly-list.listItem="${subcategoryUse.shopList}">
 <sly data-sly-test.count="${listItemList.index > 0}">
 //Do your task here if count is more than zero
 </sly>

? Passing a value to Use  class from sightly:
 <sly    data-sly-use.integerUse="${'com.....IntegerUse' @ text=item}">

 And in Use class IntegerUse.java read it as,
 String text = get("text", String.class);

 ? Iterating over a list
 Java List: firstList

 <sly data-sly-list="${quantumUse.firstList}">
 //Use list item here using '{item}'
 </sly>

 ? When a Java list contains an object holding multiple values, each value can be retrieved as below
 <a x-cq-linkchecker="valid" href="${listItem.getUrl}.html"><img src="${listItem.getitemImage}" class="image-responsive"></a>
 or
 <p>${listItem.getpriceInteger} <span>${listItem.getpriceDecimal}</span>

 ? Test multiple items in sightly

 <sly data-sly-test="${listItem.selectLogo && listItem.displayLogo}">
 OR
<div data-sly-test="${listItem.selectCategoryBadge.length > 0 && listItem.displayCategoryBadge}"

Integrate DOJO developed website with AEM

Integrate DOJO developed website with AEM

This is basically a migration of one technology to AEM. There are cases when clients wants to replace the backend technology only. AEM can be integrated with any Java script libraries. Here we are showcasing how feasible it is to integrate DOJO developed site in AEM. Adobe Experience Manager implementation requires a technical team that understands the unique development challenges a custom CMS poses. 

Feasibility?

 Dojo is a front end development technique Toolkit by the Dojo Foundation featuring DHTML and AJAX functions. Dojo work well with all of the front end techniques like HTML5, JQuery etc. to use with any backend system/applications. Dojo development requires skilled developers who are good at DOJO and dtl language.

 Dojo can be integrated with AEM through an interaction Layer. AEM exposes many of the methods to integrate with any third-party applications. This enables applications to work seamlessly when integrated. A JSON layer is used to integrate AEM with dojo in this case. 

 Can we migrate a project which runs on DOJO to AEM?

 The asnwer is yes. We can create a package of DOJO front end files (Including .html) to upload into AEM. This can be created either using package manager or through maven build.

 Once this package is ready, it can be directly uploaded into to AEM Package maneger and install. This package may have differnt page setup and locations compared to a normal AEM Project.

 Any Drawbacks?

 Yes, the template, page concept is not involved in this and we are just reusing the existing normal front end html files with DOJO. We can have an authoring environment for authoring the components but the preview is not available since we will have to develop a new page in addition to DOJO Migrated page. Also there may be some Javascript path remapping issues, which we may have to fix once deployed.

 How does the DOJO normal files talk to AEM Backend? 

 We can have a JSON layer which talks between the DOJO and AEM. The authoring environment can invoke the osgi layer to create custom JSON files which DOJO is expecting.

 Integration Details

AEM is used as backend service . OSGi (Open Service Gateway Initiative) is the Java framework which runs on AEM and generates the JSON Layer. The generated JSON layer is used to interact with dojo application. 

 Authoring, JSON Generation.

The data is authored by an author and this gets saved in AEM. User friendly authoring environment allows users to drag and drop the component and immediately start authoring. 

--------------Similar Posts:----------

Integrate AEM With DOJO

Integrate AngularJS in AEM

Personalization in AEM

Replication Agents

New AEM Features

-------------------------------------------

JSON Generation:

Once the component is saved, OSGI runs in AEM helps to generate a JSON. A Java service used to generate OSGI Bundles needs to be created to generate JSON from the authored component. 

Any format of JSON can be generated as per dojo requirement here. Dojo needs to configure above data path of JSON while interacting and generating a page component.

DOJO Layer

We need to move all DOJO Libraries to AEM. Dojo related components and templates to be moved to respective folder of AEM.

Once all settings are done, while reloading the page, UI will be loaded with the respective component by its templates from dojo but content from AEM.

 AEM Project Maintenance w.r.t dojo

New versions of AEM are available so often. Upgrades can be done without much challenges since the front end is separated from backend.

Some of the issues we faced during migration 

Cannot use AEM image rendering concept, since DOJO uses own images and paths.

File name conflicts. Space is there in DOJO

AEM Caching is not used

Deployments are complex

Previews are not possible

Site management becomes complex

Integrate AEM With DOJO

Using DOJO as AEM Front end

There are some cases where AEM needs to be integrated with DOJO.

What is DOJO
DOJO is a Javascript framework used to develop interactive, responsive websites, and mainly used as a UI tool.

DOJO can be integrated with AEM through an interaction Layer. AEM exposes many of the methods to integrate with any third-party applications. This enables applications to work seamlessly when integrated. A JSON layer is used to integrate AEM with DOJO in this analysis.

DOJO with AEM - Arch view
The architectural diagram is shown below.

OSGi (Open Service Gateway Initiative) is the Java framework which runs on AEM and generates the JSON Layer. The generated JSON layer is used to interact with DOJO application.

Once the component is saved, OSGI runs in AEM which helps to generate a JSON. A Java service used to generate OSGI Bundles needs to be created to generate JSON from the authored component.
Any format of JSON can be generated as per DOJO requirement here. A sample JSON response is given below.

http://localhost:4502/content/home/_jcr_content/parsys/myothercomponent.data.json

Steps to integrate DOJO with AEM:

We need to move all DOJO Libraries to AEM.
DOJO related components and templates to be moved to respective folder of AEM.
The page level items are split into templates and components. Same DOJO structure needs to be replicated in AEM, where in page will be divided into header, body, footer components. Content section can hold any levels of other components. The page structure in AEM is shown below.


Any impact on AEM Project Maintenance with respect to DOJO
New versions of AEM are available so often. Upgrades can be done without much challenges since the front end is separated from backend.


--------------Similar Posts:----------

Integrate AEM With DOJO

Integrate AngularJS in AEM

Personalization in AEM

Replication Agents

New AEM Features

-------------------------------------------

CQ/AEM node operations- add,delete,Recursively fetching the nodes

Delete a node

//Below code delete 'textRenderer' node if present under /content/projectname

private static final String TEXT_RENDERER_NODE_URL = "/content/projectname";
rendererNode = currentSession.getNode(TEXT_RENDERER_NODE_URL);
                                   
                                   
                                      if(rendererNode.hasNode("textRenderer"))
                                      {
                                          Node delNode = currentSession.getNode(TEXT_RENDERER_NODE_URL + "/textRenderer");
                                          delNode.remove();  
                                          currentSession.save();
                                      }
                               
Ensure to save the session after any node modification.

--------------Similar Posts:----------

Create File in AEM

Integrate AngularJS in AEM

Personalization in AEM

Replication Agents

New AEM Features

-------------------------------------------

Add a node
//Below code adds 'textRenderer' node of type 'cq:Page' under /content/projectname

private static final String TEXT_RENDERER_NODE_URL = "/content/projectname";

Node fileNode = rendererNode.addNode("textRenderer", "cq:Page");
fileNode.addMixin("rep:AccessControllable");
currentSession.save();
                                   
                                   
                                    =======================================
                                   
Recursively fetching the nodes under CQ node

Below code recursively iterates over a root node and populate the node attributes.

// Node- the root node to be iterated
// Session - current session
 public static void visitRecursively(Node node, Session currentSession) {
                       
                                       
                    try{
                           
                       
                    // get all child nodes
                          NodeIterator list = node.getNodes();
                                
                          while(list.hasNext())   {
                          
                  // get child node
                            
                          Node childNode = list.nextNode();
                          // Verify child node for cqPage type
                          if((childNode.hasProperty("jcr:primaryType")) && (childNode.getProperty("jcr:primaryType").getValue().getString()).equals("cq:Page") ){
                           
                            Node jcrNode = childNode.getNode("jcr:content");
                             
                            // Iterate some of the page properties
                            String articleTitle="";String jcrDesc="";String jcrTitle="";String keywords="";
                            if(jcrNode.hasProperty("articleTitle")){
                               
                                articleTitle = jcrNode.getProperty("articleTitle").getString();
                                log.info("articleTitle--->"+articleTitle);
                            }
                            if(jcrNode.hasProperty("jcr:description")){
                               
                                jcrDesc = jcrNode.getProperty("jcr:description").getString();
                                log.info("jcr:description--->"+jcrDesc);
                            }
                            if(jcrNode.hasProperty("jcr:title")){
                               
                                jcrTitle = jcrNode.getProperty("jcr:title").getString();
                                log.info("jcr:title--->"+jcrTitle);
                            }
                            if(jcrNode.hasProperty("keywords")){
                               
                                keywords = jcrNode.getProperty("keywords").getString();
                                log.info("keywords--->"+keywords);
                            }
                            
                            String pagePropertiesString = "articleTitle--->"+articleTitle + "jcr:description--->"+jcrDesc+"jcr:title--->"+jcrTitle + "keywords--->"+keywords ;
                       
                       
                          log.info("Page Properties :---> Node "+ childNode.getName()+ "Properties : " + pagePropertiesString );
                         
                       
                          }
                            
                          visitRecursively(childNode,currentSession);
                          }
                          }
                          catch (RepositoryException rpe){
                              log.info("Exception in recursive listing:");
                          }
                                
                }

Creating file in CQ/AEM

Create a new file under jcr node

Some cases we need to create a text or xml file under jcr nodes in CQ. In below code we are creating a text file with current jcr node name under specified location

-------Similar Posts---------------
Mapping of requests in AEM
Interact With AEM
Run Modes
AEM
Apache Sling in AEM
-------------------------------------

private static final String TEXT_RENDERER_NODE_URL = "/content/projectname";
 try {

                                // writing to file in temp location
                                FileOutputStream fop = null;
                                File file = null;
                                File testFile = null;
                                StreamResult result = new StreamResult(new StringWriter());
                                try {

                                    Path filePath = Files.createTempFile("Test" , ".txt");
                                    file = filePath.toFile();
                                    fop = new FileOutputStream(file);
                                    // get the content in bytes
                                   
                                    byte[] contentInBytes = pagePropertiesString.getBytes();
                                    fop.write(contentInBytes);
                                    fop.flush();
                                    fop.close();
                                    testFile = file;
                                } catch (IOException ioExc) {
                                    log.error(
                                            "TestFile :: IOException: ",
                                            ioExc);
                                } finally {
                                    try {
                                        if (fop != null) {
                                            fop.close();
                                        }
                                    } catch (IOException ioExc) {
                                        log.error(
                                                "TestFile :: IOException while closing output stream :",
                                                ioExc);
                                    }
                                }
                                }catch (Exception exc) {
                                    log.error("TestFile Creation Failed :: Exception: " , exc);
                                }
                               
                               
                         //Create file under jcr node
                       
                          try{
                              FileInputStream fileInputStream = new FileInputStream(testFile);
                           
                            ValueFactory valueFactory = currentSession.getValueFactory();            
                            Binary contentValue;
                            contentValue = valueFactory.createBinary(fileInputStream);
                            Node textRendererNode = currentSession.getNode(TEXT_RENDERER_NODE_URL + "/textRenderer");
                            //We are creating a new text file based on current jcr node name after converting to lower case, '' to _
                            Node fileNode = textRendererNode.addNode(jcrTitle.replace(' ', '-').toLowerCase()+".txt", "nt:file");
                            Node actualNode = (childNode.getParent()).addNode(jcrTitle+".txt", "nt:file");
                            actualNode.addMixin("mix:referenceable");
                            fileNode.addMixin("mix:referenceable");
                            Node resNode = fileNode.addNode("jcr:content", "nt:resource");
                            resNode.setProperty("jcr:data", contentValue);
                            Calendar lastModified = Calendar.getInstance();
                            lastModified.setTimeInMillis(lastModified.getTimeInMillis());
                            resNode.setProperty("jcr:lastModified", lastModified);
                            currentSession.save();
                          }catch(RepositoryException rpe){
                            log.error("Exception in Text Renderer :"+rpe.getMessage());
                        } catch (FileNotFoundException e) {
                            // TODO Auto-generated catch block
                            e.printStackTrace();
                        }  catch (Exception exc) {
                            // TODO Auto-generated catch block
                            exc.printStackTrace();
                        }

AEM/CQ Node change observer

Node Change Observer Code:
Some times we may have to observe changes in nodes.

Below code helps to observe any change in jcr nodes(Changes can be addition, deletion or modification). This helps us to observe and node for modification and process some tasks.

/** Class which observes an event at /jcr:system implementation
    *
    *
    */
  
    public class NodeObserver implements EventListener{
      
    private Logger log = LoggerFactory.getLogger(getClass());
      
        @Reference
        private SlingRepository repository;
      
        private Session session;
        private ObservationManager observationManager;
             
      
        protected void activate(ComponentContext context)  throws Exception {
            session = repository.loginAdministrative(null);
           // Listen for changes to our orders
            if (repository.getDescriptor(Repository.OPTION_OBSERVATION_SUPPORTED).equals("true")) {
                observationManager = session.getWorkspace().getObservationManager();
                //We are putting types of nodes to be observed under below string array: sample in next line
               // final String[] types = { "nt:unstructured","rep:system","rep:versionStorage","nt:frozenNode" };
               //I am just observing nt:unstructured, bcz that is my requirement
                final String[] types = { "nt:unstructured" };
                //I am observing changes under /jcr:system nodes
                final String path = "/jcr:system";
                observationManager.addEventListener(this, Event.NODE_ADDED, path, true, null, types, false);
                log.error("Observing node changes to {} nodes under {}", Arrays.asList(types), path);
            }
          
        }

        protected void deactivate(ComponentContext componentContext) throws RepositoryException {
  
            if (observationManager != null) {
                observationManager.removeEventListener(this);
            }
            if (session != null) {
                session.logout();
                session = null;
  
            }
        }
      

        public void onEvent(EventIterator itr) {
                      
            try {
                while (itr.hasNext()){
                  Node versionNode = null;
                
                  String eventPath = (itr.nextEvent()).getPath();
                  log.info("something has been added : {}", eventPath);
                
                  Node jcrContentNode = session.getNode(eventPath);
                
                  Node jcrParentNode =jcrContentNode.getParent();
                  //process nodes after checking conditions
                  if(eventPath.endsWith("jcr:content") && (null!= jcrParentNode) ){
                                  
                
                  String metaDataNodePath = eventPath + "/metadata";
                  Node metaDataNode = session.getNode(metaDataNodePath);
                  log.info("metaDataNode Created" + metaDataNode);
                
                  }
                //  break;

                }
               } catch(RepositoryException e){
               log.error("Error while processing events",e);
              }
          
        }
-------Similar Posts---------------
Mapping of requests in AEM
Interact With AEM
Run Modes
AEM
Apache Sling in AEM
-------------------------------------