Hi Team,We are using the etc/map for URL shortening for one of our site.
Below are the configurations. Everything is working fine on QA
environment but after moving to pre-prod(UAT) environment URL shortening
is not working. On mouse hover it is showing as full content
path(/content/test/en/work.html) on all the links on page instead of
short one(/work.html) even after implementing the etc/map
configurations. Can you please analysis and suggest us the solution how
to resolve the issue.Requiremen...
Hi Team,We are upgrading our AEM 6.1 Publish server to 6.3 by following
Adobe upgrade steps but while running repository migration commands it's
throwing the below error message. Can anyone please suggest us if there
is any solution to resolve the issue.Repository Migration Command: java
-Xmx4096m -jar cq-quickstart-6.3.0-p4503.jar -v -x crx2oak -xargs --
--load-profile segment-fdsError Message:24.08.2018 01:49:17.937 *INFO*
Thank you for your immediate responseIn my point of view about Lift &
Shift approach is as follows.1. Taking Fresh AEM 6.3 Instance.2. Build
the package with required content & code paths from 6.1.3. Then install
that package in AEM 6.3 Instance.Can you please suggest us whether it is
a recommended approach or not?
Hi All,We are facing many issues while performing the in-place upgrade
from 6.1 to 6.3. So wanted to check whether Lift & Shift approach is
recommended by Adobe also post upgrade by using this approach, does
adobe supports if there are any product issues in future. Please post
the reference links from adobe docs whether Lift & Shift is not
recommended or any other documentation that helps?
Hi kunwar,I have deleted the "/content/projects" from server and reran
the upgrade but still seeing some more exception in upgrade log file.
Also we have raised the Day care ticket.Have you ever faced the
javax.jcr.AccessDeniedException: Root node is not accessible Exception
while upgrading the AEM. Now only Cq62ProjectsCodeUpgrade activity is
successful out of below 20 upgrade activities. Please let me know if
there is any solution for fixing the Root node is not
Hi Kunwar,I have analyzed the upgrade log and found the following error
in upgrade.log. For download the log from below link.Upgrade file
22.03.2018 16:54:00.182 *INFO* [FelixStartLevel]
com.adobe.cq.upgradesexecutor.Activator UPGRADE STARTS - StartupMode is
UPDATE22.03.2018 16:55:02.579 *ERROR* [FelixStartLevel]
com.adobe.cq.upgradesexecutor.Activator OSGI installer finished and the
upgrade task condition was not satisf...
Thank you Hemanth for your reply. I have modified the configuration
according to AEM 6.3, still getting the same error messages during the
AEM 6.3 startup.
Log21.03.2018 12:43:09.711 *ERROR* [FelixSt...