Ensuring proper Search behavior after migration
After you finish migrating product configuration to the new portal environment, some manual adjustment is required to ensure that the Search Center functions properly on the new portal.
- Extract the MigratedThemes EAR from IBM WebSphere Application Server using the administrative console.
- Expand the EAR to a directory using the EARExpander command in the was_profile_root/bin directory.
- In the path_to_expanded_ear/MigratedThemes.ear/MigratedThemes.war/themes/html/name_of_migrated_theme directory, locate banner_searchControl.jspf, create a backup copy of the file, and then delete banner_searchControl.jspf.
- In the $PORTAL_HOME/installer/wp.ear/installableApps/wps_theme.ear/wps_theme.war/themes/html/Portal directory, locate banner_searchControl_for_migrated_themes.jspf and copy it to the path_to_expanded_ear/MigratedThemes.ear/MigratedThemes.war/themes/html/name_of_migrated_theme directory. Then, change the file name to banner_searchControl.jspf.
- Repackage the MigratedThemes.war file, repackage the MigratedThemes.ear file, and deploy the EAR in WAS using the administrative console.
- To recompile Default.jsp under WP_PROFILE/installedApps/node_name/MigratedThemes.ear/MigratedThemes.war/themes/html/name_of_migrated_theme and incorporate the updates to the other JSP files, enter:
touch Default.jsp
- Restart the portal.
Parent
Post-migration activities
WAS: EARExpander command