We retail content appears after AEM update from 6.1SP1 into AEM 6.3SP1 | Community
Skip to main content
A
Alex_Popov1
Level 4
January 23, 2018

We retail content appears after AEM update from 6.1SP1 into AEM 6.3SP1

  • January 23, 2018
  • 4 replies
  • 6100 views

Hi All,

During migration from AEM 6.1SP into AEM 6.3 we.ratail content appears.

Before an update we had nosamplecontent runmode.

Someone faced such issue?

Thank you in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

smacdonald2008
smacdonald2008
Level 10
January 24, 2018

TO remove it - simply remove the Package from Package Manager.

V
Venkata_B
Level 2
October 5, 2018

Hi,

Our environments have been upgraded from 6.1 to 6.3. The run mode was samplecontent when it was upgraded. later, we changed the runmode to nosamplecontent and the we.retail and geometrixx stuff wont go away.

I also tried to uninstall we.retail.all package but that doesnt take away the we.retail stuff.

Could someone help me by guiding me what packages need to be uninstalled ?

Thanks,

Srujana

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
January 25, 2018

Never heard of this issue. Can you restart the instance with nosamplecontent mode.

Also, you can remove the package as mentioned.

Kautuk Sahni
sureshr19072451
sureshr19072451
Level 3
April 24, 2018

What happens in case of an in place upgrade process? One of our clients did perform in place upgrade recnently on AEM 6.1 to upgrade to AEM 6.3. After the upgrade was done, infra team from customer side realized the nosamplecontent runmode is missing in sling properties. As per the documentation, the primary runmodes can't be added or changed once the installation process is complete.

I am wondering if there is any clear and complete documentation around the number of changes that we may need perform manually which otherwise nosamplecontent runmode would have automatically taken care of some of the AEM 6.3 security checklist items.

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
April 24, 2018

Use the argument to promote the runmode and things should work well. See sample (1)

nohup sudo -u crx  java -Xmx24G  -jar cq-publish-4503.jar -v -x crx2oak -xargs -- --load-profile segment-fds --promote-runmode nosamplecontent

sureshr19072451
sureshr19072451
Level 3
April 25, 2018

Thanks Kunwar. I believe this command is run to initiate the in place upgrade process. What if we need to add nosamplecontent runmode after finishing the upgrade process and server is up and running. To my knowledge it should be the same behavior as fresh install, which is not possible. Please correct me if I am wrong. And also if possible point me to any documentation related to adjusting the configurations of AEM to meet nosamplecontent behavior.

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
April 25, 2018

Runmodes once set cant be changed. Modes like author, samplecontent once set while starting a new instance can’t be changed.

you can add nosamplecontent mode once the instance has already been started. You’ll have uninstall we.retail pckages to get rid of it

K
Adobe Employee
KunwarsalujaAdobe Employee
Adobe Employee
April 25, 2018

Runmode info get’s stored in sling.options.file if the file is still valid, I think crx2oak and this promote-runmode should still work well.

I might have to test it tomorrow on my local but you can give it a go before I do

Terms & ConditionsAccessibility statement

Loading footer...