Depending on your site requirements, you can choose between different server topologies for your IBM WebSphere Portal environment. This WebSphere Portal server topology is the foundation for your social site and all the other components have to be integrated with it. This also influences the web server, database, user registry, and security layers of the deployment architecture.
: When planning for a topology, use deployment diagrams to design and visualize the relationship between all the software components of your site.
IBM WebSphere Portal supports the following server topologies:
- Single-server topology: This is the basic topology and can be used for small to medium environments. All other components can coexist on the same machine. No scalability and high availability is supported by this topology.
- Stand-alone server topology: The Portal server is installed alone on a different machine than the other components, thus providing dedicated processing capabilities. No scalability and high availability are available for this topology.
- Clustered servers topology: This is used for scalability and high availability requirements. You can have vertical clusters where all servers are located on the same machine, or you can have horizontal clusters where servers are distributed on different machines, or you can have a mix of vertical and horizontal clusters. Multiple clusters can be used to improve availability, failover, and disaster recovery. The cluster topology is also useful for distributing and replicating the session and cache data. You have the option to use the IBM HTTP Server Plug-in between IBM HTTP Server powered by Apache and the portal cluster to balance user traffic across all members of the cluster.
- Portal farm topology: This consists of multiple identically configured stand-alone server instances.
If you use IBM Web Content Manager, the following IBM WebSphere Portal topologies may apply:
- Single-server topology for Web Content Manager: This consists of the IBM WebSphere Portal and Web Content Manager that are installed both on the same server.
- Dual-server configuration for Web Content Manager: This consists of two servers or clusters, each containing IBM WebSphere Portal and Web Content Manager. The first one is used by clients to access the content that is only authored from the second one. This option is used for heavy traffic websites.
- Staging-server topology for Web Content Manager: This consists of more than two servers or clusters, each containing IBM WebSphere Portal and Web Content Manager. The content is authored in different servers and staging takes place between them in order to present the content by an one dedicated server of cluster.
For more information about WebSphere Portal Server topologies, visit |Server topologies