Digital Plunge - have you already taken the plunge?

I recently finished a book named 'Digital Strategy' by Alexander Rauser. Alexander has given current day problems during any Digital transformation and pragmatic solutions for that. Having worked in the IT industry for 17 years and last 10 years mostly into Digital Transformations for most of the fortune 500 companies, it was quite relevant to me. If you are also part of any digital transformation of any organization in any capacity, you will find it helpful too. Over the last decade, companies have thought of digital strategy as a means to market new technology or recognize upcoming trends. However, today few of those companies do realize that Digital Strategy is all about continuously improving your business to stay ahead in the curve, but some are still stuck in the old mindset. It's surprising to see  'Strategy' is missing from the Digital Strategy for many of the transformations happening, rather the focus is just on 'Marketing' (Digital Marketing

Users are contributing content more than ever before, and it's getting difficult for Enterprise systems to manage it. To cope up with this, Adobe keeps evolving their UGC ecosystem. I think it was called  Social Collaboration tool  before CQ 5.5 After CQ 5.5 it was called  Social Communities  (So-Co),  this was shortened to So-Co. With AEM 6, this was rebranded as AEM Communities. At that point, all UGC components functionality was moved into Communities from AEM. So forums, comments/ratings etc. With 6.2, the concept of a central store was introduced, so content was saved outside of AEM in a central location where all instances would read and write, this can be Mongo, or JCR (but only for single instances) or it can be cloud storage (better name than social storage) which as you know carries a cost. And then Adobe overtook another product named Livefyre which is managed comments and other UGC content in a SAAS ki

Recently I worked on one of the major enterprise project in Adobe for upgrading AEM from 5.6.1 to 6.2. It took me and my team almost 10 months to upgrade this enterprise system, due to the complexity of the project. After working on multiple upgrade projects on AEM now, I feel that even though Adobe documentation does provide lots of help, but there is still a huge difference in plan, timelines (may vary from 4 weeks to 10 months), and execution for each project (completely depends on the current architecture and topologies). I am trying to consolidate my experience and learnings on these projects in my blog. Hope it will be helpful for some of you planning for AEM upgrade I will cover each phase separately as below Kickoff, Planning & estimation Analysis/assessment/discovery workshop Actual upgradation   Post upgrade Activities Performance tuning activities Go live & Cutover Maintenance activities

There are many situations when you need to compare two AEM instances. The easiest approach is to compare packages, bundles and configurations. Here is how you can do it - Compare package managers  http://localhost:4502/crx/packmgr/service.jsp?cmd=ls Compare Bundles  http://localhost:4502/system/console/bundles.json Compare Configurations  http://localhost:4502/system/console/status-Configurations Compare system properties  http://localhost:4502/system/console/status-System%20Properties You can then compare these manually using any text comparers. Another quicker approach is to compare those using below tools by Aemstuff.com - http://www.aemstuff.com/tools/cti.html http://www.aemstuff.com/tools/coi.html

Large portion of a developer work in any Web content management tool is to display content. Here are the three ways to do so in AEM/CQ5 - 1. Through Properties Object - The properties object is an instance of the ValueMap class and contains all properties of the current resource. For example - properties.get("jcr:title") 2. Through Current Page Object – The currentPage object is an instance of the Page class, which provides some methods to access content. For example - currentPage.getTitle() 3. Through Current Node Object – The currentNode object is an instance of the Node which provides access to content via the getProperty() method. For example - currentNode.getProperty("jcr:title").getString() Here is the complete code snippet for trying all these three options Let’s test this script by requesting a page in Site Admin that implements this “Page component”. Thank you!