IBM Support

IBM WebSphere Portal 7.0.0.1 Combined Cumulative Fix Readme - cluster

Product readme


Abstract

IBM WebSphere Portal 7.0.0.1 Combined Cumulative Fix cluster installation instructions for all editions, including WebSphere Portal Express- Idle Standby.

Content

7.0.0.1: Readme for IBM WebSphere Portal 7.0.0.1 Combined Cumulative fix - cluster

Table of Contents






About Combined Cumulative Fix


These are the instructions on how to install a WebSphere Portal Combined Cumulative Fix. The Combined Cumulative Fix is a package of WebSphere Portal fixes and Web Content Manager Cumulative fixes.

Back to top





Space requirements


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

z/OS: 625 cylinders in the directory where you download the cumulative fix, 625 cylinders in the <Portal Configuration HFS>, 625 cylinders in <WebSphere Configuration HFS> and 1250 cylinders in your system temp directory.

All other platforms: 2 GB in the directory where you download the cumulative fix, 1 GB in <Portal_Install_Root>, 1 GB in <wp_profile_root> temporary disk space and 1 GB in your system temp directory, such as /tmp on Unix or Linux platforms or C:\temp on the Microsoft Windows platform.



Back to top




Cluster upgrade planning
There are two options for performing upgrade in a clustered environment. One option is to upgrade the cluster while the entire cluster has been taken offline from receiving user traffic. The upgrade is performed on every node in the cluster before the cluster is brought back online to receive user traffic. This is the recommended approach for an environment with multiple Portal clusters since 24x7 availability can be maintained. Please see the following document for details: Multiple Cluster Setup with WebSphere Portal
It is also the simplest approach to use in a single cluster environment if maintenance windows allow for the Portal cluster to be taken offline.

For single cluster environments, which cannot tolerate the outage required to take a cluster offline and perform the upgrade, you can utilize the single-cluster 24x7 availability process. Review the following requirements and limitations for performing product upgrades while maintaining 24x7 availability in a single cluster ( NOTE: Ensure that you understand this information before upgrading your cluster):

Assumptions for maintaining 24x7 operation during the upgrade process:

  • Limitations on 24x7 maintenance:

Back to top




Steps for installing Combined Cumulative Fix (single-cluster procedure)

Before you begin:

