Debugging AEM as a Cloud Service with Repository Browser
- Applies to:
- Experience Manager as a Cloud Service
- Topics:
- Developer Tools
CREATED FOR:
- Beginner
- Developer
Repository Browser is a powerful tool that provides visibility into AEM’s underlying data store, allowing for easy debugging of AEM as a Cloud Service environment. Repository Browser supports a read-only view of the resources and properties of AEM on Production, Stage, and Development, as well as Author, Publish, and Preview services.
Repository Browser is ONLY available on AEM as a Cloud Service environments (use CRXDE Lite to debug the local AEM SDK).
Accessing Repository Browser
To access Repository Browser on AEM as a Cloud Service:
-
Ensure that your user has the required access
-
Log in to Cloud Manager
-
Select the Program containing the AEM as a Cloud Service environment to debug
-
Open the Developer Console corresponding to the AEM as a Cloud Service environment to debug
-
Select the Repository Browser tab
-
Select the AEM service tier to browse
- All Authors
- All Publishers
- All Previews
-
Select Open Repository Browser
The Repository Browser opens for the selected service tier (Author, Publish, or Preview) in a read-only mode, displaying resources and properties your user has access to.
Publish and Preview access
By default, access to Publish or Preview is limited, reducing the available resources in Repository Browser. To view all resources on Publish (or Preview) add users to a Publish (or Preview) Administrators role.
Experience Manager
- Overview
- Playlists
- Introduction to AEM as a Cloud Service
- Experience Cloud integrations
- Underlying Technology
- Edge Delivery Services
- Cloud Manager
- Local Development Environment Setup
- Developing
- Debugging AEM
- AEM APIs
- Content Delivery
- Caching
- Accessing AEM
- Authentication
- Advanced Networking
- Security
- AEM Eventing
- Migration
- Content Transfer Tool
- Bulk Import of assets
- Moving to AEM as a Cloud Service
- Cloud Acceleration Manager
- Content Fragments
- Forms
- Developing for Forms as a Cloud Service
- 1 - Getting started
- 2 - Install IntelliJ
- 3 - Setup Git
- 4 - Sync IntelliJ with AEM
- 5 - Build a form
- 6 - Custom Submit Handler
- 7 - Registering servlet using resource type
- 8 - Enable Forms Portal Components
- 9 - Include Cloud Services and FDM
- 10 - Context aware cloud configuration
- 11 - Push to Cloud Manager
- 12 - Deploy to development environment
- 13 - Updating maven archetype
- Create Adaptive Form
- Custom submit service with headless form
- Create address block component
- Create clickable image component
- AEM Forms and Analytics
- Creating Countries Dropdown Component
- Creating Button Variations
- Using vertical tabs
- Using output and forms service
- Document Generation in AEM Forms CS
- Using Forms Document Services API
- Document Generation using Batch API
- PDF Manipulation in Forms CS
- Integrate with Marketo
- Store Form Submissions with Blob Index Tags
- Prefill core component based form
- Azure Portal Storage
- Save and Resume form filling
- Create Review Workflow
- Acrobat Sign with AEM Forms
- Integrate with Microsoft Power Automate
- Integrate with Microsoft Dynamics
- Integrate with Salesforce
- Store form submissions in one drive and sharepoint
- Developing for Forms as a Cloud Service
- Asset Compute Extensibility
- Multi-step Tutorials
- Expert Resources