anuradhar46910715​ Do the below and let me know if it doesn't workNavigate to http://HOST:PORT/system/console/configMgr/org.apache.sling.scripting.java.impl.JavaScriptEngineFactory on your 6.4 instanceChange SourceVM and TargetVM to 'auto' instead of values 1.5 or 1.6 whatever is in the configSaveRe...

I assume you are using the SimpleSearch API and there has been an improvement done in the API to cater to the situation you are facing.This has been taken care of in 6.4 so for 6.3, creating a dedicated index should work as a workaround. If you need to reach to support, you can mention #GRANITE-1831...

When you upload a SCORM resource, 'DAM Update Scorm Asset' kicks into extract the metadata from it and set properties like scormendpoint. So either the scorm resource archive isn't or right format or structure or the workflow never ran.You should try reupload another scorm resource and look at the l...

Colllab components are deprecated and won’t work in 6.2 and 6.3 as a new social framework was inteoduced. You should be relying on to new communities components in AEM

Yes should be fine given we whitelist the ip of monitoring tools in this config

By default AEM doesn’t ship with a cloud services for recaptcha.This must be a custom built utility so you can find that pckage or create one including pckage of etc/cloudeservices to use in dev instance

the complete CUG implementation has been rewritten in 6.3 and now is in accordance to Apache Oak.CUG for assets in AEM is available starting 6.3.1.2 so once you update to the latest maintenance releae, youd be able to use it.one last thing, don’t use CUG using classic UI (although it should be disab...

You can set the Jetty config in Felix console which allows to accept connections from specific IP addresses only. By default it is set to 0.0.0.0 which means accept all  and you can adjust the list per your need. I think it is a multivalued propertyHope this helps.

Karthi,I would recommend to do an inplace upgrade from 5.6 to 6.3 which would automatically migrate the users/groups along with the rep:policy nodes.Things have changed in-terms of properties around authorizableId/rep:principalName and also incase of LDAP users so if you manually move around the use...

Switch to JDK8 and start the instance. That should fix it,