Configure replication and transport users

Statement - why to use separate user for the replication and Transport users.

Solution :

§  The transport user should not be the admin user.

§  The replication user should not be the admin user

§  For Transport user: set up a user on the publish system that has only access rights to the relevant portions of the publish system and use that user's credentials for the transport.

§  For replication user: a user who can only see content that is supposed to be replicated. The replication user is used to collect the content to be replicated on the author system before it is sent to the publisher.

Why Replication Logs

Statement - Why Replication log configuration is needed

Pre-requisite :

                     -  AEM 6.1

Solution :

Why:

•       Keeps error.log from getting bloated

•       Isolates replication errors and warnings

How:

•       Go to Felix console and search for Apache Sling Logging Logger:

•       Log File: logs/replication.log

•       Log Level: Info

•       Logger: com.day.cq.replication

•       Add an Apache Sling Logging Writer (for log rotation)

•       Log File: logs/replication.log

How to prevent expansive queries from overloading the systems in AEM 6.1

Statement - How to  prevent expansive queries from overloading the systems

 Environment :

                         - AEM 6.1

Solution:

Add these JVM parameters in the AEM start script to prevent expansive queries from overloading the systems.

-Doak.queryLimitInMemory=500000

-Doak.queryLimitReads=100000

-Dupdate.limit=250000

-Doak.fastQuerySize=true

JVM arguments related findings

Finding ID	Title	Total Risk	Effort to fix
JVM1	Doak.queryLimitInMemory	High	Low
JVM2	Doak.queryLimitReads	Medium	Low
JVM3	Dupdate.limit	Medium	Low
JVM4	Doak.fastQuerySize	High	Low