Server topologies

Topology diagrams help you visualize different configurations that you can set up to support various user and system load requirements. The topology diagrams are representative of basic configurations.

The single-server topology illustrates a simple installation for demonstration, trying the product out, or development environment purposes. The stand-alone topology illustrates a distributed configuration. Clustered topologies illustrate more robust and load intensive hardware configurations and IBM® Web Content Manager topologies illustrate how different hardware configuration support various authoring and system load requirements. To increase capacity and availability, multiple portal servers can be clustered with IBM WebSphere® Application Server Network Deployment, where the portals share a common configuration and load is distributed evenly across all cluster instances. The high availability and failover topology illustrates WebSphere Portal in a more complex production environment.

Tip: To increase performance and throughput in all of these topologies, see "Increasing the number of servant regions".
Restriction: The serverName is hardcoded to WebSphere Portal. The serverName cannot be changed in a stand-alone environment. If you do change it, the ConfigEngine scripts do not work. For a clustered environment, see Technote 1370392 for options on replacing the WebSphere Portal JVM.