IBM WebSphere Portal for Multiplatforms V5.1
Supported hardware and software
Contents
Hardware requirements
- AIX
- HP-UX
- Linux Intel
- Linux on iSeries
- Linux on pSeries
- Linux on S/390
- Linux on zSeries
- Solaris
- Windows
See also:
AIX systems
- Processor:
- RS/6000 at 450MHz at a minimum; production environments should consider higher speeds.
- Power5
- Physical memory:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component /usr /tmp WebSphere Portal 1124 MB 50 MB WAS 968 MB 700 MB Total 2092 MB 750 MB minimum - Note: 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:
Set to double your 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
h
ostname.yourco.com, where hostname.yourco.com is the fully qualified host.name.
HP-UX systems
- Processor:
HP 9000 on PA-RISC at 440 MHz or faster
- Physical memory:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component Install directory /tmp WebSphere Portal 1124 MB 50 MB WAS 968 MB 700 MB Total 2092 MB 750 MB minimum - Note: 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:
Set to double your 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.yourco.com, where hostname.yourco.com is the fully qualified host name.
Linux Intel 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:
1.5 GB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component /opt /tmp WebSphere Portal 1124 MB 50 MB WAS 968 MB 700 MB Total 2092 MB 750 MB minimum - Note: 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:
Set to double your physical memory. For example, based on the minimum required physical memory, 3 GB of swap space is needed.
- File system size: The Linux ext2 file system, which is used by default, does not allow you to change the file system size.
Therefore, carefully plan in advance for the size of your 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.yourco.com, where hostname.yourco.com is the fully qualified host.name.
Linux on iSeries systems
- Processor:
- iSeries models that support LPAR (64-bit support only) with minimum of 450 CPW in Linux partition
- Physical memory:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component Linux partition /opt
Linux partition /tmp
WebSphere Portal 1124 MB 50 MB WAS 16GB 700 MB Total 2092 MB 750 MB minimum - Note: 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:
Set to double your 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.yourco.com, where hostname.yourco.com is the fully qualified host.name.
Linux on pSeries systems
systems:
- Processor:
- pSeries models that support Linux (64-bit support only)
- Power5
- Physical memory:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component /opt /tmp WebSphere Portal 1124 MB 50 MB WAS 968 MB 700 MB Total 2092 MB 750 MB minimum - Note: 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:
Set to double your 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.yourco.com, where hostname.yourco.com is the fully qualified host.name.
Linux on S/390 systems
systems:
- Processor:
S/390 models that support Linux (64-bit support only)
- Physical memory:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component /opt /tmp WebSphere Portal 1124 MB 50 MB WAS 968 MB 700 MB Total 2092 MB 750 MB minimum - Note: 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:
Set to double your 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.yourco.com, where hostname.yourco.com is the fully qualified host.name.
Linux on zSeries systems
- Processor:
G5, G6, or better processor
- Physical memory:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component /opt /tmp WebSphere Portal 1124 MB 50 MB WAS 968 MB 700 MB Total 2092 MB 750 MB minimum - Note: 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:
Set to double your 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.yourco.com, where hostname.yourco.com is the fully qualified host.name.
Solaris systems
- Processor:
Ultra 60 at 450MHz at a minimum; Sun Blade 2000 workstation at 1 GHz or higher is recommended.
- Physical memory:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You 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.
You can perform a custom installation of the components. The following list shows the space requirements by component:
Component /opt /tmp WebSphere Portal 1124 MB 50 MB WAS 1002 MB 700 MB Total 2126 MB 750 MB minimum - Note: 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:
Set to double your 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.yourco.com, where hostname.yourco.com is the fully qualified host.name.
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:
1024 MB or more per processor
- 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 account for any other products or components that could be installed on the WebSphere Portal machine. You can perform a custom installation of the components. The following list shows the space requirements by component:
Component Install directory (C:/) /tmp WebSphere Portal 1124 MB 50 MB WAS 968 MB 700 MB Total 2092 MB 750 MB minimum The C partition should have more than 750 MB if the Windows system directory is not C.
- Note: 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:
Set to double your 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.yourco.com, where hostname.yourco.com is the fully qualified host.name.
Software requirements
This section provides the minimum product levels that install for WebSphere Portal. Because other products frequently ship fixes, updates, and new releases, every possible configuration has not been tested.
- Supported operating systems (required on portal machine)
- Supported appservers (required on portal machine)
- Supported Web servers (Windows/UNIX - optional;
- Supported databases (required)
- Supported LDAP directories (optional)
- Supported Web browsers (required)
- Supported software for collaboration (optional)
- Supported software for content management (optional)
- Supported external security software (optional)
- Supported software for portlet development (optional)
- Other supported software (optional)
Note that...
- 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 your 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 AIX 5L V5.3 (32bit) Productivity Components requires X11 R6 libraries. AIX 5L V5.2 (32bit) + ML01 + APAR IY44183 Productivity Components requires X11 R6 libraries. If you have an AIX 5.2 single processor, then apply AIX 5.2 APAR 43952 before installing WebSphere Portal. AIX 5L V5.1 (32bit) + ML04 Productivity Components requires X11 R6 libraries. HP-UX 11i v1 HP-UX 11i (11.11) PA-RISC patches. Note: 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
- HP-UX 11i (11.20) version 1.5 for Itanium Processor Family patches (PHSS_24591)
Ensure that all Java patches for the installed Quality Packs are applied prior to installing WebSphere Portal.
Red Hat Enterprise Linux Advanced Server 3.0 for Intel (x86), update 1 Refer to Tech Note 1164634 before installation. Red Hat Enterprise Linux Advanced Server 2.1 for Intel (x86), update 3 Productivity Components requires X11 R6 libraries plus the Motif version 2.0 or later. Red Hat Enterprise Linux Advanced Server 3.0 for i/pSeries, update 1 Refer to Tech Note 1164634 before installation. Red Hat Enterprise Linux Advanced Server 3.0 for OS/390, update 1 Refer to Tech Note 1164634 before installation. SuSE Linux Enterprise Server (SLES) for Intel (x86) 8 2.4 Kernel with Service Pack 3 Productivity Components requires X11 R6 libraries plus the Motif version 2.0 or later. SuSE Linux Enterprise Server (SLES) for Intel (x86) 9 Productivity Components requires X11 R6 libraries plus the Motif version 2.0 or later. SuSE Linux Enterprise Server (SLES) for OS/390 8 2.4 Kernel, 31-bit with Service Pack 3 Sun Solaris 9 (Patch cluster of November 2003)
Sun Solaris 8 (Patch cluster of November 2003) Required patches Productivity Components requires X11 R6 libraries. 32-bit mode only. 64-bit mode is not exploited. 32-bit compatibility mode on 64-bit systems has not been tested. Microsoft Windows 2003 Enterprise Microsoft Windows 2003 Standard Microsoft Windows 2000 Advanced Server SP4 Microsoft Windows 2000 Server SP4 Microsoft Windows XP SP1a Supported for test and development purposes only. 32-bit mode only. 64-bit mode is not exploited.
Supported appservers (required on portal machine)
install WebSphere Portal on top of the following supported version of WAS.
WAS (required on portal machine) Notes Windows/UNIX + IBM WebSphere Business Integration Server Foundation V5.1.1 running on WAS 5.1.1.1 The following WAS interim fixes are also required:
- PQ91124
- PQ92923
- PQ93388
- PQ94304
- PQ94382
- PQ94554
- PQ94676
Refer to the WebSphere Portal Release Notes for the latest information about fixes.
If you have an existing copy of WebSphere Business Integration Server Foundation V5.1.1 installed, see...
$WAS_ROOT/properties/version/history...directory for a collection of installed fixes.
Supported Web servers (optional)
Use one of the following products as the Web server. In general, any Web server that is supported by WAS V5.1.1 Cumulative Fix 1 is supported. Other Web servers or versions that are not listed might also be supported.
Supported databases (required)
By default, WebSphere Portal is installed with the Cloudscape database. After installation is complete you can choose to transfer data to another supported database. Use one of the following database products to store WebSphere Portal information.
Note: Applications such as Document Manager and Portal Personalization, which use a content repository to store user objects, will not transfer user data from Cloudscape on z/OS to DB2 for OS/390 and z/OS. However, other database transfers will transfer user data as expected.
Database (required) Driver (JDBC Type) Notes +Cloudscape V5.1.60.12 Cloudscape (Type 4) Cloudscape is automatically installed during the initial installation of WebSphere Portal. After installation you can choose to transfer data to another supported database.
+ IBM DB2 Universal Database Enterprise Server Edition 8.1 FP6 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.
- If you are currently running IBM DB2 Universal Database Enterprise Server Edition 8.1 FixPak 6 (or DB2 UDB V8.2), DB2 product service recommends that you download and apply FixPak 6a or higher.
IBM DB2 Universal Database Enterprise Server Edition 8.1 FP6a 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 FP6 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.
- If you are currently running IBM DB2 Universal Database Workgroup Server Edition 8.1 FixPak 6 (or DB2 UDB V8.2), DB2 product service recommends that you download and apply FixPak 6a or higher.
IBM DB2 Universal Database Workgroup Server Edition 8.1 FP6a 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 for OS/390 and z/OS 7.1 CLI (Type 2) For z/OS and OS/390 systems only. To connect to DB2 for OS/390 and z/OS V7, DB2 Connect V8.1.6a is required on the portal machine. DB2 Connect is part of the Enterprise Editions of DB2.
PUT level 0407 with maintenance for APARs PQ90338, PQ96710 and PQ96421 is required.
Collaboration Center does not support this database.
Using DB2 UDB for z/OS as the administrative repository for WebSphere on non-S/390 platforms requires installing APARs pq48709 and pq48949 and setting the set system parameter to rrulock=yes.
Oracle Enterprise Edition 9i Release 2 (9.2.0.4) Thin (Type 4)
- Supports 64-bit Oracle 9i (on AIX and Sun Solaris) using 32-bit Oracle database client/driver.
- Supports 32-bit server/client configurations.
SQL Server Enterprise Edition 2000 SP3a Microsoft SQL Server 2000 (Type 4) Requires Microsoft SQL Server 2000 JDBC drivers.
Notes:
- A database server is required for WebSphere Portal.
- WebSphere Portal V5.1 requires all component's datasources and JDBC drivers to be XA-enabled.
- If your user repository contains more than 2000 users, a database other than Cloudscape is recommended.
- Because you 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.
Supported LDAP directories (optional)
Use one of the following software products as an LDAP directory to store user information.
LDAP server Notes + IBM Tivoli Directory Server V5.2 SuSE SLES for S/390 8 is not supported. IBM Directory Server V5.1 SuSE SLES for S/390 8 is not supported.
IBM Tivoli Directory Integrator V5.2 + IBM Lotus Domino Enterprise Server 6.5.3 IBM Lotus Domino Enterprise Server 6.5.2 IBM Lotus Domino Enterprise Server 6.5.1 IBM Lotus Domino Enterprise Server 6.0.4 IBM Lotus Domino Enterprise Server 6.0.3 IBM Lotus Domino Enterprise Server 6.0.2 IBM Lotus Domino Enterprise Server 5.0.13 IBM Lotus Domino Enterprise Server 5.0.12 Usage restrictions apply. Consult the product license for details. Novell eDirectory 8.7 Sun ONE Directory Server V5.2 Windows Active Directory 2003 Windows Active Directory 2000
Notes:
- 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 that is provided with WebSphere Portal runs on all the operating systems that are supported by WebSphere Portal.
- If you intend to use Lotus companion products, such as IBM Lotus Team Workplace or IBM Lotus Instant Messaging and Web Conferencing, the directory that is provided with Lotus Domino Enterprise Server is recommended.
- Because you 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
WebSphere Portal 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. You can find the current versions of these documents for each release of WebSphere Portal at http://www.ibm.com/websphere/portal/library. 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 re-create the reported problem using a tested LDAP server, staff will attempt to fix the problem. If the support team is not able to re-create 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)
use one of the following Web browsers to view the portal.
These Web browsers were tested by IBM. Portal behavior in Web browsers that are not listed is unknown. Web browser support varies by portlet or portal component.
Web browser (required)
Notes Additional information on fixes and support Microsoft Internet Explorer 6.0 SP1 http://www.microsoft.com Microsoft Internet Explorer 5.5 SP2 http://www.microsoft.com Mozilla Web Browser 1.6 Mozilla support note** http://www.mozilla.org/ Mozilla Web Browser 1.5 Mozilla support note** http://www.mozilla.org/ Mozilla Web Browser 1.4 Mozilla support note** http://www.mozilla.org/ Mozilla Web Browser 1.3 Mozilla support note** http://www.mozilla.org/ Netscape Communicator 7.1 Support limitation* http://www.netscape.com/ Netscape Communicator 7.0 Support limitation* http://www.netscape.com/ Netscape Communicator 6.2 Support limitation* http://www.netscape.com/ Opera Web Browser 7.23 Support limitation* http://www.opera.com/
Notes:
- A supported Web browser is required to access the portal from either a remote client or from the portal machine.
- Web browser support varies by portlet.
- *Support limitation: Due to incompatibilities of CSS and JavaScript implementations in Netscape and Opera, there are inconsistencies when Netscape or Opera are used with Document Manager and Productivity Components. Use Internet Explorer or Mozilla with these components.
- **Mozilla support note: 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.
Supported software for collaboration (optional)
Use the following software to support the collaborative features that are provided with portal.
Notes:
- These products are only supported on the following operating systems:
- AIX
- Solaris
- Windows
Currently Domino 6.x versions are not supported by the versions of Lotus Instant Messaging and Web Conferencing or Lotus Team Workplace that are shipped with some editions of WebSphere Portal.
Supported software for content management (optional)
Use the following software to support content management with portal.
Content management products (optional) Notes Additional information on fixes and support + IBM Lotus Workplace Web Content Management V5.1 http://www.lotus.com/products/product5.nsf/wdocs/homepage + Document Manager 5.1 Includes Portal productivity components http://www.ibm.com/websphere/portal/library + Portal Personalization 5.1 http://www.ibm.com/websphere/portal/library
Supported external security software (optional)
Use the following software as an external security manager for WebSphere Portal.
External security software (optional) Notes Additional information on fixes and support IBM Tivoli Access Manager for e-business 5.1 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. This version of the AMJRTE component is automatically installed with WAS V5.1.1, but must still be configured to work with WebSphere Portal.
For more information, see Using Tivoli Access Manager with WebSphere Portal.
http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/ Netegrity SiteMinder 6.0 http://www.netegrity.com/ GSKIT 7.0a Installs with IBM WAS http://www.ibm.com/software/webservers/appserv/was/
The following software is supported on the development machine.
Software for portlet development (optional) Notes Additional information on fixes and support + IBM Rational Application Developer 6.0 Includes Portal Toolkit plug ins http://www.ibm.com/software/awdtools/developer/application/ + WebSphere Portal Application Integrator Development Tool 5.1 Java 2 SDK - IBM AIX: ca131w-20020722a Win32: cn131w-20020710
LinxuIA32: cxia32131-20020710
zLinux: cx390131-20020710)
The following software is available to extend your site.
Software for portlet development (optional) Notes Additional information on fixes and support + IBM Lotus Extended Search 4.0.2 http://www.lotus.com/products/des.nsf/wdocs/home + IBM Tivoli Web Site Analyzer V4.5.5 http://www.ibm.com/software/tivoli/products/web-site-analyzer/ WebSphere Commerce Server WebSphere Portal should not be installed into a WAS cell where WebSphere Commerce Server is already installed. http://www.ibm.com/software/inf/websphere/index.jsp?tab=products/commerce + WebSphere Translation Server V5.0 http://www.ibm.com/software/pervasive/products/voice/translation_server.shtml
See also
Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.
Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.
Rational is a trademark of the IBM Corporation in the United States, other countries, or both.
AIX is a trademark of the IBM Corporation in the United States, other countries, or both.