The Repository can be configured within the Enterprise Manager. See Note 1 below.
Note 1: Once you've locked the Oracle BI Domain, you would then use the same screen back in Enterprise Manager to browse and select the RPD file, and then enter the password, twice.

Once you've entered these details you would then press the Apply button, to save the changes. At this point, the RPD gets a sequence number after it, and it's displayed as the current default online repository for the Oracle BI Domain.
Note 2: An OBIEE 11g system (or "Oracle BI Domain") is generally managed through a combination of Oracle Enterprise Manager Fusion Middleware Control, part of the Enterprise Manager "family", or through WebLogic Server Scripting Tool (WLST) scripts. Each Fusion Middleware Control instance as shipped with OBIEE 11g controls a single Oracle BI Domain (DEV, or PROD for example), and is installed along with WebLogic Server Admin Console in the WebLogic Admin Server, one of the two JVMs (the other being the managed server) that gets installed by default with OBIEE 11g. The screenshot below shows Fusion Middleware Control showing the status of the BI Server, Presentation Server and other system components within the installation.

The principal connection to an OBI Server inside the Oracle BI System is made through an Odbc Connection.
OBI Server can handle multiple repository but you can connect to only one at the same time by DSN Odbc Connection. Therefore, you must set up an ODBC connection for each repository.

C: OBIEE Caching and Cache Seeding
Cache is a component that improves performance by transparently storing data such that future requests for the same criteria can be served much faster. Like other application cache is not virtual memory in OBIEE. In OBIEE cache will be stored as files on the Hard Disk of the OBIEE Server in the form of files. By Default caching is enabled in the OBIEE server configuration.
For time-consuming Dashboard Pages, we can use the concept of cache seeding in OBIEE, this can be configured as a scheduled job that will ensure that the data is cached and readily available as and when the user runs the dashboard.

Horizonal Scaleout of System Components
* Used for adding additional managed servers (Java components) and
system components to an existing cluster
* Used for scalability and failover
* Set up via the Universal Installer > Scale Out BI System option

The rank measure is numbered from 1. The highest sales amount will be ranked 1.