Posting AEM 6 Form Data to Custom Services

You can create an Adobe Experience Manager (AEM) 6 form and submit the data to a custom AEM service. The custom service can process the data to meet your business requirements. For example, you can store the data in a database or send the data within an email message. However, to keep this article simple, the custom AEM service writes the posted data to the AEM log file.

An AEM 6 form can be consumed in a mobile device or a web browser running on a desktop. For example, consider a mobile user filling out the following AEM 6 form on an IPad device..

When the user clicks the Submit button, the form data is submitted to an AEM Sling Servlet. Once the data reaches the Sling Servlet, you can process the mobile data to meet your business requirements. For example, you can store it in a relational database, store it in the AEM JCR, or pass it to an AEM Workflow (just to give a few examples).

To read this development article, click http://helpx.adobe.com/experience-manager/using/posting-aem-6-form-data.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel. 

Scheduling Adobe Experience Manager Jobs using Apache Sling

You can create an Adobe Experience Manager (AEM) OSGi bundle that uses Sling APIs to create a custom Sling Schedule Service. This service performs an AEM job at a scheduled time. In this article, assume that the following use case exists:

1. The Scheduler Service runs each weekday and checks to determine if there are more than six stale workflow items. It uses MBean API logic to perform this task.

2. If there are more than six stale workflow items, an email message is sent to an AEM administrator.

To read this development article, click http://helpx.adobe.com/experience-manager/using/aem-first-components1.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel. 

Customizing Your First Adobe Experience Manager 6 Social Component

Adobe Experience Manager (AEM) 6 supports social components that let you build web sites that contain social functionality that lets you engage with your customers. For example, you can add functionality that lets your users leave comments on your website. AEM supports out of the box socials components. For information, see Introduction to Social Communities.

AEM also supports the ability to customize these social components to meet your business requirements. You can use the AEM Social Component Framework Java API to create a custom social component. An user can interact with an AEM web site by interacting with functionality exposed by your custom social component.

An AEM social component forms the basis of HTTP API responses and the context made available to a front end component. Sometimes you need to add more information or hide information to the default social component to meet your business requirement. You can achieve this use case by writing an AEM OSGi bundle that uses the AEM Social Component Framework Java API located in the com.adobe.cq.social.commons.client.api package. For information about this API, see Package com.adobe.cq.social.commons.

For example, you can modify the appearance of the AEM comment system by using AEM Java APIs.

 

To read this development article, click http://helpx.adobe.com/experience-manager/using/social_components.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel. 

Creating Adobe Experience Manager Sling Servlets that invoke MBean operations

You can create an Adobe Experience Manager (AEM) application that lets a user view data returned by a MBean operation. A MBean is a server-side resource that can be managed. In this use case, assume that a user wants to retrieve the number of stale workflow items, as shown in the following illustration.

The Sling Servlet that is created uses Java APIs located in the javax.management package that can be used to manage and monitor MBean operations. For information, see Package javax.management.

This article guides you through creating a Sling Servlet that uses MBean APIs to determine the number of stale workflow items located within AEM.

To read this development article, click  http://helpx.adobe.com/experience-manager/using/sling_servlet_mbean.html. 

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel. 

Creating your first AEM Service using an Adobe Maven Archetype project

This development article was written due to a request from the AEM community. It discusses how to create your first Adobe Experience Manager (AEM) custom service by using Maven and an Adobe Archetype project.

In some business use cases, you create an OSGi bundle when creating an Adobe Experience Manager (AEM) application. Although there are different ways to create an OSGi bundle, a recommended way is to use Maven and the Adobe Maven Archetype. This development article walks you through creating a basic OSGi bundle that contains a simple service named KeyService. All this service does is accept an input value and sets a key value. It also exposes a method that returns the key value and the value can be displayed within an AEM web page.

To read this development article, click, http://helpx.adobe.com/experience-manager/using/first-osgi.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel. 

Creating your first Adobe Experience Manager Component

You can create a custom Adobe Experience Manager component that you can drag from the CQ sidekick and drop onto an AEM page. Furthermore, the custom component can be displayed in an AEM LiveCopy page. However, by default, the custom component is not locked in the LiveCopy page, as shown in the following illustration.

Notice in the previous illustration, three AEM components are displayed in a LiveCopy page:

• A custom component named Echo that display text that a user enters into a CQ dialog
• An Image component
• A standard Text component

By default, the two standard AEM components have a lock, meaning that these components cannot be modified in the LiveCopy page. However, the custom component can be clicked on and modified, as shown by this illustration.

This custom component should be locked within the AEM LiveCopy page. To successfully lock the custom component, you have to add extra configuration to the custom component (this will be shown later in this development article). 

This development article walks you through creating a basic AEM custom component name Echo. All it does is let an AEM user enter a value into a dialog. Then the value is displayed in the AEM web page (this is about as simple of a custom component as you can develop). Then the component is displayed in a LiveCopy page, where it can be modified. Finally the custom component is modified further so that it’s locked within the LiveCopy page.

To read this development article, click http://helpx.adobe.com/experience-manager/using/aem-first-components.html.

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel. 

Creating a Custom AEM Dam Media Handler

You can create a custom Adobe Experience Manager (AEM) DAM media handler that is invoked when you upload a digital asset to the AEM DAM. A DAM handle processes an asset when it’s uploaded to the DAM. For example an DAM handler can generate a thumbnail generation and extract metadata.

To create an AEM DAM media handler, you create an OSGi bundle that contains a class that extends com.day.cq.dam.commons.handler.AbstractAssetHandler. For information, see AbstractAssetHandler.

To read this development article, click  http://helpx.adobe.com/experience-manager/using/damhandler.html.

To watch the video, click:

Join the Adobe Experience Cloud Community 

Join the Adobe Experience Cloud Community by clicking this banner

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with 20 years in the high tech industry. I am also a programmer with knowledge in Java, JavaScript, C#,C++, HTML, XML and ActionScript. If  you would like to see more CQ or other Adobe Digital Marketing end to end articles like this, then leave a comment and let me know what content you would like to see.

Linked In: http://www.linkedin.com/in/scottmacdonald2010

Twitter: Follow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel.