IBM Support

IBM WebSphere Portal 8.0.0.0 Combined Cumulative Fix Readme - stand-alone

Product readme


Abstract

IBM WebSphere Portal 8.0.0.0 Combined Cumulative Fix stand-alone installation instructions for all editions, including WebSphere Portal Express

Content

8.0.0.0: Readme for IBM WebSphere Portal 8.0.0.0 Combined Cumulative fix - stand-alone

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:

Need 1.25 GB of installation space (1800 cylinders on z/OS) plus 618 MB of shared data space (880 cylinders on z/OS).

Back to top




Steps for installing
Combined Cumulative Fix

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 V8.0

    1. Perform the following steps before installing Combined Cumulative fix:
      1. Before you install this combined cumulative fix, roll back any existing temporary or interim Portal fixes from your system. Check the list of fixes provided in this combined cumulative fix, and if you have temporary or interim fixes on your system that are not included in this Combined Cumulative Fix, then contact IBM Support for an updated version of that fix, or for more information.
      2. If you are running an external Web server such as IBM HTTP server, stop the Web server.
      3. Verify that the information in the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_comp.properties files is correct. If using multiple profiles, also verify that the information in each profile is correct.
        • 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.
        • Ensure that the value of the WpsContextRoot property in wkplc.properties is correct.
        • Unix/Linux/Windows/IBM i Only: 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
        • 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.
      4. 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 8.0.0.x was migrated from 7.0.x, ensure that the PortalServer/wps.properties file correctly references the profile. The Portal update procedure 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 using Multiple Profiles, verify all your profiles are at the same level before starting upgrade.
      5. Choose from the following two options to get the Combined Cumulative Fix.
        1. Download the Cumulative fix - To download the cumulative fix, perform the following steps:
          1. Download the latest Combined Cumulative fix zip file that corresponds to your Portal install on your system (e.g. 8.0.0.0-WP-WCM-Combined-CFPMnnnnn-Server-CFnn.zip, or 8.0.0.0-WP-WCM-Combined-CFPMnnnnn-Express-CFnn.zip, or 8.0.0.0-WP-WCM-Combined-CFPMnnnnn-zOS-CFnn.zip), from "Recommended Updates for WebSphere Portal and IBM Web Content Manage V8.0" .
          2. Create a directory and extract the Combined Cumulative fix zip file into this directory. Inside the zip file will be a readme file, two sample response files and the Cumulative fix. It will be named either PMnnnnn_Server.zip or PMnnnnn_Express.zip or PMnnnnn_zOS.zip, where n is the numbers associated with the version of the Combined Cumulative fix.
          3. Create a subdirectory and extract the PMnnnnn zip file to this directory. The extraction will result in a repository.config file which will be used by the IBM Installation Manager during the update.
        2. Live Repository - The Combined Cumulative fix is available for downloading and installing directly from a live repository.
      6. If you are installing as a non-root user on Unix or Linux, set permission on the PortalServer home directory tree to 777 (wrxwrxwrx) for the duration of the update.
      7. Important Notice: Unix and Linux only: If you have installed Portal Server v8.0 as a non-root user and included the optional feature "Create a new Deployment Manager Profile augmented with WebSphere Portal", please note there is an issue that could cause you to lose data in some update paths. An update should only be performed to v8.0.0.1 CF09 or later.


    2. Choose installation option:


      • Installation Steps via Graphical User Interface (Windows or Linux/Unix):
        1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. Apply the Combined Cumulative fix using IBM Installation Manager via launching the copy of IBM Installation Manager that was used to install IBM Portal Server v8.0 .
          1. Add the Combined Cumulative fix repository to the IBM Installation Manager repositories.
            1. Access the Installation Manager's "File - Preferences" pull-down menu.
            2. Access the "Repositories" panel and click "Add Repository".
            3. Navigate to the repository.config file mentioned earlier and select it.
          2. Select "Update" on the Installation Manager main window and follow the prompts to update IBM Portal Server.

      • Live Repository Installation Steps via Graphical User Interface (Windows or Linux/Unix):
        1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. Apply the Combined Cumulative fix using IBM Installation Manager via launching the copy of IBM Installation Manager that was used to install IBM Portal Server v8.0 .
          1. Access the Installation Manager's "File - Preferences" pull-down menu.
          2. Go to "Repositories" panel and click the checkbox that says "Search service repositories during installation and updates". Click apply.
          3. Select "Update" on the Installation Manager main window and follow the prompts to update IBM Portal Server.


      • Installation Steps via Command Line (Windows or Linux/Unix):
        1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. Apply the Combined Cumulative fix using IBM Installation Manager.
          1. Open a command window and switch to the eclipse subdirectory of Installation Manager. By default, this is:
            • Windows: C:\Program Files\IBM\Installation Manager\eclipse
            • Linux/Unix: /opt/IBM/InstallationManager/eclipse
          2. Run the following command, replacing <password> with your unencrypted WAS Administrator password:
            • Windows: IBMIMc.exe -silent -noSplash encryptString <password>
            • Linux/Unix: ./IBMIM -silent -noSplash encryptString <password>
          3. Make a note of the returned string, which is the encrypted version of your password that you will use in the commands shown below.
          4. Repeat the above steps for your Portal Administrator password.
          5. Run the command to launch the installation program from eclipse/tools subdirectory of Installation Manager (NOTE: Enter the command on one line):

            NOTE: If installing the Cumulative fix on Portal Express, change all instances of "PORTAL.SERVER.v80" below to "PORTAL.EXPRESS.v80".

            NOTE: Separate the properties in the -properties with a comma, no spaces between the properties.

            NOTE: Include quotation marks around filepaths that have spaces.
            • Windows: imcl.exe install com.ibm.websphere.PORTAL.SERVER.v80
              -repositories <fullpath/to/repository.config>
              -properties user.wp.portal.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<portaladminuser>,user.wp.portal.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedportaladminpassword>,user.wp.was.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<wasadminuser>,user.wp.was.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedwasadminpassword>
              -installationDirectory <portal_server_root>
              -acceptLicense
            • Linux/Unix: ./imcl install com.ibm.websphere.PORTAL.SERVER.v80
              -repositories <fullpath/to/repository.config>
              -properties user.wp.portal.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<portaladminuser>,user.wp.portal.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedportaladminpassword>,user.wp.was.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<wasadminuser>,user.wp.was.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedwasadminpassword>
              -installationDirectory <portal_server_root>
              -acceptLicense

      • Installation Steps via Silent mode (Windows, Linux/Unix, IBM i ):

        Note IBM i only: If you have WebSphere Portal Express on IBM i then use WebSphere Portal V8.0.0.1 Combined Cumulative Fix 09 (CF09) or later.
        1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. For CF01 on IBM i only: Copy /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/startManager to /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/startManager.sh (Substitute your path if you have installed Application Server in a different location.)
        3. Update the sample response file that is packaged with your Combined Cumulative fix level according to the comments in the file.
        4. Open a command window and switch to the eclipse/tools subdirectory of Installation Manager. By default, this is:
          • Windows: C:\Program Files\IBM\Installation Manager\eclipse\tools
          • Linux/Unix: /opt/IBM/InstallationManager/eclipse/tools
          • IBM i: /QIBM/ProdData/InstallationManager/eclipse/tools
        5. Run the following command to run the install silently:
          imcl -acceptLicense -input <Full_path_to_your_response_file> -log <Full_Path_to_a_log_file>

          You may also record a response file to use for silently installing the fix. See the following URL for detailed instructions on the procedure for recording an IBM Installation Manager response file: http://pic.dhe.ibm.com/infocenter/install/v1r5/index.jsp?topic=%2Fcom.ibm.silentinstall12.doc%2Ftopics%2Ft_silent_response_file_install.html
        6. For CF01 on IBM i only: Remove the copy of /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/startManager.sh


      • Installation Steps IBM z/OS:

        1. Stop active application servers which are using the WebSphere Portal and WebSphere Application Server files which are to be upgraded.
        2. Apply the Combined Cumulative fix using IBM Installation Manager.

          Note:
          If you are updating a portal server which uses a shared Portal installation directory which has already been updated with the Combined Cumulative fix, you may skip this step

          Note:
          The logged-in User ID should have the proper authority to perform IBM Installation Manager installation. Before executing the IBM Installation Manager command, be sure to check if the WAS and Portal Install files are mounted with R/W access.
          1. Open a command window and switch to the eclipse/tools subdirectory of Installation Manager. By default, this is /InstallationManager/bin/eclipse/tools.
          2. Run the following command to launch the installation program (NOTE: Enter the command on one line):

            NOTE:: Separate the properties in the -properties with a comma, no spaces between the properties.

            NOTE: Include quotation marks around filepaths that have spaces.

            ./imcl install com.ibm.websphere.PORTAL.CONTENT.v80
            -repositories <fullpath/to/repository.config>
            -properties user.was.installLocation,,com.ibm.websphere.PORTAL.CONTENT.v80=<AppServer Install Root, e.g. /usr/lpp/zWebSphere/V8R0>,user.wp.server.update.required,,com.ibm.websphere.PORTAL.CONTENT.v80=true
            -installationDirectory <PortalServer Install Root, e.g. /usr/lpp/zPortalServer/V8R0>
            -acceptLicense
    3. Additional Configuration steps:
      • If you do not have any profiles at this point (because you are in the process of migration from a previous version of WebSphere Portal 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 appropriate documentation.
      • z/OS configuration:
        • To continue, login user ID should have the proper authority to execute ConfigEngine tasks. Be sure to remount the WAS and Portal Install files as Read Only.

        • If doing an upgrade as part of a migration from a previous version (eg. 7.x), run ./ConfigEngine.sh gather-migration-files command from the <wp_profile_root>/ConfigEngine directory.

        • For CF03 and later: Run the following script from <PortalServer Install Root, e.g. /usr/lpp/zPortalServer/v8R0>/installer/wp.config/bin/ directory:
          ./ejpcfg2.sh -ACTION UPDATE -WASCONFIG <WAS_Root e.g. /WebSphere/V8R0M0/AppServer> -PORTALPW <portal_admin_password> -WASPW <was_admin_password>

        • For CF01 and CF02:
          • Run the following command from the <wp_profile_root>/ConfigEngine directory: ./ConfigEngine.sh -uninstall -offeringList PortalServer -unregisterOnly -DPortalAdminPwd=<password> -DWasPassword=<password>
          • Run the following command from the <wp_profile_root>/ConfigEngine directory: ./ConfigEngine.sh -install -offeringRoot <PortalServer Install Root, e.g. /usr/lpp/zPortalServer/V8R0> -installPath <PortalServer Install Root, e.g. /usr/lpp/zPortalServer/V8R0> -expandBinaries false
          • Run the following command from the <wp_profile_root>/ConfigEngine directory: ./ConfigEngine.sh CONFIG-WP-PTF-CF -DPortalAdminPwd=<password> -DWasPassword=<password>

      • Unix/Linux/Windows/IBM i: To update a profile after an upgrade, the following command can be used to update profiles that are not automatically updated. All profiles other than the default profile initially installed with Portal Server v8.0 need to be updated after the upgrade is done. All profiles must be at the same level for future upgrades to be applied.

        <profile_root>/ConfigEngine/ConfigEngine.sh CONFIG-WP-PTF-CF -DPortalAdminPwd=<password> -DWasPassword=<password>

    4. 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 Combined Cumulative fix.
      3. Review the following documentation "Configuration Changes and Options introduced in WP/WCM V8.0.0.0 Combined Cumulative Fixes" to see if it applies to your environment.
      4. 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.
      5. If you are using remote search service, you should update 'PSEStandalone' application on the remote search server by redeploying 'PseLibs.zip' from <PortalServer_root>/search/wp.search.libs/installableApps. Then, restart 'PSEStandalone' application or restart the remote search server. Refer to 'Preparing for remote search service' article in the IBM WebSphere Portal 8 Product Documentation for the details of deploying 'PseLibs.zip' file and 'PSEStandalone' application.




    Back to top




    Steps for Rollback of
    Combined Cumulative Fix

    NOTE: Changing the server context root after upgrading is an unsupported rollback path. To rollback 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 rollback path.

    1. Perform the following steps before you rollback the Combined Cumulative Fix:
      1. If you are running an external Web server such as IBM HTTP server, stop the Web server.
      2. Verify that the information in the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_comp.properties files is correct. If using multiple profiles, also verify that the information in each profile is correct.
        • 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.
        • 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.
        • Ensure that the value of the WpsContextRoot property in wkplc.properties is correct.
        • Unix/Linux/Windows/IBM i Only: 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
        • 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.
        • For multiple profiles: During the Combined Cumulative Fix rollback the primary profile is downgraded first if one exists (The update procedure 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.

    2. Choose Rollback option:


      • Rollback Steps via Graphical User Interface (Windows or Linux/Unix):
        1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. Rollback the Combined Cumulative fix using IBM Installation Manager via launching the copy of IBM Installation Manager that was used to install IBM Portal Server v8.0
          1. Select "Roll Back" on the Installation Manager main window and follow the prompts to rollback the IBM Portal Server to the V8.0.0.0 level.

      • Rollback Steps via Command Line (Windows or Linux/Unix):
        1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. Rollback the Combined Cumulative fix using IBM Installation Manager.
          1. Open a command window and switch to the eclipse subdirectory of Installation Manager. By default, this is:
            • Windows: C:\Program Files\IBM\Installation Manager\eclipse
            • Linux/Unix: /opt/IBM/InstallationManager/eclipse
          2. Run the following command, replacing <password> with your unencrypted WAS Administrator password:
            • Windows: IBMIMc.exe -silent -noSplash encryptString <password>
            • Linux/Unix: ./IBMIM -silent -noSplash encryptString <password>
          3. Make a note of the returned string, which is the encrypted version of your password that you will use in the commands shown below.
          4. Repeat the above steps for your Portal Administrator password.
          5. Run the command to launch the installation program from eclipse/tools subdirectory of Installation Manager (NOTE: Enter the command on one line):

            NOTE: If on Portal Express, change all instances of "PORTAL.SERVER.v80" below to "PORTAL.EXPRESS.v80".

            NOTE: Separate the properties in the -properties with a comma, no spaces between the properties.

            NOTE: Include quotation marks around filepaths that have spaces.
            • Windows: imcl.exe rollback com.ibm.websphere.PORTAL.SERVER.v80
              -properties user.wp.portal.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<portaladminuser>,user.wp.portal.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedportaladminpassword>,user.wp.was.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<wasadminuser>,user.wp.was.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedwasadminpassword>
              -installationDirectory <portal_server_root>
            • Linux/Unix: ./imcl rollback com.ibm.websphere.PORTAL.SERVER.v80
              -properties user.wp.portal.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<portaladminuser>,user.wp.portal.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedportaladminpassword>,user.wp.was.userid,,com.ibm.websphere.PORTAL.SERVER.v80=<wasadminuser>,user.wp.was.password,,com.ibm.websphere.PORTAL.SERVER.v80=<encryptedwasadminpassword>
              -installationDirectory <portal_server_root>


      • Rollback Steps via Silent mode (Windows, Unix, IBM i ):
        1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
        2. For CF01 on IBM i only: Copy /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/startManager to /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/startManager.sh (Substitute your path if you have installed Application Server in a different location.)
        3. Update the sample response file that is packaged with your Combined Cumulative fix level according to the comments in the file.
        4. Open a command window and switch to the eclipse/tools subdirectory of Installation Manager. By default, this is:
          • Windows: C:\Program Files\IBM\Installation Manager\eclipse\tools
          • Linux/Unix: /opt/IBM/InstallationManager/eclipse/tools
          • IBM i: /QIBM/ProdData/InstallationManager/eclipse/tools
        5. Run the following command to run the rollback silently:
          imcl -input <Full_path_to_your_response_file> -log <Full_Path_to_a_log_file>
        6. For CF01 on IBM i only: Remove the copy of /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/startManager.sh

      • Rollback Steps IBM z/OS:

        1. Stop active application servers which are using the WebSphere Portal and WebSphere Application Server files which are to be downgraded.
        2. Rollback the Combined Cumulative fix using IBM Installation Manager.

          Note:
          If you are updating a portal server which uses a shared Portal installation directory which has already been rolled back with the Combined Cumulative fix, you may skip this step.

          Note:
          The logged-in User ID should have the proper authority to perform IBM Installation Manager rollback. Before executing the IBM Installation Manager command, be sure to check if the WAS and Portal Install files are mounted as R/W access.
          1. Open a command window and switch to the eclipse/tools subdirectory of Installation Manager. By default, this is /InstallationManager/bin/eclipse/tools.
          2. Run the following command to launch the installation program (NOTE: Enter the command on one line):

            NOTE: Separate the properties in the -properties with a comma, no spaces between the properties.

            NOTE: Include quotation marks around filepaths that have spaces.

            ./imcl rollback com.ibm.websphere.PORTAL.CONTENT.v80
            -properties user.was.installLocation,,com.ibm.websphere.PORTAL.CONTENT.v80=<AppServer Install Root, e.g. /usr/lpp/zWebSphere/V8R0>,user.wp.server.update.required,,com.ibm.websphere.PORTAL.CONTENT.v80=true
            -installationDirectory <PortalServer Install Root, e.g. /usr/lpp/zPortalServer/V8R0>

             
          3. At the same command window, go to <PortalServer Install Root>/installer/wp.config/config/iim_includes/ directory and run the script: ./ejprlbk2.sh

        3. To continue, the login user ID should have the proper authority to execute ConfigEngine tasks. Before executing the ConfigEngine commands, be sure to remount the WAS and Portal Install files as Read Only. Run the following command: <wp_profile_root>/ConfigEngine/ConfigEngine.sh UNCONFIG-WP-PTF-CF -DPortalAdminPwd=<password> -DWasPassword=<password>



    3. Run the following command:
      • If using Multiple profiles: All profiles other than the default profile need to be Rolled back after the downgrade is done. Use the following command to downgrade the profile.

        <profile_root>/ConfigEngine/ConfigEngine.sh UNCONFIG-WP-PTF-CF -DPortalAdminPwd=<password> -DWasPassword=<password>
    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 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.
    6. Redeploy your customization, including JSPs, to the WCM portlets if you are using Web Content Manager and you customized the portlets prior to rolling back the Combined Cumulative fix.
    7. If you are using remote search service, after rolling back the cumulative fix, you should update 'PSEStandalone' application on the remote search server by redeploying 'PseLibs.zip' from <PortalServer_root>/search/wp.search.libs/installableApps. Then, restart 'PSEStandalone' application or restart the remote search server. Refer to 'Preparing for remote search service' page in the IBM WebSphere Portal 8 Product Documentation for the details of deploying 'PseLibs.zip' file and 'PSEStandalone' application.


    Back to top





    Known issues for latest Combined Cumulative Fix

    For a list of known issues for WebSphere Portal 8.0.0.0 Combined Cumulative Fixes, see IBM WebSphere Portal 8.0.0.0 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: 8.0.0.0

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

    Software edition: Enable, Express, Extend, Server

    Reference #: 7027200

    Modified date: 17 December 2013


    Translate this page: