In this scenario you have four machines: a Database server containing
the Repository database; a Database server containing the State, Runtime,
and Historical databases; the Monitor Server machine, and the Monitor Client
machine.
Important: Although WebSphere® Business Monitor runs on
Process Server 6.0.0, it only supports applications running on Process Server
6.0.1
The features to be installed on each machine are:
- On the first Database Server machine:
- On the second Database Server machine:
- State database
- Runtime database
- Historical database
- On the Monitor Server machine:
- Monitor Server: Includes Monitor Server Application (with Adaptive Action Manager)
and Monitor Server administrative console (including Monitor Server, Adaptive Action Manager, and Schema Generator).
- On the Monitor Client machine:
The following diagram illustrates the machines distribution in this scenario:
You should consider the following:
- All WebSphere Business Monitor databases
must be created before you install any of the components. You should create
the Repository database on the first database server machine, and create the
State, Runtime and Historical databases on the second database server machine
before you install the Monitor Server and Dashboard Client components.
- The Repository database must be created on the first database server machine
before you create the State, Runtime, and Historical databases on the second
database server machine.
- The Repository database must be cataloged on the second database server
machine before you create the State, Runtime, and Historical databases on
this machine. It should be also cataloged on the Monitor Server machine and
the Monitor Client machine before you install the Monitor Server and Dashboard
Client components on these machines. You can use the DB2® commands or the DB2 Control Center to catalog the Repository
database. The name used to catalog the Repository database must match the
name of the Repository database on the first database server machine.
- The State and Runtime databases must be cataloged on the Monitor Server
machine before you install the Monitor Server component. You can use the DB2 commands
or the DB2 Control
Center to catalog the State and Runtime databases. The name used to catalog
each database must match the name of the corresponding database on the second
database server machine.
- The Runtime and Historical databases must be cataloged on the Monitor
Client machine before you install the Dashboard Client component. You can
use the DB2 commands
or the DB2 Control
Center to catalog the Runtime and Historical databases. The name used to catalog
each database must match the name of the corresponding database on the second
database server machine.
Note: This scenario can be modified in several ways. One alternative is
to distribute the databases on more than two machines. For example, there
can be a separate machine for each database.