Mostly in all multi-locale projects, every developer face this scenario where client wants that every locale-specific publisher should be configured for publishing or replicating the content in aem. It is also recommended by adobe to avoid use of admin user for publishing all content.
Let’s consider below scenario where:
We have one author instance and multiple publisher connecting to the same author.
Each publisher is very specific to serving the content related to that region.
US publisher: US sites are hosted in this publisher and serves the same to end-user.
EMEA publisher: All EMEA sites content hosted here
APAC publisher: Only APAC content is hosted here.
If Content author triggers any content from the author instance, all the replication queue gets enabled and move content to all publisher. Due to this replication mechanism, all content be synced with all publisher and creates unwanted storage on publisher instance.
How to restrict data between author and publishers:
We need to create specific users related to each publisher on author USERADMIN [ http://localhost:4502/useradmin ] console.
EX: For author instance , create a user named “japan-queue” and provide the required permission as below.
Assign Specific Permissions to Users from Useradmin console:
Go to USERADMIN [ http://localhost:4502/useradmin ] console.
Create a new user with the name “japan-queue“. [ Click here to learn how to create a user in AEM]
Double click on the japan-queue user and go to the Permissions tab.
Provide read permission to / root level
From content allow only <project_specific_content_folder> and deny access to all folders.
Note: In above screenshot
* (asterisk) There is at least one local entry (either effective or ineffective). These wildcard ACLs are defined in CRX.
! (exclamation mark) There is at least one entry that currently has no effect.
We need to create specific users related to each publisher on author USERADMIN [ http://localhost:4502/useradmin ] console.
EX: For author instance , create a user named “japan-queue” and provide the required permission as below.
Assign Specific Permissions to Users from Useradmin console:
Go to USERADMIN [ http://localhost:4502/useradmin ] console.
Create a new user with the name “japan-queue“. [ Click here to learn how to create a user in AEM]
Double click on the japan-queue user and go to the Permissions tab.
Provide read permission to / root level
From content allow only <project_specific_content_folder> and deny access to all folders.
Note: In above screenshot
* (asterisk) There is at least one local entry (either effective or ineffective). These wildcard ACLs are defined in CRX.
! (exclamation mark) There is at least one entry that currently has no effect.
Creating a forward replication agent in AEM:
Once user permission is set properly, create a new forward replication agent and add the new user-id “japan-queue” in the agent user-id tab.
Go to MiscAdmin [ http://localhost:4502/miscadmin ].
Select Agents on the Author page under the Replication folder and create a new page using Replication Agent as Template.[ Click Here to Learn how to create a Replication agent in AEM]
Double click on newly created replication agent and edit its settings.
Once it is done, only content related to japan will be processed via this queue.
Once user permission is set properly, create a new forward replication agent and add the new user-id “japan-queue” in the agent user-id tab.
Go to MiscAdmin [ http://localhost:4502/miscadmin ].
Select Agents on the Author page under the Replication folder and create a new page using Replication Agent as Template.[ Click Here to Learn how to create a Replication agent in AEM]
Double click on newly created replication agent and edit its settings.
Once it is done, only content related to japan will be processed via this queue.
Testing Replication Agent in AEM:
Once done, just activate /content/japan pages and check the log. Now only Japan content should be replicated to “forward-replication-japan”.
Once done, just activate /content/japan pages and check the log. Now only Japan content should be replicated to “forward-replication-japan”.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.