CRX Access Methods
You have the choice! When it comes to accessing information, interoperability between software and data formats is key. Using industry-approved standards and widely deployed open technologies,
allows leveraging infrastructure and information for use cases not
initially predictable. Open and sustainable formats and protocols
enable your enterprise to move content management to the next level.
The Day CRX repository allows various ways to interact with the managed content, both for developers with the Java Content Repository standard, and desktop users with the ability to access Day CRX like a traditional network drive. The repository supports all file formats and can extract, convert and transform content on request.
Desktop Access

Day CRX has built-in support to access the repository via the widespread used open WebDAV protocol. On top of that, Day CRX implements the Common Internet File System protocol defined by Microsoft. Both allow the desktop user (Microsoft Windows, Apple MacOS X and Linux) to easily and securely create, read, update and delete files and folders within Day CRX.
Administrators
Bulk import and export, full or partial transfer between Day CRX repositories can easily be achieved with the built-in administration tools.
Developer Access
The Java Content Repository (JCR) application programming interface
allows Java developers to make use of the full potential of Day CRX.
The developed Java application can run on the same infrastructure or
use the performance-optimized remote connector.

Web application developers can use the built-in rapid web development framework Apache Sling. The RESTful framework provides full-featured access to the JCR and is the ideal foundation for a content service architecture. The Day CRX ships with a JavaScript connector - that provides web site developers direct repository access from within the web browser of the users.
Developers in none-Java environments have various choices - one of them is an extended WebDAV protocol that is mapping the functionality provided by the JCR API to HTTP-based WebDAV.
Developers in none-Java environments have various choices - one of them is an extended WebDAV protocol that is mapping the functionality provided by the JCR API to HTTP-based WebDAV.
