6.1.0.6: Readme for IBM WebSphere Portal 6.1 fix pack 6 (6.1.0.6) - stand-alone

Content

6.1.0.6: Readme for IBM WebSphere Portal 6.1 fix pack 6 (6.1.0.6) - stand-alone

Table of Contents

• About Fix Pack 6.1.0.6
• Space requirements
• Cluster installation instructions
• Steps for installing Fix Pack 6.1.0.6
• Steps for uninstalling Fix Pack 6.1.0.6
• Known issues
• Change History
• Additional information
• Trademarks and service marks

---

About Fix Pack 6.1.0.6

• Installing Fix Pack 6.1.0.6 with the latest WebSphere Portal Update Installer for version 6.1 raises the fix level of your product to version 6.1.0.6. If the 6.1.5 feature pack is enabled, this fix pack upgrades the 6.1.5 features to the level 6.1.5.3. If you are upgrading to 6.1.0.6 from version 6.1.0, 6.1.0.1, or 6.1.0.2 and you want to enable the feature pack, first upgrade to 6.1.0.6 and then perform the steps to install the Feature Pack 6.1.5 fix pack 3.
• Refer to the installation instructions in the Steps for installing Fix Pack 6.1.0.6 section for information.
• Fix packs can be downloaded from the version 6.1.0.6 download page, also linked above on the "Download" tab of this document.
  

Warning:
You must use latest Portal Update Installer in order to successfully install this fix pack.


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
• WebSphere Portal can be upgraded to 6.1.5.3. After upgrading to Portal 6.1.0.6, to upgrade to Portal 6.1.5.3 see 6.1.5.3: Readme for IBM WebSphere Portal 6.1.5 fix pack 3 (6.1.5.3) - stand-alone for details.

The complete list of fixes integrated into this fix pack is found in the "Fix List" tab of this document.

Back to top

---

Space requirements

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

1. Perform the following steps before upgrading to Version 6.1.0.6:
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 HTTP server, stop the Web server.
   
3. 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.
• 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.
4. 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=swg24030970.
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_6106.zip file into this directory and copy the ptflist file into this directory.
5. The WebSphere Portal 6.1.0.6 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=swg27019861. It is possible to disable the automatic application and instead manually apply the indexes. For that, make sure the following property is set on the primary node 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_comp.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 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.

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.

• 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. 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 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_6106
• Unix/Linux: PortalServer_root/update> ./updatePortal.sh -install
  -installDir "<PortalServer_root>"
  -fixpack
  -fixpackDir "<PortalServer_root>/update/fixpacks"
  -fixpackID WP_PTF_6106
• i5/OS: portal_server_root/update> updatePortal.sh -install
  -installDir "<PortalServer_root_user>"
  -fixpack
  -fixpackDir "<portal_server_root>/update/fixpacks"
  -fixpackID WP_PTF_6106
  

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. Perform the following steps if you are using IBM Web Content Manager and you created content on the release you upgraded from:
1. Redeploy your customization, including JSPs, to the local rendering portlet.
2. Run ConfigEngine.sh|bat update-properties.
3. Restart Portal Server.
4. If the portal version you upgraded from is lower than 6.1.0.1 plus PK76129 (Cumulative iFix 1 for WCM v6.1.0.1) and the portal has Web Content data, then run the following steps:
   
   To ensure all scheduled actions are reset, run the run-wcm-admin-task-schedule-actions task from the wp_profile_root/ConfigEngine directory.
   
   To reschedule all libraries and preserve the last saved date of each item:
• Windows: ConfigEngine.bat run-wcm-admin-task-schedule-actions -DallLibraries=true -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• Unix: ./ConfigEngine.sh run-wcm-admin-task-schedule-actions -DallLibraries=true -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• i5/OS: ConfigEngine.sh -profileName profile_root run-wcm-admin-task-schedule-actions -DallLibraries=true -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
  where profile_root is the name of the IBM WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.
  
  To reschedule a single library and preserve the last saved date of each item:
