In this scenario, you have two machines: the Monitor Server machine
and the Monitor Client machine. The WebSphere® Business Monitor databases
are distributed on both machines.
Important: Although WebSphere Business Monitor runs on
Process Server 6.0.0, it only supports applications running on Process Server
6.0.1
The components to be installed on each machine are:
- On the Monitor Server machine:
- Monitor Server
- State database
- Repository database
- On the Monitor Client machine:
- Dashboard Client
- Runtime database
- Historical database
The following diagram illustrates the distribution on the machines in this
scenario:
You should consider the following:
- Although WebSphere Business
Monitor runs on Process Server 6.0.0, it only supports applications running
on Process Server 6.0.1
- All WebSphere Business Monitor databases
must be created before you install any of the components. You should create
the Repository and State databases on the Monitor Server machine and create
the Runtime and Historical databases on the Monitor Client machine before
you start the installation of the Monitor Server and Dashboard Client components.
- The Repository database must be cataloged on the Client machine before
you create the Runtime and Historical databases on this machine. 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 Server machine.
- The Runtime database must be cataloged on the Server machine after the
Runtime and Historical databases are created on the Client machine. You can
use the DB2 commands
or the DB2 Control
Center to catalog the Runtime database. The name used to catalog the Runtime
database must match the name of the Runtime database on the Client machine.