Installation guide

Page 14 of 59
An improvement to the two-tier model is to install the Metadata Repository component
into the pre-existing corporate database with the “Repository Creation Assistant” tool.
This splits the Metadata Repository from the other Infrastructure components, but it
removes the need to host a small database on the OracleAS server. Even in a two-tier
model, separating the Metadata repository out from the other components improves
performance. An example of a two-tier implementation with metadata hosted in the
corporate database is shown in Figure 2.
Figure 2. Improved Two-Tier OracleAS Deployment Topology
If at least two servers are available for OracleAS, a three-tier model can be implemented.
In the simplest scenario, one server contains the J2EE, Web Cache, and Portal/BI/Forms
applications. A second server contains the Infrastructure components, including security-
related components such as Identity Management, OID, and Single Sign On, as well as
the Metadata Repository. The separation of Infrastructure components from other
components increases security (with an optional firewall) and also improves performance
by lowering contention for server resources. Again, it is recommended to deploy the
Metadata Repository into a pre-existing corporate database with the “Repca” tool. Figure
3 illustrates a simple three-tier implementation.