Search Tips   |   Advanced Search

Database topologies

Consider the database configuration options in relation to the IBM WebSphere Portal deployment scenario. The complexity of the network topology will increase as you scale from a proof-of-concept environment using Derby to systems using vertical and horizontal clustering techniques.

WebSphere Portal data can be configured in a single store or organized into database domains to meet different availability requirements, depending on the deployment scenarios for proof-of-concept and production environments. The database domains provided by WebSphere Portal help you classify and distribute portal data. Each database domain can be placed on a separate database for efficient maintenance. Additionally, each domain can be placed on a separate database server system for maximum performance.

Figure 1. Options for setting up databases

Consider whether the portal deployment requires a local database for a proof-of-concept environment; remote databases that share database domains to support normal load balancing; remote databases for high-capacity, heavy load balancinthat separate data; or a combination of database configurations.

Remember: If you install the database server on a remote system, you need to install the database client software on the WebSphere Portal system so that the portal can communicate with the remote database server.

Parent: Database considerations