AEM System Overview


ASO identifies general information about the AEM instance. Each finding provides one value of a particular type of system information.

Subtypes are used to identify different types of information:

  • aem.version: The AEM version.
  • aem.product: Detection of the use of an AEM product (Commerce, Forms, etc.).
  • node.count: The approximate node count of a certain type (Page, Asset, etc.) and the grand total of nodes.
  • The node store implementation type (SegmentNodeStore, DocumentNodeStore) and its size.
  • The data store implementation type (FileDataStore, S3DataStore, AzureDataStore).
  • maintenance.task: A maintenance task.
  • slow.query: A slow query.
  • group.membership: The number of users and sub-groups ( direct/declared members only ) in a group.
  • cqtag.count: The number of CQ tagged assets.
  • smarttag.count: The number of Smart tagged assets.
  • ccom.version: The version of Core Component package.
  • instance.type: The AEM instance type (author|publish).
  • unprocessed.asset.count: The number of unprocessed assets.
  • vanity.url.count: The number of vanity URLs.
  • index.size: Total Migratable Lucene index size.

Possible implications and risks

  • The AEM version, node counts, group membership, node store, data store implementation types, CQ Tag Count, Smart Tag Count, Core Component version, AEM instance type and Unprocessed asset count are provided for informational purposes.
  • The higher number of vanity URLs (>1000) may put a load on Dispatcher and the Publish servers with expensive queries.
  • The custom application may rely on products or features not available in AEM as a Cloud Service.
  • Upgrading with unsupported features may result in a failed upgrade and a non-functional application.

Possible solutions

  • AEM upgrades with unsupported products or features are not recommended and may not supported.
  • The unprocessed assets must be processed and the dam:assetState property on the jcr:content node of the Asset must be set to “processed” or remove these assets from the migration set before migrating to AEMaaCS.
  • Vanity URLs could be replaced with Apache Rewrites.
  • Review the release notes to learn about the latest changes in AEM as a Cloud Service.
  • Please reach out to our AEM Support Team to get clarifications or to address concerns.

On this page