Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

WCM 5.5 to AEM 6.1 Migration Scenario

Avatar

Level 2

Has somebody already successfully migrated 5.5 to 6.1?
Here's what I have done so far (unfortunately still unsuccessfull) 

 

1) workspace.xml (com.day.crx.query.lucene.LuceneHandler):
 <param name="enableConsistencyCheck" value="true" />
 <param name="forceConsistencyCheck" value="true" />
   <param name="autoRepair" value="true" />
 
2) Start Instance
3) Copy 6.1 jar to root folder
4) Stop Instance once up and running
5) Remove config from 1 (make sure no custom authentication)
6) java -jar cq-publish-8484.jar -unpack
7) java -jar cq-publish-8484.jar -v -x crx2oak
😎 java -jar cq-publish-8484.jar -v -x crx2oak
9) java -Xmx4096m -XX:MaxPermSize=2048M -jar cq-publish-8484.jar -v -x crx2oak -xargs -- -o migrate

-> Here I get a successfull migration message in the logs

10) java -jar cq-publish-8484.jar -r publish,crx3,crx3tar,nosamplecontent

-> Here I get a AuthenticationSupport service missing. Cannot authenticate request.

Any idea?

1 Accepted Solution

Avatar

Correct answer by
Employee

Hi,

"localhost:8484/system/console" shouldn't be a problem if you can log into "/crx/de/index.jsp"

Can you check error.log again please?

Regards,

Opkar

View solution in original post

0 Replies

Avatar

Employee

H,

the error you are seeing is a symptom of an exception during startup, it is likely to have occurred much earlier in your error.log. Can you check and print it here?

Regards,

Opkar

Avatar

Level 2

I finally found it, it's related to a known issue on windows.

Here's my windows migration scenario :
 

1) workspace.xml (com.day.crx.query.lucene.LuceneHandler):
   <param name="enableConsistencyCheck" value="true" />
   <param name="forceConsistencyCheck" value="true" />
   <param name="autoRepair" value="true" />
 
2) Start Instance
3) Copy 6.1 jar to root folder
4) Stop Instance once up and running
5) Rename new 6.1 jar to have the name of the old 5.5 jar
6) Remove config from 1 (make sure no custom authentication)
7) java -jar cq-publish-7676.jar -unpack
😎 java -jar cq-publish-7676.jar -v -x crx2oak
9) java -jar cq-publish-7676.jar -v -x crx2oak
 
Windows:
org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.cfg:
Backslash to Frontslash change in file : path=./crx-quickstart/repository/repository/datastore
 
10) java -Xmx4096m -XX:MaxPermSize=2048M -jar cq-publish-7676.jar -v -x crx2oak -xargs -- -o migrate
11) java -jar cq-publish-7676.jar -r publish,crx3,crx3tar,nosamplecontent (avoid sample content in live environment)
12) Regular startup as service

I did it twice and it worked fine.

 

There's one open topic left :

1) I can login to crx

2) I cannot login to system/console:

10.08.2015 15:21:39.941 *ERROR* [qtp825873524-89] org.apache.sling.auth.core.impl.SlingAuthenticator doLogin: Cannot login: No AuthenticationHandler available to handle the request

-> I changed the admin password to a new one (change it to the existing one didn't work). No I can access the system/console.

Avatar

Correct answer by
Employee

Hi,

"localhost:8484/system/console" shouldn't be a problem if you can log into "/crx/de/index.jsp"

Can you check error.log again please?

Regards,

Opkar

Avatar

Employee

After upgrade, once you have logged in to CRX or Content Explorer, you should be able to login to other modules including system console.