Product
Product |
Adobe Experience Manager |
Version |
6.2 |
Release |
Oak Cumulative Fix Packs |
Fixes for the Oak repository are delivered via Oak Cumulative Fix Packs (OCFP) which are fully supported, similarly to standard Cumulative Fix Packs. An Oak Cumulative Fix Pack is self-dependant (no dependencies). You need not worry about finding/resolving dependencies.
Install the latest cumulative fix pack for your AEM version to keep your deployment up-to-date.
If necessary, a diagnostic build on top of the latest OCFP can be made available for validation purpose before the official availability of the next OCFP. The precondition is that you have the latest OCFP running. A diagnostic build only provide the same level quality assurance as a hot fix, therefore it doesn't provide as much quality assurance as a cumulative fix pack, service pack, or product release. All official Oak fixes are released as OCFP which comes with the full support.
For more information on CFP and other types of releases, see Maintenance Release Vehicle.
The Oak Cumulative Fix Pack 1.4.8 (and beyond) contains index definitions. Before deploying the Oak 1.4.8+ CFP, it is recommended to follow the below pre-deployment procedure for preparing the corresponding index during a maintenance window, as indexing can be resource-intensive. This is a one-off procedure (no need to apply it again if you've already done it when applying a previous Oak CFP having a version >= 1.4.8).
Important: for building indices, Oak setting - limit should be set to a higher value, for example, 200000. This also requires enough heap.
During the process of async reindexing, a repository checkpoint is created. Once the indexing task has completed, it must be released as described below, to ensure smooth Revision Garbage Collection later on:
If you are using LDAP integration, then see the Known Issues section below.
Uninstalling an OCFP is not supported.
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
Feb 04, 2019 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
Nov 02, 2018 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
July 27, 2018 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
May 11, 2018 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
March 19th, 2018 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
February 14th, 2018 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
September 23rd, 2017 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
August 9th, 2017 |
Date |
Name |
Fixes |
Release Notes |
June 20th, 2017 |
Date |
Name |
Fixes |
Release Notes |
April 28th, 2017 |
Date |
Name |
Fixes |
Release Notes |
April 20th, 2017 |
Date |
Name |
Fixes |
Release Notes |
March 7th, 2017 |
Date |
Name |
Fixes |
Release Notes |
Feb 27th, 2017 |
Date |
Name |
Fixes |
Release Notes |
Jan 4th, 2017 |
Date |
Name |
Fixes |
Release Notes |
Nov 29th, 2016 |
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
Nov 9th, 2016 |
Date |
Name |
Fixes |
Release Notes |
Oct 21st, 2016 |
Date |
Name |
Fixes |
Release Notes |
Oct 11th, 2016 |
Oak 1.4.7 introduces a change in synchronization behavior of external group memberships (for example, from LDAP):
Mapping an external group to an existing local group is no longer possible. The local group needs to be created by the IDP sync process and also cannot be shared with other external IDPs anymore.
This is required to ensure boundaries between locally established group memberships and external ones, as well as to ensure boundariesbetween multiple IDPs.
The tie to an IDP is done via the now fully protected "rep: externalId" property on groups and users. For details and migration solutions see: https://issues.apache.org/jira/browse/OAK-4397
Date |
Name |
Fixes |
Release Notes |
---|---|---|---|
Oct 5th, 2016 |
Sign in to your account