Hi, not, on an application level there shouldn't be any changes required. I think that on a product level some validations were required and IIRC some Oracle-isms had to be changed Jörg

Hi @nutmix When you run(double click) the jar file, it will read the the jar file name and will pick port number from file name itself. If you don't follow jar file naming conversion (-p4502/-p4503), if port 4502 is available then it will take port 4502.If you are executing/running bath file, you should change the port explicitly by opening it in any text editor.Update the CQ_PORT in start.bat/quickstart.bat before running it.-AG

@nutmixI followed the same link and I got my pages replicated without any issue. Please have a look from the point "Configuring Replication for Multiple Publish Instances". The exact link for the same https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/replication.html?lang=en#configuring-replication-for-multiple-publish-instances I was able to view the pages from my publisher using http://localhost:4508/content/wkndmuzik/us/en/homepage.html Also to view the page ...

was crx-quickstart folder copied from Windows? if so, you can try to recreate the instance. delete the crx-quickstart and run 'java -jar aem-author-p4502.jar' again.Also, I wouldn't use -XX:MaxPermSize param, since permgen space is gone with java 8.

Thanks for the reply. Is the quickstart jar for non cloud the same as the quickstart jar for cloud? I.e. if I have both the non cloud and the cloud downloads, it doesnt matter which I use?