CRXDE is a pre-packaged stand-alone Eclipse application specifically 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.

But more often or not, CRXDE stops working and how much you try, it doesn’t open up. It does nothing when you click ok to login. People try re-installing and what not but the trick is pretty simple. Delete .crxde folder within your home directory. So, if you are using windows it will usually be under c:\ documents and settings\<your user name>.

Yes, Adobe CQ supports clustering. To increase availability, and performance, of your Production environment, it is common to combine multiple author and/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.

The Dispatcher is the Adobe CQ caching and/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.

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.

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