by default you don't need to do anything and dynamic loading of the serialization agent would take care of everything. If incase things fails, add (1) to your startup script (start.bat or terminal along with other jvm arguments) where you adjust the path of the notsoserial.jar per your deployment di...
DNashKL Check the path '/content/forms/af' and check the rep:policy nodes under it as one of the users or permissions might be missing here. Compare it with OOTB AEM instance and make adjustments
Can you check if mp-editors and content-authors group exists in the CRX ? Also, check if the "random authorizable" setting ws changed in AEM 6.1 ? If yes, this would have to reverted prior to the upgrade to 6.3
Can you add '-Djavax.net.debug=all' to your startup arguments, restart the system and retest the scenario ? Once replicated, share the stdout.log for review
content fragments in my opinion are used to expose assets from AEM so they can consumed within aem or externally. As you assets you are outside AEM, either you expose an API on the system where your assets are stored and use it OR import the metadata properties using importer and create node struct...
You can try the following approach - Use contextHub gelocation store for identifying the location of the user- Have images tagged with city tags or embed metadata pointing to city, state or province to identify the location of the assets- Use reverse geolocation APIs by google maps to identify nearb...
This looks like a case of index corruption. I would suggest to first update your instance to the latest oak release and once completed, reindex the damAssetLucene index