![]() ![]() ![]() Step 1: Declare the dependency in project’s pom.xmlīiz.netcentric.cq.tools.accesscontroltool Appending the snippets in the appropriate pom.xml should resolve both the challenges mentioned above. Sharing the configurations that need to be part of multiple pom.xml in the project structure. Often, we might need to assure ui.content is deployed prior to ACL module. In this case, ACL module should be installed only after all necessary paths are available in AEM. For example: If ACL should be applied on a content path, which is unavailable, then ACL set-up would fail. Resolution: If the issue occurs only on first installation for the maven project, then one should check the order in which modules are deployed.Issue 3: Custom user groups are created in AEM, but ACLs are missing.Also assure that the cloudManagerTarget is set to none. Resolution: Declare the dependency of acl module on “ accesscontroltool-package“. ![]() ![]() When using Cloud Manager, the acl module was deployed prior to deployment of any other maven module. The module needs to be deployed only after “ accesscontroltool-package” is installed. Issue 2: We had created a separate module for ACL deployment.Resolution: Use sub-package for deployment of “ accesscontroltool-package“.Though, I was able to deploy “ accesscontroltool-oakindex-package” via embed, “ accesscontroltool-package” didn’t install. Issue 1: The latest Project structure recommends deployment of third-party packages via embed statement.The current blog focuses on how we can deploy Netcentric AccessControlTool via the maven project created with Archetype-23. To be compatible with the new architecture, we need to follow a recommended Project Structure.ĪEM Project Archetype 23 automatically creates a maven project that is as per the AaaCS guidelines. Adobe had recently announced availability of AEM as a Cloud Service (AaaCS). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |