Abstract

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

Content

Download

Readme

Fix List

6.1.0.1: Readme for IBM WebSphere Portal 6.1 fix pack 1 (6.1.0.1) - stand-alone

Table of Contents

• What is new with Fix Pack 6.1.0.1
• About Fix Pack 6.1.0.1
• Space requirements
• Cluster installation instructions
• Steps for installing Fix Pack 6.1.0.1
• Steps for uninstalling Fix Pack 6.1.0.1
• Known issues
• Change History
• Additional information
• Trademarks and service marks

---

What is new with Fix Pack 6.1.0.1
This fix pack updates the IBM WebSphere Portal 6.1 (6.1.0.0) level to the 6.1.0.1 service release level.

This fix pack and these instructions can be used to upgrade the IBM Workplace® Web Content Management 6.1 (6.1.0.0) level to the 6.1.0.1 service release level.

This fix pack and these instructions can also be used to upgrade IBM WebSphere Portal Express 6.1 (6.1.0.0) level to the 6.1.0.1 service release level.

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.

Back to top

---

About Fix Pack 6.1.0.1

Installing Fix Pack 6.1.0.1 with the WebSphere Portal Update Installer for version 6.1 raises the fix level of your product to version 6.1.0.1.

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


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

Back to top

---

Space requirements

Space requirements vary depending on what you are installing. The size of the download is available on the version 6.1.0.1 download page. After unpacking the archive file, you download and delete the archive file to free space. Space is also required for backup files in the portal_server_root/version/backup directory and your system temp directory, such as /tmp on Unix or Linux platforms or C:\temp on the Microsoft Windows platform. The space required is about the same as the size of the fix pack which varies by product and platform.

This archived fix pack file is approximately 380MB in size. The temporary disk space used will vary depending on your platform and could be as much as 800MB during installation, and as much as 400MB after installation into your <Portal_Install_Root> directory.

Verify that the free space is available before beginning the installation.

Back to top

---

Steps for installing Fix Pack 6.1.0.1

