I have tried the following 2 ways of starting up the AEM 6.2 publish instance on my local machine after unpacking using -unpack parameter on the jar file.
1. java -jar aem-publish-p4503.jar -r nosamplecontent (publish run mode picked up from file name)
2. java -jar aem-quickstart-6.2.0.jar -r publish nosamplecontent -p4503 (publish run mode picked up from -r parameter)
The problem is with accessing the felix console (http://localhost:4503/system/console) without being logged in initially.
HTTP ERROR: 500
Problem accessing /system/console. Reason:
Here I'll have to first log in to CRX DE lite (http://localhost:4503/crx/de). Login here and then access the Felix console.
Could someone please share some thoughts on this?
Could you please confirm which would be the recommended way to set run modes.
Extract jar first using -unpack then update startup script (<cq_home>/crx-quickstart/bin/
) to change the port/runmode. And use startup script always.
Please note that I am trying this on 2 different fresh publish instances and Geometrixx sites are not installed in both cases.
Then sounds something else happening try to engage official throw support portal to investigate further.
I was bit worried about the exception being thrown on the page instead of prompting for the login screen with case 2. If this is the expected behavior, then we are good.
Also, it would be great if could confirm if the way we could login to a publish instance is by logging in to repository via directly accessing CRX de and then access the felix console. If I login to host:port/libs/cq/core/content/login.html,
/libs/granite/core/content/login.html and after login you might have to explicitly update url to /welcome.
I am prompted with a different login screen compared with author. Screenshot attached below.
Regarding CRX de lite, I am not able to explore the nodes and I am just accessing it just for logging in. (Whenever required, I modify the Davex Servlet value from /server to /crx/server to explore through the repository)
After login go to /system/console & then start the crxde bundle which is in resolved state. Then you should get nodes. For security reason bundles by default not started in publish. Alternatively you can use /crx/explorer/browser/ to access the nodes.