Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
WebSphere Portal Express Version 6.0.0.1 cumulative fix
The instructions in this section describe the verifications and steps you need to perform before you install the WebSphere Portal Express Version 6.0.0.1 cumulative fix on machines that are currently running WebSphere Portal Express Version 6.0. You need to perform these instructions regardless of which installation method you use, the Graphical User Interface or the command line.
For a list of problems fixed with this release, refer to Problems fixed in WebSphere Portal Express Version 6.0.0.1.
- Verify that your environment contains the required hardware and software supported by this cumulative fix, especially the version of WebSphere Application Server that you are running. You can download the latest WebSphere Application Server interim fixes from...
http://www.ibm.com/websphere/support
With this release of WebSphere Portal Express, supported software levels may have changed from previous versions of WebSphere Portal Express for databases and other components. If you need to upgrade any of your components, do so before applying this cumulative fix.
- For non-cluster environments only: If you are running an external Web server, such as HTTP
Server, stop the Web server.
If you have your HTTP Server configured as a Windows service, you might have to disable that service and restart the system to successfully install the upgrade.
- Ensure that all properties in the wpconfig.properties file are correct. In a clustered environment, the CellName value is not automatically updated in the wpconfig.properties file for the unmanaged node path. Thus, the CellName value needs to be checked and updated on both the primary and secondary nodes in an unmanaged node scenario.
Also, ensure that the WpsHostPort and XmlAccessPort properties have the same value in the wpconfig.properties file. In a cluster, make sure they are the same on both nodes.
- Set sync and designer values in the wpconfig_dbDomain.properties to original Cloudscape values
- Download the latest cumulative fix file and WebSphere Portal Express Update Installer.
- Download the WebSphere Portal Express Version 6.0.0.1 cumulative fix and the WebSphere Portal Express Update Installer
The following files are required:
- Cumulative fix file: WP_PTF_6001.jar
- WebSphere Portal Express Update Installer: PortalUpdateInstaller.zip
- Create the directory...
portal_server_root/update
...and unzip WebSphere Portal Express Update Installer in the directory.
On Linux, verify that the commands...
- updatePortalWizard.sh
- updatePortal.sh
...have execute permissions. If not, give both commands execute permission.
For System i5 create...
portal_server_root_prod/update
...in the Prod directory. System i5 does not support the Graphical User Interface Upgrade installer, therefore you only need to create one command.
On Windows platforms, the pkunzip utility might not decompress the download image correctly. Use another utility (such as WinZip) to unzip the image.
On System i5, you might want to unzip the files on a local machine, and then ftp the unzipped files to the iSeries server.
- Create the directory...
portal_server_root/update/fixpacks
...and store the cumulative fix JAR file in the directory.
For System i5 create...
portal_server_root_prod/update/fixpacks
...in the Prod directory.
- Download the WebSphere Portal Express Version 6.0.0.1 cumulative fix and the WebSphere Portal Express Update Installer
- If you are running WebSphere Portal Express version 6.0x and plan to configure eTrust SiteMinder as your external security manager to handle authorization and authentication in WebSphere Portal Express, keep in mind that by default, the XML configuration interface cannot access the portal through eTrust SiteMinder.
To enable the XML configuration interface to access the portal through eTrust SiteMinder, use eTrust SiteMinder to define the configuration URL...
/wps/config
...as unprotected.
After the configuration URL is defined as unprotected, only WebSphere Portal Express enforces access control to this URL. Other portal resources, such as...
/wps/myportal
...are still protected by eTrust SiteMinder. If you have already set up eTrust SiteMinder for external authorization in WebSphere Portal Express, and you want to use mlaccess, make sure you have followed the procedure to allow for xmlaccess execution. Otherwise, the fix pack configuration task will fail.
- Preserve the default Portal search collections and/or any search collections that you created in your previous versions before you upgrade.
The reason for this is that the index structure of Portal Search is not backward compatible between the different product versions.