Highlighted

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

Avatar

Avatar

Alex_Popov1

Avatar

Alex_Popov1

Alex_Popov1

23-01-2018

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.

Replies

Highlighted

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Answer

2.3K
smacdonald2008

24-01-2018

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

Highlighted

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

969

Correct Answer

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.6K

Likes

969

Correct Answer

1.1K
kautuk_sahni
Community Manager

25-01-2018

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

Also, you can remove the package as mentioned.

Highlighted

Avatar

Avatar

sureshr19072451

Avatar

sureshr19072451

sureshr19072451

24-04-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.

Highlighted

Avatar

Avatar

Kunwar

Employee

Avatar

Kunwar

Employee

Kunwar
Employee

24-04-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

Highlighted

Avatar

Avatar

sureshr19072451

Avatar

sureshr19072451

sureshr19072451

24-04-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.

Highlighted

Avatar

Avatar

Kunwar

Employee

Avatar

Kunwar

Employee

Kunwar
Employee

24-04-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

Highlighted

Avatar

Avatar

Kunwar

Employee

Avatar

Kunwar

Employee

Kunwar
Employee

24-04-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

Highlighted

Avatar

Avatar

Kunwar

Employee

Avatar

Kunwar

Employee

Kunwar
Employee

24-04-2018

Can’t add*

Note: mobile version of forums don’t allow me to edit for some reason

Highlighted

Avatar

Avatar

sureshr19072451

Avatar

sureshr19072451

sureshr19072451

25-04-2018

Yes, that was my understand as well. Thanks for your time.

I would still look forward to hear on the detailed steps to achieve nosamplecontent runmode behavior on the server which got installed without nosamplecontent runmode.