IBM Support

7.0.0.2: Readme for IBM WebSphere Portal 7.0 fix pack 2 (7.0.0.2) - stand-alone

Product readme


Abstract

IBM WebSphere Portal fix pack stand-alone installation instructions for all editions including WebSphere Portal Express.

Content

7.0.0.2: Readme for IBM WebSphere Portal 7.0 fix pack 2 (7.0.0.2) - stand-alone


7.0.0.2: Readme for IBM WebSphere Portal 7.0 fix pack 2 (7.0.0.2) - stand-alone

Table of Contents





About Fix Pack 7.0.0.2


Installing Fix Pack 7.0.0.2 with the latest WebSphere Portal Update Installer for version 7.0 raises the fix level of your product to version 7.0.0.2.

Refer to the installation instructions in the Steps for installing Fix Pack 7.0.0.2 section for information.

Fix packs can be downloaded from the version 7.0.0.2 download page, also linked above on the "Download" tab of this document.

Warning:
  • The following items are included in this fix pack:
    • Updated underlying supported hardware and software; see supported hardware and software requirements for details
    • Included APARs from many WebSphere Portal components
    • The complete list of fixes integrated into this fix pack is found in the "Fix List" tab of this document.
    • WebSphere Portal 7.0.0.2 allows the use of theme optimization. The theme optimization module framework allows you to create themes using different module extensions to contribute to different areas of the page in order to provide flexibility, enhance the user experience, and maximize performance. See 7.0.0.2: Designing a portal site using theme optimization for more information on Theme Optimization.
Back to top




Space requirements
  • Ensure that enough space is available in the following directories: 2 GB in the directory where you download the fix pack, 1 GB in <Portal_Install_Root>, 1 GB in <wp_profile> 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




