Moving tags in 6.4 as per repository restructure | Community
Skip to main content
V
vchanwalast5542
Level 2
July 5, 2019
Solved

Moving tags in 6.4 as per repository restructure

  • July 5, 2019
  • 6 replies
  • 2415 views

As per adobe 6.4 documentation, tags should be moved from etc/tags to content/cq:tags.
Administering Tags


We have multiple tenants in the same AEM instance, and each of these have separate namespace under etc tags. We are not able to move tags specific to a tenant from etc/tags to /content/cq:tags. Is this an expected behavior ? should we move all the tags under etc at the same time ?

Thanks,
Vijay.

    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 user05162

    If that's the case, you need to keep using legacy location and move tags once everything is moved to Touch UI

    6 replies

    U
    Adobe Employee
    user05162Adobe Employee
    Adobe Employee
    July 5, 2019

    Are you trying the steps below to move?

    1. Replace the references to the old model (/etc/tags) with the new one (/content/cq:tags) by using the tagID.
    2. Log in to CRXDE Lite
    3. Move the tags from /etc/tags to /content/cq:tags
    4. Restart the OSGi Component com.day.cq.tagging.impl.JcrTagManagerFactoryImpl.

    [1] Pomocník pre Adobe Experience Manager | Repository Restructuring in AEM 6.4

    V
    vchanwalast5542Author
    Level 2
    July 5, 2019

    These steps work when I move the complete set off tags from etc/tags. If I move only tenant specific tags, any new tags created for this namespace are still getting created under etc/tags. You can check this on vanilla AEM instance.

    U
    Adobe Employee
    user05162Adobe Employee
    Adobe Employee
    July 5, 2019

    As per my understanding, all the tags regardless of namespace should be moved under "/content". Any specific reason you want to move one tenant at a time?

    Also, as mentioned at [1]  The Tag Manager API supports both the legacy and the new location. When the JCR Tag Manager Factory OSGi Component starts, it detects if it is running on an upgraded instance or a legacy one, and uses the appropriate location.

    In other words, if there are still nodes under "etc/tags" AEM will still use legacy location.

    [1] Pomocník pre Adobe Experience Manager | Repository Restructuring in AEM 6.4

    V
    vchanwalast5542Author
    Level 2
    July 5, 2019

    Thanks Jaideep. So the tenant we are currently working on uses classic UI and as part of 6.4 upgrade we are working on restructuring the tags from etc/tags to /content/cq:tags. Since the tenant uses classic UI the tags are getting created under etc/tags.

    U
    Adobe Employee
    user05162Adobe EmployeeAccepted solution
    Adobe Employee
    July 5, 2019

    If that's the case, you need to keep using legacy location and move tags once everything is moved to Touch UI

      Nirmal_Jose
      Adobe Employee
      Nirmal_JoseAdobe Employee
      Adobe Employee
      July 6, 2019

      This seems to be right approach as I faced something similiar. Unless you remove the entire /etc/tags you won't see them in the /content/cq:tags

      Terms & ConditionsAccessibility statement

      Loading footer...