Home › Core Learning Journey › Lab 1 — Explore the consoles

Lab 1 — Explore the consoles

Purpose: Build muscle memory for the four consoles you will use daily: Sites, CRXDE Lite, OSGi console, Package Manager.

Who this page is for

AudienceWhy it matters to you
All engineersPairs with Session 1; requires a running local author

Prerequisites

Local author instance running on :4502 (Environment setup).

Exercises

1. Sites console (10 min)

  1. Open /sites.html. Create a folder-level page structure: PHI Academy Site → Plans.
  2. Create a page Gold Hospital Cover from any available template.
  3. Open it in the editor; add a Text component; note the edit vs preview modes.

2. CRXDE Lite (15 min)

  1. Open /crx/de and locate your new page under /content.
  2. Expand its jcr:content node — find the Text component node you authored and its text property.
  3. Observe: everything you did in the editor is just nodes and properties. This is the single most important

realisation in AEM onboarding.

3. OSGi web console (10 min)

  1. Open /system/console/bundles — find the state column (Active/Installed/Resolved).
  2. Open /system/console/configMgr — search for "Apache Sling" to see live configuration.
  3. Open /system/console/status-slinglogs — find error.log; keep this location in mind forever.

4. Package Manager (10 min)

  1. Open /crx/packmgr. Build a package filtered to your /content/phi-academy page.
  2. Download it, unzip it locally, and inspect jcr_root/ — content packages are just zipped repository trees.

Checkpoint

QuestionYou should be able to answer
Where did your authored text physically go?A property on a node under the page's jcr:content
How would you check if a deployment's bundle started?/system/console/bundles, state = Active
Where do server errors appear first?error.log via the logs console

Quick navigation

↑ SectionCore Learning Journey⌂ HomeAcademy home

Related pages