1. Perform the following steps before upgrading to Version 6.1.0.1:
   1. Review the supported hardware and software requirements for this cumulative fix. If necessary, upgrade all hardware and software before applying this cumulative fix. 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 HTTP server, stop the Web server.
      
   3. In the directory <profile-root>\ConfigEngine\properties\, verify that the information in the wkplc.properties, wkplc_comp.properties and wkplc_dbtype.properties files are correct.
      • Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
      • In the wkplc_comp.properties file, set the passwords for the database entries.
      • 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. NOTE: If you are using Microsoft Internet Protocol (IP) Version 6 and you have specified the WpsHostName property as an Internet Protocol address, normalize the Internet Protocol address by placing square brackets around the IP address as follows: WpsHostName=[my.IPV6.IP.address].
      • 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.
      • If using a database other than the default, grant permissions to databases within the framework by setting the DbUser (database name) and DbPassword (database password) parameters in the wkplc_comp.properties file.
      • Add the following line to the end of the wkplc.properties file:
        AdditionalPropertiesToFilter=newAdminPw
        
   4. Perform the following steps to download the cumulative fix pack and the WebSphere Portal Update Installer:
      1. Download the latest cumulative fix pack file and WebSphere Portal Update Installer from http://www.ibm.com/support/docview.wss?rs=688&uid=swg24020387.
      2. Create the portal_server_root/update directory and extract the WebSphere Portal Update Installer file into this directory. NOTE on Windows: The pkunzip utility might not correctly decompress the download image so use another utility such as Winzip to unzip the image.
      3. Create the portal_server_root/update/fixpacks directory and extract the 6.1.0-WP-FP001.zip file into this directory.
         
   5. 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. 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.
      
   6. The default behavior for upgrading to WebSphere Application Server version 6.1.0.19 is to set the installed Derby database to fix level 580531. WebSphere Portal version 6.1 on Application Server version 6.1.0.15 requires and installs Derby fix level 639536.
      Applying this version 6.1.0.1 fix pack will automatically set Derby back to fix level 639536 unless the following line is appended to the file <profile_home>\ConfigEngine\properties\wkplc.properties:
      updateDerby=false
      For more information, refer to "Transaction Rollback exceptions after upgrading to Application Server V6.1.0.17 or 6.1.0.19" (#1320565).
   7. Perform the following steps to change the HTTP connection timeout value for the WebSphere_Portal server:
      1. Click Servers --> Application Servers --> WebSphere_Portal>Web container settings --> Web container transport chains.
      2. Increase the timeout values for each entry listed in the web container transport chain section. Click HTTP Inbound Channel. Change the Read timeout value to 180 and change the Write timeout value to 180.
      3. Save your changes.
         
   8. Perform the following steps to change the open_cursors value if you are using an external Oracle database:
      1. Connect to your Oracle instance as the system database administrator.
      2. Write down the current open_cursors value so you can reset the value after upgrading.
      3. Run the "alter system set open_cursors=6000 scope=spfile;" task.
         NOTE: Depending on the number of resources and tables in your external Oracle instance, you may need to set open_cursors to a higher value. If, after upgrading, you receive a "maximum open cursors exceeded" error message, increase the open_cursors value and rerun the install upgrade task.
      4. Shut down and then restart your Oracle instance.

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 i5/OS, download ISA on a system other than i5/OS. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your i5/OS system. Fix what is causing the problem and then rerun the installation task.

NOTE: For optimal performance and minimal network traffic when using the Portal Update Installer's graphical Wizard interface, the upgrade steps should be run from local displays. When using remote displays, it is recommended to use the command-line interface with the Update Installer.


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 from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program.

• Enter the following command to launch the graphical user interface installation program:
  • Windows: portal_server_root\update> updatePortalWizard.bat
  • Unix/Linux: portal_server_root/update> ./updatePortalWizard.sh
    
    - OR -
    
• Perform the following steps to launch the installation program from the command line:
  1. Users of a platform-specific WebSphere Portal Update Installer (PUI) which includes the bundled Java runtime can skip this initial step. If using the Universal PUI, (which does not include the bundled Java environment), run the following command from the was_profile_root/bin directory to set up the Java environment for the WebSphere Portal Update Installer:
     • Windows: setupCmdLine.bat
     • Unix/Linux: . ./setupCmdLine.sh
  2. Open a command prompt in the was_profile_root/bin directory and enter the following command to check the status of all active application servers. NOTE: If security is not enabled, exclude the -user and -password parameters from the command:
     • Windows: serverStatus.bat -all -user username -password password
     • Unix/Linux: ./serverStatus.sh -all -user username -password password
     • i5/OS: serverStatus -all -profileName profile_root -user username -password password
       where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.
  3. Enter the following command to stop any active application servers; NOTE: If security is not enabled, exclude the -user and -password parameters from the command:
     • Windows: stopServer.bat servername -user username -password password
     • Unix/Linux: ./stopServer.sh servername -user username -password password
     • i5/OS: stopServer servername -profileName profile_root -user username -password password
  4. Enter the following command to launch the installation program (NOTE: Enter the command on one line):
     • Windows: portal_server_root\update> updatePortal.bat -install
       -installDir "C:\Program Files\IBM\WebSphere\PortalServer"
       -fixpack
       -fixpackDir "C:\ProgramFiles\IBM\WebSphere\PortalServer\update\fixpacks"
       -fixpackID WP_PTF_6101
     • Unix/Linux: portal_server_root/update> ./updatePortal.sh -install
       -installDir "/opt/WebSphere/PortalServer"
       -fixpack
       -fixpackDir "/opt/WebSphere/PortalServer/update/fixpacks"
       -fixpackID WP_PTF_6101
     • i5/OS: portal_server_root_prod/update> updatePortal.sh -install
       -installDir "/<portal_server_root_user>"
       -fixpack
       -fixpackDir "/portal_server_root_prod/update/fixpacks"
       -fixpackID WP_PTF_6101
       

3. Perform the following post installation steps:

1. If you preserved passwords during the installation and you want to manually delete the passwords, open the wkplc.properties file and include the following line in the file: PWordDelete=true. Then run the following task from the portal_server_root/config directory to delete the passwords:
   • Windows: ConfigEngine.bat action-delete-passwords-fixpack
   • Unix/Linux: ./ConfigEngine.sh action-delete-passwords-fixpack
   • i5/OS: ConfigEngine.sh -profileName profile_root action-delete-passwords-fixpack
     
2. 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.
      
3. Perform the following steps if you are using IBM Workplace Web Content Management and you created content on a 6.1 server:
   1. Redeploy your customization, including JSPs, to the Web Content Management enterprise application and the local rendering portlet.
      
4. i5/OS only: Run the CHGJOBD JOBD(QWAS61/QWASJOBD) LOG(4 00 *NOLIST) command to disable WebSphere Application Server informational logging.
5. 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 6.1.0.1 installation. Open 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.
6. Perform the following steps to change the open_cursors value back to its original value if you are using an external Oracle database:
   1. Connect to your Oracle instance as the system database administrator.
   2. Run the "alter system set open_cursors=original_value scope=spfile;" task.
   3. Shut down and then restart your Oracle instance.
7. Optional: You can follow the instructions on the Administrator's Self-Help pages for IBM WebSphere Portal version 6.1 to download, extract, and configure the Administrator self help pages.
8. Optional: The WebSphere Portal 6.1.0.1 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.

Back to top

---

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

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.

i5/OS: BEFORE YOU UNINSTALL:
The following two files need to be owned by QEJBSVR before beginning the uninstallation:

${WasUserHome}/PortalServer/config/config/services.properties.backup.6100
${WasUserHome}/PortalServer/config/PortletServiceRegistryService.properties.6101.backup

Change the ownership by issuing these commands:

/${WasUserHome}/PortalServer/config/config/chown *.backup.6100
/${WasUserHome}/PortalServer/config/config/config/chown *.backup.6100

Then, begin the uninstallation procedure as outlined below.

IMPORTANT: Uninstalling the fix pack might result in an unsupported configuration. If uninstalling because of a failed upgrade, fix what is causing the problem and run the installation task again.

1. Perform the following steps before you uninstall the Version 6.1.0.1 cumulative fix:
   1. Ensure that you have enough free space allocated for your operating system in the appropriate directories. See supported hardware and software requirements for information.
   2. If you are running an external Web server such as HTTP server, stop the Web server.
   3. Perform the following steps to change the open_cursors value if you are using an external Oracle database:
      1. Connect to your Oracle instance as the system database administrator.
      2. Write down the current open_cursors value so you can reset the value after uninstalling.
      3. Run the "alter system set open_cursors=6000 scope=spfile;" task.
         NOTE: Depending on the number of resources and tables in your external Oracle instance, you may need to set open_cursors to a higher value. If, after uninstalling, you receive a "maximum open cursors exceeded" error message, increase the open_cursors value and rerun the uninstall upgrade task.
      4. Shut down and then restart your Oracle instance.
   4. Verify that the information in the wkplc.properties, wkplc_comp.properties, wkplc_dbtype.properties, and wkplc_sourceDB.properties files are correct.
      • Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
      • 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. NOTE: If you are using Microsoft Internet Protocol (IP) Version 6 and you have specified the WpsHostName property as an Internet Protocol address, normalize the Internet Protocol address by placing square brackets around the IP address as follows: WpsHostName=[my.IPV6.IP.address].
      • 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.
      • If using a database other than the default, grant permissions to databases within the framework by setting the DbUser (database name) and DbPassword (database password) parameters in the wkplc_comp.properties file.
   5. For i5/OS only, run these two commands to correctly set the ownership on the following:
      • /<Was_User_Home>/PortalServer/config/config/chown QEJBSVR *6101.backup
      • /<Was_User_Home>/PortalServer/config/config/config/chown QEJBSVR *.backup.6100
        
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 i5/OS, download ISA on a system other than i5/OS. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your i5/OS system. Fix what is causing the problem and then rerun the installation task.
   
   NOTE: For optimal performance and minimal network traffic when using the Portal Update Installer's graphical Wizard interface, the upgrade steps should be run from local displays. When using remote displays, it is recommended to use the command-line interface with the Update Installer.
   
   
   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 from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program.
   
   • Enter the following command to launch the graphical user interface uninstallation program:
     • Windows: portal_server_root\update> updatePortalWizard.bat
     • Unix/Linux: portal_server_root/update> ./updatePortalWizard.sh
       
       - OR -
       
       
   • Perform the following steps to launch the uninstallation program from the command line:
     1. Users of a platform-specific WebSphere Portal Update Installer (PUI) which includes the bundled Java runtime can skip this initial step. If using the Universal PUI, (which does not include the bundled Java environment), run the following command from the was_profile_root/bin directory to set up the Java environment for the WebSphere Portal Update Installer:
        • Windows: setupCmdLine.bat
        • Unix/Linux: . ./setupCmdLine.sh
     2. Open a command prompt in the was_profile_root/bin directory and enter the following command to check the status of all active application servers; NOTE: If security is not enabled, exclude the -user and -password parameters from the command:
        • Windows: serverStatus.bat -all -user username -password password
        • Unix/Linux: ./serverStatus.sh -all -user username -password password
        • i5/OS: serverStatus -all -profileName profile_root -user username -password password
     3. Enter the following command to stop any active application servers. NOTE: If security is not enabled, exclude the -user and -password parameters from the command:
        • Windows: stopServer.bat servername -user username -password password
        • Unix/Linux: ./stopServer.sh servername -user username -password password
        • i5/OS: stopServer servername -profileName profile_root -user username -password password
     4. Enter the following command to launch the uninstallation program (NOTE: Enter the command on one line):
        • Windows: C:\Program Files\IBM\WebSphere\PortalServer\update> updatePortal.bat -uninstall
          -installDir "C:\Program Files\IBM\WebSphere\PortalServer"
          -fixpack
          -fixpackID WP_PTF_6101
        • Unix/Linux: /usr/WebSphere/PortalServer/update> ./updatePortal.sh -uninstall
          -installDir "/usr/WebSphere/PortalServer"
          -fixpack
          -fixpackID WP_PTF_6101
        • i5/OS: portal_server_root_prod/update> updatePortal.sh -uninstall
          -installDir "/<portal_server_root_user>"
          -fixpack
          -fixpackID WP_PTF_6101
3. 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.
4. If you previously customized any configuration files in the portal_server_root/config directory (<portal_server_root_user>/config directory for iSeries), check to see if uninstalling the fix pack 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. Perform the following steps to change the open_cursors value back to its original value if you are using an external Oracle database:
   
   1. Connect to your Oracle instance as the system database administrator.
   2. Run the "alter system set open_cursors=original_value scope=spfile;" task.
   3. Shut down and then restart your Oracle instance.
6. If you preserved passwords during the uninstallation and you want to manually delete the passwords, open the wkplc.properties file and include the following line in the file: PWordDelete=true. Then run the following task from the portal_server_root/config directory to delete the passwords:
   • Windows: ConfigEngine.bat action-delete-passwords-fixpack
   • Unix/Linux: ./ConfigEngine.sh action-delete-passwords-fixpack
   • i5/OS: ConfigEngine.sh -profileName profile_root action-delete-passwords-fixpack
7. In order to restore the ability to create Virtual Portals, run the following commands in this order: ./ConfigEngine action-express-update-vp
   ./ConfigEngine.sh stop-portal-server -DWasPassword=wpsadmin
   ./ConfigEngine.sh start-portal-server

Back to top

---

Known issues

Problem: Opera® Web browser only: Enter key cannot focus on the Search button if some other button lies above it.
Solution: This is a current limitation of the product.

Problem: Applying this Portal fix pack as non-root user on Linux or Unix platforms or as non-Administrators on Microsoft Windows is only supported when the Portal was originally installed as non-root user / non-Administrator and is running with a non-root user / non-Administrator ID.
Solution: Refer to "WebSphere Portal upgrade fails when running Portal as a non-root user" (#1296466) for more information.

Problem: Spellchecker function does not work in Common PIM Portlet Mail when used through Apple Safari browser.
Solution: This is a known issue in this release.

Problem: After installing the fix pack on Linux or Unix variants, the file <WP_root>/migration/WPmigrate.sh has permissions -rw-r--r-- or 644 and is not executable.
Solution: Manually set the permissions to -r-xr-x--- or 550 in order to use the command.

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

---