Supported hardware and software for WebSphere Portal V6.0

Supported hardware and software for WebSphere Portal V6.0

+
Search Tips | Advanced Search

Contents

Hardware requirements
Software requirements

Overview

For the latest information on requirements, locate this topic in the information center.
If you are using a version of software that is older than what is listed, that is unsupported. If you are using a version of software newer than what is listed, view the WebSphere Portal Support Statement to determine if the software is supported.

IBM WebSphere Portal versions 6.0.0.0 and 6.0.0.1

IBM WebSphere Portal versions 6.0.0.0 and 6.0.0.1 may experience an assortment of problems on WebSphere Application Server version 6.0.2.17 with install- and clustering-related tasks. Applying WebSphere Portal fix for APAR number PK38907 and Application Server fix for APAR number PK38983 will overcome the problems.

IBM WebSphere Portal Version 6.0.1

Beginning with refresh pack 1 for WebSphere Portal version 6.0 (6.0.1), the fixpack updates will replace the default themes and skins if updates are provided, and any customized content will be replaced. For more information, see, Default themes and skins will be overwritten by refresh pack 1 (6.0.1) installation

Hardware requirements

See also: Prepare the operating system.
Installation times will vary based on system characteristics, including processor speed, available disk space, and physical memory size. Installation on systems with the minimum requirements will take several hours.

IBM AIX systems
HP-UX systems
IBM iSeries systems
Linux Systems

Linux Intel systems
Linux on POWER
Linux on zSeries systems

Sun Solaris systems
Microsoft Windows systems

IBM AIX systems

Processor:

RS/6000 at 450MHz at a minimum; production environments should consider higher speeds.
Power5

Physical memory:
Under minimal load, WebSphere Portal can function with 2G of RAM. However, 4G is an optimal starting point for RAM in a production environment.
Disk Space:
The following values are required if you use the installation program to install IBM WebSphere Application Server, extensions and fixes, and WebSphere Portal (including IBM Cloudscape). These values do account for any other products or components that could be installed on the WebSphere Portal machine.
We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory (/usr) Temp directory (/tmp)
WebSphere Portal (including Cloudscape) 1.5GB 750 MB
WebSphere Application Server, extensions and fixes 2.0 GB 750 MB
Total 3.5 GB 1.5 GB minimum

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.
Virtual memory/Swap space:
This value should be equal to double the physical memory. At minimum, this should be at least equal to the physical memory.
Network connectivity:
To use portal across a network, the following elements are required for the portal machine:

Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.

Configured fully qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host.name. To ensure that this is configured correctly, issue the ping command from a command line. For example, ping hostname.example.com, where hostname.example.com is the fully qualified host.name.

HP-UX systems

Processor:
HP 9000 on PA-RISC at 440 MHz or faster

Physical memory:

Under minimal load, WebSphere Portal can function with 2G of RAM. However, 4G is an optimal starting point for RAM in a production environment.

Disk Space:
The following values are required if you use the installation program to install WAS, extensions and fixes, and WebSphere Portal (including Cloudscape). These values do account for any other products or components that could be installed on the WebSphere Portal machine.
We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory Temp directory (/tmp)
WebSphere Portal (including Cloudscape) 1.5 GB 750 MB
WAS, extensions and fixes 2.0 GB 750 MB
Total 3.5 GB 1.5 GB minimum

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.

Virtual memory/Swap space:
This value should be equal to double the physical memory. At minimum this should be at least equal to the physical memory.

Network connectivity
To use portal across a network, the following is required for the portal machine:

Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.

Configured fully qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host.name. To ensure that this is configured correctly, issue the ping command from a command line. For example, ping hostname.example.com, where hostname.example.com is the fully qualified host.name.

IBM iSeries systems

This section provides the minimum IBM iSeries hardware requirements to use WebSphere Portal on iSeries. Use the IBM Workload Estimator for iSeries for help with sizing all system configurations.
Systems that do not meet the recommended minimums can be used in environments that support a limited number of users and where longer server initialization times can be tolerated.

Processor:
Recent iSeries and eServer i5 models with at least 750 CPW. Production environments should consider servers with a higher CPW rating.

Physical memory:
2 GB at a minimum. Production environments will require more memory.

Disk Space:
The following values are required if you use the installation program to install WAS, extensions and fixes, and WebSphere Portal. These values do not account for any other products or components that could be installed on the WebSphere Portal machine.
We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory (/opt) Temp directory (/tmp)
WebSphere Portal and WAS V6.0.2.x and each WAS profile configured for use with WebSphere Portal V6.0.x 3.5 GB 750 MB

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.
These minimum requirements are based on a non-cluster environment running a single WAS profile. To run multiple WAS profiles at the same time, additional system resources are required.
These requirements represent the recommended minimum requirements. Deployments which must support many users or require shorter response times might require additional resources.

Linux Intel systems

Processor:
CPU speeds of late-model, mid-range to high-end servers are recommended (32-bit support only). Pentium 800MHz or equivalent at a minimum. Production environments should consider the Pentium 4 processor at 1.4GHz or higher.

Physical memory:

Under minimal load, WebSphere Portal can function with 2G of RAM. However, 4G is an optimal starting point for RAM in a production environment.

Disk Space:
The following values are required if you use the installation program to install WAS, extensions and fixes, and WebSphere Portal (including Cloudscape). These values do account for any other products or components that could be installed on the WebSphere Portal machine. We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory (/opt) Temp directory (/tmp)
WebSphere Portal (including Cloudscape) 2.4 GB 750 MB
WAS, extensions and fixes 1.5 GB 750 MB
Total 3.9 GB 1.5 GB minimum

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.

Virtual memory/Swap space:
This value should be equal to double the physical memory. For example, based on the minimum required physical memory, 3 GB of swap space is needed. At minimum, this should be at least equal to the physical memory.

File system size
The Linux ext2 file system, which is used by default, does not allow you to change the file system size. Therefore, you should carefully plan in advance for the size of the file system in order to avoid related problems. The following disk space is required for each directory:

/ 1.5 GB or more (root directory)
/opt 2.5 GB or more. The default directory to install WebSphere Portal on Linux is /opt, which you could change to any directory you like later. By default, /opt is under / file system in default. If you choose to install WebSphere Portal under /usr, 3.5 GB or more is recommended.
/home 500 MB or more (home directory)

Network connectivity
To use portal across a network, the following elements are required for the portal machine:

Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.

Configured fully qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host.name. To ensure that this is configured correctly, issue the ping command from a command line. For example, ping hostname.example.com, where hostname.example.com is the fully qualified host.name.

Linux on POWER

Processor:

POWER is a term used to refer to IBM system product lines including:

iSeries models that support LPAR (64-bit support only) with minimum of 450 CPW in Linux partition

pSeries models that support Linux (64-bit support only)

BladeCenter JS20

OpenPower

that are based on IBM Power Architecture technology and run the same Linux distributions from Red Hat and Novell SUSE.

Power5

Physical memory:
Under minimal load, WebSphere Portal can function with 2G of RAM. However, 4G is an optimal starting point for RAM in a production environment.

Disk Space:
The following values are required if you use the installation program to install WAS, extensions and fixes, and WebSphere Portal (including Cloudscape). These values do account for any other products or components that could be installed on the WebSphere Portal machine.
We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory (/opt) Temp directory (/tmp)
WebSphere Portal (including Cloudscape) 2.4 GB 750 MB
WAS, extensions and fixes 1.5 GB 750 MB
Total 3.9 GB 1.5 GB minimum

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.

