+

Search Tips   |   Advanced Search

Remote search cumulative fix instructions for HCL WebSphere Portal

This cumulative fix can only be applied to an existing functional version of HCL WebSphere Portal v8.5+ remote search or document conversion services (DCS) server, with or without a previous cumulative fix applied.

If we apply a cumulative fix HCL WebSphere Portal, we also apply the corresponding cumulative fix to the remote server.

If you originally installed the remote service using manual steps, use manual steps to upgrade it, to update the we copy and extract updated files from the primary portal server and to the search server. Refer to the Updating remote search using manual steps external link section of the HCL Product Documentation for the details of setting up the application.

What's new: For a list of the Fixes which have gone into each CF, visit Combined Cumulative Fix Strategy.

Space Requirements: Ensure 250 MB of disk space is available in the download directory to download the cumulative fix, 1 MB in the installation directory, and 75 MB in the shared data space, which is the directory where Installation Manager temporarily stores downloaded files for use during the update.

If we configured a user or group other than wpsadmin for the security role mapping for the PSEStandalone application, before the update, add the property portalAdminUser=<username> replacing <username> with the username e.g. wpsbind in...

If you missed this configuration step, we can still manually re-add the user or groups after the update.

See Portal Upgrade Best Practices.

Backing up the Installation Manager data: Backup the contents of the IBM Installation Manager data directory on the server we are upgrading in the event you lose connection during the upgrade, as this could corrupt the data directory. The default locations of these directories are:

Known Issues: Review the Known issues for combined cumulative fix topic page to be aware of any known issues for the HCL WebSphere Portal Version 8.5 CF releases.

Review supported hardware/software requirements: For Portal v8.5 CF08 or later, the minimum recommended WebSphere Application Server level is at least WAS 8.5.5.6 with the corresponding JDK level applied.

Review the (supported hardware and software requirements external link) for this cumulative fix. If necessary, upgrade all hardware and software before applying this cumulative fix, including interim fixes required for WebSphere Application Server.

Check fixes installed on the system: All temporary or interim fixes on your system must be removed before installing this cumulative fix. Also check whether the fixes installed on the system are included in the list of fixes provided in this cumulative fix. If we have temporary or interim fixes on the system that are not included in this cumulative fix then contact HCL Software Support for an updated version of those fixes or for more information. Download the cumulative fix: If we are installing the cumulative fix using a live repository, then you do not need to download the cumulative fix to your server.


Download and extract the cumulative fix

  1. Download the latest zip file that corresponds to the installation on your system. Go to HCL Software Licensing Portal or HCL Software Support page and download the HCL WebSphere Portal Remote Search CF file 8.5-WP-RemoteSearch-CFPInnnnn-CFnn.zip.

  2. Create a directory and extract the downloaded zip file into this directory. Inside the zip file are a readme file, sample response files, and the actual cumulative fix file itself. The cumulative fix file is named as follows, where nn represents the CF number associated with this cumulative fix: WP8500CFnn_Remote.zip.

  3. Create a subdirectory and extract theWP8500CFnn_Remote.zip file to this directory. The extraction results in a repository.config file that is used by IBM Installation Manager during the update.


Steps for installing the cumulative fix

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory:

      ./serverStatus.sh -all

  3. Launch the IBM Installation Manager that was used to install HCL WebSphere Portal Remote Search v8.5.

  4. Use Installation Manager, click File > Preferences.

  5. Go to the Repositories panel and click "Add Repository".

  6. Navigate to the repository.config file mentioned earlier and select it.

  7. Select Update and follow the prompts to update HCL WebSphere Portal Remote Search.

  8. If we are running an external web server, restart it now.


Use a live repository via the Graphical User Interface

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory:

      ./serverStatus.sh -all

  3. Launch the IBM Installation Manager that was used to install HCL WebSphere Portal Remote Search v8.5.

  4. Use Installation Manager, click...

      File > Preferences > Repositories panel > Search service repositories during installation and updates > Apply.

  5. Select Update and follow the prompts to update HCL WebSphere Portal Remote Search.

  6. If we are running an external web server, restart it now.


Use a command line

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory:

      ./serverStatus.sh -all

  3. Launch the installation program of IBM Installation Manager. NOTE: The command is shown here on multiple lines for clarity, but the entire command must be entered on one line. Include quotation marks around file paths that include spaces. For Unix/Linux:

      /opt/IBM/InstallationManager/eclipse/tools
      ./imcl install com.ibm.websphere.PORTAL.REMOTESEARCH.v85 -repositories <fullpath/to/repository.config> -installationDirectory <portal_remotesearch_root> -acceptLicense

  4. If we are running an external web server, restart it now.


