Redirect Tool using etc/map | Community
Skip to main content
S
s1101v
Level 3
January 9, 2021
Solved

Redirect Tool using etc/map

  • January 9, 2021
  • 3 replies
  • 2500 views

Hello Community - I have a requirement to provide the user interface/utility to the authors to manage the redirects which will eventually be stored in etc/map config. I know that we have ACS Redirect Manager but the requirement is to build a custom one. Could someone provide some suggestions?

 

@arunpatidar , @joerghoh , @briankasingli , @vanegi 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by raj_mandalapu

I can interpret it in two ways,

I think, the ACS Redirect Manager helps us to manage redirects at the Apache level, but I see that
you are expecting to store redirect configurations at etc/map level, seems like you want to configure internal redirects.

If that is the case, then you need to write a custom logic

1. You can reuse ACS redirect manager interface, check the below link for reference page
https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/05e6e86fb69aff6afe7c3e4297b2be1d787e268a/ui.apps/src/main/content/jcr_root/apps/acs-commons/components/utilities/redirectmappage/content.jsp
2. On submit button click, you can call servlet and check whether mapping entries exist under etc/map, if does not exist then create a new one using Node API

If the requirement is not storing under etc/map then you need to do analysis or do simple POC whether ACS redirect manager is meeting all your requirements or not, if not then you need to do reverse engineering.

3 replies

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
January 9, 2021

@s1101v,

Building your own custom one, I suggest you reverse engineer the ACS Redirect Manager, understand why did they decide to design this redirect manage. Then execute your own. (you should also try to set it up on your local publisher + dispatcher, see how it works).

I think their ACS Redirect Manager makes sense to me, as rules are coming from static files within the web server, the redirect rules take effect before reaching to the AEM publishers... you wouldn't want your publishers to be taking the load.

I hope this helps.

    P
    praveenjain
    Level 3
    January 10, 2021

    Agreed on point mentioned by BrianKasingli.

    Just wanted to understand how your custom requirment are different from ACS Redirect Manager.

    If its just about the UI then you can override it and appyling styling, functionality remains same.

    - Praveen

      S
      s1101vAuthor
      Level 3
      January 10, 2021
      The requirement is only to give the provision to add/remove/edit existing/new redirect from the UI.
        raj_mandalapu
        raj_mandalapuAccepted solution
        Level 7
        January 11, 2021

        I can interpret it in two ways,

        I think, the ACS Redirect Manager helps us to manage redirects at the Apache level, but I see that
        you are expecting to store redirect configurations at etc/map level, seems like you want to configure internal redirects.

        If that is the case, then you need to write a custom logic

        1. You can reuse ACS redirect manager interface, check the below link for reference page
        https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/05e6e86fb69aff6afe7c3e4297b2be1d787e268a/ui.apps/src/main/content/jcr_root/apps/acs-commons/components/utilities/redirectmappage/content.jsp
        2. On submit button click, you can call servlet and check whether mapping entries exist under etc/map, if does not exist then create a new one using Node API

        If the requirement is not storing under etc/map then you need to do analysis or do simple POC whether ACS redirect manager is meeting all your requirements or not, if not then you need to do reverse engineering.

          Terms & ConditionsAccessibility statement

          Loading footer...