Monday, 25 November 2013

Creating a Custom Reporting Service for Adobe Experience Manager

You can create a custom reporting service for Adobe Experience Manager (AEM) that stores AEM data. A benefit of creating a custom service is you can develop it to meet your business requirements and integrate the reporting service to use data queried from an AEM service. For example, you can create an AEM solution that queries enterprise data that a digital marketer is interested in viewing. Then you can write out the data to a report and store the report in the AEM Java Content Repository (JCR).

This development article extends an AEM application that is built by following another AEM development article that queries data from MySQL using a DataSourcePool. Before following this article, create the DataSourcePool application by following this article: Injecting a DataSourcePool Service into an Adobe Experience Manager OSGi bundle.

In this article, an option is added to the web application that lets a user specify if the queried data is written to a custom report. Consider the following AEM web application.

This development article walks you through how to build this custom reporting service. To read this development article, click

Note: Adobe Experience Manager supports reports without creating a custom reporting service. You can create a report by configuring JCR nodes and properties. For information, see Developing Reports.

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.

TwitterFollow the Digital Marketing Customer Care team on Twitter @AdobeExpCare.

YouTube: Subscribe to the AEM Community Channel

1 comment:

  1. This comment has been removed by a blog administrator.