AEM Foundation & Repository
You are reading the AEM 6.3 version of AEM Foundation & Repository.
- The new version of the Oak Segment Tar present in AEM 6.3 requires a repository migration. This step is mandatory if you are upgrading from an older version of TarMK or want to switch the new Segment Tar from another type of persistence. For more information on what the benefits of the new Segment Tar are, see the Migrating to Oak Segment Tar FAQ.
- AEM 6.3 implements the 2017 Adobe Marketing Cloud UI design. Further - the user interface has been fully transitioned to the Web Component based Coral 3 UI framework.
- The Classic UI is included in AEM 6.3. Mind that most entry points from within the Touch-optimized UI, that were enabled by default in version 5.6-6.2, to switch to the Classic UI equivalent have been disabled by default.
- Adobe is planning to deprecate the Classic UI in AEM in April 2018. The 2018 release of AEM will still contain the Classic UI as it is part of current AEM release. Following that, Adobe is planning to remove the Classic UI from AEM in April 2019. Read more.
- Pre-Upgrade Maintenance Optimization has been enhanced for automation by allowing pre-upgrade tasks to be triggered using JMX.
- Pre-Upgrade Compatibility Checks allow you to quickly perform compatibility checks on your APIs with the new version
- Post Upgrade Check Automation makes it easier to check for errors after an upgrade.
- Upgrade process has been made more resilient
- Please see https://docs.adobe.com/docs/en/aem/6-3/upgrade.html for more details on these features.
- Cost efficient CDN implementation for DAM using Amazon S3 and Amazon CloudFront
- Security - Configuration
- Support for all OSGI configuration properties to be stored in a protected encrypted form instead of clear text
- Configurable Admin password; This feature allows admin password to be set using the command line when installing a new AEM instance.
- Security - CUG
- Security - OAuth
- AEM's OAuth server can revoke previously granted access tokens and refresh tokens
- Custom OAuth Scopes can be defined for use by AEM's OAuth server
- Security -CORS
- Support for Cross-Origin Resource Sharing (CORS) requests with separate policies for different origins and resource paths
- Security - UI
- Disk & Memory monitoring: OS-managed resources like disk and memory can now be viewed together with AEM activities on the timeline view in the Operations Dashboard Monitoring section. This enables observations on how AEM activities impacts system resources and vice versa.
- Content Distribution Monitoring exposes status of content for activation in Content Distribution via JMX
Was this helpful?
Thank you for submitting your feedback.