AEM Archives – Argil DX

Posts

AEM-DTM-Target Integration. Simplified! – Part1

Introduction:
Let’s start with the introduction of three gems of Adobe Experience Cloud crown:

AEM – Adobe Experience Manager(AEM) is a web content management system with a lot of powerful features to manage, organise and deliver the content with best in class experience. AEM came to Adobe with the acquisition of Day Software in 2010, earlier it was known as Day CQ (Communique). For this article, we are using AEM 6.3 version.
DTM – Dynamic Tag Management(DTM) is a tag management tool which offers tools to integrate Adobe Experience Cloud Solutions as well as solutions like Google Analytics etc.DTM used to be known as ‘Satellite’ before Adobe had acquired it in 2013.
Target – Adobe Target is a personalization solution of Adobe Experience Cloud Suite, which delivers the personalisation of content based on different type rules. Target came to Adobe with the acquisition of Omniture in 2009. In this article, we are going to demonstrate the Target VEC capabilities.

Architecture:
AEM can be integrated with Target directly without using DTM. However, it’s recommended to use the DTM in between due to listed benefits:

Efficiency –DTM allows you to optimise the loading time of multiple tools and marketing tags.
Reduce Cost – Minimise the development cost as once Data Layer is in place multiple solution can leverage the same.
Flexibility – DTMallows you to quickly test and optimise tags without being bound by release cycles.
Multiple Sites – Using DTM you can manage multiple sites from the single console.

AEM is usually connected with DTM using AEM Cloud Services and Target is connected to DTM using Experience Cloud configuration. Here is the relevant diagram:

Request Flow:
How a request flows from AEM to Target via DTM:

AEM starts rendering a site page.
Site has a DTM script attached along with Data Layer. DTM script is associated with a relevant property. Data Layer discussed below.
DTM Property has Target added to it, which raises a request to Target and share required data.
Target pushes its response back to AEM instance using mbox js. Note: Now mbox.js has a newer and updated alternative which is known as at.js
AEM page got Target response which gets rendered on the page.

Data Layer:
As you might have noticed in request flow that AEM site has got the DTM Script and Data Layer associated. Data layer is a W3C standard to store values in javascript object. Data layer is created at AEM and consumed by DTM to get the required data from AEM instance and push to any solution like Analytics, Target etc. We are going to create a sample data layer below in DTM Rules section.

DTM Setup:
To get the access of DTM, one has to raise the request with Adobe Client Care with proper information. Once the access is granted, go to https://dtm.adobe.com and login with the credentials provisioned by Client Care.

To start with DTM, create a new property with the URL of the website. Thereafter add the required tools in the property like Adobe Analytics or Adobe Target. In AEM configuration, we are going to use same DTM Property in order to integrate the AEM with Analytics, Target, etc.

For this article we are going to add Adobe Target, for this we need Client Code which will be provided by the Client Care or alternatively you can try adding using Experience Cloud membership.

DTM Property

Adding Tool in DTM Property

Adding Target as a Tool in DTM Property

DTM Rules:
In above steps you have created a new DTM property, added Target as a tool in the same property. Now you need to know how to play with data, DTM uses data layer to get the data from AEM instance. For example, using Target you need to render homepage of website based on browser, location, devices etc or you can also get the user specific details like age, gender, interests etc. Hence you need to get all such information from AEM in data layer. For example, here the data layer:

   var dataLayer = {}
   dataLayer.page = {
        pageInfo: {
            pageName: document.title,
            url: document.location
        }
   }

var dataLayer = {}

