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.
You have applied Patch 19336952: Allow site specific keyword redirects to your Tools and Frameworks 11.1 deployment
You have created keyword redirect groups for sites in your application.
The keyword redirect group JSON files are located in the import\pages folder at:
<
app dir
>\config\import\pages\<site_id
>\<page>\redirects\
To update the keyword redirect groups you must complete the following steps:
Move your redirect group folder from its location in the
import\pages
folder to theimport\redirects
folder.Update your search results page template with a
redirectGroup
property.All pages and rules based on a template that has been updated with the new
redirectGroup
property must also have theredirectGroup
property. Update thecontent xml
files of search results pages with a string value containing the redirects folder name. All other content based on the updated template can have aredirectGroup
property with no value.
Follow these instructions:
Export the application for which you want to update keyword redirect groups.
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\
Note
Cutting it, rather than copying it, ensures that you actually remove the folder from its old location.
Navigate to the redirects folder for the application (not a site):
<app dir>\config\import\redirects
For example:
Discover\config\import\redirects
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
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.Oracle recommends editing the
redirects\_.JSON
file to remove the line that contains theenableThesaurus
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" } ] }
Navigate to the
template.xml
file for the page template on which your search results page is based:\import\templates\<page>\template.xml.
Use a text editor to add a
redirectGroup
property to thetemplate.xml
file.<Property name="redirectGroup"><String/></Property>
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\
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>
Import the content with the new keyword group updates.
Navigate to the
<app dir>
\control\<app dir>
/control/From the command line, import the updated content by entering the following commands:
For example:
runcommand.bat IFCR importContent pages c:\myexports\Discover\config\import\pages
runcommand.bat IFCR importContent redirects c:\myexports\Discover\config\import\redirects
and
runcommand.bat IFCR importContent templates c:\myexports\Discover\config\import\templates
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: