WebSphere Portal Performance Tuning

A Portal solution often differs from traditional solutions by having several functional nodes mapped to several products and custom built applications. When a client makes a request and until the client receives the response many different components are invoked.

Having many different and individual components always introduces numerous potential bottlenecks to the solution. You need to consider:

• Network
• Firewall
• Network Dispatcher
• Authentication Proxy
• HTTP Server
• Application Server
• LDAP server
• Content Management System
• Portal Server
• Portlet Applications
• Database
• Domino / Sametime / Quickplace Server
• External Applications