Database Reference
In-Depth Information
Although this relatively simple architecture may be sufficient for an initial deployment, you might need to grow
it into a more scalable, available architecture. There are four levels of deployment that you could use with EM12c to
achieve higher scalability and availability. Of course, as in any architecture requiring both scalability and availability,
trade-offs need to be made in terms of increasing cost as performance and availability increase.
Level 1
Figure
1-3
shows a
level 1
deployment. The OMS and repository are installed either on a single host or, more
preferably, on two separate hosts. However, neither of these hosts has any failover configured.
Level 2
For
level 2
, the OMS is installed on shared storage and uses VIP-based (virtual IP-based) failover. The repository
database is protected by using local physical standby database technology. Usually, this means that level 2 deployments
use double the number of machines used by level 1. Level 2's active/passive configuration (albeit located locally rather
than having remote passive sites), leads to a downtime window when failing over from the active site to the passive site.
This architecture is shown in Figure
1-4
.
EM12c
Console
Target with
OMA /plug-in
Target with
OMA /plug-in
Target with
OMA /plug-in
Shared
Storage
Active
OMS
Standby
OMS
Shared
Storage
Active
Repository
Standby
Repository
Figure 1-4.
Schematic diagram of a level 2 deployment