Silent mode installation

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory:

      ./serverStatus.sh -all

  3. For IBM i only, Run the following command from qshell:

      chown QEJBSVR /QIBM/UserData/WebSphere/AppServer/V85/ND/profiles/prs_profile/ConfigEngine/properties/wkplc.properties

  4. Open a command window and switch to the eclipse/tools subdirectory of Installation Manager. By default, this is:

      /opt/IBM/InstallationManager/eclipse/tools

  5. Update the sample response file packaged with your cumulative fix level according to the comments in the file. We can also record a response file to use to install the fix in silent mode. Go to the HCL Software Support page for detailed instructions for recording an IBM Installation Manager response file.

    Note: The feature set listed in your response file must match the feature set we have installed. We cannot add or remove features during the cumulative fix update. The feature set listed in the sample response file is:

      features='main.ce,main.rs.install,main.dcs.install,main.rs.deploy,main.dcs.deploy'

    If the server we are applying the fix to is configured only as a remote search server, then you should remove main.dcs.deploy from this list.

    • Example (Remote Search server only):

        features='main.ce,main.rs.install,main.dcs.install,main.rs.deploy'

    • Example (Document Conversion server only):

        features='main.ce,main.rs.install,main.dcs.install,main.dcs.deploy'

  6. Install in silent mode:

      imcl -acceptLicense -input <Full_path_to_your_response_file> -log <Full_Path_to_a_log_file> -showProgress

  7. If we are running an external web server, restart it now.


Use Console Mode

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory:

      ./serverStatus.sh -all

  3. Start the IBM Installation Manager in console mode.

      cd /opt/IBM/InstallationManager/eclipse/tools
      ./imcl -c

  4. Add the repositories:

    • Enter P to go to the Preferences menu.
    • Enter 1 to go to the Repositories menu.
    • Enter D to add repositories.
    • Type the path for the HCL WebSphere Portal Remote Search v8.5 CF repository file.
    • Enter A to apply your repositories and return to the Preferences menu.
    • Enter R to return to the Main menu.

  5. Select Update and follow the prompts to update HCL WebSphere Portal.

  6. If we are running an external web server, restart it now.

Reminder: Known IssuesGo to Known Issues in this topic section to be aware of any known issues for HCL WebSphere Portal CF releases.


Steps for rolling back the cumulative fix

NOTE: The steps in these sections for rolling back the cumulative fix describe how to roll back from a successful update to a previous level. However, rolling back from a failed update does not guarantee return to a dependable state. When an update fails, it is advised that you fix the cause of the failure and try again for a successful update; to return to a previous level, we must depend on a system and database backup and restore. There are several different methods to roll back the cumulative fix, and they are:

Choose one method that is available for the system. Follow the detailed steps for that option, and then proceed with the Post Rollback Steps. Use a Graphical User Interface to roll back (available on Windows, Linux, and Unix operating systems):

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory:

      ./serverStatus.sh -all

  3. Open a command window and switch to the eclipse/tools subdirectory of Installation Manager. For Unix/Linux:

      /opt/IBM/InstallationManager/eclipse/tools

  4. Launch the installation program of IBM Installation Manager: NOTE: The command is shown here on multiple lines for clarity, but the entire command must be entered on one line. Include quotation marks around file paths that include spaces. For Unix/Linux:

      ./imcl rollback com.ibm.websphere.PORTAL.REMOTESEARCH.v85 -installationDirectory <portal_remotesearch_root>

  5. If we are running an external web server, restart it now.


Use silent mode to roll back

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory.

      ./serverStatus.sh -all

  3. cd /opt/IBM/InstallationManager/eclipse/tools
  4. Update the sample response file packaged with your cumulative fix level according to the comments in the file.

  5. Roll back in silent mode:

      imcl -input (Full_path_to_your_response_file) -log (Full_Path_to_a_log_file) -showProgress

  6. If we are running an external web server, restart it now.


Use Console Mode for roll back

  1. If we are running an external web server such as IBM HTTP server, stop the web server.

  2. Stop any active application servers using the stopServer command. To see which application servers are active, use the serverStatus command from the (prs_profile)/bin directory.

      ./serverStatus.sh -all

  3. Start the IBM Installation Manager in console mode:

      cd /opt/IBM/InstallationManager/eclipse/tools
      ./imcl -c

  4. Select Roll back and follow the prompts to roll back HCL WebSphere Portal Remote Search.

  5. If we are running an external web server, restart it now.

Parent topic: Combined Cumulative Fix (CF) strategy