If your deployment of Tools and Frameworks meets all of the following criteria you must update your keyword redirect groups after you migrate to 11.2.

To update the keyword redirect groups you must complete the following steps:

Follow these instructions:

  1. Export the application for which you want to update keyword redirect groups.

  2. In the destination directory, navigate to the page that contains the relevant redirects folder for a site: <app dir>\config\import\pages\<site_id>\<page>\

    For example:

    Discover\config\import\pages\DiscoverCameras\browse\
  3. Cut the redirects folder.

  4. Navigate to the redirects folder for the application (not a site): <app dir>\config\import\redirects

    For example:

    Discover\config\import\redirects
  5. Paste the redirects folder that you just cut into this folder.

    This results in a redirects folder nested inside a redirects folder. For example:

    Discover\config\import\redirects\redirects
                   
  6. Rename the nested redirects folder with a name that is appropriate for your site's keyword redirect group.

    For example:

    Discover\config\import\redirects\DiscoverCameras
                   

    Make a note of the folder name because you need this information when you edit the content.xml of the search results page.

  7. Oracle recommends editing the redirects\_.JSON file to remove the line that contains the enableThesaurus property. This property is not currently used.

    For example, remove the bold text in the following example:

    {
        "ecr:type": "redirect-group",
        "displayName": "Discover Cameras",
        "enableStemming": "TRUE",
        "enableThesaurus": "FALSE",
        "redirects": [
            {
                "matchmode": "MATCHEXACT",
                "url": "/browse/cameras/_/N-1z141ya",
                "searchTerms": "camera"
            },
            {
                "matchmode": "MATCHEXACT",
                "url": "/contact-us",
                "searchTerms": "locations"
            }
        ]
    }
  8. Navigate to the template.xml file for the page template on which your search results page is based: \import\templates\<page>\template.xml.

  9. Use a text editor to add a redirectGroup property to the template.xml file.

    <Property name="redirectGroup"><String/></Property>
  10. Navigate to the context.xml file for the relevant search results page for the site.

    For example, the context.xml file for Discover Cameras whose search results can be rendered by a browse page would be stored at: pages\DiscoverCameras\browse\

  11. Use a text editor to update the context.xml file with the site-based keyword redirect group name appropriate for your site. The group name must match the folder name where the redirects JSON is stored.

    For example, for Discover Cameras, the redirects group string has the following name:

    </Property>
      <Property name="redirectGroup">
        <String>/redirects/DiscoverCameras</String>
      </Property>
  12. Import the content with the new keyword group updates.

If you do not update either the template or content.xml for the search results page, then business users editing content in the Experience Manager might see the following warning:


Copyright © Legal Notices