Wednesday, 18 December 2013

Developing AEM OSGi bundles that use Jackrabbit UserManager APIs

You can develop an Adobe Experience Manager (AEM) OSGi bundle that uses Jackrabbit UserManager APIs to perform AEM user operations. This API provides access to both AEM users and groups and is located in the
org.apache.jackrabbit.api.security.user Java package.

Using an OSGi bundle that contains these APIs, you can retrieve AEM user identifier values and perform a task using these values. In this development article, the retrieved AEM user identifier values are written to the Adobe CQ log file.

7.12.2013 17:25:09.689 *INFO* [0:0:0:0:0:0:0:1 [1387319109155] GET /content/Blog.html HTTP/1.1] com.aem.users.SearchUsersImpl Retrieved USER admin
17.12.2013 17:25:09.689 *INFO* [0:0:0:0:0:0:0:1 [1387319109155] GET /content/Blog.html HTTP/1.1] com.aem.users.SearchUsersImpl Retrieved USER replication-receiver
17.12.2013 17:25:09.708 *INFO* [0:0:0:0:0:0:0:1 [1387319109155] GET /content/Blog.html HTTP/1.1] com.aem.users.SearchUsersImpl Retrieved USER anonymous
17.12.2013 17:25:09.709 *INFO* [0:0:0:0:0:0:0:1 [1387319109155] GET /content/Blog.html HTTP/1.1] com.aem.users.SearchUsersImpl Retrieved USER zachary.w.mitchell@spambob.com


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

Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner

About the Author

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 16 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 Inhttp://www.linkedin.com/in/scottmacdonald2010
TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

Friday, 13 December 2013

Adobe Experience Manager Community in 2014

As 2013 closes out, it's time to reflect back on the year and what the AEM community team did in 2013. It was a very busy year and we performed many tasks. We launched the new Digital Marketing support communities, created task-based AEM developer articles,  and engaged with the community in different social channels such as Twitter, Facebook groups and Linked in.

Looking ahead to 2014, we have a lot of content planned out. We will be delivering a lot  more AEM 'How To' articles based on your feedback. One area where we are going to spend time on is XType articles. We have heard the community in its request for more how to articles that discuss how to work with XType data types to create advanced AEM components.

NOTE: If there is a certain topic that  you would like to see -- please leave a comment and us know what you want. 

Another exciting thing coming up in 2014 is the annual Digital Marketing summit:



This is an excellent chance to come out, meet with the Digital Marketing community, and learn more about Adobe Digital Marketing.

Another big event in 2014 is the release of the next major version of Adobe Experience Manager. More on that as the date gets closer.

Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner

About the Author

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 16 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 Inhttp://www.linkedin.com/in/scottmacdonald2010
TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.

Monday, 2 December 2013

Creating a HTML Parser Service for Adobe Experience Manager

You can create a custom Adobe Experience Manager (AEM) HTML parser service that accepts HTML and parses it. By parsing HTML, you can retrieve HTML tag values. For example, consider the following HTML.

<div><p>Hello JSoup - this is now a CQ service.</p></div>

Once you pass this HTML to the custom AEM HTML parser service, you can get the value of the <p> tag, as shown in the following illustration.

An AEM web page that parses HTML by calling the custom HTML parser service
To create a custom AEM HTML parser service, you can use the JSOUP library. That is, the application logic required to parse HTML is developed by using the JSOUP API. For information about this API, see:

http://jsoup.org/

The Java logic that parses HTML is implemented as an OSGi bundle that is built using Declarative Services (DS) and Maven. The OSGi bundle is a managed component, which means that the OSGi service container creates the OSGi instance. To read this development article, click: http://helpx.adobe.com/experience-manager/using/html-parser-service.html.

Adobe Digital Marketing Community

Join the Adobe Digital Marketing Community. Start by clicking this banner

About the Author

I (Scott Macdonald) am a Senior Digital Marketing Community Manager at Adobe Systems with over 16 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 Inhttp://www.linkedin.com/in/scottmacdonald2010
TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeMktgCare.