Cumulative Fix instructions: Farm | HCL Digital Experience 8.5

The procedures below describe these steps in detail.

Ensure that enough disk space is available in the following directories:

• For all platforms: 2.0 GB in the download directory to download the cumulative fix, 1.5 GB in Portal_Install_Root, 1 GB temporary disk space in (wp_profile_root), and 1.66 GB in the shared data space, which is the directory where Installation Manager temporarily stores downloaded files for use during the update.
• For Solaris: It is recommended that you allocate swap space equal to at least twice your physical RAM to avoid memory errors during the configuration of this cumulative fix.

Alternatively, the following ConfigEngine tasks have also been integrated into CF09 or later to globally disable and enable syndication (These tasks can be used in place of the manual updates linked above:

• <wp_profile root>/ConfigEngine/ConfigEngine.sh|.bat disable-syndication-auto-scheduler

• <wp_profile root>/ConfigEngine/ConfigEngine.sh|.bat enable-syndication-auto-scheduler

The default locations of these directories are:

• Windows: C:\ProgramData\IBM\InstallationManager
• Linux/UNIX root users: /var/ibm/InstallationManager
• Linux/UNIX non-root users: /home/(user id)/var/ibm/InstallationManager
• IBM i: Installation location: /QIBM/ProdData/InstallationManager
• IBM i: Agent data location: /QIBM/UserData/InstallationManager

Review the Supported Hardware and Software Requirements article for this cumulative fix. If necessary, upgrade all hardware and software before applying this cumulative fix, including interim fixes required for WebSphere Application Server.

1. Edit the <wp_profile root>/ConfigEngine/properties/wkplc.properties file and ensure the following values are set correctly:
   • WasRemoteHostName=<the hostname of your WAS instance>
   • WasSoapPort=<the soap port of your WAS instance>
   • WasUserid=<your WAS admin user>
   • WasPassword=<your WAS admin pwd>
   • PortalAdminId=<your Portal Admin ID>
   • PortalAdminPwd=<your Portal Admin password>
   • WpsHostName=<Your Portal hostname>
   • WpsHostPort=<The port you use to access Portal>
   • WpsContextRoot=<your Portal context root>
2. Edit the <wp_profile root>/ConfigEngine/properties/wkplc_dbdomain.properties file and ensure the following values are set correctly:
   • release.DbPassword=<your database user password>
   • community.DbPassword=<your database user password>
   • customization.DbPassword=<your database user password>
   • jcr.DbPassword=<your database user password>
   • likeminds.DbPassword=<your database user password>
   • feedback.DbPassword=<your database user password>
3. Edit the <wp_profile root>/ConfigEngine/properties/wkplc_comp.properties file and ensure the following values are set correctly:
   • XmlAccessHost=<your Portal hostname>
   • XmlAccessPort=<the port you use to access Portal>
   Note: In a Farm Portal environment, the WasRemoteHostName should be the local hostname and the WasSoapPort should be the soap port of the HCL Portal server.
   Note: If your server is configured with database runtime users, for example, feedback.DbRuntimeUser=<your feedback database runtime user>, ensure to set their password values correctly as well, for example, in feedback.DbRuntimePassword=<your feedback database runtime user password>.

The update process removes plain text passwords from the wkplc*.properties files. To keep these passwords in the properties files, include the following line in the wkplc.properties file:

PWordDelete=false

In Unix/Linux environments, you must install the cumulative fix as the same user which you used to install HCL Portal originally. This could be either root or a non-root user. If you need to use a non-root user, ensure the following conditions are met:

• If you are installing as a non-root user on Unix or Linux, the umask setting for your login session must be set to 0022 or better. (umask is a setting that controls what file permissions are set for newly created files and directories. A value of 0022 correspond to permission settings of (rwxr-xr-x).) If the umask is not set appropriately by default, you must set it when you start Installation Manager or when you open a command-line utility to run Installation Manager commands.
• The non-root user has a ulimit - n setting of at least 18192. This must be a number and not unlimited.
• The non-root user owns the AppServer, PortalServer, ConfigEngine, and Portal profile directories and has read/write access to all files in these directories. Permission settings of 755 (rwxr-xr-x) are sufficient.
• Do not use sudo or su to install the fix pack. Either use root explicitly or use a non-root user that meets the above conditions.

To open a command-line utility to run Installation Manager commands:

1. Open a command line window.
2. Run this command to check your current umask setting:

   umask

3. If necessary, run this command to set the umask:

   umask 0022

After running Installation Manager to install the new Portal code but before running the applyCF.sh or applyCF.bat command to update the Portal profile, perform these steps:

1. Open a command Window and switch to the ConfigEngine home directory. By default this is:
   • Unix/Linux: /opt/IBM/WebSphere/ConfigEngine
   • Windows: C:\IBM\WebSphere\ConfigEngine
   • IBM i: /QIBM/ProdData/WebSphere/ConfigEngine
2. Make a backup copy of the ConfigEngine script. This file is named ConfigEngine.bat for Windows and ConfigEngine.sh for all other platforms.
3. Make sure your user has write permissions for the script file and open it in a text editor.
4. Look for the text EJBDEPLOY_JAVA_HOME in the script. If you do not find it, no further action is necessary and you can continue with the installation. If you do find it, delete every line that contains the text EJBDEPLOY_JAVA_HOME anywhere in the line. (There should be 3 such lines in the .sh script and 2 lines in the .bat script.)
5. Save the file.

If you are installing the cumulative fix using a live repository, then you do not need to download the cumulative fix to your server. If you need to download the cumulative fix, then you can follow these steps.

1. Download the latest zip file that corresponds to the installation on your system, as shown in this table. You can also find more information about the latest fixes on the HCL Software page.

   Installed Offering	HCL Portal Server
   Cumulative fix to download	8.5-WP-WCM-Combined-CFPInnnnn-Server-CFnn.zip 8.5-9.0-WP-WCM-Combined-CFPInnnnn-Server-CFnn.zip CF14 or later

2. Create a directory and extract the zip file(s) into this directory. Inside the zip file is a readme file, sample response files (Server only), and the actual cumulative fix file itself. The cumulative fix files are named as follows, where nn represents the CF number associated with this cumulative fix:
   • WP8500CFnn_Server.zip (HCL Portal Server)
3. Create a sub-directory and extract the appropriate WP8500CFnn_ zip file to this directory. The extraction results in a repository.config file that is used by IBM Installation Manager during the update.

There are several different methods to install the cumulative fix, and they are:

• Use a Graphical User Interface (GUI)
• Use a live repository via the Graphical User Interface
• Use a command line
• Use silent mode installation
• Use console mode installation

1. If you are running an external web server such as IBM HTTP server, stop the web server.
2. Stop any active application servers by using the stopServer command. To see which application servers are active, use the serverStatus command from the (wp_profile)/bin directory and again from the (cw_profile)/bin directory:
   • Unix/Linux:

     ./serverStatus.sh -all

   • Windows:

     serverStatus.bat -all

3. Launch the IBM Installation Manager that was used to install HCL Portal V8.5.
4. Using 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 Portal.
8. After installation completes, proceed with the Additional configuration steps.

1. If you are running an external web server such as IBM HTTP server, stop the web server.
2. Stop any active application servers by using the stopServer command. To see which application servers are active, use the serverStatus command from the (wp_profile)/bin directory and again from the (cw_profile)/bindirectory:
   • Unix/Linux:

     ./serverStatus.sh -all

   • Windows:

     serverStatus.bat -all

3. Open a command window and switch to the eclipse/tools sub-directory of Installation Manager. By default, this is:
   • Unix/Linux: /opt/IBM/InstallationManager/eclipse/tools
   • Windows: C:\Program Files\IBM\Installation Manager\eclipse\tools
4. Run the following command to launch the installation program of IBM Installation Manager.
   Note: The commands are 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.
   • Unix/Linux:

     ./imcl install com.ibm.websphere.PORTAL.SERVER.v85 -repositories (fullpath/to/repository.config) -installationDirectory (portal_server_root) -acceptLicense

   • Windows:

     imcl.exe install com.ibm.websphere.PORTAL.SERVER.v85 -repositories (fullpath/to/repository.config) -installationDirectory (portal_server_root) -acceptLicense

5. After installation completes, proceed with the Additional configuration steps.

1. If you are running an external web server such as IBM HTTP server, stop the web server.
2. Stop any active application servers by using the stopServer command. To see which application servers are active, use the serverStatus command from the (wp_profile)/bin directory and again from the (cw_profile)/bin directory:
   • Unix/Linux:

     ./serverStatus.sh -all

   • Windows:

     serverStatus.bat -all

   • IBM i:

     serverStatus -all

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

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

4. Open a command window and switch to the eclipse/tools sub-directory of Installation Manager. By default, this is:
   • Unix/Linux: /opt/IBM/InstallationManager/eclipse/tools
   • Windows: C:\Program Files\IBM\Installation Manager\eclipse\tools
   • IBM i: /QIBM/ProdData/InstallationManager/eclipse/tools
5. Update the sample response file that is packaged with your cumulative fix level according to the comments in the file. You can also record a response file to use to install the fix in silent mode. Go to 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 you have installed. You cannot add or remove features during the cumulative fix update. The feature set listed in the sample response file is:

   features='ce.install,portal.binary,portal.profile'

   If you do not have any profiles on this node (because you are in the process of migration from a previous version of HCL Portal, or creating multiple profiles, or you originally installed Portal 8.5 as a binary install), then you should remove the 'portal.profile' feature from this list:

   features='ce.install,portal.binary'

6. Run the following command to install in silent mode:

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

7. After installation completes, proceed with the Additional configuration steps.

1. If you are running an external web server such as IBM HTTP server, stop the web server.
2. Stop any active application servers by using the stopServer command. To see which application servers are active, use the serverStatus command from the (wp_profile)/bin directory and again from the (cw_profile)/bin directory:
   • Unix/Linux:

     ./serverStatus.sh -all

   • Windows:

     serverStatus.bat -all

   • IBM i:

     serverStatus -all

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

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

4. Open a command window and switch to the eclipse/tools sub-directory of Installation Manager. By default, this is:
   • Unix/Linux: /opt/IBM/InstallationManager/eclipse/tools
   • Windows: C:\Program Files\IBM\Installation Manager\eclipse\tools
   • IBM i: /QIBM/ProdData/InstallationManager/eclipse/tools
5. Run the command to start the IBM Installation Manager in console mode:

   For Unix/Linux:

   ./imcl  -c

   Windows:

   imcl.exe -c

   IBM i:

   ./imcl  -c

6. Complete the following steps to 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 your HCL Portal Version 8.5. CF repository file.
   • Enter A to apply your repositories and return to the Preferences menu.
   • Enter R to return to the Main menu.
7. Select Update and follow the prompts to update HCL Portal.
8. After installation completes, proceed with the Additional configuration steps.

(profile_root)/bin/osgiCfgInit.sh|bat 

applyCF.sh -Dskip.profile.template.update=true

ConfigEngine.sh cf-create-profile-templates

Execute the following command from within the path of the profile to configure.

• Unix/Linux:

  (profile_root)/PortalServer/bin/applyCF.sh -DPortalAdminPwd=(password) -DWasPassword=(password)

• Windows:

  (profile_root)\PortalServer\bin\applyCF.bat -DPortalAdminPwd=(password -DWasPassword=(password)

• IBM i:

  (profile_root)/PortalServer/bin/applyCF.sh -DPortalAdminPwd=(password) -DWasPassword=(password)

If you are installing the CF on an empty portal then extra steps are required to avoid upgrade errors.

• If you have created any custom content on top of the empty portal, you must first use XMLAccess to export the Portal content. From the wp_profile_root/PortalServer/bin directory run:

  xmlaccess.bat/sh -user Portal_admin_user -password Portal_admin_password -url http://<myhost>:<port>/wps/config -in <Portal home>/doc/xml-samples/Export.xml -out result.xml

• Upgrade the portal profile to the new CF level. Because many of the expected artifacts will not exist in an empty portal, you must define the isEmptyPortal property when performing this step:
  • Unix/Linux:

    <profile_root>/PortalServer/bin/applyCF.sh -DisEmptyPortal=true -DPortalAdminPwd=<password> -DWasPassword=<password>

  • Windows:

    <profile_root>\PortalServer\bin\applyCF.bat -DisEmptyPortal=true -DPortalAdminPwd=<password> -DWasPassword=<password>

  • IBM i:

    <profile_root>/PortalServer/bin/applyCF.sh -DisEmptyPortal=true -DPortalAdminPwd=<password> -DWasPassword=<password>

  Important: If the applyCF command fails for any reason, check the error logs and correct error conditions before continuing.
• Following a successful run of the applyCF script, re-run the empty-portal task to remove Portal artifacts that were reintroduced with the CF, as these may cause runtime errors:
  • Unix/Linux:

    <profile_root>/ConfigEngine/ ./ConfigEngine.sh empty-portal -DWasPassword=<password> -DPortalAdminPwd=<password>

  • Windows:

    <profile_root>/ConfigEngine/ ConfigEngine.bat empty-portal -DWasPassword=<password> -DPortalAdminPwd=<password>

  • IBM i:

    <profile_root>/ConfigEngine/ ConfigEngine.sh empty-portal -DWasPassword=<password> -DPortalAdminPwd=<password>

• If you exported custom content in step #1 above, you can now use XMLAccess to reimport that content. From the wp_profile_root/PortalServer/bin directory run:

  xmlaccess.bat/sh -user <Portal_admin_user> -password <Portal_admin_password> -url http://<myhost>:<port>/wps/config -in result.xml -out importResults.xml

On the Farm Support Server execute the following command from within the path of the profile to configure. Note: If the Farm Support Server only has read-only access to the Portal Binaries use the -DSharedBinaries=true flag with the applyCF command.

• Unix/Linux:

  <profile_root>/PortalServer/bin/applyCF.sh -DPortalAdminPwd=<password> -DWasPassword=<password>

• Windows:

  <profile_root>\PortalServer\bin\applyCF.bat -DPortalAdminPwd=<password> -DWasPassword=<password>

• IBM i:

  <profile_root>/PortalServer/bin/applyCF.sh -DPortalAdminPwd=<password> -DWasPassword=<password>

Important: If the applyCF command fails for any reason, check the error logs and correct error conditions before re-running.

If you are installing the CF on an empty portal then extra steps are required to avoid upgrade errors.

1. If you have created any custom content on top of the empty portal, you must first use XMLAccess to export the Portal content. From the wp_profile_root/PortalServer/bin directory run:

   xmlaccess.bat/sh -user Portal_admin_user -password Portal_admin_password -url http://<myhost>:<port>/wps/config -in <Portal home>/doc/xml-samples/Export.xml -out result.xml

2. Upgrade the portal profile to the new CF level. Because many of the expected artifacts will not exist in an empty portal, you must define the isEmptyPortal property when performing this step:
   • Unix/Linux:

     <profile_root>/PortalServer/bin/applyCF.sh -DisEmptyPortal=true -DPortalAdminPwd=<password> -DWasPassword=<password>

   • Windows:

     <profile_root>\PortalServer\bin\applyCF.bat -DisEmptyPortal=true -DPortalAdminPwd=<password> -DWasPassword=<password>

   • IBM i:

     <profile_root>/PortalServer/bin/applyCF.sh -DisEmptyPortal=true -DPortalAdminPwd=<password> -DWasPassword=<password>

   Important: If the applyCF command fails for any reason, check the error logs and correct error conditions before continuing.
3. Following a successful run of the applyCF script, re-run the empty-portal task to remove Portal artifacts that were reintroduced with the CF, as these may cause runtime errors.
   • Unix/Linux:

     <profile_root>/ConfigEngine/ ./ConfigEngine.sh empty-portal -DWasPassword=<password> -DPortalAdminPwd=<password>

   • Windows:

     <profile_root>/ConfigEngine/ ConfigEngine.bat empty-portal -DWasPassword=<password> -DPortalAdminPwd=<password>

   • IBM i:

     <profile_root>/ConfigEngine/  ConfigEngine.sh empty-portal -DWasPassword=<password> -DPortalAdminPwd=<password>

4. If you exported custom content in step #1 above, you can now use XMLAccess to reimport that content. From the wp_profile_root/PortalServer/bin directory run:

   xmlaccess.bat/sh -user <Portal_admin_user> -password <Portal_admin_password> -url http://<myhost>:<port>/wps/config -in result.xml -out importResults.xml

1. If you are running an external web server such as IBM HTTP Server and you are using the WebSphere Application Server automatic generation and propagation of the plug-in, then restart the web server. If you are not using the automatic generation and propagation, then perform the following steps:

• Regenerate the web server plug-in.
• Copy the plugin-cfg.xml file to the plugin directory.
• Restart the web server.

6. If using Web Content Manager and have installed any official extensions (such as the WCM Multilingual Solution (MLS) or WCM Social Media Publisher (SMP)), then run the following task to update them:

• Unix/Linux:

  <profile_root>/ConfigEngine/ConfigEngine.sh action-update-wcm-extensions -DWasPassword=<password> -DPortalAdminPwd=<password>

• Windows:

  <profile_root>\ConfigEngine\ConfigEngine.bat action-update-wcm-extensions -DWasPassword=<password> -DPortalAdminPwd=<password>

• IBM i:

  <profile_root>/ConfigEngine/ConfigEngine.sh action-update-wcm-extensions -DWasPassword=<password> -DPortalAdminPwd=<password>

The task can be run even if you are not sure if you had the extensions enabled. If you want to check if they were enabled the following tasks can be used:

• for MLS use:

  ConfigEngine.sh|bat action-is-wcm-mls-enabled

• for SMP use:

  ConfigEngine.sh|bat action-is-wcm-smp-enabled

10. Prior to CF07, it was recommended to set the DB2 database configuration parameter dft_queryopt to a value of 2 as this was tested to provide the best balance of query optimization time and query execution time for the SQL produced by the JCR. For CF07 or later, this recommendation has been changed to use a value of 5 in conjunction with the testing and changes made to the JCR and JCR schema. This setting is NOT updated automatically within your JCR Database Domain configuration as part of the CF07 (or later) upgrade. This can be done manually by customers by executing the following SQL against the JCR Domain Database:

db2 update db cfg for JCRDBNAME using DFT_QUERYOPT 5

OR It can also be done by running the following ConfigEngine task:

configure-jcr-db2-dft-queryopt

11. If DB2 Log Archiving is used (for example, HADR or Rollforward recovery), run the following task with HCL Portal server stopped:

• Unix/Linux:

  <profile_root>/ConfigEngine/ConfigEngine.sh reconfigure-jcr-for-hadr -DWasPassword=<password> -DPortalAdminPwd=<password>

• Windows:

  <profile_root>\ConfigEngine\ConfigEngine.bat reconfigure-jcr-for-hadr -DWasPassword=<password> -DPortalAdminPwd=<password>

• IBM i:

  <profile_root>/ConfigEngine/ConfigEngine.sh reconfigure-jcr-for-hadr -DWasPassword=<password> -DPortalAdminPwd=<password>

Limitations

1. Changing the server context root after upgrading is an unsupported rollback path. To roll back after changing the context root, you must first change the server context root to the values of the previous version.
2. When rolling back a CF install, if you have configured an empty context root you cannot roll back to a CF level that does not support the empty context root capability. For instance, if you have applied CF08 and have configured an empty context root you cannot rollback to CF07. If you have applied CF09 and have configured an empty context root you can roll back to CF08 but you would not be able to roll back if your previous CF level was CF07 or prior.
3. Configuring HCL Portal from a stand-alone environment to a clustered environment after upgrading is an unsupported rollback path.

Before you begin rollback

1. The HCL Portal rollback scripts depend on the wkplc.properties being up to date and accurate, particularly with the password properties. If you are using multiple profiles, verify that the information in each profile is correct.
2. Edit the <wp_profile root>/ConfigEngine/properties/wkplc.properties file and ensure the following values are set correctly:
   • WasRemoteHostName=<the hostname of your WAS instance>
   • WasSoapPort=<the soap port of your WAS instance>
   • WasUserid=<your WAS admin user>
   • WasPassword=<your WAS admin pwd>
   • PortalAdminId=<your Portal Admin ID>
   • PortalAdminPwd=<your Portal Admin password>
   • WpsHostName=<Your Portal hostname>
   • WpsHostPort=<The port you use to access Portal>
   • WpsContextRoot=<your Portal context root>
   Note: In a Farm Portal environment, the WasRemoteHostName should be the local hostname and the WasSoapPort should be the soap port of the HCL Portal server.
3. Edit the <wp_profile root>/ConfigEngine/properties/wkplc_dbdomain.properties file and ensure the following values are set correctly:
   • release.DbPassword=<your database user password>
   • community.DbPassword=<your database user password>
   • customization.DbPassword=<your database user password>
   • jcr.DbPassword=<your database user password>
   • likeminds.DbPassword=<your database user password>
   • feedback.DbPassword=<your database user password>
4. Edit the <wp_profile root>/ConfigEngine/properties/wkplc_comp.properties file and ensure the following values are set correctly:
   • XmlAccessHost=<your Portal hostname>
   • XmlAccessPort=<the port you use to access Portal>

The update process removes plain text passwords from the wkplc*.properties files. To keep these passwords in the properties files, include the following line in the wkplc.properties file:

PWordDelete=false

There are several different methods to roll back the cumulative fix, and they are:

• Use a Graphical User Interface (GUI) to roll back
• Use a command line roll back
• Use silent mode roll back
• Use console mode roll back

1. On the Farm Master Server execute the following command from within the path of the profile to configure. Note: If you are rolling back the CF on an empty portal then many of the expected artifacts will not exist and the rollbackCF command will fail. In this case you must define the isEmptyPortal property on the command line.
   Example:

   rollbackCF.sh -DisEmptyPortal=true

   • Unix/Linux:

     (profile_root/PortalServer/bin/rollbackCF.sh -DPortalAdminPwd=(password) -DWasPassword=(password)

   • Windows:

     (profile_root)\PortalServer\bin\rollbackCF.bat -DPortalAdminPwd=(password) -DWasPassword=(password) 

   • IBM i:

     (profile_root)/PortalServer/bin/rollbackCF.sh -DPortalAdminPwd=(password) -DWasPassword=(password)

   Important: If the rollbackCF command fails for any reason, check the error logs and correct error conditions, then stop HCL Digital Experience before re-running.
2. On the Farm Support Server execute the following command from within the path of the profile to configure.
   Note: If you are rolling back the CF on an empty portal then many of the expected artifacts will not exist and the rollbackCF command will fail. In this case you must define the isEmptyPortal property on the command line.

   Example:

   rollbackCF.sh -DisEmptyPortal=true 

   Note: If the Farm Support Server only has read-only access to the Portal Binaries use the -DSharedBinaries=true flag with the rollbackCF command:

   • Unix/Linux:

     (profile_root)/PortalServer/bin/rollbackCF.sh -DPortalAdminPwd=(password) -DWasPassword=(password)

   • Windows:

     (profile_root)\PortalServer\bin\rollbackCF.bat -DPortalAdminPwd=(password) -DWasPassword=(password

   • IBM i:

     (profile_root)/PortalServer/bin/rollbackCF.sh -DPortalAdminPwd=(password) -DWasPassword=(password)

   Important: If the rollbackCF command fails for any reason, check the error logs and correct error conditions, then stop HCL Digital Experience before re-running.
3. If you are running an external web server, and you are using the WebSphere Application Server automatic generation and propagation of the plug-in, then restart the web server. If you are not using the automatic generation and propagation, then perform the following steps:
   • Regenerate the web server plugin.
   • Copy the plugin-cfg.xml file to the plugin directory.
   • Restart the web server.
4. If you previously customized any configuration files in the wp_profile_root/PortalServer/config directory, check to see if rolling back the cumulative fix affected those files by restoring a version of the files that was saved when the cumulative fix was originally installed. If it did affect the files, you must perform the same customization on the restored version of each file.
5. If necessary, redeploy any customizations, including JSPs, to the WCM portlets (if using HCL Web Content Manager), any other portlets, or any other Portal enterprise applications, if these were customized prior to rolling back the cumulative fix.
6. If using HCL Web Content Manager and have installed any official extensions (such as the WCM Multilingual Solution (MLS) or WCM Social Media Publisher (SMP)), then run the following task to update them:
   • Unix/Linux:

     (profile_root)/ConfigEngine/ConfigEngine.sh action-update-wcm-extensions -DWasPassword=(password) -DPortalAdminPwd=(password)

   • Windows:

     (profile_root)\ConfigEngine\ConfigEngine.bat action-update-wcm-extensions -DWasPassword=(password) -DPortalAdminPwd=(password)

   • IBM i:

     (profile_root)/ConfigEngine/ConfigEngine.sh action-update-wcm-extensions -DWasPassword=(password) -DPortalAdminPwd=(password)

   The task can be run even if you are not sure if you had the extensions enabled. If you want to check if they were enabled the following tasks can be used:
   • For MLS, use:

     ConfigEngine.sh|bat action-is-wcm-mls-enabled

   • For SMP, use:

     ConfigEngine.sh|bat action-is-wcm-smp-enabled

7. For rollback to CF03 or earlier level only: If the Brightcove integration was enabled, remove the old Brightcove plugins, then configure HCL Portal to add the new Brightcove plugins.
8. For rollback to CF03 or earlier level only: If using Rich Media Edition, remove the Rich Media Edition plugin, restart the Portal Server, then configure HCL Portal to add the Rich Media Edition plugins.
9. If you have set up a remote search server or document conversion server for use with HCL Portal Version 8.5, then whenever you roll back a cumulative fix to the portal server, you should also roll back the corresponding cumulative fix to the remote server.
10. Clear the browser cache.