dataLayer.page = {

pageInfo: {

pageName: document.title,

url: document.location

}

Once the data-layer is all set, fetch the values from data layer and set it in DTM data elements. We use these data elements in different types of rules. DTM has got three type of rules:
1. Event Based Rule – Rules executed when visitor interacts with on-page elements.
2. Page Load Rule – Rules executed when visitor loads the page.
3. Direct Call Rule – Rules executed when you want to tell DTM to do something specifically.

DTM Rules

Creating a data element using data layer is quite straight forward. You can see the below screenshot, here we have created a new data element Page Title which is mapped with pageName field of data layer created above.

Data Elements

DTM Workflow:
Every property in DTM follows a standard workflow. Workflow has got three steps:

Creation of property and rules.
Approve the newly added and modified rules.
Publish the property to make the changes live.

AEM-DTM Integration:
There are two ways to integrate DTM with AEM:

Using Cloud Services
Embed JS

Using Cloud Services:

Using AEM admin console, go to Tools > Deployment > Cloud Services. Find ‘Dynamic Tag Management’ and click on ‘Configure now’. Provide a Title and Name of the configuration keeping Parent Configuration field intact. Enter the details as below:

Property	Description
API Token	The value of the API Token property of your Dynamic Tag Management user account. AEM uses this property to authenticate with Dynamic Tag Management.
Company	The company with which your login ID is associated.
Property	The name of the Web Property that you created for managing the tags for your AEM site.
Include Production Code on Author	Select this option to cause the AEM author and publish instances to use the production version of the Dynamic Tag Management libraries. When this option is not selected, the Staging Settings apply to the author instance, and the Production Settings apply to the publish instance.

There is an option to self-host the DTM libraries which means AEM will host the DTM libraries if this option is checked, if we want to use the libraries from the cloud then we should uncheck this option. Here we are using later one.

Embed JS:

Go to the DTM Console using https://dtm.adobe.com and click on the relevant property.
Go to Embed tab, copy the Header and Footer staging script, go to the AEM author instance and copy the script in header and footer of the website respectively. Similarly, copy the header and footer production script and put in the AEM publish instance.

Let’s say you have integrated DTM with AEM using one of the above-mentioned method, assign the DTM config to the root of your site using AEM Sites console.

DTM-AEM Connection Test:
Now you need to test whether DTM script is getting loaded with your website. In browser, try to open any page of your website where you have assigned the DTM config and open browser console. If “_satellite” object exists then it means DTM script is getting loaded. You can also try retrieving the data elements that you have created in DTM using “_satellite.dataElements”. If you are able to find all the details, you are good to go.

If _satellite object doesn’t exist, it means page doesn’t have the DTM header/footer script. You can view the source of the page to confirm the same.

Satellite Object

Satellite Data Elements

DTM Debugging Tools:
In DTM we play with different types of scenarios and scripts, hence we might need to check if the scripts are working fine and order they are getting executed.
There are couple browser plugins are available which proved to be quite for debugging.

Launch Switch:
It enables the logging in console and as well as we can test the changes using staging script, before making the changes live.

There are two button available on the plugin console. Tweaking them will do the following:
Debug: It enables the logging of the rules, you can also add the logs using _satellite.notify(“info”).
Staging: It will enable the changes you have made in property which you have not published. This is used for testing the changes before making them live.

Download URL for Chrome: https://chrome.google.com/webstore/detail/launch-and-dtm-switch/nlgdemkdapolikbjimjajpmonpbpmipk

Tagtician:
It shows the detailed information about all the DTM Rules.
Download URL Chrome: https://chrome.google.com/webstore/detail/tagtician-for-adobe-dtm/hiaoiehpkillodoeillmodjcadmfmcbg

Reference:
Adobe DTM Documentation: https://marketing.adobe.com/resources/help/en_US/dtm/

This is the first part 1 of “AEM-DTM-Target Integration. Simplified!” where you have learned how to setup DTM, create DTM property and data elements, integrate DTM with AEM and debug DTM. In Part 2, you will learn how to create different types of rules in DTM, use these rules to share the information to Target, Target activities, Target audience and how to use Target VEC (Visual Enhanced Composer) along with the Target debugging tweaks.

Working with Boutique Versus Large Implementers

September 12, 2018/0 Comments/in News /by Blake Kendrick

All companies looking for AEM implementation services face the decision between working with boutique versus large companies. The decision can have major impacts on the type of service you will receive and how your company will be handled and valued. There are advantages and disadvantages to working with both, and this makes the decision even more of a challenge.

In order to begin making a decision, you must evaluate how important these AEM implementation services are for your firm and your long-term goals. You must step into the shoes of both boutique and larger system integration organizations to understand how they view your company within their entire portfolio. Larger firms may have more experience because of their more expansive network and resources, but that comes at a substantial cost for clients–splitting these resources and sharing time.

First and foremost, when selecting what type of business to work with, consider how much work and attention you will get out of each dollar you spend. Larger enterprises have at least double and often many more clients than boutique firms. This means that everything the larger firm has to offer will have to be divided amongst their whole pipeline. With larger implementation firms, that means a greater divisor. Businesses looking for AEM implementation want dedicated attention, so whenever there is a problem, it can be resolved as quickly and efficiently as possible. If attention is the function of time divided by number of clients, then it is clear that smaller firms are the best choice if you require innovative and dedicated solutions.

Secondly, it is essential to consider the economic factor: how much a firm will value the amount you are paying them resulting in a higher level of prioritization. The money you pay a business to handle your services will always be worth more to the smaller firm than the larger one. You want your deal to be gold for the company managing your services.

Furthermore, as a smaller firm, we are truly invested in our client’s success and interpersonal relationships. People we work with mean more to us than simply being a source of revenue or a mechanism to hit profitability targets; we care about your business as much as you do, and we will strive to perform our best for mutual triumph.

In order for a system integrator to see you as a key client and a massive opportunity, your deal size has to be massive compared to the other clients. This would mean that the money you are giving the business matters for that business to succeed. With larger firms, you deal size is a small fraction of their portfolio and likely equal to their other clients meaning that they don’t give your project much value.

Larger companies have a variety of clients. This means they have to optimize systems and strategies to be implemented across the board for each client they have. Rather than fitting the system for the client, these firms fit clients into the systems. Even if their clients don’t necessarily fit in those “system boxes”, a larger firm will find a way to make their clients fit the firm’s process, not the other way around.

The other cost of having larger firms try to fit you into their systems is that these large businesses will be stubborn and refuse to adjust their strategies resulting in a lack of creativity. With your project, you desire the AEM implementer’s work to be adapted to fit your needs. Your case can be extremely specialized, and the result you get may not be optimal for the strategies you need. Creativity is the key to obtaining the best results.

Another point to consider is that if you choose to work with a large business, the majority of the people working on your case are junior and lower-level partners. With boutique firms, you have direct access to its top developers. The founder has oversight on all accounts, and higher, senior-level persons do the bulk of the work to ensure quality service. This means less chances for mistakes and/or miscommunication. When you call into these boutique firms, you have a higher likelihood of speaking with a senior representative or even founding partner than you do at a larger firm.

Also, boutique firms work to ensure that they hire and keep the best workers because they can’t run the risk of sunk costs from a worker not producing the needed results. For this, you know that everyone staffed on your project has gone through extensive interview and training processes to make sure they are the best possible candidates to be working at those firms.

Larger firms have their perks. With more experience comes more exposure to multiple industries and integrations, but an increased risk of inexperienced developers working on your project. Infrastructure and systems have been tested on a number of clients, and they have been optimized several times. With more experience comes more knowledge to be used in creating the best services. Larger companies have the ability to see with other clients which systems work and don’t allowing them to optimize as they have an abundance of clients to churn through.

Both sides have their advantages. Working with larger firms for AEM implementation grants you access to more experience because of the firms more expansive network and resources. You also feel confident that the systems have been tested and optimized therefore less likelihood of failure. With small firms you have greater emphasis to detail and dedication to quality service, especially from senior staff members. Since smaller firms have fewer clients, you are valued more highly and receive more customized attention. Ultimately, you must consider how important these implementation services are for your firm and your long term goals and make a decision from there.

TRIGGERING A WORKFLOW USING EVENT LISTENERS IN AEM

August 20, 2018/0 Comments/in AEM, AEM Technical /by Anirudh Garg

AEM Version: 6.2
Target Audience: AEM Developers

Introduction

In AEM 6.2 Workflows, we can trigger a workflow when a DAM Asset is created, modified, or deleted within a given path. In this article, we will explore triggering workflows from our code based on events in the JCR.

Suppose you have a workflow that creates custom renditions of assets in addition to the default AEM renditions, when the asset is under “/content/dam/ProjectName/images/”. You would have set up two launchers for triggering this workflow: one with event type as “Node Create” and one with “Node Modified”. We can also achieve the same functionality through our code, without touching the GUI.

Requirement

When assets are moved into a certain folder structure in DAM, trigger a workflow that creates a 100px X 100px thumbnail of our image.

Fig 1: Before Moving the asset, no custom thumbnail. Fig 2: Desired result after moving the asset, the new thumbnail.

Analysis

The intuitive thought is that when an asset is moved, a new node is created in the new location and the old one is deleted. However, experience shows that AEM does not create a new node in the destination folder on Node Move. We know this because the ‘jcr:Created’ property does not change. AEM does not even change the last modified date.

Fig 3: Creation Timestamp Before Moving the Asset. Fig 4: Creation Timestamp is the same after moving

Fig 5: Modification Timestamp Before Moving the Asset. Fig 6: Modification Timestamp is the same after moving.

What if we copy the asset?

On copying the asset, a new version of the same is created. This triggers the Node Creation launcher.

Fig. 7: No versions before copying the asset. Fig. 8: Version created after copy-pasting the asset.

Approach

Event Listeners

AEM supports observation, which enables us to receive notifications of persistent changes to the workspace. A persisted change to the workspace is represented by a set of one or more events. Each event reports a single simple change to the structure of the persistent workspace in terms of an item added, changed, moved or removed. There are thus 7 possible events at the JCR level, viz:

Node Added
Node Moved
Node Modified
Node Removed
Property Added
Property Removed
Property Changed

We connect with the observation mechanism by registering an event listener with the workspace. An event listener is a class implementing the EventListener interface, that responds to the stream of events to which it has been subscribed. An event listener is added to a workspace with:

void ObservationManager. 
addEventListener(EventListener listener, 
int eventTypes, 
String absPath,
boolean isDeep, 
String[] uuid, 
String[] nodeTypeName, 
boolean noLocal)

void ObservationManager.

addEventListener(EventListener listener,

int eventTypes,

String absPath,

boolean isDeep,

String[] uuid,

String[] nodeTypeName,

boolean noLocal)

(A detailed explanation of each parameter is given with the code example in the package as well as the at the end of this article) As defined by the EventListener interface, listener must provide an implementation of the onEvent method:

void EventListener.onEvent(EventIterator events)

1	void EventListener.onEvent(EventIterator events)

When an event occurs that falls within the scope of the listener, the repository calls the onEvent method invoking our logic which processes/responds to the event. In our case, we will register an event listener to listen for “Node Moved” events under “/content/dam/images” so that when an asset is moved to that folder, our workflow can be triggered.

Implementation

When the component is activated, the activate(…) method is called. It contains a call to ObservationManager.addEventListener(…) for registering the event listener. The deactivate(…) method contains logic for deregistering the event listener, and is triggered when the bundle is being stopped.

When the relevant event occurs, the onEvent(…) method is called, which contains logic for processing the event. In our case, we trigger a workflow.

The following is the relevant code from ThumbnailNodeMovedListener.java:

protected void activate(ComponentContext ctx) { 

try { 
. 
. 
. 
// Building the parameters for adding the event listener 


// Whether the subfolders of the given path should also be watched 

boolean isDeep = true; 

// Only events whose associated node has one of the UUIDs in this list will be 

// received. If this parameter is null then no UUID-related restriction is 

// placed on events received. 

String[] uuid = null; 

// Only events whose associated node has one of the node types (or a subtype of 

// one of the node types) in this list will be received. If this parameter is 

// null then no node type-related restriction is placed on events received. 

String[] nodeTypeName = null; 
 

// If noLocal is true, then events generated by the session through which the 

// listener was registered are ignored. Otherwise, they are not ignored. 

boolean noLocal = true; 

// Registering the event listener 

observationManager.addEventListener(this, Event.NODE_MOVED, ASSET_UPDATE_PATH, isDeep, uuid, nodeTypeName, 

noLocal); 

} 

} 

 

public void onEvent(EventIterator itr) { 

while (itr.hasNext()) { 

Event currentEvent = itr.nextEvent(); 

try { 
. 
. 
.  

// Create a workflow session 

WorkflowSession wfSession = workflowService.getWorkflowSession(localSession); 

// Get the workflow model 

WorkflowModel wfModel = wfSession.getModel(THUMBNAIL_WORKFLOW_PATH); 


// Get the Workflow data. The first parameter in the newWorkflowData method is 

// the payloadType. Just a fancy name to let it know what type of workflow it is 

// working with. 

WorkflowData wfData = wfSession.newWorkflowData(JCR_PATH, currentEvent.getPath()+ORIGINAL_RENDITION_RELATIVE_PATH); 

// Start the Workflow. 

wfSession.startWorkflow(wfModel, wfData); 

} 
. 
. 
.

protected void activate(ComponentContext ctx) {

try {

// Building the parameters for adding the event listener

// Whether the subfolders of the given path should also be watched

boolean isDeep = true;

// Only events whose associated node has one of the UUIDs in this list will be

// received. If this parameter is null then no UUID-related restriction is

// placed on events received.

String[] uuid = null;

// Only events whose associated node has one of the node types (or a subtype of

// one of the node types) in this list will be received. If this parameter is

// null then no node type-related restriction is placed on events received.

String[] nodeTypeName = null;

// If noLocal is true, then events generated by the session through which the

// listener was registered are ignored. Otherwise, they are not ignored.

boolean noLocal = true;

// Registering the event listener

observationManager.addEventListener(this, Event.NODE_MOVED, ASSET_UPDATE_PATH, isDeep, uuid, nodeTypeName,

noLocal);

}

public void onEvent(EventIterator itr) {

while (itr.hasNext()) {

Event currentEvent = itr.nextEvent();

try {

// Create a workflow session

WorkflowSession wfSession = workflowService.getWorkflowSession(localSession);

// Get the workflow model

WorkflowModel wfModel = wfSession.getModel(THUMBNAIL_WORKFLOW_PATH);

// Get the Workflow data. The first parameter in the newWorkflowData method is

// the payloadType. Just a fancy name to let it know what type of workflow it is

// working with.

WorkflowData wfData = wfSession.newWorkflowData(JCR_PATH, currentEvent.getPath()+ORIGINAL_RENDITION_RELATIVE_PATH);

// Start the Workflow.

wfSession.startWorkflow(wfModel, wfData);

}

Download this code (including the workflow):

Build it using

mvn clean install -PautoInstallPackage

1	mvn clean install -PautoInstallPackage

N.B: Creating a workflow is not part of this tutorial, and therefore a ready workflow has been provided in the code package. However, if you want to learn to create workflows, here is an excellent resource: ->

/workflow-in-aem/

References

Adobe Consulting Services. (2018, March 20). acs-aem-samples/SampleJcrEventListener.java at master · Adobe-Consulting-Services/acs-aem-samples. Retrieved from Github: https://github.com/Adobe-Consulting-Services/acs-aem-samples/blob/master/bundle/src/main/java/com/adobe/acs/samples/events/impl/SampleJcrEventListener.java

Day Software AG. (2018, March 20). JCR 2.0: 12 Observation (Content Repository for Java Technology API v2.0). Retrieved from Adobe Docs: https://docs.adobe.com/docs/en/spec/jcr/2.0/12_Observation.html

How to Change Data Type (Typecast) in AEM, Use @TypeHint

August 3, 2018/0 Comments/in AEM, AEM Technical /by Arpit Rathi

Problem Statement:

How to convert a variable from one data type to another data type in AEM.

For a use case where a number field is used in dialog and further data will be utilized in Sightly (HTL) for numeric comparison operations. Problem can come up as data will be stored in String format and comparison can only be made on same data type elements.

Solution:

@TypeHint: It is used to forcefully define the data type of a property. It can be used as following:

Scenario:

I have a number field in my dialog with name ‘sponsoredPosition’, by default it’s value is stored in String format and I wanted it to be stored in Long format instead of String.

Steps:

In the component add a node, parallel to the ‘sponsoredPosition’ node (The one of which data type needs to be changed) of the type nt:unstructured.

In the new node add following properties:
ignoreData{Boolean} = true
value{String} = Long
Name{String} [email protected]
sling:resourceType{String} = granite/ui/components/foundation/form/hidden.

Here,

(a) ignoreData, as the name suggests tells value of this field should not be stored.

(b) In value field you must define the data type in which you want your data to be stored.

(c) In Name field add ‘@TypeHint’ suffix to the property name of original node whose value was stored in string(by default) .

(d) Resource type hidden is used for hiding it in dialog.

<sponsoredPosition
  jcr:primaryType="nt:unstructured"
  sling:resourceType="granite/ui/components/foundation/form/numberfield"
  fieldLabel="Sponsored Content Position"
  max="{Long}3"
  min="{Long}2"
  value="3"
  name="./sponsoredPosition"/>
  <sponsoredPositionTypeHint
    jcr:primaryType="nt:unstructured"
    sling:resourceType="granite/ui/components/foundation/form/hidden"
    ignoreData="{Boolean}true"
    name="./sponsoredPosition@TypeHint"
    value="Long"/>

<sponsoredPosition

jcr:primaryType="nt:unstructured"

sling:resourceType="granite/ui/components/foundation/form/numberfield"

fieldLabel="Sponsored Content Position"

max="{Long}3"

min="{Long}2"

value="3"

name="./sponsoredPosition"/>

<sponsoredPositionTypeHint

jcr:primaryType="nt:unstructured"

sling:resourceType="granite/ui/components/foundation/form/hidden"

ignoreData="{Boolean}true"

name="./[email protected]"

value="Long"/>

BLOG SUMMARY & BUSINESS GOAL

This blog is intended to provide technical AEM users a solution to an asked question and tactical training on the topic: How to Typecast in AEM.

Conclusion

Adding @TypeHint solved the issue, now value is being stored in Long format instead of String.

Interested in more training and support for your organisation using AEM CMS? Request a consultation to discuss Argil DX managed services.

Crypto Support in AEM

March 16, 2018/1 Comment/in AEM Technical /by Pankaj Bansal

Recently, we came across a business requirement where we had to save API keys (secured date) in OSGI service. One of the recommendations based on Adobe Health Check is to encrypt data (API keys) to store them in JCR more securely. The same can be achieved using Crypto Support.

The Crypto Support Bundle provides a service which encrypts/decrypts binary or String data in AEM. On exploring further, it seems to be nailing the issue of encryption and decryption in just few minutes. Crypto support is necessary to store the password in a salted or hashed form in the JCR so as to make the password storage secure and to avoid any breach.

The following steps will elaborate the mechanism to generate an encrypted key.

Step 1: Protecting the Plain Text

Crypto Support bundle provides a service that allows users to generate the “Protected Text” from the “Plain Text” input.

Open the URL http://<host>:<port>/system/console/crypto

In the “Plain Text” field, add the string which needs to be encrypted and press the protect button. “Protected Text” field will show the encrypted string to be used. plain text string The encryption algorithm used in this procedure is symmetric key encryption namely AEM algorithm, CBC mode with PKCS5 padding used from RSA JSafe library.

For instance, while setting up the SMTP configurations, it is not ideal to keep the password as a plain text in the OSGI config. Best way to do is to encrypt the password using Crypto Support and then use the Protected Text in the SMTP Configurations.

Next step is to decrypt the protected text in the backend code so as to fetch the original password, which is easy.

Step 2: Decrypt the protected text.

Since the OSGI configuration has the “Protected Text” configured, it is required to decrypt the value before actually using it.

Following code sample is used to decrypt the password:

@Reference
private CryptoSupport cryptoSupport;

private void setEmailConfiguration(Object smtpHost,Object smtpPort,Object smtpUser,Object smtpPwd,Object from Address){

        String password=PropertiesUtil.toString(smtpPwd,StringUtil.EMPTY);
        if(this.cryptoSupport.isProtected(password)){
            this.smtpPassword=this.cryptoSuport.unProtect(password);
            } else {
            this.smtpPassword=password;
            }
        }

@Reference

private CryptoSupport cryptoSupport;

private void setEmailConfiguration(Object smtpHost,Object smtpPort,Object smtpUser,Object smtpPwd,Object from Address){

String password=PropertiesUtil.toString(smtpPwd,StringUtil.EMPTY);

if(this.cryptoSupport.isProtected(password)){

this.smtpPassword=this.cryptoSuport.unProtect(password);

} else {

this.smtpPassword=password;

}

The method unprotect(String cipherText) unprotects (decrypts) the string to return the plain text. We can also check if the String is already protected by using isProtected(String text)method. This method returns true if String provided is protected.

Note that we are not done yet. The protected string generated by Crypto Support will be different for different instances. One last step is required to make sure same protected text can be used throughout. It is an optional step, if different protected strings need to be used on different instances.

Step 3 (Optional): To make the protected text same for all the AEM instances.

If we intend to use the same protected text for all the environments (it is recommended to use different password for production environment to ensure data integrity), then we need to follow below steps.

Download the hmac and master files from the /etc/key current instance.The encryption uses a key which is created with AEM installation in OS filesystem under crx-quickstart. These are binary files which are randomly generated at start of Adobe Granite Crypto Support bundle.
Create the /etc/key node for the destination instance and copy the above two files.
Deploy the code and make sure to restart “com.adobe.granite.crypto” for very first time you upload these key and make cryptography effective.

Note: If we manually stop the Crypto Support bundle, then AEM login fails and the user will be unable to login with any user. Hence, it is always recommended to use CURL command at root directory of the server with admin user only to restart the crypto support bundle.

CURL command to stop the bundle:
curl -u admin:admin
http://<host>:<port>/system/console/bundles/com.adobe.granite.crypto -F action=stop

CURL command to start the bundle:
curl -u admin:admin
http://<host>:<port>/system/console/bundles/com.adobe.granite.crypto -F action=start

Hope this helps you all to smoothly implement encryption/ decryption of the passwords!

We have tested on AEM 6.2

WORKFLOW PURGE SCHEDULER

March 9, 2018/0 Comments/in AEM Technical /by Sukriti Kohli

There are various situations while working on a project where workflows become unmanageable and multitude of workflow instances get triggered. This can lead to various problems which must be resolved in order to maintain a healthy state of the server and uplift the performance of the website. In this blog, we will discuss about such situations and remedial actions to purge the workflows on periodic basis with the help of some features.

Use Case:

Many situations such as content syncing, content migration, development issues, bulk execution or some unpredictable situations lead to massive number of workflow instances running concurrently on an environment. This can lead to performance issues for that particular server.

One such situation occurred while doing a content syncing from one environment to another. When DAM was synced, it triggered abundant of workflow instances of ‘DAM Update Asset’ and ‘Dam Metadata WriteBack’ as various assets were being added to DAM folder of content. DAM Update Asset workflow gets triggered on adding a new asset to DAM. This initiated to uncountable number of workflow instances pertaining to these two workflows which had a performance impact on the server.

Why should we purge unwanted or completed workflow instances?

Multitude of concurrent running workflow instances lead to performance issues on the server. It is essential to purge these instances in so as to manage the size of JCR repository. Running instances pose a performance threat but even completed workflow instances should also be purged as nodes in the repository gets accumulated and it is beneficial to clean them up for the long run to manage disk space and performance. Bloated repository will also have an impact on the queries that are run to search the workflow hierarchies. So, workflow purging should be set as one of the maintenance tasks that must be carried out repeatedly.

Workflow Purge Scheduler

Workflow Purge Scheduler is a categorized as Sling Service Factory so we can create an instance of the same. It is a configuration which we can configure in Felix Console and manage the workflow purge scheduling as per the requirements.

Log into Apache web console, host:port/system/console/configMgr
Search for ‘Adobe Granite Workflow Purge Configuration’ which can help in managing the purge schedule of the workflow instances. Since, this is a Service Factory so we can create multiple instances of this configuration to cater to different criteria parallelly. For example, we can run this scheduler on different models setting different age/ time for a workflow after which it will be marked for purging. To add another instance of this configuration, click on ‘+’ sign in front of the original configuration. The factory PID for this configuration instance will be ‘com.adobe.granite.workflow.purge.Scheduler’. Note that PID of this instance will be set when the configuration instance is saved. It will be assigned with a unique ID appended to the Factory PID of the configuration like com.adobe.granite.workflow.purge.Scheduler-myidentifier where myidentifier is a unique id.
Configure this to set up the scheduler to purge the workflows. It has following fields:
1. Job Name: This name is given to the particular purge instance. This is a descriptive name.
2. Workflow Status: It is a dropdown with options ‘Completed’ and ‘Running’. Choose which status of workflows to purge.
3. Models to purge: It is a multifield in which can set different models to purge. We can configure the ids of the models that are selected for purge. If left blank, it will be effective on all the models. For example, workflow model id is in the form of ‘/etc/workflow/models/dam/update_asset/jcr:content/model’ for DAM Update Asset Workflow. It can be seen from host:port/libs/cq/workflow/content/console.html.
4. Workflow Age: It is a field to enter number of days after which the workflow(s) will be purged.

We can make this configuration as a part of the codebase by adding the config file to the code base. It will be in the form of an xml file placed inside /apps/config node. Note that the name of the xml file should be same as the name of the PID that is of the configuration in Felix console ‘com.adobe.granite.workflow.purge.Scheduler.xml’. If we make an instance of the ‘Workflow Purge Scheduler’ then PID should be something similar to: ‘com.adobe.granite.workflow.purge.Scheduler.config.[some-arbitrary-id].xml’.

We can add entry to the xml file giving default value of the fields that will be sent as a part of the code package.

<?xml version="1.0" encoding="UTF-8"?> 
<jcr:root 
xmlns:sling="http://sling.apache.org/jcr/sling/1.0" 
xmlns:jcr="http://www.jcp.org/jcr/1.0" 
jcr:primaryType="sling:OsgiConfig" 
scheduledpurge.name="DAM Purge " 
scheduledpurge.workflowStatus="Running" 
scheduledpurge.modelIds="‘/etc/workflow/models/dam/update_asset/jcr:content/model " 
scheduledpurge.daysold="1" />

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root

xmlns:sling="http://sling.apache.org/jcr/sling/1.0"

xmlns:jcr="http://www.jcp.org/jcr/1.0"

jcr:primaryType="sling:OsgiConfig"

scheduledpurge.name="DAM Purge "

scheduledpurge.workflowStatus="Running"

scheduledpurge.modelIds="‘/etc/workflow/models/dam/update_asset/jcr:content/model "

scheduledpurge.daysold="1" />

Workflow Remover

There might be situations when we do not require a regular service or a scheduler for purging the workflows but need to remove workflow instances on a particular instance. This might be the scenario during content sync when multiple instances of a workflow get triggered and need to be cleaned up at one time. ACS(Adobe Consulting Services) AEM Commons

provides a functionality of Workflow Remover which is a user interface to remove some unwanted instances of workflows as per the requirement.

Navigate to Tools and go to ACS AEM Commons. Click on Workflow Remover.
Configure this to set up the scheduler to purge the workflows. It has following fields:
1. Status: Any status among Completed, Aborted, Running, Suspended or Stale can be selected.
2. Payload Paths: We enter regex expressions to match the payload path of the workflow.
3. Batch Size: To decide the JCR batch size in which removal of workflow will take place. Default value is 1000.
4. Max Duration: Enter time in minutes to force terminate the workflow removal process. We can set it 0 to disable it. We can leave it blank for no such limit of this workflow removal process.
5. Workflows older than: Workflow instances must be created before older than the date specified here.
6. Workflow Models: It lists all the workflow models that can be removed. If no option is selected specifically by the user, then all the workflow models are eligible for removal meeting the criteria defined.

Workflow Remover of ACS AEM Commons can be set as a scheduled service too in the configuration given as ‘ACS AEM Commons- Workflow Instance Removal- Scheduled Service’ in the Felix Console.

It needs to be configured similar to the UI given in Tools. It has the following fields:

Cron Expression: Cron expression at which the removal scheduled service will run.
Workflow Status: It is a multifield to enter the status of workflows that needs to be removed using this scheduled service. (ABORTED, COMPLETED, STALE, SUSPENDED, RUNNING). ABORTED and COMPLETED are by default.
Workflow models are paths till jcr:content/models of a particular workflow that needs to be removed using this service.
Payload Patterns: This is a regex expression which when matched with the given payload removed that particular workflow instance. Example: /content/dam/.*/.*\.mp4(/.*)?
Older than UTC TS: This field is used to specify time in milliseconds to remove workflow instances which are older than this UTC Time.
Batch Size: This pertains to removal of workflow nodes as defined by the batch size. The default size is 1000.
Max duration: It defines the maximum time (in minutes) till when this workflow process will keep on executing. It defaults to 0 which means that there is no limit for this workflow scheduler to run and remove the workflow instances.

Similar to Workflow Purge Configuration, it can be entered as the part of codebase as an xml file in the config node in apps.

So, there are two configurations and UI in Tools by the help of which we can purge the workflow instances automatically without manual work to make the performance consistent and repository clear of unwanted workflow instances.

Hope this helps you all at some point in the project to kill multiple unwanted workflow instances.

Ref:

https://adobe-consulting-services.github.io/acs-aem-commons/features/workflow-remover/index.html

Opening properties html in a New Tab on Card Click in Omnisearch

March 2, 2018/1 Comment/in AEM Technical /by Anirudh Garg

Introduction:

Omnisearch can be triggered by pressing “/” (forward slash) on a sites.html page, or clicking on the Magnifying glass icon in the top bar.

Fig. 1 – Opening Omnisearch

By default, the results are displayed as cards in an aesthetically pleasing manner. Clicking on a result card opens its properties page in the same tab, but this erases our results page. Going back takes us to the sites.html page from which we initiated the search. If we want to get the same results again, we have to enter the same search term and scroll to the same position. This can get really tiring when you have multiple items to check/modify.

Fig. 2 – Results in Card view

Requirement:

Preserve Omnisearch results in sites.html

We want to preserve the results, so that we can go back and forth without any overheads. This would increase authors’ efficiency and thus save time.

Analysis:

In Omnisearch, an AJAX call passes the search parameters to a Sling servlet which returns the results’ HTML markup. Granite UI receives this rudimentary markup, picks only the tags and attributes it needs, translates them to Coral UI-specific tags, and modifies the DOM dynamically. The rendering and behaviour is handled by Coral UI. Sites.html (Touch UI) has thus been designed as a Single Page Application (SPA), powered by the Coral UI and Granite UI libraries.

When we go back from the properties page, it redirects us to the previous URL. Since it did not store the search results, we don’t see them. Only the initial page source (which is stored in the browser history/cache) is served.

Proposed solution:

The card click should open the link in a new tab

When the user clicks on the card, the properties page will open in a new tab, thereby preserving the results as they were. After the user is done with the property changes, they can close the tab and return to the results.

Limitation is that this will only work on card click for sites.html. It will not work for:

Clicking the Quick Icons (they appear on mouse hover on the card)
List view
Assets, projects, or any other admin interface.

Discovery:

The following are the relevant points from the control flow:

There is <link rel=”properties” href=”…”/> a node in every card’s DOM. The href attribute stores the address to which we have to navigate.
Shell clientlib listens for clicks on the cards. On being invoked, the listener picks the link tag with the rel=”properties” property from the relevant card, and navigates to it.

Search results rendering is not a simple task in AEM. Features were probably added over a long time and by different teams with different architects, which has resulted in a spaghetti implementation. Control flow follows confusing paths and there is no consistent data source. Some datasource paths are defined in /libs and can be overridden, while some are hardcoded into the Omnisearch bundle, which makes extending capabilities very tough. This is why the scope of this blog is limited to its current state.

Nevertheless, the new tab functionality for sites.html can be modified without meddling too much with Adobe code.

Fig. 3 – Desired result. Properties page opens in a new tab

Approach:

Overlay the Shell clientlib.

We shall overlay the Shell clientlib under /apps, which lets us accomplish our task with minimal effort.

Implementation

Copy the folder: “/libs/granite/ui/components/shell”
Paste it under /apps such that the path is: “/apps/granite/ui/components/shell”
Delete all the files in this folder, except “js/omnisearch.js”
Open “js/omnisearch.js”
Go to line 827
Replace the existing function with:

$(document).on("click", "#granite-omnisearch-result-content .foundation-collection-navigator", function(event) {
var element = $(event.currentTarget).find("link[rel=properties]");
if(this.hasAttribute("data-foundation-collection-navigator-href")){
var href = element.attr("href");
if (href) {
window.location = href;
}
}
else {
var href = element.attr("href");
if (href) {
window.open(href, "_blank");
}
}
event.preventDefault();
});

$(document).on("click", "#granite-omnisearch-result-content .foundation-collection-navigator", function(event) {

var element = $(event.currentTarget).find("link[rel=properties]");

if(this.hasAttribute("data-foundation-collection-navigator-href")){

var href = element.attr("href");

if (href) {

window.location = href;

}

else {

var href = element.attr("href");

if (href) {

window.open(href, "_blank");

}

event.preventDefault();

});

Fig. 4 – The overlaid JS file and modified content

Line 838 is the relevant code for sites.html. We changed it from window.location = href to window.open(href,“_blank”) which opens the page in a new tab.

The condition on Line 829 detects if the search was performed in assets.html. If it evaluates to true, then the default/old code is executed. Had we not placed the check, then a card-click in assets.html would have opened the link in the same tab and a new tab as well. This is because assets.html cards have an additional attribute called data-foundation-collection-navigator-href. When this attribute is combined with the attribute data-foundation-collection-navigator, Granite UI treats the card as a link. So, that would have opened the new page in the same tab, and our code (line 829) would have opened it in a new tab.

Conclusion:

Now when you go to “host:port/sites.html/” and search something, the card click will open the properties page in a new tab.

Anirudh Garg

AEM Developer

Adding Custom Asset Metadata in AEM CMS and How to Use It – Argil DX

January 8, 2018/0 Comments/in AEM Technical /by Arpit Rathi

PROBLEM STATEMENT

Working in AEM CMS and need to add custom metadata like tags, dates, or text properties to images and videos? Read this quick how-to from our AEM experts.

Step 1:

Go to projects page ( http://localhost:4502/projects.html ).

Select ‘Tools’ from the right rail and then go to ‘Assets’ and select ‘Metadata Schema’.

Step 2:

Click on add button and provide a name to your schema.

In this case, I have created a schema named ‘DemoSchema’.

Step 3:

Select your schema from the list by checking the checkbox and click on edit.

Here you will get an empty form in tab layout with all the widgets present in the right section, we can drag and drop widgets to our form.

Step 4:

Provide a name for your tab from settings and drag widgets onto the form.

Step 5:

Select a widget and go to setting option on the top right.

· Provide name to a field using ‘Field Label’.

· In ‘Map to property’ field give the property path in which you want the value to be stored inside the image file. This property will be automatically created once this field will get authored.

· Give placeholder (If required), choose distinct options like required, editable, empty in read-only.

· If a field is wrongly placed either drag it to right position or delete it using the delete icon below properties.

Step 6:

After making your schema. Select your schema and click on ‘Apply to folders icon on the top rail and select the folders on which you want your schema to be applied.

Properties will look like this:

Step 7:

To utilize these properties in sightly used in AEM CMS, make a java class using resource API.

In Java, I have injected the image path and then I’ve extracted resource out of it using resource resolver and extracted properties out of it.

@Model(adaptables = { Resource.class, SlingHttpServletRequest.class }, cache = true) 

public class ImageMetadataModel { 

 

@Inject 

@Optional 

private String imagePath; 

 

@SlingObject 

private ResourceResolver resourceResolver; 

 

public String getProperty () { 

Resource resource = resourceResolver.getResource(imagePath +“/jcr:content”); 

String property = “”; 

if (resource != null) { 

ValueMap valueMap = resource.getValueMap(); 

if (valueMap.containsKey(“propertyname”)) { 

property = valueMap.get(“propertyname”, String.class); 

} 

} 

return property; 

} 

}

@Model(adaptables = { Resource.class, SlingHttpServletRequest.class }, cache = true)

public class ImageMetadataModel {

@Inject

@Optional

private String imagePath;

@SlingObject

private ResourceResolver resourceResolver;

public String getProperty () {

Resource resource = resourceResolver.getResource(imagePath +“/jcr:content”);

String property = “”;

if (resource != null) {

ValueMap valueMap = resource.getValueMap();

if (valueMap.containsKey(“propertyname”)) {

property = valueMap.get(“propertyname”, String.class);

}

return property;

}

Interested in more training and support for your organization using AEM CMS? Request a consultation to discuss Argil DX managed services.

AEM Dispatcher Setup for Linux

June 7, 2017/0 Comments/in AEM /by Himani Hasiza

Installing dispatcher for AEM in Apache Web-server in Linux may get little tricky, as documentation provided by Adobe on Installation of Dispatcher in Linux is not sufficient, and if we take it in analogy and try doing same way we do in Windows, then we face some issues locating the appropriate files.

Prerequisites for Dispatcher Setup

Apache 2.2 web-server – In Ubuntu 12.0 and higher, Apache 2.2 web-server is pre-installed, but in case it is not there, you can find the installation instructions here.
Dispatcher Module – Appropriate dispatcher module can be downloaded from Adobe Package Share.

Installation Instructions

Considering Apache web-server is already setup in system, go ahead and extract dispatcher module using following command:

tar -xvzf <dispatcher..xxxx..yyyy.tar.gz>

1

tar -xvzf <dispatcher..xxxx..yyyy.tar.gz>
Once you have extracted the files, now you have to move the appropriate files to their respective apt path.
Move “dispatcher-apache2.x-4.1.x.so” to “/usr/lib/apache2/modules”. There you will find all the modules already being loaded by apache 2 webserver.
Adobe recommends to give a soft name to your dispatcher module, but you don’t need it as once setup is done, you will be hardly using it again.
Now go ahead and create a folder conf under “/etc/apache2/”, and move “dispatcher.any” file under this folder. Make sure that you don’t move your dispatcher.any file to ‘conf.d’ folder which is already present.
Now is the time to edit and map module file that you added and map the dispatcher.any file. Go ahead and edit apache2.conf file present under “etc/apache2/”.

Scroll to the end, put some nice comments about you adding some new configs, and add following:

LoadModule dispatcher_module /usr/lib/apache2/modules/dispatcher-apache2.2-4.1.5.so

<IfModule disp_apache2.c>
# location of the configuration file. eg: 'conf/dispatcher.any'
DispatcherConfig conf/dispatcher.any

# location of the dispatcher log file. eg: 'logs/dispatcher.log'
DispatcherLog /var/log/apache2/dispatcher.log

# log level for the dispatcher log
# 0 Errors
# 1 Warnings
# 2 Infos
# 3 Debug
DispatcherLogLevel 3

# if turned to 1, the dispatcher looks like a normal module
DispatcherNoServerHeader 0

# if turned to 1, request to / are not handled by the dispatcher
# use the mod_alias then for the correct mapping
DispatcherDeclineRoot 0

# if turned to 1, the dispatcher uses the URL already processed
# by handlers preceeding the dispatcher (i.e. mod_rewrite)
# instead of the original one passed to the web server.
DispatcherUseProcessedURL 0

# if turned to 1, the dispatcher does not spool an error
# response to the client (where the status code is greater
# or equal than 400), but passes the status code to
# Apache, which e.g. allows an ErrorDocument directive
# to process such a status code.
DispatcherPassError 0
</IfModule>

LoadModule dispatcher_module /usr/lib/apache2/modules/dispatcher-apache2.2-4.1.5.so

# location of the configuration file. eg: 'conf/dispatcher.any'

DispatcherConfig conf/dispatcher.any

# location of the dispatcher log file. eg: 'logs/dispatcher.log'

DispatcherLog /var/log/apache2/dispatcher.log

# log level for the dispatcher log

# 0 Errors

# 1 Warnings

# 2 Infos

# 3 Debug

DispatcherLogLevel 3

# if turned to 1, the dispatcher looks like a normal module

DispatcherNoServerHeader 0

# if turned to 1, request to / are not handled by the dispatcher

# use the mod_alias then for the correct mapping

DispatcherDeclineRoot 0

# if turned to 1, the dispatcher uses the URL already processed

# by handlers preceeding the dispatcher (i.e. mod_rewrite)

# instead of the original one passed to the web server.

DispatcherUseProcessedURL 0

# if turned to 1, the dispatcher does not spool an error

# response to the client (where the status code is greater

# or equal than 400), but passes the status code to

# Apache, which e.g. allows an ErrorDocument directive

# to process such a status code.

DispatcherPassError 0

</IfModule>

Also add the following config to the end of apache2.conf file, which loads the dispatcher in web-server.

<Directory />

<IfModule disp_apache2.c> 
# enable dispatcher for ALL request. if this is too restrictive, 
# move it to another location
SetHandler dispatcher-handler
</IfModule>

Options FollowSymLinks
AllowOverride None

</Directory>

# enable dispatcher for ALL request. if this is too restrictive,

# move it to another location

SetHandler dispatcher-handler

</IfModule>

Options FollowSymLinks

AllowOverride None

</Directory>

Comments given above are self explanatory but, you can still go and edit configs if needed as per following descriptions:

DispatcherConfig: Location and name of the configuration file (Can be given as an absolute or relative path)
DispatcherLog: Location and name of the log file (Can be given as an absolute or relative path)
DispatcherLogLevel: Log level for the log file
DispatcherNoServerHeader: Whether to use the Apache or CQ server header
DispatcherDeclineRoot: Defines whether to decline requests to the root “/”
DispatcherUseProcessedURL: Defines whether to use the original request URL or to use one already processed by other handlers (ie: mod_rewrite)
- Note: This is essential for rewriting incoming links (stripping away the ‘content/{site_name}’)
DispatcherPassError: Defines whether CQ or Apache will handle HTTP 40x error codes
SetHandler (Apache parameter): Forces all matching files to be processed by a handler

Make sure, that path that is provided for load module, matches with the path where you placed your dispatcher module. Also match the name and version of dispatcher module, and change the config as required.
Now configure dispatcher.any file. Edit /renders section in dispatcher.any.

/renders { /rend01 { /hostname "localhost" [2]--> /port "80" } } /cache { /docroot "/var/cache/apache2/<cqcache>" }

1
2
3
4
5
6
7
8
9
10
11
12

/renders
{
/rend01
{
/hostname "localhost"
[2]--> /port "80"
}
}
/cache
{
/docroot "/var/cache/apache2/<cqcache>"
}

By default you may find port set to 8000 or 8080, change it to 80.
Give whatever soft-name you want to give to your cache folder in place of “cqcache”
Restart the apache server to let webserver take effect. You can restart apache server by using following command:

sudo /etc/init.d/apache2 restart

1

sudo /etc/init.d/apache2 restart
Once server is restarted and you get [OK] message, go and check /var/log/apache2/dispatcher.log file. If it says dispatcher initialized with correct cache path, it means dispatcher is successfully setup and ready to be used.

Now you just need to configure your CQ replication agent, and point dispatcher flush agents to correct port.

I tested this today itself i.e. 14th Oct 2013 on Ubuntu 13 64 bit debian based OS. It worked like wonder for me. Please post your comments and queries if you have any issues with it, and also if there are better ways to do it. Cheeeerz.

Dynamic Options values in AEM dialog dropdown Using $PATH

June 7, 2017/3 Comments/in AEM /by Himani Hasiza

In this post, I will explain a real project use-case, where I need to populate a Dropdown in my component dialog with dynamic values, but the condition are-

1. These values can only be fetched from the current resource or current page object.
2. Another condition is that this dropdown must be auto-populated when the dialog opened.

For example, The drop down values can be the list of all parent pages of the page where this component was dropped.

Q1). How will you go for it?

You will think about ajax call because the dropdown can be filled with dynamic values using options property.

Q2). Yes, you are right then, what will you call from the options property?

Sling Servlet

If your answer is Sling Servlet then, I have some questions for you-

Q1). How will you get the current resource or current page object in that servlet?
Q2). If you are trying to pass the path of current resource then How will you do that?

OK, I think you are well understood what am I trying to say. How to get current resource or current page object into the called Sling Servlet.

Maybe you can do it using some other approach but in this post I will explain, How I complete this task?

In place of servlet I have created a JSP file under same component node with some selector (For ex. options.json). For Ex. My component structure is-

Now, I have set some properties on my drop-down dialog node. These properties are shown in figure-

Here you will notice that, I have used $PATH, this will return the path of the component wherever it is dropped. Then I used Sling Script Resolution Principle to call my options.json.jsp file.

For writing this blog, I had created dummy data but in actual, I had created a Sling Service and from one of it’s methods, I was getting the JSON values.

<%@page session="false"%>
<%@page contentType="application/json"
            pageEncoding="utf-8"
            import="java.util.Map,
                    java.util.TreeMap,
                    com.day.cq.commons.TidyJSONWriter" %>
<%@include file="/libs/foundation/global.jsp" %>
<%
    TidyJSONWriter w = new TidyJSONWriter(out);
    w.setTidy(true);
    w.array();
	TreeMap<String, String> options = new TreeMap<String, String>();
	options.put("Page1","Parent Page One");
	options.put("page2","Parent Page Two");
	options.put("page3","Parent Page Three");
    for (Map.Entry<String, String> e: options.entrySet()) {
        w.object();
        w.key("value").value(e.getKey());
        w.key("text").value(e.getValue());
        w.endObject();
    }
    w.endArray();
%>

<%@page session="false"%>

<%@page contentType="application/json"

pageEncoding="utf-8"

import="java.util.Map,

java.util.TreeMap,

com.day.cq.commons.TidyJSONWriter" %>

<%@include file="/libs/foundation/global.jsp" %>

TidyJSONWriter w = new TidyJSONWriter(out);

w.setTidy(true);

w.array();

TreeMap<String, String> options = new TreeMap<String, String>();

options.put("Page1","Parent Page One");

options.put("page2","Parent Page Two");

options.put("page3","Parent Page Three");

for (Map.Entry<String, String> e: options.entrySet()) {

w.object();

w.key("value").value(e.getKey());

w.key("text").value(e.getValue());

w.endObject();

}

w.endArray();

Here, you should follow standard coding practices and should remove these scriptlets from JSP file to some java file. But the key point is that this JSP must return the values in JSON format. If you are using Sightly then same code will work or if you want to use HTML in place of JSP then it will work perfectly fine.

I am also sharing the Git repository link where you can find demo examples for these properties.
Git repository link is –

https://bitbucket.org/accunitysoft/accunity-blog-snippets

Happy Coding..!!

Ankur Chauhan
Tech Lead

Posts

AEM-DTM-Target Integration. Simplified! – Part1

Working with Boutique Versus Large Implementers

How to Change Data Type (Typecast) in AEM, Use @TypeHint

BLOG SUMMARY & BUSINESS GOAL

Crypto Support in AEM

WORKFLOW PURGE SCHEDULER

Opening properties html in a New Tab on Card Click in Omnisearch

Adding Custom Asset Metadata in AEM CMS and How to Use It – Argil DX

PROBLEM STATEMENT

Step 1:

Step 2:

Step 4:

Step 5:

Step 6:

Step 7:

AEM Dispatcher Setup for Linux

Prerequisites for Dispatcher Setup

Installation Instructions

Recent Insights

Certified Partnerships

US Headquarter

APAC Headquarter

Posts

BLOG SUMMARY & BUSINESS GOAL

PROBLEM STATEMENT

Step 1:

Step 2:

Step 4:

Step 5:

Step 6:

Step 7:

Prerequisites for Dispatcher Setup

Installation Instructions

Q1). How will you go for it?

Q2). Yes, you are right then, what will you call from the options property?

Q1). How will you get the current resource or current page object in that servlet? Q2). If you are trying to pass the path of current resource then How will you do that?

Recent Insights

Certified Partnerships

US Headquarter

APAC Headquarter

Q1). How will you get the current resource or current page object in that servlet?
Q2). If you are trying to pass the path of current resource then How will you do that?