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 the .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.