Saturday, 31 August 2013

General FAQs for Adobe Experience Manager

How can I fix CRXDE when it stops working?

CRXDE is a pre-packaged stand-alone Eclipse application designed for CQ and CRX. It enables developers to work efficiently, providing broad set of tools to easily create a project, create and manage files, folders, templates, components, dialogs, nodes, properties, scripts and bundles while logging, debugging, and integrating with SVN.

Sometimes it stops working and regardless of how much you try, it doesn’t open up. It does nothing when you click ok to login. People try reinstalling and what not but the trick is simple. Delete .crxde folder within your home directory. So, if you are using windows it is usually under c:\ documents and settings\<your user name>.

Does Adobe CQ support clustering?

Yes, Adobe CQ supports clustering. To increase availability, and performance, of your Production environment, it is common to combine multiple author or publish instances, by either making them available to different groups of users or by load balancing them behind a Dispatcher configuration. For more information, see http://dev.day.com/docs/en/cq/current/exploring/concepts.html#Clustering and Load Balancing

What is the Dispatcher?

The Dispatcher is the Adobe CQ caching or load balancing tool that helps realize a fast and dynamic Web authoring environment. For caching, the Dispatcher works as part of an HTTP server, such as Apache, with the aim of storing (or "caching") as much of the static website content as possible and accessing the website's layout engine as infrequently as possible. In a load balancing role, the Dispatcher distributes user requests (load) across different clustered CQ instances (renders). For caching, the Dispatcher module uses the Web server's ability to serve static content. The Dispatcher places the cached documents in the document root of the Web server.

For information about using the Dispatcher with multiples domains, see http://dev.day.com/docs/en/cq/current/deploying/dispatcher/disp_domains.html.


For information about troubleshooting Dispatcher flushing issues, see http://helpx.adobe.com/adobe-cq/kb/troubleshooting-dispatcher-flushing-issues.html.


For additional Dispatcher information, see http://helpx.adobe.com/adobe-cq/using/dispatcher-faq.html.


Does Adobe CQ support integration with third-party LDAP systems?

Adobe CQ interfaces with LDAP systems, such as Apache Directory or Windows Active Directory, using the Java Authentication and Authorization Service (JAAS). For information, see http://helpx.adobe.com/adobe-cq/using/configuring-cq-apache-directory-service.html.

For a walk-through on configuring Adobe CQ to use Apache Directory Services, see http://helpx.adobe.com/adobe-cq/using/configuring-cq-apache-directory-service.html.

What is an OSGi bundle?

An OSGi bundle is a Java module that can be deployed to the Adobe CQ service layer. You can use an OSGi bundle to create custom services within Adobe CQ. An OSGi operation can be called from other services or JSPs. For a detailed walkthrough on creating an OSGi bundle as part of creating a CQ application, see Querying Adobe Experience Manager Data using the JCR API.


What is the Adobe CQ JCR?

The Adobe CQ JCR stands for the Java content repository. You can store data as nodes and node properties. Data is stored within properties that belong to a node. You can store, access, update, and delete nodes and properties.

How can I modify the JCR?

You can dynamically modify the JCR using the JCR Java API or the SlingPostServlet. For information about using the JCR API, see Programmatically Accessing Adobe CQ Content using the JCR API.

What is the SlingPostServlet?

A Sling Post Servlet is another way in which you can modify the Adobe CQ JCR. Using a Sling Post Servlet, you can store, access, update, and delete nodes and properties. For example, the following Post creates a node:

<form action="/mynode" method="POST">
<input type="text" name="title">
<textarea name="body">
</form>

This POST action creates a node named mynode. Properties title and body are set. For more information, see http://dev.day.com/docs/en/cq/current/developing/sling_cheatsheet.html.

To learn how to build an Adobe CQ mobile application that submits mobile data to the Adobe CQ JCR using a Sling Post Servlet, see Using Sling Post Servlets to submit mobile data to Adobe CQ.

To learn how to build a .NET client application that submits data to the Adobe CQ JCR using a Sling Request, see Submitting data to the Adobe CQ JCR using a .NET client application.


How can I query data from the JCR?

You can use the Java Query API to query data from the JCR. For example, you can create an Adobe CQ application that queries the JCR based on user input and display the result set in a client web page. For information, see Querying Adobe Experience Manager Data using the JCR API


Can I use other frameworks within Adobe CQ?

Yes, you can use other frameworks within Adobe such as jQuery. Using additional frameworks lets you extend the functionality of Adobe CQ. For information, see Integrating the jQuery Framework into Adobe CQ


Can I use third-party APIs to create custom CQ widgets?

Yes, you can use third-party APIs to create custom widgets. For example, you can use Google MAP API to create a map widget that you can add to the CQ sidekick. For information, see Integrating custom CQ widgets with third-party libraries.

Can I integrate Adobe CQ with third-party web services?

Yes, you can create Adobe CQ applications that can consume a third-party web service. See Creating Adobe CQ bundles that consume web services.

Is there Adobe CQ best practice information?

Yes, for information about Adobe CQ best practices, see CQ best practices.

Is there Adobe CQ configuration information?

Yes, for information about configuring Adobe CQ, see Configuring CQ.

Is there Adobe CQ installation information?

Yes, for information about installing Adobe CQ, see Installing CQ.


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, 30 August 2013

Creating a CQ widget that supports image drag and drop

You can create an AEM component that manages text and an image. Furthermore, the component created in this article has a CQ Dialog that lets a user select an image during design time. The component is used by the CQ parsys system, supports a Dialog with multiple tabs, and enables the functionality offered by the Content Finder (for example, drag-and-drop).