Virtual memory/Swap space:
This value should be equal to double the physical memory. At minimum, this should be at least equal to the physical memory.

Network connectivity
To use portal across a network, the following elements are required for the portal machine:

Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.

Configured fully qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host.name. To ensure that this is configured correctly, issue the ping command from a command line. For example, ping hostname.example.com, where hostname.example.com is the fully qualified host.name.

For any linux operating system, the libstdc++-3.3.3-41 shared object library is required prior to installation of WebSphere Portal.

Linux on zSeries systems

Processor:
G5, G6, or better processor

Physical memory:
Under minimal load, WebSphere Portal can function with 2G of RAM. However, 4G is an optimal starting point for RAM in a production environment.

Disk Space:
The following values are required if you use the installation program to install WAS, extensions and fixes, and WebSphere Portal (including Cloudscape). These values do account for any other products or components that could be installed on the WebSphere Portal machine.
We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory (/opt) Temp directory (/tmp)
WebSphere Portal (including Cloudscape) 2.4 GB 750 MB
WAS, extensions and fixes 1.5 GB 750 MB
Total 3.9 GB 1.5 GB minimum

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.

Virtual memory/Swap space:
This value should be equal to double the physical memory. At minimum, this should be at least equal to the physical memory.

Network connectivity
To use portal across a network, the following elements are required for the portal machine:

Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.

Configured fully qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host.name. To ensure that this is configured correctly, issue the ping command from a command line. For example, ping hostname.example.com, where hostname.example.com is the fully qualified host.name.

Sun Solaris systems

Processor:

Ultra 60 at 450MHz at a minimum; Sun Blade 2000 workstation at 1 GHz or higher is recommended.

Physical memory:
Under minimal load, WebSphere Portal can function with 2G of RAM. However, 4G is an optimal starting point for RAM in a production environment.

Disk Space:
The following values are required if you use the installation program to install WAS, extensions and fixes, and WebSphere Portal (including Cloudscape). These values do account for any other products or components that could be installed on the WebSphere Portal machine.
We can perform a custom installation of the components. The following list shows the space requirements by component:

The /var/tmp directory must contain 300MB or more of free space.

We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory (/opt) Temp directory (/tmp)
WebSphere Portal (including Cloudscape) 1.5 GB 750 MB
WAS, extensions and fixes 1.7 GB 750 MB
Total 3.2 GB 1.5 GB minimum

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.

Virtual memory/Swap space:

This value should be equal to double the physical memory. At minimum this should be at least equal to the physical memory.

For Solaris 9, swap space must be double the physical memory, especially if the physical memory is 1024 MB per processor.

Network connectivity
To use portal across a network, the following elements are required for the portal machine:

Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.

Configured fully qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host.name. To ensure that this is configured correctly, issue the ping command from a command line. For example, ping hostname.example.com, where hostname.example.com is the fully qualified host.name.

Microsoft Windows systems

Processor:

CPU speeds of late-model, mid-range to high-end servers are recommended. Pentium 800MHz or equivalent at a minimum. Production environments should consider the Pentium 4 processor at 1.4GHz or higher.

Physical memory:

Under minimal load, WebSphere Portal can function with 2G of RAM. However, 4G is an optimal starting point for RAM in a production environment.

Disk Space:

The following values are required if you use the installation program to install WAS, extensions and fixes, and WebSphere Portal (including Cloudscape). These values do account for any other products or components that could be installed on the WebSphere Portal machine.
We can perform a custom installation of the components. The following list shows the space requirements by component:

Component Install directory (C:/) Temp directory (/tmp)
WebSphere Portal (including Cloudscape) 2.4 GB 750 MB
WAS, extensions and fixes 1.5 GB 750 MB
Total 3.9 GB 1.5 GB minimum
The C partition should have more than 750 MB if the Windows system directory is not C.

If you are installing WebSphere Portal on a system that has an existing WAS installation on a different partition than the partition to which you are installing WebSphere Portal, the partition containing the existing WAS must have at least 300MB of free space.

Virtual memory/Swap space:
This value should be equal to double the physical memory. At minimum, this should be at least equal to the physical memory.

File system
NTFS file system is recommended.

Because the installation program does not check cluster sizes on a file system, install on an NTFS file system to ensure that you have enough disk space. If you intend to install on a FAT file system, make sure that you have enough disk space prior to installation. For information, refer to the Microsoft support Web site, http://support.microsoft.com, and search for content about default cluster sizes for FAT file systems.

Network connectivity
To use portal across a network, the following elements are required for the portal machine:

Network adapter and connection to a physical network that can carry IP packets. For example, Ethernet, Token Ring, ATM, and so on.

Configured fully qualified host.name. The portal system must be able to resolve an IP address from its fully qualified host.name. To ensure that this is configured correctly, issue the ping command from a command line. For example, ping hostname.example.com, where hostname.example.com is the fully qualified host.name.

Software requirements

This section provides the minimum product levels that you should install for WebSphere Portal. Because other products frequently ship fixes, updates, and new releases, every possible configuration has not been tested.
The software listed here is for multiple offerings. Refer to Product overview > Components overview for a list of software provided with each offering.

Operating systems (required on portal machine)
Application servers (required on portal machine)
web servers (optional)
Databases (required)
lDAP directories (optional)
Web browsers (required)
Software for collaboration (optional)
Software for content management (optional)
External security software (optional)
Software for portlet development
Other supported software
Software for license management

How to read software requirements information

Software that is marked with a plus sign (+) is shipped with specific editions of WebSphere Portal. Access to this software, either from the WebSphere Portal discs or from the downloaded images, is required. Other software that is not marked might also be shipped with the edition of WebSphere Portal.

Software that is shipped with WebSphere Portal is supported only on the platforms that portal supports.

Usage restrictions apply for some software. Consult the product license for details.

Access to software that is shipped with WebSphere Portal, either from the WebSphere Portal discs or from the downloaded images, is required for installation.

Supported operating systems (required on portal machine)

One of the following operating systems is required on the machine where WebSphere Portal will be installed:

Operating system (required) Notes

IBM AIX

AIX V5.3 Maintenance Level 02 Supported in 32-bit and 64-bit modes on Power 4, Power 5, OpenPower, and BladeCenter machines.
AIX V5.2 Maintenance Level 05 Supported in 32-bit and 64-bit modes on Power 4, Power 5, OpenPower, and BladeCenter machines.

HP-UX

HP-UX v11iv2 64-bit mode only. 32-bit mode is not exploited.
HP-UX 11i v1
32-bit mode only. 64-bit mode is not exploited.
Set the maximum open files number before running the portal server. To set the open files and the maximum stack size number, execute the following command in the shell:
ulimit -n 10240
ulimit -s 8198
...before running the portal server.
The latest GOLDQPK11i patches are required for WAS.
HP-UX 11i (11.11) PA-RISC patches.
This list does not show dependency patches. On the web page from which you download the patch, click the "dependency" link and make sure you install dependency patches as well.

PHCO_24777
PHCO_25452
PHKL_24255
PHKL_24569
PHKL_24751
PHKL_25389
PHKL_25729
PHKL_25840
PHNE_24035
PHSS_25092
PHKL_25368

Ensure that all Java patches for the installed Quality Packs are applied prior to installing WebSphere Portal.

IBM i5/OS (OS/400 for iSeries)

i5/OS V5R3
Supported on Power 4, Power 5, OpenPower and BladeCenter machines. 64-bit mode only. 32-bit mode is not exploited.
The recommended system level is 5722SS1 i5/OS V5R3 with cumulative PTF group SF99530 level 5298 or later and IBM DB2 Universal Database™ for iSeries™ PTF group 99502 level 8. Here are three commands we can issue to determine if the system's software is at the recommended level:

