Upgrade

For upgrade issues, refer to the Upgrade Guide for Unix.

When you upgrade Java ES 4 to Java ES 5, the search migration fails. (#6440906)

Solution:

Do the following:

1. Before running the psugrade script, open the Java ES 4 search.conf file.

   The search.conf file is located in the /var/opt/SUNWps/https-server/portal/config directory.

2. In the search.conf file, change libdir="/opt/SUNWps/lib" to libdir="/opt/SUNWps.bak/lib:/opt/SUNWps/lib".

   where /opt/SUNWps is the Java ES 4 installation directory.

3. Run the psupgrade script.

After the upgrade, some of the customization made to the search server configuration are not migrated to the UpgradeSearch. For the migration that is not handled by psugrade, manual carry over from upgraded Portal Server 6.3.1 is needed. These operations should be performed after stopping all search related processes, such as search webapp, robot, rdregister, autoclassify, and profiler.

1. Copy the following files to the upgraded search server directory:

   cp $SRC/config/taxonomy.rdm $DEST/config cp $SRC/config/filterrules.conf $DEST/config cp $SRC/config/import.conf $DEST/config cp $SRC/config/classification.conf $DEST/config cp $SRC/config/schema.rdm $DEST/config

   where SRC is the path to the old search server directory and DEST is the path to the new upgraded search server directory.

2. Depending on what was customized in Portal Server 6.3x, do the following:

   • For Robot, use the Portal Server 7.1 administration console's robot/properties to reconfigure the robot.conf's parameter such as proxy and authentication. Use the Portal Server 7.1 administration console's robot/filter to update the robot filter properties with the customization done on Portal Server 6.3.1's /var/opt/SUNWps.bak/server/portal/config/filter.conf file.

   • For federated search databases, refer to the Portal Server 7.1 configuration guide for more information on how to set up Federated Search.

3. Restart the search server web container and search related processes.