Oak Documentation and Best Practices

• Minimal TarMK architecture guidelines
  
• Single TarMK instance
• TarMK cold standby
• TarMK farm (for Publish tier)

TarMK performance

• TarMK performance benchmarks

High availability

• TarMK cold standby

• MongoMK cluster with failover (for AEM Author tier)
• Minimal MongoDB deployment for AEM

Requirements for using MongoMK

• Supported MongoDB versions
• Prerequistes and recommendations for MongoMK deployments

• TarMK vs MongoMK guidelines
• Exceptions for choosing MongoMK over TarMK for AEM Author
• Exceptions for choosing MongoMK over TarMK for AEM Publish
• AEM architecture scaling guidelines

RDBMK is under restricted support, only to be used with AEM Forms Author, and limited to the supported RDBMS.

The data store is the part of the repository that stores large binary files, where as the nodestore stores small data like node definitions and properties. It is recommended the nodestore is persisted by the mechanism aligned with the selection microkernel (TarMK stores the nodestore in tar files, MongoMK stores the nodestore in MongoDB) however the data store should always be stored in the file system or an Amazon S3 bucket(s).

File Data Store (FDS)

• The File Data Store (FDS) is the default data store type for TarMK and MongoMK in AEM 6.3.
• FDS can be persisted on local disk, NAS or SAN. 
• FDS is also sharable via the Shared Data Store configuration (see Shared Data Store section below).
• Any production deployment should have at a minimum a File Data Store configured for all AEM instances (Author and Publish).

Amazon S3 Data Store (S3DS)

• The Amazon S3 Data Store (S3DS) stores files in Amazon S3 buckets. 
• S3DS is "infinitely scalable" and recommended for Data Stores over 5TB in size.
• S3DS is sharable via the Shared Data Store confguration (see below).

Shared Data Store

The Shared Data Store configuration allow a single Data Store to be used by multiple AEM instances. This offers a number of efficiencies for AEM systems where large/volumes of files are shared across AEM instances, but also has several limitations.

General guidelines

• Disk space
• Virtualization
• Parallelization of AEM instances
• AEM Author sizing calculations
• AEM Publish sizing calculations
• AEM scalability guidelines
• Disk sizing for AEM Assets (Excel-based Disk Sizing tool)

TarMK guidelines

• TarMK performance benchmarks

MongoMK guidelines

• MongoMK Disk and RAM recomendations
• MongoMK performance benchmarks

• Recommended TarMK settings
• Nodestore configuration

Cold standby

• TarMK cold standby set up
• Cold standby configuration parameters
• First time synchronization

• Recommended MongoMK settings
• Nodestore configuration
• Data Store configuration

• OS optimizations and NUMA
• Linux configurations and requirements
• Using virtualised environments (VMWare ESX and Amazon Web Services)

• Network configuration

MongoDB security

• MongoDB security configurations

Dispatcher

• MongoMK deployments require special Dispatcher configurations

Data Store configurations

• File Data Store
• Amazon S3 Data Store

Shared Data Store

• Configuring Shared Data Store
• Configuring binaryless replication

• AEM Assets monitoring best practices

MongoMK 

• MongoDB Cloud Manager
• MongoDB Ops Manager
• Operating system monitoring
• Log aggregation

Data Store

• Checking for Data Store consistency

• Running online revision clean-up
• Monitoring online revision clean-up
• Troubleshooting online revision clean-up
• Online revision clean-up and backups

Offline revision clean-up

• When to use offline revision clean-up
• Running offline revision clean-up
• Increasing performance of offline revision clean-up
• Offline revision clean-up FAQ
• TarMK offline clean-up - Increase performance, avoid memory issues and track progress    

Revision clean-up and TarMK cold standby

• Cold standby repository maintenance

Garbage collection is the process of re-claiming disk space form the repositories Data Store. Garbage collection must be run frequently, during off-hours.

• Running garbage collection via the Operations console
• Running garbage collection via JMX MBean
• Scheduling the execution of garbage collection
• Garbage collection and backups

Garbage collection on a Shared Data Store

• Running garbage collection on a Shared Data Store

Gargbage collection and TarMK cold standby

• Cold standby repository maintenance 

General considerations

• Backup frequency considerations
• Avoid running concurrently with Data Store garbage collection or Nodestore revision clean-up

Offline backup

• Offline snapshot-based backup

Online backup

• Configuring AEM online backup
• AEM online backup Operations console
• AEM online backup JMX MBean
• AEM online backup HTTP API (for automation)
• AEM online backup performance benchmarks
• Filesystem snapshot backups
• Package-based backups

Restoring from backup

• Restoring online backups

MongoDB backup and restore

• Use the native MongoDB backup tools

All microkernels

• Analyzing slow or blocked processes
• Common AEM Sites performance issues
• Common AEM Assets performance issues
• Memory issues
• Indexing issues
• Corrupt Oak indexes
• Slow re-indexing

TarMK

• Analyzing unusual repository growth
• Fix inconsistencies when SegmentNotFound issues occur

• Key AEM 6.3 enhancements
• AEM version feature comparison matrix
• AEM 6.3 release notes

Key repository features

• Online revision clean-up

AEM upgrades can be broken out into phases, each phase with a set of prepatory and execution steps.

Overview

• AEM upgrade overview

Planning the upgrade

• Planning the upgrade to AEM 6.3
• Understanding the crx2oak migration tool

Pre-upgrade steps

• Pre-upgrade maintenance tasks
• Same-name-sibling (SNS) detection for TarPM to Oak upgrades

Understanding the upgrade procedure

• Upgrading TarMK AEM Author
• Upgrading MongoMK Author cluster
• Upgrading TarMK Publish farm
• Final upgrade steps

Performing the upgrade

• Perform the in-place upgrade

Post-upgrade steps

• Post-upgrade checks and troubleshooting

AEM feature considerations

• Upgrading search forms
• Deprecated and removed features
  

Custom application considerations

• Upgrading code and customizations
• Obsolete OSGi bundles and APIs

• Post upgrade checks and troubleshooting

Oak provides two main types of indexes: Lucene Property Indexes and Property Indexes.

• Lucene Property Index vs. Property Index
• AEM provides a Lucene Fulltext index and a Counter index, however these are used as-is.

SOLR server integration

• AEM supports integrating with SOLR server to persist indexes, but this is rarely required or recommended.

• Overview of Lucene Property Indexes
• Lucene Property Index complete specification

• Overview of the Property Index
• Property Index complete specification

• Reasons for re-indexing
• How to re-index

Tools and approaches

• The Index Manager to re-index any index
• Text pre-extraction for re/indexing of Lucene indexes with binary text extraction
• reindex=true to re-index any index
• refresh=true to refresh lucene indexes
• Abort re-indexing

Troubleshooting

• Slow re-indexing

Writing queries

• Recommended query languages: Query Builder, JCR-SQL2 and XPath

Understanding and troubleshooting queries

• Troubleshooting slow queries guide
• Explain Query tool
• Query Builder debugger
  • http://host:port/libs/cq/search/content/querydebug.html
• Query logging
• AEM Chrome Plug-in^† with Sling Log Tracer v1.0.2+

† denotes community supported tooling.