• Windows: ConfigEngine.bat run-wcm-admin-task-schedule-actions -Dlibrary=libraryname -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• Unix: ./ConfigEngine.sh run-wcm-admin-task-schedule-actions -Dlibrary=libraryname -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• i5/OS: ConfigEngine.sh -profileName profile_root run-wcm-admin-task-schedule-actions -Dlibrary=libraryname -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
  where profile_root is the name of the IBM WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.
  
3. Optional: The WebSphere Portal 6.1.0.6 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. If you have customized the AJAX proxy (by editing proxy-config.xml) you will need to redo the customizations after the 6.1.0.6 fix pack upgrade. For that follow these steps:
1. Compare the backup copy of your customized file that is stored in the directory ${WP_PROFILE}/ConfigEngine/config/backup_files/<date>/... with the new 6.1.0.6 file in ${WP_PROFILE}/config/cells/<cell>/applications/AJAX Proxy Configuration.ear/deployments/AJAX Proxy Configuration/wp.proxy.config.war/WEB-INF/proxy-config.xml
2. Merge your customization into the new file
3. Deploy the updated proxy-config.xml with the following steps described in the InfoCenter http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v615/dev/ajax_proxy_globl_cfg.html
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.6 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.
6. Install any APARs that must be applied. Refer to the Recommended fixes and updates for the WebSphere Portal and Web Content Manager page.
7. If you disabled the database index application before the fix pack installation, modify the following property to its 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=swg27019861.
8. Optional: If coming from a release prior to 6.1.0.4 and when using the Web Content Manager JSR 286 portlet and using the default Portal theme for Web Content Manager Rendering, see the following document for improving the rendering performance: WebSphere Portal 6.1.0.4 Base Tag change.
9. If upgrading from WebSphere Portal 6.1.5 to 6.1.5.3 and using the share pages feature or the creation of templates in mashups: With WebSphere Portal 6.1.5.1, the default access control default behavior was changed to prevent possible security exposures in case of malicious users. With the changed behavior certain functions in WebSphere Portal cannot be used any more by non admin users. See the following document for details on those changes and how to enable the functionality again for certain users: WebSphere Portal Access Control default behavior changes to prevent security exposure.
10. Optional: If using Web Content Manager and this step was not done in 6.1.0.4 or 6.1.0.5, you can apply indexes to the JCR database that will help with performance: Run the JCR database schema migration to update the database indexes. Run the following task - replace <previous version> with 6.1.0.0 or 6.1.0.1 or 6.1.0.2 or 6.1.0.3 or 6.1.0.4 or 6.1.0.5 depending which release you are upgrading from. If you are upgrading from 6.1.5 use 6.1.0.3 for <previous version>:
• Windows: ConfigEngine.bat upgrade-jcr-database-601x-to-6100 -DPreviousPortalVersion=<previous version> -DWasPassword=<WasPassword> -Djcr.DbPassword=<jcrdb password>
• Unix/Linux: ./ConfigEngine.sh upgrade-jcr-database-601x-to-6100 -DPreviousPortalVersion=<previous version> -DWasPassword=<WasPassword> -Djcr.DbPassword=<jcrdb password>
• i5/OS: ConfigEngine.sh upgrade-jcr-database-601x-to-6100 -DPreviousPortalVersion=<previous version> -DWasPassword=<WasPassword> -Djcr.DbPassword=<jcrdb password>
11. After performing upgrade to 6.1.0.6, refer to database specific product information to ensure a reorg/runstats command has been run to ensure proper database performance.

Back to top

---

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

NOTE: If WebSphere Portal feature pack 6.1.5.x has been enabled after a fix pack upgrade then before the fix pack can be uninstalled the WebSphere Portal feature pack 6.1.5.x must be uninstalled first. For example: If the WebSphere Portal feature pack 6.1.5.3 is enabled after upgrading to 6.1.0.6, then 6.1.5.3 must be uninstalled before uninstalling 6.1.0.6. See 6.1.5.3: Readme for IBM WebSphere Portal 6.1.5 fix pack 3 (6.1.5.3) - stand-alone for details on uninstalling feature pack.

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 6.1.0 or 6.1.0.1 --> upgrade Portal --> change server context root --> uninstall upgrade.
An example of a supported uninstall path is: Install Portal 6.1.0 or 6.1.0.1 --> 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 6.1.0.6 fix pack:
1. Ensure that you have enough free space allocated for your operating system in the appropriate directories.
2. If you are running an external Web server such as HTTP server, stop the Web server.
3. 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.
• 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.
• 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.
4. The WebSphere Portal 6.1.0.6 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=swg27019861. It is possible to disable the automatic application and instead manually apply the indexes. For that, make sure the following property is set on the primary node 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_comp.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 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.
   
   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.
   