GO LICPGM will display all the installed licensed programs

wrkptfgrp will display and allow you to work with all installed PTF groups

dspptf will display PTF status; for example, temporarily or permanently applied

The IBM DB2 for iSeries database is only supported for WebSphere Portal on an iSeries system. The information for DB2 and its required PTFs are located in the Supported databases section.
i5/OS V5R4 The recommended system level is 5722999 i5/OS V5R4 with 64 bit JVM with cumulative PTF group SF99540 level 6024 or later and IBM DB2 Universal Database for iSeries PTF group 99504 level 2.
The IBM DB2 for iSeries database is only supported for WebSphere Portal on an iSeries system. The information for DB2 and its required PTFs are located in the Supported databases section.

Linux

Red Hat Enterprise Linux (RHEL) 3.0 Update 6, V4.0

Enterprise Server (ES)
Advanced Server (AS)
Workstation (WS)
Desktop for (x86-32)

32-bit mode only. 64-bit mode is not exploited
WS & Desktop are only supported as developer platforms.
For any Linux operating system, the libstdc++-3.3.3-41 shared object library is required prior to installation of WebSphere Portal. Refer to these Tech Notes before installation:

1201306

Set the system-wide maximum open files number to 10240 before running the WebSphere Portal installation program. This may be accomplished by root invoking ulimit -n 10240. Some systems may require a reboot before this value takes effect. Consult the operating system manual. .
Red Hat Enterprise Linux AS on Power 3.0 Update 6 & V4.0
For any Linux operating system, the libstdc++-3.3.3-41 shared object library is required prior to installation of WebSphere Portal.
Red Hat Enterprise Linux AS for zSeries 3.0 Update 6 & V4.0 Update 1 (31-bit and 64-bit)

Productivity Components requires X11 R6 libraries in addition to the following libraries:

openmotif
openmotif21-libs
openmotif-devel
openmotif-libs

For any Linux operating system, the libstdc++-3.3.3-41 shared object library is required prior to installation of WebSphere Portal.
Set the system-wide maximum open files number to 10240 before running the WebSphere Portal installation program. This may be accomplished by root invoking ulimit -n 10240. Some systems may require a reboot before this value takes effect. Consult the operating system manual.
SuSE, SuSE SLES 9, 2.6 Kernel (x86) SP1 32-bit mode only, 64-bit mode is not exploited.
SuSE is only supported as a developer platform. Productivity Components requires X11 R6 libraries in addition to the following libraries:

openmotif
openmotif21-libs
openmotif-devel
openmotif-libs

Set the system-wide maximum open files number to 10240 before running the WebSphere Portal installation program. This may be accomplished by root invoking ulimit -n 10240. Some systems may require a reboot before this value takes effect. Consult the operating system manual.
SuSE SLES 9, 2.6 Kernel (Power) SP1
SuSE SLES 9, 2.6 Kernel (zSeries) SP1

Sun Solaris

Sun Solaris 10 64-bit mode only. 32-bit mode is not exploited.
Sun Solaris 9 (with patch cluster of November 2005 or later) 64-bit mode only. 32-bit mode is not exploited.

Microsoft Windows

Microsoft Windows 2003 Enterprise SP1 32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows 2003 Standard SP1 32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows 2000 Advanced Server SP4 32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows 2000 Server SP4 32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows XP SP1 & SP2 Supported for test and development purposes only. (32-bit mode only. 64-bit mode is not exploited.)

[Back to top]

Supported application servers (required on portal machine)

You must install WebSphere Portal on top of the following supported version of WAS.

Windows and UNIX