Familiarize yourself with the Portal Upgrade Best Practices available from IBM Remote Technical Support for WebSphere Portal.

  • Portal Upgrades: Best Practices for V7.0
  • For instructions on how to validate your environment prior to the upgrade, see the instructions for running the Health Checker tool for WebSphere Portal at:

  • Health Checker tool for WebSphere Portal V7.0
  • IMPORTANT: Certain security configurations can cause failures with the upgrade. Please check the following technote to see if this may apply to your environment.

  • Fix Pack 7.0.0.1 fails at action-import-defaultnodes-wp.filestore/base task.


  • NOTE: When instructed to stop or start the WebSphere_Portal server, stop or start all Portal server instances including vertical cluster members on the node.
    1. Perform the following steps before installing to the Combined Cumulative Fix:
      1. Before you install this combined cumulative fix, check to see if the list of fixes already installed on your system is included in the list of fixes provided in this combined cumulative fix. If you have temporary, interim or cumulative fixes on your system that are not included in this Combined Cumulative Fix, then uninstall those fixes before installing this Combined Cumulative Fix and contact IBM Support for an updated version of that fix, or for more information.
      2. Verify that the information in the wkplc.properties, wkplc_dbtype.properties, wkplc_dbdomain.properties, and wkplc_comp.properties files is correct on each node in the cluster. If using multiple profiles, also verify that the information in each profile is correct. WebSphere Portal 7 introduced support for multiple profiles. See the following link for multiple profiles Supporting multiple profiles: wp7.
        1. Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
        2. Ensure that the DbUser (database user) and DbPassword (database password) parameters are defined correctly for all database domains in the wkplc_dbdomain.properties file.
        3. Unix/Linux/Windows/IBM i Only: The WebSphere Portal Update Installer 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.
        4. Ensure that the value of the XmlAccessPort property in wkplc_comp.properties matches the value of the port used for HTTP connections to the WebSphere Portal server.
      3. Special considerations for multiple profiles or binary install or migration upgrade:
        1. If you did a binary installation and created a WebSphere Portal profile later, or your Portal 7.0.0.x was migrated from 6.1.x, ensure that the PortalServer/wps.properties file correctly references the profile. The Portal Update Installer uses the wps.properties file to determine which profile is the primary profile to update. Failure to complete this step could result in an inoperable Portal server after the Combined Cumulative Fix installation completes.
          1. Edit the <PortalServer root>/wps.properties file in a text editor
          2. Add these two properties if they do not already exist:
            ProfileName=<your profile name, e.g. wp_profile>
            ProfileDirectory=<your profile directory, e.g. /opt/IBM/WebSphere/wp_profile>

            Note: The ProfileDirectory property should use forward slash (/) instead of backslash (\) on Windows.
        2. If you have created multiple profiles. the Portal Update Installer will automatically upgrade all profiles. If you want to specify which profiles are updated, then complete the following steps:
          1. Edit the <PortalServer root>/wps.properties file in a text editor
          2. Add this property if it does not already exist:
            AutoUpdateMultipleProfiles=<comma separated list of profile names, e.g. wp_profile, wp_profile2, wp_profile3>
        3. If using Multiple Profiles, verify all your profiles are at the same level before starting upgrade.
      4. Perform the following steps to download the cumulative fix and the WebSphere Portal Update Installer:
        1. Download the latest Combined Cumulative fix (e.g. 7.0.0.1-WP-WCM-Combined-CFPMnnnnn-CFnnn), and the latest WebSphere Portal Update Installer from http://www.ibm.com/support/docview.wss?uid=swg24027857.
        2. Create the PortalServer_root/update directory and extract the WebSphere Portal Update Installer file into this directory.
        3. Create the PortalServer_root/update/fixes directory and extract the 7.0.0.1-WP-WCM-Combined-CFPMnnnnn-CFnnn.zip file into this directory, where n is the numbers associated with the version of the Combined Cumulative fix. Note for z/OS users: refer to Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer for detailed descriptions of how to execute steps ii. and iii. above.
      5. Ensure that all nodes have been synchronized before starting to upgrade.

    2. Ensure that automatic synchronization is disabled on all nodes to be upgraded. When the automatic synchronization is enabled, the node agent on each node automatically contacts the deployment manager at startup and at every synchronization interval to attempt to synchronize the node's configuration repository with the master repository managed by the deployment manager.
      1. In the administrative console for the deployment manager, select System administration > Node agents in the navigation tree.
      2. Click nodeagent for the required node.
      3. Click File Synchronization Service.
      4. Uncheck the Automatic Synchronization check box on the File Synchronization Service page to disable the automatic synchronization feature and then click OK.
      5. Repeat these steps for all other nodes to be upgraded.
      6. Click Save to save the configuration changes to the master repository.
      7. Select System administration > Nodes in the navigation tree
      8. Select all nodes that are not synchronized, and click on Synchronize
      9. Select System administration > Node agents in the navigation tree
      10. For the primary node, select the nodeagent and click Restart
      11. Select the nodeagents of all additional nodes and click Stop


        NOTE
        : Do not attempt to combine steps 3 and 4 together! The update must be performed first on the primary node and then on the additional nodes, in accordance with the below instructions.

    3. Perform the following steps to upgrade WebSphere Portal on the primary node:
      1. Only Required if following the 24x7 single cluster upgrade: Stop IP traffic to the node you are upgrading:
        • z/OS only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,QUIesce,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,QUIesce,POrt=<portnum>.
          Reactivate it by replacing the QUIesce with RESUME keyword.
        • If you are using the Web server plug-in for load balancing, perform the following steps to stop traffic to the node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members.
          2. Locate the cluster member you are upgrading and change the value in the Configured weight column to zero. NOTE: Record the previous value to restore the setting when the upgrade is complete.
          3. Click Update to apply the change.
        • Note that the web server plug-in will check periodically for configuration updates based on the value of Refresh Configuration Interval property for the Web server plug-in (default value is 60 seconds). You can check this value on the Deployment Manager administrative console by selecting Servers>Server Types>Web Servers>web_server_name>Plug-in Properties.
        • If automatic propagation of the plug-in configuration file is enabled on the web server(s) disable it from the Deployment Manager administrative console by going to Servers>Server Types>Web Servers>web_server_name>Plug-in Properties. and unchecking Automatically propagate plug-in configuration file.
      2. Choose either the graphical user interface installation option or the command line installation option:

        NOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line).

        NOTE: If the installation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task.


        If using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall="true", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI.



        Enter the following command to launch the graphical user interface installation program:
        • Windows: PortalServer_root\update> updatePortalWizard.bat
        • Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh

          -- OR --
        • Perform the following steps to launch the installation program from the command line:
          1. Enter the following command to launch the installation program (NOTE: Enter the command on one line):
            • Windows: PortalServer_root\update> updatePortal.bat -install
              -installDir "<PortalServer_root>"
              -fix
              -fixDir "<PortalServer_root>\update\fixes"
              -fixes < Cumulative fix >
            • Unix/Linux: PortalServer_root/update> ./updatePortal.sh -install
              -installDir "<PortalServer_root>"
              -fix
              -fixDir "<PortalServer_root>/update/fixes"
              -fixes < Cumulative fix >
            • i5/OS: portal_server_root/update> updatePortal.sh -install
              -installDir "<portal_server_root>"
              -fix
              -fixDir "<portal_server_root>/update/fixes"
              -fixes < Cumulative fix >
            • z/OS: If the Health Checker Tool for WebSphere Portal V7.0 has not been run then it needs to be run before installing the Combined Cumulative Fix. Execute the following commands to install the Combined Cumulative Fix:
              1. From <was_profile_root>/bin directory:
                . ./setupCmdLine.sh
              2. PortalServer_root/update> ./updatePortal.sh -install
                -installDir "<PortalServer_root>"
                -fix
                -fixDir "<PortalServer_root>/update/fixes"
                -fixes <Cumulative fix>

                Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer. Submit the JCLs, and then return here to continue.

      3. If you do not have any profiles at this point (because you are in the process of migration from WebSphere Portal 6.1 or Installing an additional node for a cluster or creating multiple profiles) no post installation steps are necessary and you can continue with the next steps that create the profiles as outlined by the according documentation.
      4. z/OS: If doing an upgrade as part of a migration from a previous version (eg. 6.x), run ./ConfigEngine.sh gather-migration-files command from the <wp_profile_root>/ConfigEngine directory.
      5. Run the following command:
        • z/OS: <wp_profile_root>/PortalServer/bin/UpdateProfile.sh install CF skipPreCheckProfile
        • All other platforms: To update a profile after an upgrade, the following command can be used to update profiles that are not included in AutoUpdateMultipleProfiles. All profiles that were not included in AutoUpdateMultipleProfiles need to be updated after the upgrade is done. All profiles must be at the same level for future upgrades to be applied. See the following link for multiple profiles Supporting multiple profiles: wp7.

          <wp_profile_root>/PortalServer/bin/UpdateProfile.bat|.sh install CF

      6. This cumulative fix provides updates to OSGi bundles. After installing the cumulative fix, run "<profile location>/bin/osgiCfgInit.sh" (for IBM i the command is just osgiCfgInit, for Microsoft Windows the command is osgiCfgInit.bat) to clear the caches and make the OSGi container pick up the updates to the modified OSGi bundles. Note that it is recommended to stop the portal server before running the osgiCfgInit command.
      7. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
      8. Only Required if following the 24x7 single cluster upgrade: Restore IP traffic to the node you upgraded:
        • z/OS Only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,RESUME,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,RESUME,POrt=<portnum>.
        • If you are using the Web server plug-in for load balancing, perform the following steps to restore traffic to the upgraded node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members to obtain a view of the collection of cluster members.
          2. Click Update to apply the change.
        • If you previously disabled automatic propagation of the Web server(s), re-enable it now using the Deployment Manager administration console by going to Servers>Server Types>Web Servers>web_server_name>Plug-in Properties and checking Automatically propagate plug-in configuration file .
        • If you are not using automatic generation and propagation for the Web server plug-in, manually generate and/or propagate the plugin-cfg.xml file to the Web servers.



          NOTE: Do not attempt to upgrade additional nodes until after completing Step 3 (Primary Node)! The update for the primary must be performed and completed first then upgrade any additional nodes. Additional nodes upgrades can be performed sequentially or in parallel. Update the additional nodes in accordance with the below instructions.
    4. Perform the following steps to upgrade WebSphere Portal on each additional node after completing the upgrade on the primary node:
      1. Only Required if following the 24x7 single cluster upgrade: Stop IP traffic to the node you are upgrading:
        • z/OS only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,QUIesce,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,QUIesce,POrt=<portnum>.
          Reactivate it by replacing the QUIesce with RESUME keyword.
        • If you are using the Web server plug-in for load balancing, perform the following steps to stop traffic to the node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members to obtain a view of the collection of cluster members.
          2. Locate the cluster member you are upgrading and change the value in the Configured weight column to zero. NOTE: Record the previous value to restore the setting when the upgrade is complete.
          3. Click Update to apply the change.
        • Note that the web server plug-in will check periodically for configuration updates based on the value of Refresh Configuration Interval property for the Web server plug-in (default value is 60 seconds). You can check this value on the Deployment Manager administrative console by selecting Servers>Server Types>Web Servers>web_server_name>Plug-in Properties.
      2. Choose either the graphical user interface installation option or the command line installation option:

        NOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line).

        NOTE: If the installation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task.


        If using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall="true", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI.




        Enter the following command to launch the graphical user interface installation program:
        • Windows: PortalServer_root\update> updatePortalWizard.bat
        • Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh

          -- OR --
        • Perform the following steps to launch the installation program from the command line:
          1. Enter the following command to launch the installation program (NOTE: Enter the command on one line):
            • Windows: PortalServer_root\update> updatePortal.bat -install
              -installDir "<PortalServer_root>"
              -fix
              -fixDir "<PortalServer_root>\update\fixes"
              -fixes < Cumulative fix >
            • Unix/Linux: PortalServer_root/update> ./updatePortal.sh -install
              -installDir "<PortalServer_root>"
              -fix
              -fixDir "<PortalServer_root>/update/fixes"
              -fixes < Cumulative fix >
            • i5/OS: portal_server_root/update> updatePortal.sh -install
              -installDir "<portal_server_root>"
              -fix
              -fixDir "<portal_server_root>/update/fixes"
              -fixes < Cumulative fix >
            • z/OS: If the Health Checker Tool for WebSphere Portal V7.0 has not been run then it needs to be run before installing the Combined Cumulative Fix. Execute the following commands to install the Combined Cumulative Fix:
              1. From <was_profile_root>/bin directory:
                . ./setupCmdLine.sh
              2. PortalServer_root/update> ./updatePortal.sh -install
                -installDir "<PortalServer_root>"
                -fix
                -fixDir "<PortalServer_root>/update/fixes"
                -fixes <Cumulative fix>

                Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer. Submit the JCLs, and then return here to continue.

      3. If you do not have any profiles at this point (because you are in the process of migration from WebSphere Portal 6.1 or Installing an additional node for a cluster or creating mutliple profiles) no post installation steps are necessary and you can continue with the next steps that create the profiles as outlined by the according documentation.
      4. z/OS: If doing an upgrade as part of a migration from a previous version (eg. 6.x), run ./ConfigEngine.sh gather-migration-files command from the <wp_profile_root>/ConfigEngine directory.
      5. Run the following command:
        • z/OS: <wp_profile_root>/PortalServer/bin/UpdateProfile.sh install CF skipPreCheckProfile
        • All other platforms: To update a profile after an upgrade, the following command can be used to update profiles that are not included in AutoUpdateMultipleProfiles. All profiles that were not included in AutoUpdateMultipleProfiles need to be updated after the upgrade is done. All profiles must be at the same level for future upgrades to be applied. See the following link for multiple profiles Supporting multiple profiles: wp7.

          <wp_profile_root>/PortalServer/bin/UpdateProfile.bat|.sh install CF

      6. This cumulative fix provides updates to OSGi bundles. After installing the cumulative fix, run "<profile location>/bin/osgiCfgInit.sh" (for IBM i the command is just osgiCfgInit, for Microsoft Windows the command is osgiCfgInit.bat) to clear the caches and make the OSGi container pick up the updates to the modified OSGi bundles. Note that it is recommended to stop the portal server before running the osgiCfgInit command.
      7. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
      8. Only Required if following the 24x7 single cluster upgrade: Restore IP traffic to the node you upgraded:
        • z/OS Only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,RESUME,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,RESUME,POrt=<portnum>.
        • If you are using the Web server plug-in for load balancing, perform the following steps to restore traffic to the upgraded node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members to obtain a view of the collection of cluster members.
          2. Click Update to apply the change.
    5. Perform the following post-cluster installation upgrade steps:
      1. Re-enable automatic synchronization on all nodes in the cluster if you disabled it earlier.
        1. In the administrative console for the deployment manager, select System administration > Node agents in the navigation tree.
        2. Click nodeagent for the required node.
        3. Click File Synchronization Service.
        4. Check the Automatic Synchronization check box on the File Synchronization Service page to enable the automatic synchronization feature and then click OK.
        5. Repeat these steps for all remaining nodes.
        6. Click Save to save the configuration changes to the master repository.
        7. Select System administration > Nodes in the navigation tree
        8. Select all nodes that are not synchronized, and click on Synchronize
        9. Select System administration > Node agents in the navigation tree
        10. Select all node agents where automatic synchronization has been re-enabled and click Restart.
      2. Redeploy your customization, including JSPs, to the WCM portlets if you are using Web Content Manager and you customized the portlets prior to installing the Combined Cumulative fix.
        1. To update the deployed remote rendering portlet:
        2. To update the deployed PDM Doc List Portlet:
        3. Log out of Portal for changes to take effect.
      3. Review the following documentation "Configuration Changes and Options introduced in WP/WCM V7.0.0.1 and 7.0.0.2 Combined Cumulative Fixes" to see if it applies to your environment.



    Back to top




    Steps for uninstalling
    Combined Cumulative Fix (single-cluster procedure)


    NOTE: Changing the server context root after upgrading is an unsupported uninstall path. To uninstall after changing the context root, you must first change the server context root back to the values of the previous version.


    NOTE: Configuring Portal Server from a stand-alone environment to a cluster environment after upgrading is an unsupported uninstall path.

    NOTE: When instructed to stop or start the WebSphere_Portal server, stop or start all Portal server instances including vertical cluster members on the node.
    1. Perform the following steps before you uninstall the Combined Cumulative Fix:

      NOTE: The steps listed in this point need to be performed on all nodes.
      1. Verify that the information in the wkplc.properties, wkplc_dbtype.properties, wkplc_dbdomain.properties, and wkplc_comp.properties files are correct on each node in the cluster. If using multiple profiles, also verify that the information in each profile is correct. See the following link for multiple profiles Supporting multiple profiles: wp7.
        • Unix/Linux/Windows/IBM i Only:The WebSphere Portal Update Installer 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.
      2. Ensure that all nodes have been synchronized before starting to uninstall.
    2. Perform the following steps to disable automatic synchronization:
      1. In the administrative console for the deployment manager, select System administration>Node agents in the navigation tree.
      2. Click nodeagent for the required node.
      3. Click File Synchronization Service.
      4. Uncheck the Automatic Synchronization check box on the File Synchronization Service page to disable the automatic synchronization feature and then click OK.
      5. Repeat these steps for all other nodes to be downgraded.
      6. Click Save to save the configuration changes to the master repository.
      7. Select System administration > Nodes in the navigation tree.
      8. Select all nodes that are not synchronized, and click on Synchronize.
      9. Select System administration > Node agents in the navigation tree.
      10. For the primary node, select the nodeagent and click Restart.
      11. Select the nodeagents of all additional nodes and click Stop.



        NOTE: Do not attempt to combine steps 3 and 4 together! The uninstall must be performed first on the primary node and then on the additional nodes, in accordance with the below instructions.
    3. Perform the following steps to uninstall the cumulative fix on the primary node:
      1. Only Required if following the 24x7 single cluster uninstall: Stop IP traffic to the node where you are uninstalling:
        • z/OS only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,QUIesce,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,QUIesce,POrt=<portnum>.
          Reactivate it by replacing the QUIesce with RESUME keyword.
        • If you are using the Web server plug-in for load balancing, perform the following steps to stop traffic to the node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members to obtain a view of the collection of cluster members.
          2. Locate the cluster member you are downgrading and change the value in the Configured weight column to zero. NOTE: Record the previous value to restore the setting when the downgrade is complete.
          3. Click Update to apply the change.
        • Note that the web server plug-in will check periodically for configuration updates based on the value of Refresh Configuration Interval property for the Web server plug-in (default value is 60 seconds). You can check this value on the Deployment Manager administrative console by selecting Servers>Server Types>Web Servers>web_server_name>Plug-in Properties.
        • If automatic propagation of the plug-in configuration file is enabled on the web server(s) disable it from the Deployment Manager administrative console by going to Servers>Server Types>Web Servers>web_server_name>Plug-in Properties and unchecking Automatically propagate plug-in configuration file.
      2. Choose either the graphical user interface uninstallation option or the command line uninstallation option:

        NOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line).

        NOTE: If the uninstallation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task.



        If using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall="true", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI.
        • Enter the following command to launch the graphical user interface uninstallation program:
          • Windows: PortalServer_root\update> updatePortalWizard.bat
          • Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh

            - OR -
          • Perform the following steps to launch the uninstallation program from the command line:
            1. Enter the following command to launch the uninstallation program (NOTE: Enter the command on one line):
              • Windows: PortalServer_root\update> updatePortal.bat -uninstall
                -installDir "<PortalServer_root>"
                -fix
                -fixes < Cumulative fix >
              • Unix/Linux: PortalServer_root/update> ./updatePortal.sh -uninstall
                -installDir "<PortalServer_root>"
                -fix
                -fixes < Cumulative fix >
              • i5/OS: portal_server_root/update> updatePortal.sh -uninstall
                -installDir "<portal_server_root>"
                -fix
                -fixes < Cumulative fix >
              • z/OS: If the Health Checker Tool for WebSphere Portal V7.0 has not been run then it needs to be run before uninstalling the Combined Cumulative Fix. Execute the following commands to uninstall the Combined Cumulative Fix:
                1. From <was_profile_root>/bin directory:
                  . ./setupCmdLine.sh
                2. PortalServer_root/update> ./updatePortal.sh -uninstall
                  -installDir "<PortalServer_root>"
                  -fix
                  -fixes <Cumulative fix>

                  Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer. Submit the JCLs, and then return here to continue.
      3. Run the following command:
        • z/OS: <wp_profile_root>/PortalServer/bin/UpdateProfile.sh uninstall CF skipPreCheckProfile
        • All other platforms: To downgrade a profile after an uninstall, the following command can be used to downgrade all profiles (including the primary profiles). See the following link for multiple profiles Supporting multiple profiles: wp7.

          <wp_profile_root>/PortalServer/bin/UpdateProfile.bat|.sh uninstall CF

      4. If you previously customized any configuration files in the wp_profile_root/PortalServer/config directory, check to see if uninstalling 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. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
      6. Only Required if following the 24x7 single cluster uninstall: Restore IP traffic to the node where you uninstalled:
        • z/OS Only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,RESUME,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,RESUME,POrt=<portnum>.
        • If you are using the Web server plug-in for load balancing, perform the following steps to restore traffic to the downgraded node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members to obtain a view of the collection of cluster members.
          2. Click Update to apply the change.
        • If you previously disabled automatic propagation of the Web server(s), re-enable it now using the Deployment Manager administration console by going to Servers>Server Types>Web Servers>web_server_name>Plug-in Properties and checking Automatically propagate plug-in configuration file.
        • If automatic plug-in generation and propagation is disabled, manually generate and/or propagate the plugin-cfg.xml file to the Web servers.



          NOTE: Do not attempt to uninstall additional nodes until after completing the Step 3 (Primary Node)! The uninstall for the primary must be performed and completed first then uninstall any additional nodes. Additional nodes uninstalls can be performed sequentially or in parallel. uninstall the additional nodes in accordance with the below instructions.

    4. Perform the following steps to uninstall the cumulative fix on the additional node; NOTE: Repeat this step for each additional node:
      1. Only Required if following the 24x7 single cluster uninstall: Stop IP traffic to the node where you are uninstalling:
        • z/OS only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,QUIesce,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,QUIesce,POrt=<portnum>.
          Reactivate it by replacing the QUIesce with RESUME keyword.
        • If you are using the Web server plug-in for load balancing, perform the following steps to stop traffic to the node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members to obtain a view of the collection of cluster members.
          2. Locate the cluster member you are downgrading and change the value in the Configured weight column to zero. NOTE: Record the previous value to restore the setting when the downgrade is complete.
          3. Click Update to apply the change.
        • Note that the web server plug-in will check periodically for configuration updates based on the value of Refresh Configuration Interval property for the Web server plug-in (default value is 60 seconds). You can check this value on the Deployment Manager administrative console by selecting Servers>Server Types>Web Servers>web_server_name>Plug-in Properties.
      2. Choose either the graphical user interface uninstallation option or the command line uninstallation option:

        NOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line).

        NOTE: If the uninstallation fails, use the IBM Support Assistant to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task.



        If using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall="true", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI.
        • Enter the following command to launch the graphical user interface uninstallation program:
          • Windows: PortalServer_root\update> updatePortalWizard.bat
          • Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh

            - OR -
          • Perform the following steps to launch the uninstallation program from the command line:
            1. Enter the following command to launch the uninstallation program (NOTE: Enter the command on one line):
              • Windows: PortalServer_root\update> updatePortal.bat -uninstall
                -installDir "<PortalServer_root>"
                -fix
                -fixes < Cumulative fix >
              • Unix/Linux: PortalServer_root/update> ./updatePortal.sh -uninstall
                -installDir "<PortalServer_root>"
                -fix
                -fixes < Cumulative fix >
              • i5/OS: portal_server_root/update> updatePortal.sh -uninstall
                -installDir "<portal_server_root>"
                -fix
                -fixes < Cumulative fix >
              • z/OS: If the Health Checker Tool for WebSphere Portal V7.0 has not been run then it needs to be run before uninstalling the Combined Cumulative Fix. Execute the following commands to uninstall the Combined Cumulative Fix:
                1. From <was_profile_root>/bin directory:
                  . ./setupCmdLine.sh
                2. PortalServer_root/update> ./updatePortal.sh -uninstall
                  -installDir "<PortalServer_root>"
                  -fix
                  -fixes <Cumulative fix>

                  Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer. Submit the JCLs, and then return here to continue.
      3. Run the following command:
        • z/OS: <wp_profile_root>/PortalServer/bin/UpdateProfile.sh uninstall CF skipPreCheckProfile
        • All other platforms: To downgrade a profile after an uninstall, the following command can be used to downgrade all profiles (including the primary profiles). See the following link for multiple profiles Supporting multiple profiles: wp7.

          <wp_profile_root>/PortalServer/bin/UpdateProfile.bat|.sh uninstall CF

      4. If you previously customized any configuration files in the wp_profile_root/PortalServer/config directory, check to see if uninstalling 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. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
      6. Only Required if following the 24x7 single cluster downgrade: Restore IP traffic to the node where you uninstalled:
        • z/OS Only: If you are using Sysplex Distributor, then
          VARY TCPIP,,SYSPLEX,RESUME,JOBNAME=<WP_Controler> or
          VARY TCPIP,,SYSPLEX,RESUME,POrt=<portnum>.
        • If you are using the Web server plug-in for load balancing, perform the following steps to restore traffic to the downgraded node:
          1. In the Deployment Manager administrative console, click Servers>Clusters>WebSphere application server clusters>cluster_name>Cluster members to obtain a view of the collection of cluster members.
          2. Click Update to apply the change.
    5. Perform the following post-uninstallation steps
      1. Re-enable automatic synchronization on all nodes in the cluster if you disabled it earlier.
        1. In the administrative console for the deployment manager, select System administration > Node agents in the navigation tree.
        2. Click nodeagent for the required node. 
        3. Click File Synchronization Service.
        4. Check the Automatic Synchronization check box on the File Synchronization Service page to enable the automatic synchronization feature and then click OK.
        5. Repeat these steps for all remaining nodes.
        6. Click Save to save the configuration changes to the master repository.
        7. Select System administration > Nodes in the navigation tree.
        8. Select all nodes that are not synchronized, and click on Synchronize.
        9. Select System administration > Node agents in the navigation tree.
        10. Select all node agents where automatic synchronization has been re-enabled and click Restart.
      2. Redeploy your customization, including JSPs, to the WCM portlets if you are using Web Content Manager and you customized the portlets prior to uninstalling the Combined Cumulative fix.
        1. To update the deployed remote rendering portlet:
        2. To update the deployed PDM Doc List Portlet:
        3. Log out of Portal for changes to take effect.



    Back to top




    Known issues for latest Combined Cumulative Fix


    Problem: Page theme is changed to current Portal default theme when changing page content layout.
    Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.


    Problem: If a WCM cumulative fix is installed on a Websphere portal 7.0.0.0 or 7.0.0.1 server where the date of the server install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
    Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.


    Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
    Solution
    : The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.


    Problem: After uninstall of combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
    Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.


    Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
    Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.


    Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
    Solution: This is documented as a known limitation.


    Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
    The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
    Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.


    For a list of known issues for Previous WebSphere Portal 7.0.0.1 Combined Cumulative Fixes, see IBM WebSphere Portal 7.0.0.1 Combined Cumulative Fix Previous Known Issues for details.

    Back to top




    Additional information

    You can find additional information on the WebSphere Portal support page.

    Back to top




    Trademarks and service marks

    For trademark attribution, visit the IBM Terms of Use Web site.

    Back to top

    Document information

    More support for: WebSphere Portal

    Software version: 7.0.0.1

    Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS

    Software edition: Enable, Express, Extend, Server

    Reference #: 7021247

    Modified date: 06 December 2012