IBM®
Skip to main content
    Country/region select      Terms of use
 
 
   
     Home      Products      Services & solutions      Support & downloads      My account     
 
developerWorks
AIX and UNIX
IBM Systems
Information Mgmt
Lotus
New to Lotus
Products
How to buy
Downloads
Live demos
Technical library
Training
Support
Forums & community
Events
Rational
Tivoli
WebSphere
Architecture
Autonomic computing
Java™ technology
Linux
Multicore acceleration
Open source
SOA and Web services
Web development
XML
About dW
Submit content
Feedback


developerWorks  >  Lotus  >  Forums & community  >  Deployments, Performance, & Interoperability (DPI) Lab Blog

Deployments, Performance, & Interoperability (DPI) Lab Blog

developerWorks
Official blog for the Lotusphere 2008 DPI Lab

What is a best practices approach to supported Portal versions in a deployment?

I've been asked what is a best practices approach to support WebSphere Portal and WebSphere Application Server versions in a typical production environment.

Here's the simple (but important) answer:

Although other configurations and versions may be supported, my advice is:
Stick to the suggestions made on the WebSphere Portal Server Support Page: http://www-306.ibm.com/software/genservers/portal/support/" title="http://www-306.ibm.com/software/genservers/portal/support/">http://www-306.ibm.com/software/genservers/portal/support/

The section "Recommended fixes and updates" contains quality recommendations about version dependencies between WebSphere Portal, WCM, WebSphere Application Server and WebSphere Process Server.

Image:What is a best practices approach to supported Portal versions in a deployment ?
It is a best practice approach to regularly check the Support Page for important updates.

If you plan to update a certain component of your deployment, check the dependencies first and download other necessary fixes, if applicable.

Markus Nagel | 22 January 2008 05:42:39 PM ET | | Comments (0)

    About IBM Privacy Contact