WAS V6.0.2.9 Base +
WebSphere Process Server 6.0.1.1
On 64-bit Linux on zSeries and Power5 platforms, install 32-bit WAS
GNU compiler collection (GCC, version 3.3.2) for HP-UX 11. For GCC version later than 3.3.2, symbolic link libstdc++.sl.5 -> libstdc++.sl.6.2" in /usr/local/lib must be created manually after installing the GCC compiler.
The following WAS V6.0.2.9 interim fixes are also required (unless noted, all fixes are for iSeries, too...

PK23493 (not for iSeries )
PK26123
PK25630
PK24463
PK21704
PK18492
PK23985
PK24014
PK21870
PK21793
PK21927
PK20404
Java SDK 1.4.2 SR4 Cumulative Fix for IBM WAS (not for iSeries )
PK23358
PK23535
PK24146
PK25597
PK25804

The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is:
\projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries

If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases.
Read about the IBM Update Strategy for WAS V6.0. releases here.
The following WebSphere Process Server interim fixes are also required (unless noted, all fixes are for iSeries, too.):

IY84662 (not for iSeries )
IY82199 (not for iSeries )
IY83206
JR23774 (not for iSeries )
JR24221 (not for iSeries )
PK27024
PK22180
JR24190 (not for iSeries )
JR23478 (Linux only)

WAS 6.0.2.9 Base +
WAS Network Deployment (ND) 6.0.2.9 +
WebSphere Process Server 6.0.1.1
The following WAS V6.0.2.9 interim fixes are also required (unless noted, all fixes are for iSeries, too.) :

PK23493 (not for iSeries )
PK26123
PK25630
PK24463
PK21704
PK18492
PK23985
PK24014
PK21870
PK21793
PK21927
PK20404
Java SDK 1.4.2 SR4 Cumulative Fix for IBM WAS (not for iSeries )
PK23358
PK23535
PK24146
PK25597
PK25804

The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is:
\projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries

If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases.
Read about the IBM Update Strategy for WAS V6.0. releases here.
The following WebSphere Process Server interim fixes are also required (unless noted, all fixes are for iSeries, too.):

IY84662 (not for iSeries )
IY82199 (not for iSeries )
IY83206
JR23774 (not for iSeries )
JR24221 (not for iSeries )
PK27024
PK22180
JR24190 (not for iSeries )
JR23478 (Linux only)

WAS 6.0.2.9 Base +
Certain components of WebSphere Process Server 6.0.1.1
The following WAS V6.0.2.9 interim fixes are also required:

PK23493 (not for iSeries )
PK26123
PK25630
PK24463
PK21704
PK18492
PK23985
PK24014
PK21870
PK21793
PK21927
PK20404
Java SDK 1.4.2 SR4 Cumulative Fix for IBM WAS (not for iSeries )
PK23358
PK23535
PK24146
PK25597
PK25804

The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is:
\projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries

If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases.
Read about the IBM Update Strategy for WAS V6.0. releases here.
The following WebSphere Process Server interim fixes are also required (unless noted, all fixes are for iSeries, too.):

IY84662 (not for iSeries )
IY82199 (not for iSeries )
IY83206
JR23774 (not for iSeries )
JR24221 (not for iSeries )
PK27024
PK22180
JR24190 (not for iSeries )
JR23478 (Linux only)

IBM i5/OS

i5/OS V5R3:
IBM WAS V6.0.2.9 Base or ND
Requires WebSphere PTF group SF99301 (level 14 or higher) and PTF 5733-060 SI24576I
The following WAS V6.0.2.9 interim fixes are also required.
PK00274 should not be installed on iSeries.
When you install additional interim fixes, ensure that the interim fix that you want to apply is iSeries compatible.

PK18492
PK20404
PK21704
PK21793
PK21870
PK21927
PK22180
PK23358
PK23535
PK23985
PK24014
PK24146
PK24463
PK25597
PK25630
PK25804
PK26123
PK27024

The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is:
\projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries

If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases.
Read about the IBM Update Strategy for WAS V6.0. releases here.

WAS has support for Internet Protocol V4 (IPv4) and Internet Protocol V6 (IPv6). However, on the OS/400 platform, WAS V6 and later only supports IPv4.

i5/OS V5R4:
IBM WAS V6.0.2.9 Base or ND

Requires WebSphere PTF group SF99312 (level 3 or higher) and PTF 5733-060 SI24576
PK00274 should not be installed on iSeries.
When you install additional interim fixes, ensure that the interim fix that you want to apply is iSeries compatible.
The following WAS V6.0.2.0 interim fixes are also required.

PK18492
PK20404
PK21704
PK21793
PK21870
PK21927
PK22180
PK23358
PK23535
PK23985
PK24014
PK24146
PK24463
PK25597
PK25630
PK25804
PK26123
PK27024

The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is:
\projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries

If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases.
Read about the IBM Update Strategy for WAS V6.0. releases here.
The following program temporary fix is required to be installed on i5/OS V5R4 before installing WebSphere Portal:
5722SS1 PTF SI23811

WAS has support for Internet Protocol V4 (IPv4) and Internet Protocol V6 (IPv6). However, on the OS/400 platform, WAS V6 and later only supports IPv4.

Supported Web servers (optional)

We can use one of the following products as the Web server. In general, any Web server that is supported by WAS Cumulative Fix 3 is supported. Other Web servers or versions that are not listed might also be supported.

Web server (optional) Notes
Apache Server 2.0.49 & 2.0.52 Includes CERT Advisory CA-2002-17
+ IBM HTTP Server 2.0.47.1 The fix PK13784 is also required.
IBM HTTP Server 6.0, 6.0.1, 6.0.2 The fix PK13784 is also required.
IBM HTTP Server for i5/OS V5R3 and V5R4 HTTP Server for iSeries is provided natively on iSeries and is not bundled with or installed by WebSphere Portal.
The license program number is 5722DG1.
Issue the command GO LICPGM to display all the installed licensed programs
Microsoft Internet Information Server 6.0 Supported on Microsoft Windows Server 2003.
+ IBM Lotus Domino (as Web server) 7.0
IBM Lotus Domino (as Web server) 6.5.5
IBM Lotus Domino (as Web server) 6.5.4

Sun Java System Web Server, Enterprise Edition 6.1 SP3 Support for AIX was discontinued with 6.x editions.
Sun Java System Web Server, Enterprise Edition 6.0 SP9 Support for AIX was discontinued with 6.x editions.

Supported databases (required)

By default, WebSphere Portal is installed with the Cloudscape database. After installation is complete we can choose to transfer data to another supported database. We can use one of the following database products to store WebSphere Portal information. We can use one of the following database products to store WebSphere Portal data.

Database (required) Driver (JDBC Type) Notes
+ IBM Cloudscape V5.1.60.41 Cloudscape Type 4 Cloudscape is automatically installed during the initial installation of WebSphere Portal. After installation we can choose to transfer data to another supported database.
+ IBM DB2 Universal Database Enterprise Server Edition 8.2 FP5 CLI (Type 2)

Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver.

Supports 32-bit server/client configurations.

IBM DB2 Universal Database Enterprise Server Edition 8.1 FP12 CLI (Type 2)

Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver.

Supports 32-bit server/client configurations.

+ IBM DB2 Universal Database Workgroup Server Edition 8.2 FP5 CLI (Type 2)

Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver.

Supports 32-bit server/client configurations.

IBM DB2 Universal Database Workgroup Server Edition 8.1 FP12 CLI (Type 2)

Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver.

Supports 32-bit server/client configurations.

IBM DB2 Universal Database for z/OS 7.1
PUT level 0603 with maintenance for APAR PK21599 or later service level.
CLI (Type 2) DB2 Connect V8.1.9a or later is required on the portal machine. DB2 Connect is part of the Enterprise Editions of DB2.
DB2 UDB for z/OS as the administrative repository for WebSphere on non-S/390 platforms requires setting the DB2 for z/OS system parameter to rrulock=yes.
IBM DB2 Universal Database for z/OS 8.1
PUT level 0603 with maintenance for APAR PK21599 or later service level
CLI (Type 2)
Connect V12 or later is required on the portal machine. DB2 Connect is part of the Enterprise Editions of DB2
DB2 UDB for z/OS as the administrative repository for WebSphere on non-S/390 platforms requires setting the DB2 for z/OS system parameter to rrulock=yes.
IBM DB2 Universal Database for iSeries V5R3 Supports 32 bit JVM with cumulative PTF group SF99269 (level 10 or later).
The IBM DB2 for iSeries database is only supported for WebSphere Portal on an iSeries system.
The following program temporary fixes are required to be installed on DB2 for iSeries V5R3:

cumulative PTF group SF99503 level 8 or higher
PTF SI24550

Here are three commands we can issue to determine if the system's software is at the recommended level:

GO LICPGM will display all the installed licensed programs

wrkptfgrp will display and allow you to work with all installed PTF groups

dspptf will display PTF status; for example, temporarily or permanently applied

IBM DB2 Universal Database for iSeries V5R4 Supports 64 bit JVM with cumulative PTF group SF99291 (level 2 or higher)
The following program temporary fixes are required to be installed on DB2 for iSeries V5R4:

cumulative PTF group SF99504 level 1 or higher
PTF SI24569
PTF SI24629

Oracle Enterprise Edition 10g Release 1 and Release 2 Thin (Type 4)

Oracle Database clustering using RAC on all supported Oracle levels. Supports connect time failover.

Supports 64-bit Oracle 10g Release 1 using 32-bit Oracle database client/driver.

Supports 32-bit server/client configurations.

Supports High Availability Disaster Recovery (HADR) Feature
The following patches are required for Oracle 10.2.0.2:

4939157
5055175

Oracle Enterprise Edition 9i Release 2 Thin (Type 4)

Oracle Database clustering via RAC on all supported Oracle levels. Supports connect time failover.

Supports 64-bit Oracle 9i using 32-bit Oracle database client/driver.

Supports 32-bit server/client configurations.

Must use patch level 9.2.0.5 or greater.

Supports High Availability Disaster Recovery (HADR) Feature

Microsoft SQL Server Enterprise Edition 2000 SP4 Microsoft SQL Server 2000 (Type 4) Requires Microsoft SQL Server 2000 JDBC drivers.
SQL Server Standard Server 2000 SP4 Microsoft SQL Server 2000 (Type 4) Requires Microsoft SQL Server 2000 JDBC drivers.

A database server is required for WebSphere Portal.
WebSphere Portal Version 6.0 requires all component's datasources and JDBC drivers to be XA-enabled.
If the user repository contains more than 2000 users, a database other than Cloudscape is recommended. If you choose to transfer from Cloudscape to DB2 for iSeries, there is no option to transfer back to Cloudscape.
Because we can install the database server on a different machine from where WebSphere Portal is installed, you might be able to install the database server on an operating system that is different from the operating system on the portal machine.
Document Manager and the Run-time Server are supported on all databases.
A 64-bit DB2 (on AIX and Sun Solaris) is supported on platforms that have a 32-bit DB2 client driver available

Supported LDAP directories (optional)

We can use one of the following software products as an LDAP directory to store user information.

LDAP server (optional) Notes
IBM Tivoli Directory Server V6.0 Add APAR IO002714 6.0.0.1-TIV-ITDS-IF0001 available at IBM Support.
+ IBM Tivoli Directory Server V5.2

For 5.2.0.3-TIV-ITDS-IF0001 or earlier, add APAR IO02697 (This will update Tivoli Directory Server to Fix Pack 3) available at IBM Support

For 5.2.0.3-TIV-ITDS-IF0007, add APAR IO02697 available at IBM Support

For 5.2.0.3-TIV-ITDS-LA0011, add APAR IO02697. Contact IBM Tivoli Support organization.

SuSE SLES for S/390 8 is not supported. For detailed requirements information for the LDAP server, see the Tivoli Directory Server Installation and Configuration Guide.

+ IBM Lotus Domino 7.0.1 Apply SPR KLIN6LRTHJ to be able to return Groups and Users by direct lookup
+ IBM Lotus Domino 6.5.5 Apply SPR LORN6FKK9Q to make Group Lookup full functional
+ IBM Lotus Domino 6.5.4 Apply SPR LORN6FKK9Q to make Group Lookup full functional
Novell eDirectory 8.7.3
Sun Java System Directory Server V5.2

Microsoft Active Directory 2003
Microsoft Active Directory 2000
Microsoft Active Directory Application Mode (ADAM) 2003

Using an LDAP server is optional for WebSphere Portal.

Not all LDAP servers that are listed run on all operating systems supported by WebSphere Portal. The LDAP server provided with WebSphere Portal runs on all the operating systems that are supported by WebSphere Portal.

If you intend to use Domino Extended Products, such as IBM Lotus QuickPlace or IBM Lotus Sametime, the directory provided with IBM Domino Enterprise Server is recommended.

Because we can install the LDAP server on a different machine from where WebSphere Portal is installed, you might be able to install the LDAP server on an operating system that is different from the operating system on the portal machine.

Support for LDAP servers spans two categories:

Fully tested and supported LDAP servers:
The list of fully tested LDAP servers for each release of WebSphere Portal is documented in the information center and in the Supported Hardware and Software document for each release. WebSphere Portal support accepts problem reports for the appropriate WebSphere Portal releases using the tested directory servers. These problem reports receive high-priority attention. Features that are tested with these directories include relatively simple search and retrieval functions for user and group objects. Functions outside this scope, such as dynamic groups, referrals, or the Active Directory Global Catalog feature, are considered advanced features and have not been tested with WebSphere Portal. WebSphere Portal support encourages customers to work with their LDAP provider for additional support on these advanced features.

Untested and partially supported LDAP servers:
In general, WebSphere Portal support makes a best effort to support directory servers that have not been tested with WebSphere Portal. WebSphere Portal support accepts problem reports for the appropriate WebSphere Portal releases using untested directory servers. If WebSphere Portal support can recreate the reported problem using a tested LDAP server, staff will attempt to fix the problem. If the support team is not able to recreate the problem on a tested LDAP server, customers are referred to the LDAP provider for further assistance.

Submitting requests for additional LDAP support WebSphere Portal Development accepts customer requirements for LDAP support and functionality enhancements. Formal requirements are reviewed for consideration if they are submitted through the applicable IBM marketing or sales representative. Customer requirements must address one of the following areas:

Formal LDAP support for additional LDAP products, platforms, or configurations not currently supported, as previously indicated.

Functional enhancements that either extend or exploit WebSphere Portal LDAP integration capabilities.

Supported Web browsers (required)

You must use one of the following Web browsers to view the portal. These Web browsers were tested by IBM on servers that support the following client operating systems or desktop products:

Red Hat Enterprise Linux WS v3.0/Red Hat Desktop
SUSE Linux Professional 9.3 from Novell/Novell Linux Desktop 9
Microsoft Windows 2000
Microsoft Windows XP Professional

Portal behavior in Web browsers that are not listed, or in Web browsers that are listed but on client operating systems that are unlisted, is unknown. Web browser support varies by portlet or portal component. Refer to the documentation provided with each portlet or portal component for additional browser support information.

Web browser (required) Notes
Microsoft Internet Explorer V7.0 See IBM WebSphere Portal support statement for Microsoft Internet Explorer version 7.
You must install APAR# PK36354 , which adds Internet Explorer 7 as a recognized client
Microsoft Internet Explorer V6.0 SP1 (SP2 for Windows XP)
Microsoft Internet Explorer 6.0 SP1
FireFox 1.5.0.3
Mozilla Web Browser 1.7 The JavaScript option must be enabled. If the Mozilla browser is automatically installed along with the operating system, the JavaScript option is enabled by default.
Netscape Communicator 8.1 Due to incompatibilities of CSS and JavaScript implementations in Netscape, there are inconsistencies when Netscape is used with Document Manager and Productivity Components.
Apple Safari 2.0 Apple Safari support is limited. Document Manager, Web Content Management Authoring, the Rich Text Editor, People Components, Common Personal Information Manager Portlets, Drag-and-Drop Portlets,the flyout icons, Templates and Applications, Builder Portlets, and Domino and Extended Products Portlets cannot support the Safari browser.

A supported Web browser is required to access the portal from either a remote client or from the portal machine.
Internet Protocol V6.0 is supported. If you choose to use IPv6a,, verify that the database and any other software you are using supports Internet Protocol V6. If WebSphere Portal is installed on IPv6, then all browsers that access it must also have IPv6. The First Steps page runs in Internet Explorer on Windows and will not work because Internet Explorer does not support IPv6 at this time. For more information, refer to the WAS Website.
Web browser support varies by portlet.
The collaborative portlets that use the STLinks applet for people awareness (listed under People Finder portlet, people awareness, and Person menu problems in Troubleshooting Domino and Extended Products and Portlets) may support fewer browsers/client platforms for awareness than for using the portlet without awareness. The STLinks applet is limited to the browsers and client platforms supported by the release of the Lotus Sametime software running on the Lotus Sametime server configured as the back-end server for the portlets that use the STLinks applet.
In certain portlets, such as My Lotus QuickPlaces and Lotus Web Conferencing, people awareness features are supported by either Collaborative Services in the portal or by the STLinks applet, depending on the part of the portlet functionality. Therefore, if a browser/client platform combination is unsupported by the Lotus Sametime software, awareness may work in all portlet features except those where the STLinks applet supports it -- for example when a separate browser window is opened in the My Lotus QuickPlaces portlet.
The Domino Web Access portlet supports only browsers/client platforms supported by the Domino Web Access software running on the Domino messaging/application server configured to work with the portlet.
The Domino Document Manager portlet supports only browsers/client platforms supported by the Lotus Domino Document Manager software running on the Domino messaging/application server configured to work with the portlet.

Supported software for collaboration (optional)

Use the following server software to support the collaborative features that are provided with portal – the People Finder portlet, Domino and Extended Products Portlets, and Common Personal Information Management portlets, as well as Collaborative Services.

+ IBM Lotus Domino 7.0.1
IBM Lotus Domino 6.5.5
IBM Lotus Domino 6.5.4
IBM Lotus Domino 6.5.3
IBM Lotus Domino 6.5.2
IBM Lotus Domino 6.5.1
IBM Lotus Domino 6.0.4
IBM Lotus Domino 6.0.3
IBM Lotus Domino 6.0.2
+ IBM Lotus Sametime 7.0
IBM Lotus Instant Messaging and Web Conferencing 6.5.1
+ IBM Lotus QuickPlace 7.0
IBM Lotus Team Workplace 6.5.1

These products are supported on only the following operating systems:

AIX
Solaris
Windows
i5/OS

Usage restrictions apply for some software. Consult the product license for details.
Access to software that is shipped with WebSphere Portal, either from the WebSphere Portal discs or from the downloaded images, is required for installation.
Because we can install each server on a different machine from where WebSphere Portal is installed, you might be able to install each server on an operating system that is different from the operating system on the portal machine.
The Common Mail and Common Calendar portlets require Lotus Domino 6.5.4, 6.5.5, 7.0, or 7.0.1. A Domino Interim Fix Pack may be required on any Lotus Domino messaging server that functions as a back end for the Common PIM portlets. Contact IBM Support to determine whether such a Fix Pack is required and how to obtain it.
For release 6.5.x only, Lotus Sametime is called IBM Lotus Instant Messaging and Web Conferencing.
For full support of features in the My Lotus QuickPlaces portlet, an Interim Fix Pack may be required on any Domino server that runs QuickPlace 7.0. Contact IBM Support to determine whether such a Fix Pack is required and how to obtain it.
For release 6.5.x only, Lotus QuickPlace is called IBM Lotus Team Workplace.

Supported software for content management (optional)

We can use the following software to support content management with portal.

Content management products (optional) Notes

+ IWWCM 6.0

+ Document Manager Includes Portal productivity components
+ Portal Personalization
OS/400 - Additional Fonts (5722SS1, Option 43) Required software for Document Manager on i5/OS.
Issue the command GO LICPGM to display all the installed licensed programs.

Supported external security software (optional)

Use the following software as an external security manager for WebSphere Portal.

IBM Tivoli Access Manager for e-business Version 6.0
IBM Tivoli Access Manager for e-business V5.1
Computer Associates eTrust SiteMinder 6.0
Computer Associates eTrust SiteMinder 5.5

When using Tivoli Access Manager 5.1 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the V5.1 fix pack 2 level or later. This version of the AMJRTE component is automatically installed with WAS Version 5.1.1 or later, but must still be configured to work with WebSphere Portal.
For more information, see Using Tivoli Access Manager with WebSphere Portal .

Supported software for portlet development

The following software is supported on the development machine.

Software for portlet development (optional) Notes
IBM Rational Application Developer V7.0
+ WebSphere Portal Application Integrator Development Tool 5.1
IBM WebSphere Portlet Factory 6.0
Java 2 SDK - IBM AIX: ca131w-20020722a
Win32: cn131w-20020710
LinuxIA32: cxia32131-20020710z
Linux: cx390131-20020710

For the latest information about development platforms and local debugging requirements, see the topic Development environment configurations, in the WebSphere Portal information center.

Other supported software

The following software is available to extend the site.

Software for portlet development (optional) Notes
WebSphere Commerce Server WebSphere Portal should not be installed into a WAS cell where WebSphere Commerce Server is already installed.

Supported software for license management

WebSphere Portal is enabled to work with the following software.

Software for portlet development (optional) Notes
IBM Tivoli License Compliance Manager
Not supported at this time on i5/OS.
IBM Tivoli License Compliance Manager V2.2 FixPack 1 is required to properly monitor the WebSphere Portal product offerings.

[Back to top]

Parent topic:
Supported hardware and software

Windows and UNIX
WAS V6.0.2.9 Base + WebSphere Process Server 6.0.1.1	On 64-bit Linux on zSeries and Power5 platforms, install 32-bit WAS GNU compiler collection (GCC, version 3.3.2) for HP-UX 11. For GCC version later than 3.3.2, symbolic link libstdc++.sl.5 -> libstdc++.sl.6.2" in /usr/local/lib must be created manually after installing the GCC compiler. The following WAS V6.0.2.9 interim fixes are also required (unless noted, all fixes are for iSeries, too... PK23493 (not for iSeries ) PK26123 PK25630 PK24463 PK21704 PK18492 PK23985 PK24014 PK21870 PK21793 PK21927 PK20404 Java SDK 1.4.2 SR4 Cumulative Fix for IBM WAS (not for iSeries ) PK23358 PK23535 PK24146 PK25597 PK25804 The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is: \projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases. Read about the IBM Update Strategy for WAS V6.0. releases here. The following WebSphere Process Server interim fixes are also required (unless noted, all fixes are for iSeries, too.): IY84662 (not for iSeries ) IY82199 (not for iSeries ) IY83206 JR23774 (not for iSeries ) JR24221 (not for iSeries ) PK27024 PK22180 JR24190 (not for iSeries ) JR23478 (Linux only)
WAS 6.0.2.9 Base + WAS Network Deployment (ND) 6.0.2.9 + WebSphere Process Server 6.0.1.1	The following WAS V6.0.2.9 interim fixes are also required (unless noted, all fixes are for iSeries, too.) : PK23493 (not for iSeries ) PK26123 PK25630 PK24463 PK21704 PK18492 PK23985 PK24014 PK21870 PK21793 PK21927 PK20404 Java SDK 1.4.2 SR4 Cumulative Fix for IBM WAS (not for iSeries ) PK23358 PK23535 PK24146 PK25597 PK25804 The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is: \projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases. Read about the IBM Update Strategy for WAS V6.0. releases here. The following WebSphere Process Server interim fixes are also required (unless noted, all fixes are for iSeries, too.): IY84662 (not for iSeries ) IY82199 (not for iSeries ) IY83206 JR23774 (not for iSeries ) JR24221 (not for iSeries ) PK27024 PK22180 JR24190 (not for iSeries ) JR23478 (Linux only)
WAS 6.0.2.9 Base + Certain components of WebSphere Process Server 6.0.1.1	The following WAS V6.0.2.9 interim fixes are also required: PK23493 (not for iSeries ) PK26123 PK25630 PK24463 PK21704 PK18492 PK23985 PK24014 PK21870 PK21793 PK21927 PK20404 Java SDK 1.4.2 SR4 Cumulative Fix for IBM WAS (not for iSeries ) PK23358 PK23535 PK24146 PK25597 PK25804 The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is: \projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases. Read about the IBM Update Strategy for WAS V6.0. releases here. The following WebSphere Process Server interim fixes are also required (unless noted, all fixes are for iSeries, too.): IY84662 (not for iSeries ) IY82199 (not for iSeries ) IY83206 JR23774 (not for iSeries ) JR24221 (not for iSeries ) PK27024 PK22180 JR24190 (not for iSeries ) JR23478 (Linux only)
IBM i5/OS
i5/OS V5R3: IBM WAS V6.0.2.9 Base or ND	Requires WebSphere PTF group SF99301 (level 14 or higher) and PTF 5733-060 SI24576I The following WAS V6.0.2.9 interim fixes are also required. PK00274 should not be installed on iSeries. When you install additional interim fixes, ensure that the interim fix that you want to apply is iSeries compatible. PK18492 PK20404 PK21704 PK21793 PK21870 PK21927 PK22180 PK23358 PK23535 PK23985 PK24014 PK24146 PK24463 PK25597 PK25630 PK25804 PK26123 PK27024 The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is: \projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases. Read about the IBM Update Strategy for WAS V6.0. releases here. WAS has support for Internet Protocol V4 (IPv4) and Internet Protocol V6 (IPv6). However, on the OS/400 platform, WAS V6 and later only supports IPv4.
i5/OS V5R4: IBM WAS V6.0.2.9 Base or ND	Requires WebSphere PTF group SF99312 (level 3 or higher) and PTF 5733-060 SI24576 PK00274 should not be installed on iSeries. When you install additional interim fixes, ensure that the interim fix that you want to apply is iSeries compatible. The following WAS V6.0.2.0 interim fixes are also required. PK18492 PK20404 PK21704 PK21793 PK21870 PK21927 PK22180 PK23358 PK23535 PK23985 PK24014 PK24146 PK24463 PK25597 PK25630 PK25804 PK26123 PK27024 The install images of the required V6.0.2.9 interim fixes can be found on the WebSphere Portal Setup CD. Example for iSeries is: \projects\b\build.portal\builds\wp600.mp_ofr\wp600_244_04\cdimg\iSeries\I-Setup\was6_fixes\iseries If the WAS version is higher than 6.0.2.9, you may need to download some of the interim Fixes (if they were not included in the Fix Pack) from the Fix list for WAS V6.0.2, noting that interim Fixes are dependent on the WAS version. You may install interim Fixes with the Update Installer for WAS V6.0. releases. Read about the IBM Update Strategy for WAS V6.0. releases here. The following program temporary fix is required to be installed on i5/OS V5R4 before installing WebSphere Portal: 5722SS1 PTF SI23811 WAS has support for Internet Protocol V4 (IPv4) and Internet Protocol V6 (IPv6). However, on the OS/400 platform, WAS V6 and later only supports IPv4.

Component	Install directory (/usr)	Temp directory (/tmp)
WebSphere Portal (including Cloudscape)	1.5GB	750 MB
WebSphere Application Server, extensions and fixes	2.0 GB	750 MB
Total	3.5 GB	1.5 GB minimum

Component	Install directory	Temp directory (/tmp)
WebSphere Portal (including Cloudscape)	1.5 GB	750 MB
WAS, extensions and fixes	2.0 GB	750 MB
Total	3.5 GB	1.5 GB minimum

Component	Install directory (/opt)	Temp directory (/tmp)
WebSphere Portal (including Cloudscape)	2.4 GB	750 MB
WAS, extensions and fixes	1.5 GB	750 MB
Total	3.9 GB	1.5 GB minimum

/	1.5 GB or more (root directory)
/opt	2.5 GB or more. The default directory to install WebSphere Portal on Linux is /opt, which you could change to any directory you like later. By default, /opt is under / file system in default. If you choose to install WebSphere Portal under /usr, 3.5 GB or more is recommended.
/home	500 MB or more (home directory)

Operating system (required)	Notes
IBM AIX
AIX V5.3 Maintenance Level 02	Supported in 32-bit and 64-bit modes on Power 4, Power 5, OpenPower, and BladeCenter machines.
AIX V5.2 Maintenance Level 05	Supported in 32-bit and 64-bit modes on Power 4, Power 5, OpenPower, and BladeCenter machines.
HP-UX
HP-UX v11iv2	64-bit mode only. 32-bit mode is not exploited.
HP-UX 11i v1	32-bit mode only. 64-bit mode is not exploited. Set the maximum open files number before running the portal server. To set the open files and the maximum stack size number, execute the following command in the shell: ulimit -n 10240 ulimit -s 8198 ...before running the portal server. The latest GOLDQPK11i patches are required for WAS. HP-UX 11i (11.11) PA-RISC patches. This list does not show dependency patches. On the web page from which you download the patch, click the "dependency" link and make sure you install dependency patches as well. PHCO_24777 PHCO_25452 PHKL_24255 PHKL_24569 PHKL_24751 PHKL_25389 PHKL_25729 PHKL_25840 PHNE_24035 PHSS_25092 PHKL_25368 Ensure that all Java patches for the installed Quality Packs are applied prior to installing WebSphere Portal.
IBM i5/OS (OS/400 for iSeries)
i5/OS V5R3	Supported on Power 4, Power 5, OpenPower and BladeCenter machines. 64-bit mode only. 32-bit mode is not exploited. The recommended system level is 5722SS1 i5/OS V5R3 with cumulative PTF group SF99530 level 5298 or later and IBM DB2 Universal Database™ for iSeries™ PTF group 99502 level 8. Here are three commands we can issue to determine if the system's software is at the recommended level: GO LICPGM will display all the installed licensed programs wrkptfgrp will display and allow you to work with all installed PTF groups dspptf will display PTF status; for example, temporarily or permanently applied The IBM DB2 for iSeries database is only supported for WebSphere Portal on an iSeries system. The information for DB2 and its required PTFs are located in the Supported databases section.
i5/OS V5R4	The recommended system level is 5722999 i5/OS V5R4 with 64 bit JVM with cumulative PTF group SF99540 level 6024 or later and IBM DB2 Universal Database for iSeries PTF group 99504 level 2. The IBM DB2 for iSeries database is only supported for WebSphere Portal on an iSeries system. The information for DB2 and its required PTFs are located in the Supported databases section.
Linux
Red Hat Enterprise Linux (RHEL) 3.0 Update 6, V4.0 Enterprise Server (ES) Advanced Server (AS) Workstation (WS) Desktop for (x86-32)	32-bit mode only. 64-bit mode is not exploited WS & Desktop are only supported as developer platforms. For any Linux operating system, the libstdc++-3.3.3-41 shared object library is required prior to installation of WebSphere Portal. Refer to these Tech Notes before installation: 1201306 Set the system-wide maximum open files number to 10240 before running the WebSphere Portal installation program. This may be accomplished by root invoking ulimit -n 10240. Some systems may require a reboot before this value takes effect. Consult the operating system manual. .
Red Hat Enterprise Linux AS on Power 3.0 Update 6 & V4.0	For any Linux operating system, the libstdc++-3.3.3-41 shared object library is required prior to installation of WebSphere Portal.
Red Hat Enterprise Linux AS for zSeries 3.0 Update 6 & V4.0 Update 1 (31-bit and 64-bit)	Productivity Components requires X11 R6 libraries in addition to the following libraries: openmotif openmotif21-libs openmotif-devel openmotif-libs For any Linux operating system, the libstdc++-3.3.3-41 shared object library is required prior to installation of WebSphere Portal. Set the system-wide maximum open files number to 10240 before running the WebSphere Portal installation program. This may be accomplished by root invoking ulimit -n 10240. Some systems may require a reboot before this value takes effect. Consult the operating system manual.
SuSE, SuSE SLES 9, 2.6 Kernel (x86) SP1	32-bit mode only, 64-bit mode is not exploited. SuSE is only supported as a developer platform. Productivity Components requires X11 R6 libraries in addition to the following libraries: openmotif openmotif21-libs openmotif-devel openmotif-libs Set the system-wide maximum open files number to 10240 before running the WebSphere Portal installation program. This may be accomplished by root invoking ulimit -n 10240. Some systems may require a reboot before this value takes effect. Consult the operating system manual.
SuSE SLES 9, 2.6 Kernel (Power) SP1
SuSE SLES 9, 2.6 Kernel (zSeries) SP1
Sun Solaris
Sun Solaris 10	64-bit mode only. 32-bit mode is not exploited.
Sun Solaris 9 (with patch cluster of November 2005 or later)	64-bit mode only. 32-bit mode is not exploited.
Microsoft Windows
Microsoft Windows 2003 Enterprise SP1	32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows 2003 Standard SP1	32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows 2000 Advanced Server SP4	32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows 2000 Server SP4	32-bit mode only. 64-bit mode is not exploited.
Microsoft Windows XP SP1 & SP2	Supported for test and development purposes only. (32-bit mode only. 64-bit mode is not exploited.)

Web server (optional)	Notes
Apache Server 2.0.49 & 2.0.52	Includes CERT Advisory CA-2002-17
+ IBM HTTP Server 2.0.47.1	The fix PK13784 is also required.
IBM HTTP Server 6.0, 6.0.1, 6.0.2	The fix PK13784 is also required.
IBM HTTP Server for i5/OS V5R3 and V5R4	HTTP Server for iSeries is provided natively on iSeries and is not bundled with or installed by WebSphere Portal. The license program number is 5722DG1. Issue the command GO LICPGM to display all the installed licensed programs
Microsoft Internet Information Server 6.0	Supported on Microsoft Windows Server 2003.
+ IBM Lotus Domino (as Web server) 7.0
IBM Lotus Domino (as Web server) 6.5.5
IBM Lotus Domino (as Web server) 6.5.4
Sun Java System Web Server, Enterprise Edition 6.1 SP3	Support for AIX was discontinued with 6.x editions.
Sun Java System Web Server, Enterprise Edition 6.0 SP9	Support for AIX was discontinued with 6.x editions.

Database (required)	Driver (JDBC Type)	Notes
+ IBM Cloudscape V5.1.60.41	Cloudscape Type 4	Cloudscape is automatically installed during the initial installation of WebSphere Portal. After installation we can choose to transfer data to another supported database.
+ IBM DB2 Universal Database Enterprise Server Edition 8.2 FP5	CLI (Type 2)	Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver. Supports 32-bit server/client configurations.
IBM DB2 Universal Database Enterprise Server Edition 8.1 FP12	CLI (Type 2)	Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver. Supports 32-bit server/client configurations.
+ IBM DB2 Universal Database Workgroup Server Edition 8.2 FP5	CLI (Type 2)	Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver. Supports 32-bit server/client configurations.
IBM DB2 Universal Database Workgroup Server Edition 8.1 FP12	CLI (Type 2)	Supports 64-bit DB2 (on AIX and Sun Solaris) using 32-bit DB2 database client/driver. Supports 32-bit server/client configurations.
IBM DB2 Universal Database for z/OS 7.1 PUT level 0603 with maintenance for APAR PK21599 or later service level.	CLI (Type 2)	DB2 Connect V8.1.9a or later is required on the portal machine. DB2 Connect is part of the Enterprise Editions of DB2. DB2 UDB for z/OS as the administrative repository for WebSphere on non-S/390 platforms requires setting the DB2 for z/OS system parameter to rrulock=yes.
IBM DB2 Universal Database for z/OS 8.1 PUT level 0603 with maintenance for APAR PK21599 or later service level	CLI (Type 2)	Connect V12 or later is required on the portal machine. DB2 Connect is part of the Enterprise Editions of DB2 DB2 UDB for z/OS as the administrative repository for WebSphere on non-S/390 platforms requires setting the DB2 for z/OS system parameter to rrulock=yes.
IBM DB2 Universal Database for iSeries V5R3		Supports 32 bit JVM with cumulative PTF group SF99269 (level 10 or later). The IBM DB2 for iSeries database is only supported for WebSphere Portal on an iSeries system. The following program temporary fixes are required to be installed on DB2 for iSeries V5R3: cumulative PTF group SF99503 level 8 or higher PTF SI24550 Here are three commands we can issue to determine if the system's software is at the recommended level: GO LICPGM will display all the installed licensed programs wrkptfgrp will display and allow you to work with all installed PTF groups dspptf will display PTF status; for example, temporarily or permanently applied
IBM DB2 Universal Database for iSeries V5R4		Supports 64 bit JVM with cumulative PTF group SF99291 (level 2 or higher) The following program temporary fixes are required to be installed on DB2 for iSeries V5R4: cumulative PTF group SF99504 level 1 or higher PTF SI24569 PTF SI24629
Oracle Enterprise Edition 10g Release 1 and Release 2	Thin (Type 4)	Oracle Database clustering using RAC on all supported Oracle levels. Supports connect time failover. Supports 64-bit Oracle 10g Release 1 using 32-bit Oracle database client/driver. Supports 32-bit server/client configurations. Supports High Availability Disaster Recovery (HADR) Feature The following patches are required for Oracle 10.2.0.2: 4939157 5055175
Oracle Enterprise Edition 9i Release 2	Thin (Type 4)	Oracle Database clustering via RAC on all supported Oracle levels. Supports connect time failover. Supports 64-bit Oracle 9i using 32-bit Oracle database client/driver. Supports 32-bit server/client configurations. Must use patch level 9.2.0.5 or greater. Supports High Availability Disaster Recovery (HADR) Feature
Microsoft SQL Server Enterprise Edition 2000 SP4	Microsoft SQL Server 2000 (Type 4)	Requires Microsoft SQL Server 2000 JDBC drivers.
SQL Server Standard Server 2000 SP4	Microsoft SQL Server 2000 (Type 4)	Requires Microsoft SQL Server 2000 JDBC drivers.

LDAP server (optional)	Notes
IBM Tivoli Directory Server V6.0	Add APAR IO002714 6.0.0.1-TIV-ITDS-IF0001 available at IBM Support.
+ IBM Tivoli Directory Server V5.2	For 5.2.0.3-TIV-ITDS-IF0001 or earlier, add APAR IO02697 (This will update Tivoli Directory Server to Fix Pack 3) available at IBM Support For 5.2.0.3-TIV-ITDS-IF0007, add APAR IO02697 available at IBM Support For 5.2.0.3-TIV-ITDS-LA0011, add APAR IO02697. Contact IBM Tivoli Support organization. SuSE SLES for S/390 8 is not supported. For detailed requirements information for the LDAP server, see the Tivoli Directory Server Installation and Configuration Guide.
+ IBM Lotus Domino 7.0.1	Apply SPR KLIN6LRTHJ to be able to return Groups and Users by direct lookup
+ IBM Lotus Domino 6.5.5	Apply SPR LORN6FKK9Q to make Group Lookup full functional
+ IBM Lotus Domino 6.5.4	Apply SPR LORN6FKK9Q to make Group Lookup full functional
Novell eDirectory 8.7.3
Sun Java System Directory Server V5.2
Microsoft Active Directory 2003
Microsoft Active Directory 2000
Microsoft Active Directory Application Mode (ADAM) 2003

Web browser (required)	Notes
Microsoft Internet Explorer V7.0	See IBM WebSphere Portal support statement for Microsoft Internet Explorer version 7. You must install APAR# PK36354 , which adds Internet Explorer 7 as a recognized client
Microsoft Internet Explorer V6.0 SP1 (SP2 for Windows XP)
Microsoft Internet Explorer 6.0 SP1
FireFox 1.5.0.3
Mozilla Web Browser 1.7	The JavaScript option must be enabled. If the Mozilla browser is automatically installed along with the operating system, the JavaScript option is enabled by default.
Netscape Communicator 8.1	Due to incompatibilities of CSS and JavaScript implementations in Netscape, there are inconsistencies when Netscape is used with Document Manager and Productivity Components.
Apple Safari 2.0	Apple Safari support is limited. Document Manager, Web Content Management Authoring, the Rich Text Editor, People Components, Common Personal Information Manager Portlets, Drag-and-Drop Portlets,the flyout icons, Templates and Applications, Builder Portlets, and Domino and Extended Products Portlets cannot support the Safari browser.

Content management products (optional)	Notes
+ IWWCM 6.0
+ Document Manager	Includes Portal productivity components
+ Portal Personalization
OS/400 - Additional Fonts (5722SS1, Option 43)	Required software for Document Manager on i5/OS. Issue the command GO LICPGM to display all the installed licensed programs.

Software for portlet development (optional)	Notes
IBM Rational Application Developer V7.0
+ WebSphere Portal Application Integrator Development Tool 5.1
IBM WebSphere Portlet Factory 6.0
Java 2 SDK - IBM	AIX: ca131w-20020722a Win32: cn131w-20020710 LinuxIA32: cxia32131-20020710z Linux: cx390131-20020710