• 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. 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_6106
• Unix/Linux: PortalServer_root/update> ./updatePortal.sh -uninstall
  -installDir "<PortalServer_root>"
  -fixpack
  -fixpackID WP_PTF_6106
• i5/OS: portal_server_root/update> updatePortal.sh -uninstall
  -installDir "/<PortalServer_root_user>"
  -fixpack
  -fixpackID WP_PTF_6106
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 fix pack was originally installed. If it did affect the files, you must perform the same customization on the restored version of each file.
5. Note: Required for Express edition only: In order to restore the ability to create Virtual Portals, run the following commands:
   
• Windows: ConfigEngine.bat action-express-update-vp -DWasPassword=password
• Unix/Linux: ./ConfigEngine.sh action-express-update-vp -DWasPassword=password
• i5/OS: ConfigEngine.sh action-express-update-vp -DWasPassword=password
  
  Restart PortalServer.
  
6. When uninstalling from 6.1.0.6 to 6.1.0.1 and if 6.1.0.1 was an upgrade from 6.1.0.0 (eg. the problem does not happen if 6.1.0.1 was initially a Full Install).
• Windows: ConfigEngine.bat update-ear -DconfigExtensionList=-applyPTF6101 -DComponentList=wp.ear,prereq.odc,wp.oob.content/packager
• Unix/Linux: ./ConfigEngine.sh update-ear -DconfigExtensionList=-applyPTF6101 -DComponentList=wp.ear,prereq.odc,wp.oob.content/packager
• i5/OS: ConfigEngine.sh -profileName profile_root update-ear -DconfigExtensionList=-applyPTF6101 -DComponentList=wp.ear,prereq.odc,wp.oob.content/packager
7. Perform the following steps if you are using Web Content Manager and you created content on the release you downgraded from:
1. Redeploy your customization, including JSPs, to the local rendering portlet.
2. If the portal version is lower than 6.1.0.1 plus PK76129 (Cumulative iFix 1 for WCM v6.1.0.1) and the portal has Web Content data, then run the following steps:
   
   To ensure all scheduled actions are reset, run the run-wcm-admin-task-schedule-actions task from the wp_profile_root/ConfigEngine directory.
   
   To reschedule all libraries and preserve the last saved date of each item:
• Windows: ConfigEngine.bat run-wcm-admin-task-schedule-actions -DallLibraries=true -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• UNIX: ./ConfigEngine.sh run-wcm-admin-task-schedule-actions -DallLibraries=true -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• i5/OS: ConfigEngine.sh -profileName profile_root run-wcm-admin-task-schedule-actions -DallLibraries=true -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
  where profile_root is the name of the IBM WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.
  
  To reschedule a single library and preserve the last saved date of each item:
• Windows: ConfigEngine.bat run-wcm-admin-task-schedule-actions -Dlibrary=libraryname -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• Unix: ./ConfigEngine.sh run-wcm-admin-task-schedule-actions -Dlibrary=libraryname -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
• i5/OS: ConfigEngine.sh -profileName profile_root run-wcm-admin-task-schedule-actions -Dlibrary=libraryname -DpreserveDates=true -DPortalAdminId=username -DPortalAdminPwd=password
  where profile_root is the name of the IBM WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.
8. If you disabled database updates during the uninstall of 6.1.0.6 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=swg27019861

Back to top

---

Known issues

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

For a list of known install and uninstall issues for WebSphere Portal 6.1.0.6/6.1.5.3, see IBM WebSphere Portal 6.1.0.6/6.1.5.3 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

---