In order to exploit the benefits of load balancing in a server group, it is
important to consider how to set up this complex environment. You
should consider:
- Installing the source database, the DB2 Everyplace control (DSYCTLDB) and
message database (DSYMSGDB), and the WebSphere Application Server database
repository (WAS40) on a remote server. Running one or more of these
databases on separate servers is one way to prevent a single point of
failure.
- Cataloging the DB2 Everyplace control and message database, and the
WebSphere Application Server database repository before you install WAS and
DB2 Everyplace. If you do this in advance, extra configuration tasks
can be avoided.
- Cataloging each mirror database as a local database as required by DPropR
for replication purposes.
- Installing the HTTP Server on another physical machine for security
purposes. An easy way to do this, is to install WAS on the server with
a local WAS database only, and copy the plug-in configuration into WebSphere
after everything is setup.
Related concepts
Related tasks