Steps for installing
Fix Pack 7.0.0.2

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 7.0
  • For instructions on how to validate your upgrade 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.

    1. Perform the following steps before upgrading to Version 7.0.0.2:
      1. Review the supported hardware and software requirements for this fix pack. If necessary, upgrade all hardware and software before applying this fix pack. NOTE: You can download the latest WebSphere Application Server interim fixes from http://www.ibm.com/software/webservers/appserv/was/support/.
      2. If you are running an external Web server such as IBM HTTP server, stop the Web server.
      3. IBM i only: Database transfer must have been performed from the Apache Derby database to another database prior upgrading to Portal version 7.0.0.2.
      4. Verify that the information in the wkplc.properties, wkplc_comp.properties,wkplc_dbdomain.properties and wkplc_dbtype.properties files are correct. 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.
        • Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
        • Ensure that the DbUser (database user) and DbPassword (database password) parameters are defined correctly for all database domains in the wkplc_dbdomain.properties file.
        • 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.
        • 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.
      5. Special considerations for multiple profiles or binary install:
        1. If you did a binary installation and created a WebSphere Portal profile later, 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 Fix Pack 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.
      6. Perform the following steps to download the Fix Pack, the ptflist file, and the WebSphere Portal Update Installer:
        1. Download the fix pack file, the ptflist file, and the latest WebSphere Portal Update Installer from http://www.ibm.com/support/docview.wss?uid=swg24031676.
        2. Create the PortalServer_root/update directory and extract the WebSphere Portal Update Installer file into this directory.
        3. Create the PortalServer_root/update/fixpacks directory and extract the WP_PTF_7002.zip file into this directory and copy the ptflist file into this directory.
      7. The WebSphere Portal 7.0.0.2 fix pack performs index (schema) modifications to the Portal databases during the fix pack application. Please see the following documentation for the details: http://www.ibm.com/support/docview.wss?uid=swg27023802. It is possible to disable the automatic application and instead manually apply the indexes. For that, make sure the following property is set in wkplc_dbtype.properties before starting the fix pack application: DbSafeMode=true. If DbSafeMode is not set to true then ensure that the DbUser in the wkplc_dbdomain.properties file for all domains on DB2 has explicit DBADM authority.
    2. Choose either the graphical user interface installation option or the command line installation option:

      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.
      • 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. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
          2. 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>"
              -fixpack
              -fixpackDir "<PortalServer_root>\update\fixpacks"
              -fixpackID WP_PTF_7002
            • Unix/Linux: PortalServer_root/update> ./updatePortal.sh -install
              -installDir "<PortalServer_root>"
              -fixpack
              -fixpackDir "<PortalServer_root>/update/fixpacks"
              -fixpackID WP_PTF_7002
            • IBM i: portal_server_root/update> updatePortal.sh -install
              -installDir "<portal_server_root>"
              -fixpack
              -fixpackDir "<portal_server_root>/update/fixpacks"
              -fixpackID WP_PTF_7002

        • 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.
        • 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 7002
    3. Perform the following post installation steps:
      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 plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps:
        1. Regenerate the Web server plugin.
        2. Copy the plugin-cfg.xml file to the Plugin directory.
        3. Restart the Web server.
      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 fix pack.
        1. To update the deployed remote rendering portlet:
          • Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
          • Log in to Portal as the Portal Administrator
          • Navigate to: Administration / Portlet Management / Web Modules
          • Find and select the remote rendering portlet web module
          • Click the Update Portlet Icon to the right of the selected portlet
          • Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
          • Click Next and Finish
        2. To update the deployed PDM Doc List Portlet:
          • Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
          • Log in to Portal as the Portal Administrator
          • Navigate to: Administration / Portlet Management / Web Modules
          • Find and select the PDM Doc List Portlet web module
          • Click the Update Portlet Icon to the right of the selected portlet
          • Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
          • Click Next and Finish
        3. Log out of Portal for changes to take effect.
      3. Optional: The WebSphere Portal 7.0.0.2 fix pack does not update any of the business portlets or Web Clipping portlet as these are served from the IBM WebSphere Portal Business Solutions catalog. If this fix pack is updating a fresh installation of WebSphere Portal, you should download the latest available portlets and portlet applications from the Portal Catalog. If you already have the version of the business portlets or Web Clipping portlet needed or if you are not using these functions at all, no additional steps are necessary.
      4. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.
      5. Set the following caching property: cacheinstance.com.ibm.wps.ac.RolesCache.firstLevelCacheSize=0 in the Resource Environment Provider WP_CacheManagerService from the administrative console following the steps to set configuration service properties from the following link: Setting service configuration properties.
      6. If you upgraded from a prior release with additional interim fixes installed, you will need to reinstall any interim fixes that were not integrated into the version 7.0.0.2 installation. The following list shows you which fixes were not integrated. You can also check later by opening the CheckAdditionalEfixes_date_time.log file, located in the portal_server_root/version/log directory for the list of interim fixes that must be reinstalled. Before reinstalling the interim fix, go to the WebSphere Portal product support page to see if there is a newer version of the interim fix because these are often specific to a version and release of the product; and search on the APAR number to find more information.
      7. Install any APARs that need to be applied. See the Recommended fixes and updates for WebSphere Portal and Web Content Manager page.
      8. If you disabled the database index application before the fix pack installation, modify the following property to is original value. Edit wkplc_dbtype.properties and set: DbSafeMode=false. You also need to manually apply all database changes as explained here: http://www.ibm.com/support/docview.wss?uid=swg27023802.
      9. After performing upgrade to 7.0.0.2, refer to database specific product information to ensure a reorg/runstats command has been run to ensure proper database performance.
      10. To ease the usability of the Web Content Manager Authoring UI when creating a new authoring templates and site areas the behavior was changed with WCM CF 7 and Portal 7.0.0.1 fix pack. Therefore the default child placement position that will be used with WebSphere Portal 7.0.0.2 is "end". Before WebSphere Portal 7.0.0.1 or WCM Cumulative Fix 7 or higher, the default child placement position was "start".
      11. WCM Authoring Search may not work after an upgrade to 7.0.0.2. Reference the known issues to resolve this problem.


    Back to top




    Steps for uninstalling
    Fix Pack 7.0.0.2
    Perform the following steps to uninstall Version 7.0.0.2:

    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.
    An example of an unsupported uninstall path is: Install Portal 7.0.0.0 --> upgrade Portal --> change server context root --> uninstall upgrade.
    An example of a supported uninstall path is: Install Portal 7.0.0.0 --> change server context root --> upgrade Portal --> uninstall upgrade.

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

    IMPORTANT: If uninstalling because of a failed upgrade, fix what is causing the problem and rerun the installation task. Uninstalling the fix pack might result in an unsupported configuration.
    1. Perform the following steps before you uninstall the Version 7.0.0.2 fix pack:
      1. If you are running an external Web server such as HTTP server, stop the Web server.
      2. Verify that the information in the wkplc.properties, wkplc_comp.properties, wkplc_dbdomain.properties and wkplc_dbtype.properties files are correct. 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.
        • Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
        • If using a database other than the default, grant permissions to databases within the framework by setting the DbUser (database user) and DbPassword (database password) parameters in the wkplc_dbdomain.properties file.
        • 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.
        • 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.
        • WebSphere Portal 7 introduced support for multiple profiles. During the fix pack uninstall the primary profile is downgraded first if one exists (The Update Installer also supports the update case for a binary only install without profiles). The primary profile is identified by two properties, ProfileDirectory and ProfileName. Ensure these properties are set before starting the downgrade process. The fix pack install will automatically downgrade all Portal profiles (associated with the corresponding wp_home) by default.
        • To prevent the fix pack uninstall from downgrading all profiles, the following property can be used in <wp_home>/wps.properties to specify which profiles to downgrade.

          AutoUpdateMultipleProfiles=profile1,profile2,....,profileN
        • If using Multiple Profiles, verify all your profiles are at the same level before starting downgrade.
      3. If the task "deploy-7002-theme" has been run on the Portal system, first ensure the "7.0.0.2 Theme" is NOT set as the default Portal theme nor assigned to any page. Then, the "remove-7002-theme" task must be run, before uninstalling the 7.0.0.2 fix pack.
      4. The WebSphere Portal 7.0.0.2 fix pack performs index (schema) modifications to the Portal databases during the fix pack application. Please see the following documentation for the details: http://www.ibm.com/support/docview.wss?uid=swg27023802. It is possible to disable the automatic application and instead manually apply the indexes. For that, make sure the following property is set in wkplc_dbtype.properties before starting the fix pack application: DbSafeMode=true. If DbSafeMode is not set to true then ensure that the DbUser in the wkplc_dbdomain.properties file for all domains on DB2 has explicit DBADM authority.
    2. Choose either the graphical user interface uninstallation option or the command line uninstallation option:

      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.


      • 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. Ensure to stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. 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>"
            -fixpack
            -fixpackID WP_PTF_7002
          • Unix/Linux: PortalServer_root/update> ./updatePortal.sh -uninstall
            -installDir "<PortalServer_root>"
            -fixpack
            -fixpackID WP_PTF_7002
          • IBM i: portal_server_root/update> updatePortal.sh -uninstall
            -installDir "<portal_server_root>"
            -fixpack
            -fixpackID WP_PTF_7002
    3. To downgrade a profile after an uninstall, the following command can be used to downgrade profiles that are not included in AutoUpdateMultipleProfiles. All profiles that were not included in AutoUpdateMultipleProfiles need to be downgraded after the uninstall 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 uninstall 7002

    4. 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 plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps:
      1. Regenerate the Web server plugin.
      2. Copy the plugin-cfg.xml file to the Plugin directory.
      3. Restart the Web server.
    5. If you previously customized any configuration files in the wp_profile_root/PortalServer/config, check to see if uninstalling the fix pack affected those files by restoring a version of the files that was saved when the fix pack was originally installed. If it did affect the files, you must perform the same customization on the restored version of each file.
    6. 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 fix pack.
      1. To update the deployed remote rendering portlet:
        • Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
        • Log in to Portal as the Portal Administrator
        • Navigate to: Administration / Portlet Management / Web Modules
        • Find and select the remote rendering portlet web module
        • Click the Update Portlet Icon to the right of the selected portlet
        • Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
        • Click Next and Finish
      2. To update the deployed PDM Doc List Portlet:
        • Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
        • Log in to Portal as the Portal Administrator
        • Navigate to: Administration / Portlet Management / Web Modules
        • Find and select the PDM Doc List Portlet web module
        • Click the Update Portlet Icon to the right of the selected portlet
        • Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
        • Click Next and Finish
      3. Log out of Portal for changes to take effect.
    7. If you disabled database updates during the uninstall of 7.0.0.2 by setting DbSafeMode=true,then do the following:
      1. Edit wkplc_dbtype.properties and set DbSafeMode=false.
      2. Manually apply all database changes manually as explained here: http://www.ibm.com/support/docview.wss?uid=swg27023802
    8. Verify that your system is operational by entering the server's URL in a browser and logging in to browse the content.




    Back to top




    Known issues

    For a list of known runtime issues for WebSphere Portal 7.0.0.2, see IBM WebSphere Portal 7.0.0.2 Known Runtime Issues for details.

    For a list of known install and uninstall issues for WebSphere Portal 7.0.0.2, see IBM WebSphere Portal 7.0.0.2 Known Install/Uninstall Issues for details.

    Back to top


    Change History
    Initial Release

    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.2

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

    Software edition: Enable, Express, Extend, Server

    Reference #: 7021850

    Modified date: 17 September 2012


    Translate this page: