JCR (Java Content Repository)

🔍 What Is It?

JCR in AEM is the Java Content Repository that stores pages, components, assets, and configuration as nodes and properties. AEM uses the Java Content Repository, implemented through Apache Jackrabbit Oak, as the storage layer for site content, components, templates, assets, and many configuration areas. In practice, JCR is the content tree behind paths like /content, /apps, /conf, and /content/dam.

When people search for "AEM JCR" or "what is JCR in AEM," they usually want the direct answer: JCR is the repository model that stores everything as nodes and properties, and AEM reads that tree to render pages, resolve resources, and support authoring.

Quick Facts

• →Used in: Pages, components, DAM assets, templates, permissions, and repository-backed configuration
• →Best for: Understanding how AEM stores content and how Sling resolves real page data
• →Interview importance: High because JCR is a core AEM fundamentals topic
• →Production relevance: High because repository structure affects queries, performance, permissions, and debugging
• →Related topics: Sling, CRXDE Lite, client libraries, components
• →Last updated: July 2026

Key Concepts

• →Node - A repository item similar to a folder or file, such as cq:Page or nt:unstructured
• →Property - A key-value pair stored on a node, such as jcr:title
• →Node type - The structure rules for a node and the child nodes or properties it can contain
• →Path - The unique location of a node, such as /content/mysite/en/home
• →UUID - A stable identifier for repository-level operations

Common Node Types

• →cq:Page - An AEM page
• →cq:PageContent - The content node under a page
• →cq:Component - A component definition
• →nt:unstructured - A flexible content node
• →dam:Asset - A DAM asset

🎯 Why Do We Need It?

JCR matters because AEM is a repository-first platform. Pages, dialogs, authoring values, assets, and many configuration areas all depend on the way content is structured in the repository.

Developers who understand JCR can read content paths faster, debug authoring issues with more confidence, and reason clearly about Sling Models, permissions, indexing, and query behavior.

Interview Relevance

• →Interviewers ask JCR to test whether you understand the storage model behind AEM pages and components
• →A strong answer explains nodes, properties, paths, and how sling:resourceType connects content to rendering
• →Senior interviews usually push into query performance, repository structure, permissions, and Cloud Service-safe repository changes

🏗️ What Happens in Real Projects?

Production Usage

JCR is used every time an author creates a page, updates a component dialog, uploads an asset, or publishes a content structure that AEM later renders through Sling. Repository-backed paths also drive queries, permissions, content packages, editable templates, and many operational debugging flows.

For example:

• →Creating /content/mysite/en/home creates a cq:Page and a jcr:content node
• →Dialog values are saved as properties on component content nodes
• →Component definitions and template structures are stored in repository paths such as /apps and /conf
• →Sling Models often read JCR-backed resources and properties during rendering

Where to go next

• →Read Sling after JCR so repository structure connects to resource resolution and models
• →Read Client Libraries after that to connect stored content to frontend delivery
• →Use AEM interview prep once you can explain JCR paths, node types, and sling:resourceType clearly

⚙️ How It Works

Node Structure Example:

/content/mysite/en/home          <- cq:Page node
  jcr:content/                   <- cq:PageContent node
    jcr:title = "Home"
    sling:resourceType = "mysite/components/page/home"
    root/                        <- nt:unstructured
      hero/                      <- nt:unstructured (hero component)
        sling:resourceType = "mysite/components/hero"
        heading = "Welcome"
        ctaLabel = "Learn More"

Accessing JCR in Code:

// From a Sling Model
@Inject
private Resource resource;

// Get the ValueMap (properties)
ValueMap props = resource.getValueMap();
String title = props.get("jcr:title", "Default Title");

// Navigate to child
Resource hero = resource.getChild("root/hero");

// JCR Session (lower-level)
Session session = resourceResolver.adaptTo(Session.class);
Node node = session.getNode("/content/mysite/en/home");

💻 Example

JCR Node Structure — How a typical AEM page looks in the JCR.

/content/
  mysite/                        [sling:Folder]
    en/                          [sling:Folder]
      home/                      [cq:Page]
        jcr:content/             [cq:PageContent]
          jcr:title: "Home Page"
          jcr:description: "Welcome to My Site"
          sling:resourceType: "mysite/components/page/home"
          cq:template: "/conf/mysite/settings/wcm/templates/home"
          root/                  [nt:unstructured]
            sling:resourceType: "wcm/foundation/components/responsivegrid"
            hero/                [nt:unstructured]
              sling:resourceType: "mysite/components/hero"
              heading: "Welcome to My Site"
              subtext: "Discover our products"
              ctaLabel: "Shop Now"
              ctaLink: "/content/mysite/en/products"

🤔 Common Confusions

🚨 Common Production Issues

✅ Best Practices

🏛️ Architect's Note

💬 Frequently Asked Questions

🎯 Key Takeaways

🔗 Related Topics

🎯 Practice this topic in interviews

↗ Where this topic fits