Automating tests helps in ensuring the integrity of the implementation over the changes in the codebase. It saves cost and laborious efforts of regression in long run avoiding repetitive test activities increasing the reliability of the application. Automating tests is … read the rest.
Tag: AEM
Building Single Page Application (SPA) with Adobe Experience Manager (AEM)
Adobe Experience Manager (AEM) is one of the most popular enterprise web content management systems (WCMS). Traditionally, it’s made for building content heavy websites. Credits to its beautiful java stack, enterprises push its sphere building dynamic web applications on it. … read the rest.
Accessing logs through browser in AEM 6.2
Format
http://localhost:4502/system/console/slinglog/tailer.txt?tail=<N> &name=/logs/<log-file-name>
Examples
http://localhost:4502/system/console/slinglog/tailer.txt?tail=500&name=/logs/error.log
http://localhost:4502/system/console/slinglog/tailer.txt?tail=500&name=/logs/request.log
AEM Multi Site Manager (MSM) – A scenario
Context
Let’s take an example of a hardware business ABC having presence all over North American continent with United States as it central office. ABC sells it hardware through different brand names. ABC procured AEM license and wants to set … read the rest.
Factors driving AEM DAM content hierarchy
- MIME type / meta data schema / Meta data profile / Processing profile – Anything to do with treatment of assets and their metadata.
- Permissions (ACL).
- Brand, regional and language factors.
- Content life cycle esp. archival requirements.
- Browsing behavior.
- Less
Factors driving the site structure design in AEM
- Multi regional, multi lingual needs (MSM – Multi Site Management).
- Content re-use (Through live copy, language copy).
- Content distribution (Roll out).
- Translations
- Access Control (Permissions).
- SEO.
- Consistency and cache selective invalidation.
- URLs
- Site browsing in author site console.
Continuous delivery (CD) and AEM
Technology trends are driven by the business needs. As competition soaring high in the market and software eating the business, the time to convert ideas into usable software is demanded to be very short, in fact in minutes for certain … read the rest.
2-stack 3-layer approach to CMS
Martin flower’s 2-stack 3-layer approach to CMS. It’s strikingly similar to AEM deployment model with missing preview layer. This could be a viable model with AEM OOTB too.
… read the rest.We applied the editing-publishing separation pattern in building a two-stack
AEM and shared file systems (example – EFS) in cloud
Bumped on the shared file system service provided by AWS which they call as Elastic File System (EFS). EFS is more like a file system in a network mounted on multiple compute (EC2) instances. All the compute instances can read … read the rest.
AEM 6.0 Architect Certification tips
I took up Adobe Experience Manager (AEM) 6.0 Architect certification (9A0-385) recently. I thought to jot down few pointers for my fellow enthusiasts aspiring for passing this exam. You may find this post useful. Please post your question as comment … read the rest.
Creating a unique identifier for a node in JCR apart from path.
If you ever want to create an unique identifier for a node in JCR, you would’ve to add a mixin type [mix:referenceable] to it. Once you add this mixin, repository creates a UUID (Unique Idnetifier) for the node automatically.
You … read the rest.
Mechanism to avoid sticky connection for CUG access in AEM 6.1
In a publish farm setup, if there is a need for Closed User Group (CUG) access for protected pages, we would’ve to setup sticky connection in load balancer.
AEM 6.1 introduces a new authentication mechanism using cryptographic token which would … read the rest.
New run mode addressing security in AEM 6.1
AEM 6.1 introduces a run mode ‘nosamplecontent’ which address few security configurations required for production instance. This may not get your production instance 100% secure. You are still asked to use the security checklist to keep a check on known … read the rest.
AEM touch UI Vs Classic UI – Which one to go for.
Clearly, Adobe moving towards touch UI across marketing cloud solutions to provide an unified experience. However, classic UI is going to stay.
Quote from Adobe doc –
… read the rest.Adobe has not announced that the classic UI is deprecated in 6.1; and
When to go for MongoMK in AEM
MongoMK (realized through MongoDB) was introduced to address the need of scaling author nodes horizontally. General notion is that a typical author node supports 30 concurrent users. What if there is more than 30 concurrent users when a single machine’s … read the rest.
AEM and User generated content
AEM was made for traditional one way websites. With Web 2.0, there was question of how AEM suits user generated content as it’s replication concept to share data across publish farm was the bottleneck. AEM trying to meet this gap … read the rest.
Binary data store in AEM
In AEM 6.x, binaries are by default chuncked and stored in the Node data store – Segment (TarMK) or Document (MongoMK). Options provided to store binary data (>4kb) in a separate data store – file system or S3 bucket. Separate … read the rest.
Solr in AEM
Embedded Solr is only recommended for development in cases where you want to deploy a standalone Solr in production (i.e. to simplify the dev setup)
Source: adobe.com… read the rest.