A CQ Widget that allows an image to be dragged from the content finder


When the user selects an image, it is displayed within the widget.

The CQ widget displays an image


In this article, the image is editable by a content author and can be dragged-and-dropped from the Content Finder.

For this article, the image:
1. Is a Dialog Widget (xtype of smartimage).
2. Must be configured in the Component's cq:editConfig to allow for dragging- and-dropping of images from the Content Finder, as shown in this illustration.

The CQ widget supports drag and drop from the Content Finder
To read this development article, click:

http://helpx.adobe.com/experience-manager/kb/creating-cq-widget-supports-image.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.


Saturday, 24 August 2013

Get your Adobe Experience Manager: Classroom in a Book

As an Adobe Experience Manager (AEM) professional, you will be interested in the following AEM book that will be available in early Sept 2013:

 





Here is the TOC listing:

Getting Started
Ch 1: The Basics
Ch 2: Evaluating AEM
Ch 3: Managing Content
Ch 4: Digital Asset Management
Ch 5: Metadata and Tagging
Ch 6 Multilingual Content
Ch 7: Workflows
Ch 8: Social Communities
Ch 9: E-Commerce
Ch 10: Mobile for Marketers
Ch 11: Architecture Basics
Ch 12: Administration Basics
Ch 13: Web Analytics
Ch 14: Marketing Campaign Management  
Ch 15: Dynamic Content
Ch 16: Integrating AEM
Ch 17: Technical Basics
Ch 18: Defining Requirements
Ch 19: User Experience Design
Ch 20: The Implentation Process




Thursday, 22 August 2013

Creating a custom Excel Service for Adobe Experience Manager

While helping answer forums for Adobe Experience Manager, an AEM user asked how to create a CQ service that is able to import an Excel spreadsheet, read the data from the excel spreadsheet, and update the AEM Java Content Repository (JCR) with data read from the spreadsheet. While this is not an out-of-the-box feature, it does not mean that Adobe CQ cannot perform this use case. One of the most powerful features of AEM is the ability to develop custom services.

You can create a custom AEM service that  accepts an Excel spreadsheet, reads the data within the spreadsheet, and writes the data to the AEM JCR. For example, consider the following spreadsheet that contains customer data. Once you upload this file to AEM, the custom service reads the customer data and persists the data in the AEM JCR.

An Excel Spreadsheet that contains customer data

This development article walks you through how to create a custom AEM service that accepts a spreadsheet, reads the data and updates the AEM JCR with the data. To read this development article, click:

http://helpx.adobe.com/experience-manager/using/creating-custom-excel-service-experience.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.

Monday, 19 August 2013

Creating an AEM DAM Image component using the Query Builder API

You can create an Adobe Experience Manager image component that displays images located in the Adobe CQ Digital Asset Management (DAM) repository by using the Query Builder API. This API requires that you define search parameters, and an optional filter. After you execute the query, the results are stored in a result set. You can display the result set in an Adobe CQ web page. For information, see http://dev.day.com/docs/en/cq/current/javadoc/com/day/cq/search/QueryBuilder.html.

The CQ DAM is a digital asset management tool that is fully integrated with the CQ platform and enables your enterprise to share and distribute digital assets. Users across an organization can manage, store, and access images, videos, documents, audio clips, and rich media such as Flash files for use on the web, in print, and for digital distribution. For more information, see CQ Digital Asset Management.

The image component that is created in this development article uses the AEM Query Builder API within JSP application logic. That is, a JSP uses the Query Builder API to retrieve digital assets from the AEM DAM and then displays the images in the web page. In contrast, you can also create a server-side OSGi bundle that uses the Query Builder API to search the Adobe CQ repository. See Creating Adobe CQ OSGi bundles that use the Query Builder API.

The following illustration shows the simple JSP component that is created in this development article.


To read this development article, click:
http://helpx.adobe.com/experience-manager/using/aem-dam-image-components.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.

Saturday, 17 August 2013

Querying and Persisting Adobe AEM data into MySQL

You can create an Adobe CQ web application that performs database operations on a relational database. In this development article, the CQ web application queries and updates a MySQL database. That is, a user can create a new customer record that is stored in the Customer table. Likewise, a user can view all Customer records, as shown in the following illustration.



The Java JDBC API is used within an OSGi bundle that queries customer data based on three options:

1 - All customers (both active and past customers are displayed as shown in the previous illustration).
2 - Active customers (only active customers are displayed).
3 - Past customers (only past customers are displayed).

This development article walks you through creating an AEM application that queries data from MySQL and displays the data in client web page. To read this development article, click:

Querying and Persisting Adobe AEM data into MySQL


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.

Thursday, 1 August 2013

Creating AEM applications that use the Query Builder API to display search results

You can create an AEM application that searches the CQ repository for assets and displays the results to the end user. For example, you can search CQ pages under a specific repository node (for example, in a child node under /content) and look for a specific search term. All pages that satisfy the search criteria are included in the search results. To search the Adobe CQ repository, you use Query Builder API. This API requires that you define search parameters, and an optional filter. After you execute the query, the results are stored in a result set. You can display the result set in an Adobe CQ web page.

When working with the Query Builder API, you can use a Java API or a Restful API. This development article uses the Adobe CQ Query Builder Java API to perform searches.

A user specifies search criteria and the CQ repository is searched using the defined criteria 

You can search the AEM repository and display the data result set. For example, here is the data result set for CQ pages located under /content and using the search term: "Geometrixx".

 Results produced by using the Query Builder API

To read this development article, click: http://helpx.adobe.com/experience-manager/using/using-query-builder-api.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.